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. |
14th January 2011, 03:00 | #1 | Link |
Guest
Posts: n/a
|
x264 and 2nd pass artifacts
Hi,
I'm facing a new problem when encoding blu-ray compatible x264 stuff, I can get the stream to mux on scenarist now but there are artifacts at different places on the video like this (resized for convenience): This screenshot is from the beginning of the video (it starts at frame 102) so I could see it easily, I tried various decoders to confirm the problem is on the encoded video, Then I tried : - encoding the whole video (170975 frames) multiple times and changing some settings in 2 passes but I always get the artifacts approximately at the same place, - encoding the first 500 frames (tried 10000 too) in 2 passes and there's no problem this time - encoding the first 500 frames (the second pass only) using the whole video 1st pass stats file and I get the artifacts again So it seems there's something bad on the stats file when I encode the whole thing :/ Here is the last test command line I used : x264 --bitrate 20000 --preset fast --tune film --weightp 1 --bframes 3 --nal-hrd vbr --vbv-maxrate 35000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --b-pyramid strict --slices 4 --aud --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 --fps 24000/1001 --force-cfr --stats filmc.stats --output out.264 video.avs As for the qpfile, the 1st chapter only starts at frame 9521 Here are some of the files : blocky video (cut from the whole file) : http://r4di.us/temp/outblocky.264 corresponding stats file (maybe from another of the bad encodes) : http://r4di.us/temp/filmblocky.stats stats file from a 10000 frames encode without problem : http://r4di.us/temp/filmok.stats Could someone help with this ? |
14th January 2011, 05:44 | #4 | Link | |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,989
|
Quote:
Derek
__________________
These are all my personal statements, not those of my employer :) |
|
14th January 2011, 16:24 | #6 | Link | |
Guest
Posts: n/a
|
Quote:
- a .m2ts cut from the 10 first seconds of the original source - the stats files (the mbtree was 2GB so i cut 40MB from the start, it seems it still works) - the .avs file loading the .m2ts - the .bat file with the 2nd pass command line - the x264 binary (win32) URL : http://r4di.us/temp/x264stuff.zip (66MB) With those files I could not reproduce the same blocky thing like in the snapshot above but looks like some frames are skipped at the place, I'll try with other stats file if needed, Btw when I check the output file from the 1st pass I can't see the problem happen (at the beginning of the video at least) only the 2nd pass has it Last edited by radius; 14th January 2011 at 18:41. |
|
15th January 2011, 00:01 | #8 | Link |
Guest
Posts: n/a
|
I've been encoding cuts of the video like this :
- 50000 first frames -> no artifacts - 100000 first frames -> no artifacts - 150000 first frames -> no artifacts - 170900 first frames -> this one as artifacts the movie is 170975 so the last encode only misses only a couple of seconds, i guess it's not really related with x264 but I don't get why the full and near full encodes could make the rest of the video corrupted :/ ... |
15th January 2011, 17:19 | #11 | Link | |
Guest
Posts: n/a
|
Quote:
just tested using dds2 this way : LoadPlugin("C:\Program Files (x86)\Haali\MatroskaSplitter\avss.dll") DSS2("U:\Bad Boys 1995 Bluray 1080p AVC DTS-HD MA5.1-CHDBits\BDMV\STREAM\00011.m2ts", fps=23.976) I'm still getting the problem at the same place :/ should I test the other methods ? |
|
16th January 2011, 08:16 | #13 | Link |
Guest
Posts: n/a
|
Am guessing that's enough to get the thread closed ...
But in follow-up, DSS2 will indeed use the same decoder as DSS, so should limit resolution attempts to FFMS2 / DGSource as source filters ... Am guessing it's Windows 7 without the Media Foundation Bypass Tool being deployed ... 7ek |
16th January 2011, 13:46 | #14 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Where do you have that file from ???
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
17th January 2011, 13:59 | #15 | Link |
Guest
Posts: n/a
|
My bad, it's just a copy / paste found when searching for usage of DSS2 with avisynth
Btw I did not disable Media Foundation as said 7ekno. I just encoded using x264 (from http://x264.nl/) with the internal ffms decoder using directly my .m2ts file as input, It encoded without the artifact error, could you tell if it's OK to encode using the embedded decoder or should I always use avisynth ? |
17th January 2011, 14:24 | #16 | Link |
Registered User
Join Date: Mar 2005
Location: Finland
Posts: 2,641
|
AviSynth is only needed for advanced filtering and editing. If you have a nice progressive source and don't want to denoise, x264's internal decoders and filtering system are fine.
Last edited by nm; 17th January 2011 at 14:26. |
18th January 2011, 21:53 | #18 | Link |
My iPod was a gift!
Join Date: Aug 2006
Posts: 57
|
I've seen similar corrupted video frames recently and I don't even encode such large files. I just encoded some TV shows to my iPod with the latest MeGUI which contains the latest x264 and started seeing this recently. When going back to the older version of x264 (r1649) everything looks and plays back perfectly.
|
|
|