|
|
Do you mean exporting Ranges aka Time spans (not Regions) like in attached screenshot? initiated via Session > Export > Export to Audio file? So how can I reproduce this? Is this step by step recipe correct? * new Session * create 3 range markers * Session > Export > .. to audio file * File format: wav 16bit, session-rate, normalize to peak *Time span: select timespan 1 and 3 * Export And yes, to normalize first the raw data needs to be written to a temporary file. That can then be analyzed to find peak volume before writing the actual file. export_time_spans.png (36,742 bytes) |
|
|
Greetings, thank you for looking into this. My apologies: yes, I did mean time spans/ranges (and not regions). Your recipe is very close, here are my steps for reproducing this: * new Session * import some 24 bit WAV files * create 4 range markers * Session > Export to audio files... * File format: wav 16bit, session-rate, normalize to peak (-1.00 dB) *Time span: click on "Select All" to have all ranges selected, then manually deselect ("unclick") range "session" * click "Export" expected behaviour: all 4 ranges get exported (rendered/normalized/written into output file) actual behaviour (when normalization is _not_ enabled): as expected behaviour actual behaviour (when normalization _is_ enabled): first range gets exported correctly, then the playhead (red line) jumps to the beginning of the _2nd_ range on the timeline, the export dialog displays "Exporting "<name of 2nd range>" (timespan of 3 of 4)", and progress stops and Ardour hangs. Please see two attached screenshots illustrating the situation. Notice the ranges on the timeline, the playhead, vs. what the export dialog shows. 01 selected ranges.png (55,644 bytes) 02 ranges on timeline, confused export progress dialog.png (245,899 bytes) |
|
|
Some initial investigation shows this is more complicated. Apparently it is caused to using the audio callback to trigger the next range. Using the "Dummy" backend I can export just fine, but Portaudio/ASIO hangs. If you're comfortable using a text editor, while Ardour is not running edit %localappdata%\Ardour8\config and unhide the Dummy backend: <Option name="hide-dummy-backend" value="0"/> after that you can later use Menu > Window > Audio/MIDI Setup... Audio System: None/Dummy, and exporting multiple regions should work. I'll keep investigating this issue now. |
|
|
Fixed in 8.7.42 - available from https://nightly.ardour.org/ |
|
|
Thank you, I confirm 8.7.42 fixes the issue and the export now completes correctly and successfully. There remains the (very) minor issue of temporary files (one per time span) being left behind on disk after the export completes. |
|
|
> There remains the (very) minor issue of temporary files (one per time span) being left behind on disk after the export completes. I cannot reproduce this. temporary files are removed after a multi region export w/normalization. Could it be that you are just seeing the old remnant files from previous failed exports? |
|
|
No, it seems still unresolved: I just tried with 8.10 freshly downloaded, and exporing a single range into MP3 with normalization turned on does still leave a temp file behind after the export has finished with the expected result and behaviour otherwise; the temporary file remains on disk even after I quit Ardour. (But this is a really minor annoyance only.) kép.png (13,421 bytes) |
- Anonymous
