Open BelT327l opened 6 years ago
The DURATION
there is a tag added by the encoder (ffmpeg?) not the duration opusdec sees. Do you get the same issue if you encode the original wav with opusenc? That might help determine where the issue is between your opus file and opusdec.
The problem was the filesizelimit of wav (32bit) it stops at exactly 3hours and 6 min...
Now the way at larger 3 hours ++ files is aiff; aac/opus -> aiff -> lame-mp3 or flac on good music files.
That sounds like more of a workflow problem. (What's the deal with flac from lossy input anyways? And why is it placed next to LAME?)
WAV more than 4 GiB now (2019) works using an unofficial convention. It's not as great as RF64 because the time shown will always be wrong, but the data is there. 40307422b42c64319ef059131c6162e67e777465
Got this several times...
if i opusdec one opusfile ta wav; opusdec "RE WS 033 yy-mm-dd.opus" "RE WS 033 yy-mm-dd.wav" Decoding to 48000 Hz (2 channels) Encoded with Lavf57.83.100 language=ger DURATION=03:39:14.641000000 encoder=Lavf57.83.100 Decoding complete. ``
In terminal it shows the correct time; but if i open that wav file; it shows the wrong time... vlc, mpv, different players show the wrong time... i deleted those "bad" files and restarted re-re-decoding but anytime the same issue guess problem is anywhere...anywhere the same problem... anywhere is a cachefile or sth. for the media preview or tag or sth. else; dont think its a decoding / opusdec issue...
This wasnt the end of encoding: target is mp3; but this issue makes it hard to finish work on files.