JackSA
28th June 2009, 09:58
Hey guys,
I'm having an issue with ffmpeg of late (and a google/doom9 search yielded very little).
I used to be able to create an audio stream based on the AC3 codec from a .VOB -> .AVI conversion with the ATAG set to 0x2000 (Dolby AC3) AC3 ... no issues there and all media players could play the resulting XVID.avi file.
However, recently I've noticed that ffmpeg tags the AC3 audio stream like this -> 0xfffe (Extensible wave format) AC3, which confuses home media players, and the .avi can't play.
I tried to retag the audio stream but that didn't help. I'm using SVN-r19285 version of ffmpeg (latest), and looking at the SVN log it seems that waveformat-extensible was added in SVN-r18372.
Did anyone else run into this issues? And please let me know how you've fixed it. An example CLI I use is here ->
ffmpeg -i nput.VOB -map 0.0 -map 0.2 -vcodec libxvid -b 2000k -g 300 -bf 2 -qmin 2 -vtag XVID -acodec ac3 -ac 6 -ab 384k -async 1 -f avi movie.avi
Cheers,
JackSA
I'm having an issue with ffmpeg of late (and a google/doom9 search yielded very little).
I used to be able to create an audio stream based on the AC3 codec from a .VOB -> .AVI conversion with the ATAG set to 0x2000 (Dolby AC3) AC3 ... no issues there and all media players could play the resulting XVID.avi file.
However, recently I've noticed that ffmpeg tags the AC3 audio stream like this -> 0xfffe (Extensible wave format) AC3, which confuses home media players, and the .avi can't play.
I tried to retag the audio stream but that didn't help. I'm using SVN-r19285 version of ffmpeg (latest), and looking at the SVN log it seems that waveformat-extensible was added in SVN-r18372.
Did anyone else run into this issues? And please let me know how you've fixed it. An example CLI I use is here ->
ffmpeg -i nput.VOB -map 0.0 -map 0.2 -vcodec libxvid -b 2000k -g 300 -bf 2 -qmin 2 -vtag XVID -acodec ac3 -ac 6 -ab 384k -async 1 -f avi movie.avi
Cheers,
JackSA