Creating 2 seconds on wma files

[RunrigCorvusCoraxFan]

Has anyone tested this yet?

[steve]

What format are you exporting as? (I can't see that in your video).
If you import the exported song back into Audacity, how long does Audacity say it is?

[Gale Andrews]

Has anyone tested this yet?

Thanks for the report. There is no issue with FFmpeg 2.2.2 itself run at the command-line, outside of Audacity. The Audacity problem is only in how Audacity is writing the length into the file headers, not with the actual length of the file, which is correct.

Perhaps due to some change in the new FFmpeg version that Audacity didn't take account of, Windows, MediaInfo, dBPowerAmp and Foobar2000 all think a 1.025 seconds WMA file exported by Audacity 2.0.6 is 3.023 seconds long, whereas they see the same file exported by 2.0.5 as 1.025 seconds long. However both the 2.0.5 and 2.0.6 file are the expected length - try dragging the file from 2.0.6 back into Audacity.

So if you play the file in Media Player, the play bar will look like about 3 seconds, but the file will stop playing as expected just after 1 second.

Note that like MP3, WMA is not length accurate, as per the design of the format. Some milliseconds of silence padding is added to the start of the file, and the exported file is extended by a little less than the padding, meaning a very little of the audio is lost from the end of the exported file.


Gale

[RunrigCorvusCoraxFan]

Thanks for the report. There is no issue with FFmpeg 2.2.2 itself run at the command-line, outside of Audacity. The Audacity problem is only in how Audacity is writing the length into the file headers, not with the actual length of the file, which is correct.

Perhaps due to some change in the new FFmpeg version that Audacity didn't take account of, Windows, MediaInfo, dBPowerAmp and Foobar2000 all think a 1.025 seconds WMA file exported by Audacity 2.0.6 is 3.023 seconds long, whereas they see the same file exported by 2.0.5 as 1.025 seconds long. However both the 2.0.5 and 2.0.6 file are the expected length - try dragging the file from 2.0.6 back into Audacity.

So if you play the file in Media Player, the play bar will look like about 3 seconds, but the file will stop playing as expected just after 1 second.

Note that like MP3, WMA is not length accurate, as per the design of the format. Some milliseconds of silence padding is added to the start of the file, and the exported file is extended by a little less than the padding, meaning a very little of the audio is lost from the end of the exported file.

OK Gale. I got your message. I unistalled 2.5 with 2.6. I exported a track which was 1:56 in 2,05, on exporting, same duration. On 2.6, with the new ffmeg, it was 1.58. Now when playing in through JetAudio, it's 1:56, yet on explorer, its 1:58, opening the file, the wave length runs to 1.58 ?

[Gale Andrews]

On 2.6, with the new ffmeg, it was 1.58. Now when playing in through JetAudio, it's 1:56, yet on explorer, its 1:58, opening the file, the wave length runs to 1.58

Opening the file where? Are you talking about 1 minute, 58 seconds?

If I export a 1 minute 56 seconds selection in Audacity 2.0.7-alpha, the WMA is 1 minute 56 seconds and 7 milliseconds when imported back into Audacity, much as one would expect.


Gale

[RunrigCorvusCoraxFan]

Opening the file from the folder, I haven't compared the minniseconds; but surely if you export as wma on 2.5 and it has the same durations, that 2.6 would be the same.

[Gale Andrews]

Opening the file from the folder, I haven't compared the minniseconds; but surely if you export as wma on 2.5 and it has the same durations, that 2.6 would be the same.

The actual file length exported in 2.0.6 is the same as in 2.0.5, but other applications read the reported length of the 2.0.6 files as 2 seconds longer than they actually are.


Gale

[RunrigCorvusCoraxFan]

Same issue here. I ripped album

4:56

It converted at 4:58