View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005887 | ardour | bugs | public | 2014-03-18 16:10 | 2020-04-19 20:16 |
| Reporter | don3 | Assigned To | x42 | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Summary | 0005887: Ardour3 "bounce to region list with processing" does not use fader automation | ||||
| Description | Version tested: 3.5.357 (downloaded binaries) Steps to reproduce: 1: Launch A3, open a new session. 2: Import an existing audio file to a track. (Or create a track and record some audio.) For this test, use an audio sample that has a visually obvious waveform -- speech, music, or a constant sine wave or noise would work. Silence would not be a good choice. 3: Turn on fader automation for the track, and select Play mode for the fader "track". 4: Add automation points that create some radical volume changes - which should make some visually obvious changes in the resulting waveform. (For example, start the region at -inf, go up to 0 dB in the middle, than back down to -inf at the end.) 5: Switch to range mode and drag a range with includes the region. 6: Context-click on the range, select "Bounce Range to Region List With Processing". New region should appear in region list. 7: Drag the new region from the region list to the track, to a convenient location later in time. Expected result: Waveform in the new region should be affected by the gain automation in the original. At least this is my impression of what should happen, based on what I've read - this is the first time I've tried to use this feature. Actual result: Waveform in the new region appears to be the same as the original. Playing the new region confirms that the fader settings had no noticeable effect. | ||||
| Additional Information | Attempting to bounce a region that includes a track with a plug-in results in a crash. This has already been reported in bugs 0005302 and 0005404. As further (visual) confirmation that the original and new regions are the same, the new one can dragged on top of the original, and the waveforms will exactly overlay each other. However, my first attempt at this did not work -- the new region's waveform looked significantly smaller, but uniformly so - it still didn't follow the fader automation. Turned out this was another bug that I've seen fairly often but haven't figured out how to reliably reproduce. Zooming in or out a step restores the proper waveform display, and it stays correct after going back to the original zoom. (For a while...) | ||||
| Tags | No tags attached. | ||||
|
|
In Revision 3.5-357-gce4d125 Ardour still does not render any fader-settings or plugins when bouncing a range or region. But I see, that I can actually *export* a range including processing as expected. So it looks like there is no actual technical hindrance but merely a problem with the bouncing-mechanism that appeares not to automatize the export->import->put onto track as new region, that works perfectly OK when done by hand. |
|
|
fixed in 3.5-2052-ga0037ee (development branch https://github.com/Ardour/ardour/commit/3be01ea5 ) - should be part of the next release |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-03-18 16:10 | don3 | New Issue | |
| 2014-03-22 13:16 | zettberlin | Note Added: 0015718 | |
| 2014-05-26 03:28 | x42 | Status | new => assigned |
| 2014-05-26 03:28 | x42 | Assigned To | => x42 |
| 2014-05-26 03:33 | x42 | Relationship added | related to 0005403 |
| 2014-05-26 15:14 | x42 | Note Added: 0015816 | |
| 2014-05-26 15:14 | x42 | Status | assigned => resolved |
| 2014-05-26 15:14 | x42 | Resolution | open => fixed |
| 2020-04-19 20:16 | system | Note Added: 0023308 | |
| 2020-04-19 20:16 | system | Status | resolved => closed |
