Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th August 2015, 00:44 | #1 | Link |
Registered User
Join Date: Oct 2009
Location: crow-land
Posts: 540
|
videolan x264 broken in latest releases ?
Using the binaries over at Videolan:
A bug seems to have appeared commencing with r2579 binary when processing a vanilla mpeg2 .mpg interlaced TV file capture file. The mpeg2 files are from VideoReDo and are the result of "QuickStreamFix" which have then been successfully edited without error by VRD. A very large number of these error messages appear Code:
[mpeg2video @ 00000000032504c0] releasing zombie picture - r2538 works without the error message - issue appears in r2579 - issue persists in r2597 I wonder what is Code:
[mpeg2video @ 00000000032504c0] releasing zombie picture I have reverted to r2538 ... any recommendations ? |
30th August 2015, 12:49 | #2 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Well, this error/warning is not from x264 (libx264) itself, but from the built-in FFmpeg (libavcodec) MPEG-2 decoder.
So, apparently, something has changed on the FFmpeg side. Probably whoever is making the "VideoLAN" builds of x264 has updated to a newer (different) FFmpeg version. And newer FFmpeg is now spitting out those warnings. Is there actually some corruption (decoding error) in the re-encoded file? Otherwise, just ignore those warnings. Quite possible the issue has always existed, but newer FFmpeg has become more verbose/picky. (BTW: The term "zombie" in programming usually refers to something that it is no longer active/alive, but has not been released from memory yet. Like a "zombie process" is a process that has terminated, but it's PID still exists)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 30th August 2015 at 14:23. |
30th August 2015, 14:34 | #3 | Link | |
Registered User
Join Date: Oct 2009
Location: crow-land
Posts: 540
|
Thanks. In the absence of any info on the videolan forum (their threads on x264 have been deleted) I guess I'll stick with r2538 which doesn't yield the very many messages.
Quote:
Unless you have a suggestion, I guess I'll work out what the equivalent ffmpeg commandline is for this Code:
"%X264EXEx32%" --thread-input --threads %xthreads% --frames "%FRAMES%" --profile high --level 4.1 --preset slow --interlaced --tff --no-cabac --crf %CRF% --sar 64:45 --colormatrix bt470bg -o "%PARtemph264%" "576i-mpeg2.mpg" Code:
"%MP4Boxexe%" -add "%PARtemph264%" -add "%parmp3%":lang=eng -isma -new "%PARmp3mp4%" |
|
30th August 2015, 14:40 | #4 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Have you tried, for example, the Komisar's build?
http://komisar.gin.by/
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
|