View Issue Details

IDProjectCategoryView StatusLast Update
0005361ardourbugspublic2020-04-19 20:16
ReporterRicardus Assigned ToSaBer  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0005361: A3 writes damaged file when exporting two WAVs at the same time (different word length and SR)
DescriptionWhen I exported 16/44.1 and 26/96 WAV files at the same time from a client's 96K session, it wrote one WAV file at 16/44.1 of an odd length (more than twice the length of the song). The first part of the WAV was what looked like a proper export of the song at 16/44.1, but with a few clicks and pops, and the next 5 mins was hiss normalized to the setting I chose.
Additional InformationTwo files require two unique names.
TagsNo tags attached.

Activities

in0giro

2013-03-06 15:21

reporter   ~0014682

subscribe

x42

2013-03-06 19:59

administrator   ~0014684

From IRC:

< rgareus> SaBer: did you see Ricardus' bug report 0005361? export two .wav file w/different settings -> same filename is used for both

< SaBer> rgareus: different channels and timespans are taken into account, but different formats are not

SaBer

2013-03-06 20:07

developer   ~0014685

I think the issue can be solved like this:

The used export format configuration needs to be added to the ExportFilename instances, along with a boolean, which is set to true if there are several formats with the same extension (e.g. ".wav") selected. The format is then added to the filenames when necessary.

I don't have time to fix this during this week, but if someone else wants to, go ahead...

SaBer

2013-03-17 10:40

developer   ~0014731

Should be fixed in git

system

2020-04-19 20:16

developer   ~0023199

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.

Issue History

Date Modified Username Field Change
2013-03-05 23:32 Ricardus New Issue
2013-03-06 15:21 in0giro Note Added: 0014682
2013-03-06 19:59 x42 Note Added: 0014684
2013-03-06 20:07 SaBer Note Added: 0014685
2013-03-17 08:45 SaBer Status new => assigned
2013-03-17 08:45 SaBer Assigned To => SaBer
2013-03-17 10:40 SaBer Note Added: 0014731
2013-03-17 10:40 SaBer Status assigned => resolved
2013-03-17 10:40 SaBer Resolution open => fixed
2020-04-19 20:16 system Note Added: 0023199
2020-04-19 20:16 system Status resolved => closed