View Full Version : why x264v721 doesn't have --nal-hrd option ?
survivant001
19th January 2008, 14:30
why the latest version of x264 doesn't have --nal-hrd option ?
I found a version 669i and 675 that has been patched.
It's for suing the movie encoded by x264 into Encore CS3.
thanks
LoRd_MuldeR
19th January 2008, 14:39
Because that patch was *not* submitted to the x264 SVN and hence will be missing in all "official" builds...
Atak_Snajpera
19th January 2008, 15:06
http://forum.doom9.org/showthread.php?t=133652
tymoxa
19th January 2008, 20:21
You can try this (http://www.mediafire.com/?brjqdtu1zy4). Made with this a couple *.avc that was not rejected by scenarist. BDMV-on-DVD playable on BDP-S300 and BDP-LX70a.
Trahald
21st January 2008, 20:20
tymoxa - thanks for the link to the patched 721
survivant001
23rd January 2008, 01:01
someone got this error with scenarist and x264 ?
I tried with the build 721 patched with hdr and still the same problem with scenerist... buffer underflows.
tymoxa
23rd January 2008, 11:13
survivant001
with this line (source is 720p)
x264.exe --crf 18.0 --level 4.1 --min-keyint 1 --deadzone-inter 6 --deadzone-intra 6 --ref 3 --no-fast-pskip --bframes 3 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --vbv-bufsize 9000 --vbv-maxrate 25000 --vbv-init 1.0 --threads auto --no-dct-decimate --no-psnr --no-ssim --nal-hrd --mvrange 511 --aud --sar 1:1 --aq-strength 1.0 --progress --pulldown 64 --output output.264 input.avs
i have no errors in scenarist HDMV.
Sagittaire
23rd January 2008, 11:31
Well I don't make BD but with BD profil you can use for 720p24
--min-keyint 2 --max-keyint 28 (min & max)
--vbv-bufsize 30000 --vbv-maxrate 40000
why --pulldown 64 ...?
pulldown flag are not necessary for BD
you can use 3 bframe with pyramidal structure too.
tymoxa
23rd January 2008, 11:53
Sagittaire
Thanks for the tips...
Without --pulldown 64 i get some jerkiness playback.
survivant001
23rd January 2008, 13:24
thanks guys
I'll try the command line. The problem that I have is with a 720p.
There is a difference for 1080p in the command line ?
Dethis
23rd January 2008, 13:33
Well I don't make BD but with BD profil you can use for 720p24
--min-keyint 2 --max-keyint 28 (min & max)
--vbv-bufsize 30000 --vbv-maxrate 40000
why --pulldown 64 ...?
pulldown flag are not necessary for BD
you can use 3 bframe with pyramidal structure too.
Isn't it 1sec the max I-frame distance for BD. This equals to --max-keyint 24 for p24 (or perhaps 23 for 23.97 framerate)?
survivant001
23rd January 2008, 17:54
my frist sucessful test with a problematic movie (no buffer underflows in scenarist) Oh ya.. I'm tryig to convert the movie for the PS3. Maybe I'll have to tweak to command line later.. but the first step is to be able to create a m2ts.
D:\DVD-convertion\encode\temp_dr_strange>x264.exe --crf 22.0 --level 4.1 --min-keyint 2 --keyint 28 --deadzone-inter 6 --deadzone-intra 6 --ref 3 --no-fast-pskip --bframes 3 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --vbv-bufsize 30000 --vbv-maxrate 40000 --vbv-init 1.0 --threads auto --no-dct-decimate --no-psnr --no-ssim --nal-hrd --mvrange 511 --aud --sar 1:1 --aq-strength 1.0 --progress --pulldown 64 --output 720p.264 movie.avs
avis [info]: 1280x720 @ 23.98 fps (109920 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX MMXEXT SSE SSE2 SSE3 3DNow!
x264 [info]: slice I:5073 Avg QP:16.33 size: 67730ta 0:00:00
x264 [info]: slice P:78161 Avg QP:18.24 size: 17741
x264 [info]: slice B:26686 Avg QP:21.57 size: 4578
x264 [info]: mb I I16..4: 37.1% 17.5% 45.4%
x264 [info]: mb P I16..4: 9.6% 6.0% 2.9% P16..4: 48.3% 4.4% 0.9% 0.0% 0
.0% skip:27.9%
x264 [info]: mb B I16..4: 1.6% 1.1% 0.8% B16..8: 15.4% 0.6% 0.7% direct:
4.9% skip:74.8%
x264 [info]: 8x8 transform intra:28.7% inter:14.4%
x264 [info]: ref P 80.1% 12.4% 7.5%
x264 [info]: ref B 79.0% 12.7% 8.3%
x264 [info]: kb/s:3232.4
encoded 109920 frames, 10.77 fps, 3233.52 kb/s
and another sucessful test (generate a m2ts.. still don't know if I'll be able to play it):
D:\DVD-convertion\encode\temp_dr_strange>x264.exe --threads auto --thread-input --keyint 14 --min-keyint 2 --vbv-maxrate 24000 --vbv-bufsize 14745 --mvrange 511 --level 4.1 --bframe 1 --bime --weightb --ref 3 --mixed-refs --direct auto --deblock -1:-1 --crf 22 --stats "x264_stat.log" --qcomp 0.50 --ipratio 1.10 --pbratio 1.10 --partitions "all" --8x8dct --me "dia" --subme 1 --trellis 0 --deadzone-intra 6 --deadzone-inter 6 --no-fast-pskip --no-dct-decimate --aud --nal-hrd --sar 1:1 --aq-strength 0.25 --aq-sensitivity 0 --progress -o sagittaire.264 movie.avs
avis [info]: 1280x720 @ 23.98 fps (109920 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX MMXEXT SSE SSE2 SSE3 3DNow!
x264 [info]: slice I:8862 Avg QP:15.05 size: 85822 PSNR Mean Y:52.04 U:55.01
V:55.68 Avg:52.77 Global:50.97
x264 [info]: slice P:81142 Avg QP:15.59 size: 29669 PSNR Mean Y:51.93 U:54.34
V:54.99 Avg:52.54 Global:50.95
x264 [info]: slice B:19916 Avg QP:16.76 size: 9374 PSNR Mean Y:51.93 U:54.46
V:55.16 Avg:52.58 Global:50.60
x264 [info]: mb I I16..4: 30.0% 27.6% 42.4%
x264 [info]: mb P I16..4: 21.2% 7.1% 3.2% P16..4: 53.2% 3.0% 1.5% 0.3% 0
.2% skip:10.4%
x264 [info]: mb B I16..4: 1.4% 1.1% 0.8% B16..8: 20.4% 0.5% 0.9% direct:
20.2% skip:54.7%
x264 [info]: 8x8 transform intra:24.1% inter:16.6%
x264 [info]: direct mvs spatial:97.3% temporal:2.7%
x264 [info]: ref P 84.3% 10.0% 5.7%
x264 [info]: ref B 79.7% 13.0% 7.3%
x264 [info]: SSIM Mean Y:0.9950088
x264 [info]: PSNR Mean Y:51.940 U:54.415 V:55.076 Avg:52.565 Global:50.882 kb/s:
5853.77
encoded 109920 frames, 18.28 fps, 3515.75 kb/s
someone can tell me what I did wrong with my previous command line ?
x264.exe --pass 2 --bitrate 7200 --stats ".stats" --progress --keyint 300 --bframes 3 --qpmin 7 --qpmax 51 --no-psnr --mixed-refs --trellis 1 --ref 3 --filter 0,0 --subme 6 --direct auto --vbv-bufsize 12000 --vbv-maxrate 26000 --me dia --no-ssim --level 4.1 --weightb --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --threads auto --thread-input --aud --nal-hrd --sar 1:1 --output "movie.264" "movie.avs"
oh ya.. with my command line I obtain a video of 3.8gigs and with your command line is around 1.87gigs. Don't know if my buffer underflows is cause by that.. I'll try to customize your command line to have a larger movie.
First observation : with the sagittaire.264 (I didn't put pulldown) I can fastforward the movie m2ts. but I can with the other one.
audyovydeo
23rd January 2008, 18:27
... with my command line I obtain a video of 3.8gigs and with your command line is around 1.87gigs...
"first" cmdline did a crf22 and obtained a 1.87GB file with 3515 bitrate
"your" cmdline specified bitrate 7200 and you got a 3.8GB file.
Normal.
If you're satisfied with the quality, you dont need to do another run at all.
cheers
audyovydeo
survivant001
23rd January 2008, 22:53
thanks audyovydeo
but your answer is not really what I'm looking for. I know the bitrate change the file size.. but my question is : "Why a movie encoded by my command line give error in scenarist and not the others ? " if I can figure that out, I'll be able to convert movie without hassle.
Dethis
23rd January 2008, 23:33
thanks audyovydeo
but your answer is not really what I'm looking for. I know the bitrate change the file size.. but my question is : "Why a movie encoded by my command line give error in scenarist and not the others ? " if I can figure that out, I'll be able to convert movie without hassle.
KEYINT 300 !!!
survivant001
23rd January 2008, 23:50
I want your help for this one :
Can someone explain me what the options does and when to use them. I know there is not a solutions for everything, but I want to know how to tweak the setting and when. Like that I won't steal the command line of others without knowing what it does :)
Suppose the encoding time is not important and for source 720p and 1080p (23.976 and 29.97) (my target is the PS3, so I'll use only options that are supported). The goal is the best quality.
--pass 2 (should we use pass 2 with bitrate or crf ? )
--bitrate 7200
--keyint 300 (how di I choose this one?)
--min-keyint 2 (why a min ?, and how choose it)
--bframes 3 (how determine this one ?
--qpmin 7 (only use in no crf ? )
--qpmax 51
--no-psnr (what is this ? )
--mixed-refs
--trellis 1
--ref 3
--filter 0,0
--subme 6
--direct auto
--vbv-bufsize 12000
--vbv-maxrate 26000
--me dia
--no-ssim
--weightb
--b-rdo
--bime
--analyse p8x8,b8x8,i4x4,i8x8 (ok for the ps3)
--8x8dct
--aud (needed for the scenarist and Encore cs3.. why ? )
--nal-hrd (needed for the scenarist and Encore cs3.. why ? )
--sar 1:1 (needed for the scenarist and Encore cs3.. why ? )
--mvrange 511
--deblock -1:-1
--crf 20
--qcomp 0.50
--ipratio 1.10
--pbratio 1.10
--deadzone-intra 6
--deadzone-inter 6
--no-dct-decimate
--aq-strength 0.25
--aq-sensitivity 0
--pulldown ( I used 32 for a test and I obtain : "Value of FrameRateCode is not supported in the BD standard" in scenarist)
Dark Shikari
23rd January 2008, 23:56
I want your help for this one :
Can someone explain me what the options does and when to use them. I know there is not a solutions for everything, but I want to know how to tweak the setting and when. Like that I won't steal the command line of others without knowing what it does :)
Suppose the encoding time is not important and for source 720p and 1080p (23.976 and 29.97) (my target is the PS3, so I'll use only options that are supported). The goal is the best quality.See this guide (http://ffmpeg.x264.googlepages.com/) for my own detailed explanations of most of these options.
Some of those options seem quite odd, especially using ME DIA with all those high-end options...
Atak_Snajpera
24th January 2008, 00:06
@survivant001
You should start experimenting with PS3 profile.
My simple tests showed that PS3 profile +
--aud
--nal-hrd
--sar 1:1
works quite well.
survivant001
24th January 2008, 01:13
@survivant001
You should start experimenting with PS3 profile.
what do you mean by that.. were do I get this profile ?
I did the profile ps3 for automkv, but it's not working everytime.. that's why I want to understand the settings
survivant001
24th January 2008, 01:21
See this guide (http://ffmpeg.x264.googlepages.com/) for my own detailed explanations of most of these options.
Some of those options seem quite odd, especially using ME DIA with all those high-end options...
thanks.. that explain a lot..
option like
--ipratio <float>(x264)
Qscale difference between I-frames and P-frames.
I suppose I don't have to play with that.. the default should be enough for me.
and for "me dia".. I choose that only for speeding the process in my test. normally is "umh" :)
now I still need to know which values to choose for 1080p vs 720p.. and anime vs movie in high motion.. movie like comedy.. things like that
Atak_Snajpera
24th January 2008, 01:22
try --keyint with lower values
survivant001
25th January 2008, 01:46
thanks with --keyint at 14 it works (that's wierd because in my first tests, I was using 15 and got buffer underflows).. I'll keep the setting 14
the flag : --crf it's for one pass right ? the 2 pass is still better than crf ?
when should I use --aq-strength and aq-sensitivity flag ?
Atak_Snajpera
25th January 2008, 12:39
survivant001
There is new TS muxer http://forum.doom9.org/showthread.php?t=134104
Try to import your raw .264 files (optimized for scenarists) and then use tsremux. Let me know if M2TS is working or not on PS3.
buzzqw
25th January 2008, 13:02
Try to import your raw .264 files (optimized for scenarists) and then use tsremux. Let me know if M2TS is working or not on PS3.
yea.. let me know too!
BHH
Atak_Snajpera
25th January 2008, 13:43
Success Amigos !!!!
I was able to create working M2TS on PS3!!!
1) download this build http://www.mediafire.com/?brjqdtu1zy4
and then use PS3 profile + --aud --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000
my settings:
--crf 20 --level 4.1 --sar 1:1 --aud --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000 --filter 0,0 --aq-strength 1 --aq-sensitivity 0 --ref 3 --mixed-refs --bframes 3 --b-rdo --bime --weightb --direct auto --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --output
2) use TSMuxer
http://forum.doom9.org/showthread.php?t=134104
3) remux TS to M2TS using TSRemux
http://forum.doom9.org/showthread.php?t=125447
It is working even with 1280x544 :) Now I have to check other resolutions and framerate. No more crazy Scenarists and Encores :)
survivant001
25th January 2008, 15:35
good news that.. but scenarist still can be use.. I need to find a way to add subtitle, maybe the only way is AVCHD... still need to find one.
@Atak_Snajpera : I had trouble with keyint for 2 particular movies.. the default value was to high.. maybe you should add the default value in your command line if we need to change it later.
Atak_Snajpera
25th January 2008, 15:52
I had trouble with keyint for 2 particular movies
Problem in scenarist or during playback on PS3?
lexor
25th January 2008, 16:08
and then use PS3 profile + --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000
just so we clear, PS3 profile in your tool or megui? in this forum you never know, unless they are the same?
Also for those who've successfully done a re-encode, how is the overhead of ts & co. containers relative to mkv/mp4? I know vob makes files way larger, thus throwing bitrate calcs (like the one in megui) out of the window. Oh and one last question, does PS3 still has 4gb limit on these m2ts files?
Atak_Snajpera
25th January 2008, 16:28
As a matter of fact only these settings are really required
--level 4.1 --sar 1:1 --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000 --ref (no more than 4)
survivant001
25th January 2008, 19:32
Problem in scenarist or during playback on PS3?
more problematic than that.. I wasn't able to generate the mux part. Buffer underflows error.
I just change keyint 15 to 14.. and it works. I played with all kind of values for vbv-buffer and vbv-max and didn,t change a thing.. only the keyint worked.
but like I said.. my command worked with others movies.. the important is that is work now.
I need to find if I want to use bitrate or crf.. and find the usefullness of aq. (more tweaking)
I'll try to convert few movies and see if they all work (mux with scenarist + mux with tsmuxer.. to see if I can keep the same result with both of them.. if so, I,ll stop using scenarist :) )
Atak_Snajpera
25th January 2008, 20:20
how is the overhead of ts & co. containers relative to mkv/mp4?
ts is 4% larger than mp4
m2ts is 6% larger than mp4
I hope my quick measurements are correct.
Oh and one last question, does PS3 still has 4gb limit on these m2ts files?
With m2ts you can go above 4GB
tymoxa
25th January 2008, 21:40
well... scenarist give me a 9% overhead for m2ts
got almost the same with tsmuxer>tsremux... 8.9%
Atak_Snajpera
25th January 2008, 23:27
well... scenarist give me a 9% overhead for m2ts
got almost the same with tsmuxer>tsremux... 8.9%
That's funny but my files are only 5.5% bigger than mkv.
lexor
26th January 2008, 04:57
Alright, this is going to sound noobish, but how exactly do you get the m2ts files onto the PS3. I use TVersity for all the other files and it works great sharing my PC's hardrive, but though I added the m2ts file to it the PS3 doesn't see it. What alternatives are there? The file is just a little too big for DVD5 (I made the mkv for DVD5 way back and don't feel like re-encoding it, and m2ts inflated the size), and obviously it's nowhere big enough for DVD9. I got 40gb PS3, so no flash readers. So... I got the file and no way to play it without wasting media? Any other free alternative to TVersity exists, or am I not using TVersity correctly?
jamos
26th January 2008, 08:09
Success Amigos !!!!
I was able to create working M2TS on PS3!!!
1) download this build http://www.mediafire.com/?brjqdtu1zy4
and then use PS3 profile + --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000
my settings:
--crf 20 --level 4.1 --sar 1:1 --nal-hrd --vbv-bufsize 9000 --vbv-maxrate 25000 --filter 0,0 --aq-strength 1 --aq-sensitivity 0 --ref 3 --mixed-refs --bframes 3 --b-rdo --bime --weightb --direct auto --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --output
2) use TSMuxer
http://forum.doom9.org/showthread.php?t=134104
3) remux TS to M2TS using TSRemux
http://forum.doom9.org/showthread.php?t=125447
It is working even with 1280x544 :) Now I have to check other resolutions and framerate. No more crazy Scenarists and Encores :)
can you get dts/dolby true hd in the m2ts to work on the ps3? or do you still have to convert to ac3?
And I am assuming your just playing with the h264 stream with x264 correct? so the first step would be to use mkvextract?
Atak_Snajpera
26th January 2008, 08:16
but how exactly do you get the m2ts files onto the PS3
PSP and DVD+RW
And I am assuming your just playing with the h264 stream with x264 correct? so the first step would be to use mkvextract?
Video must be re-encoded with special switches
jamos
26th January 2008, 08:20
PSP and DVD+RW
Video must be re-encoded with special switches
yes i see, can you give me the command line you used for TSMUXER i cant read russian :p thanks for your help.
edit: n/m I see that tsmuxer has a gui interface.. :p
D-Train
27th January 2008, 02:15
Thanks for posting your mini guide Atak_Snajpera! I was able to get a brand new encode playing on my PS3 no problem. Unfortunately I have a ton of existing encodes that just don't seem to work. I always get a corrupted data message from the PS3. I'm sure it's that some of the encode parameters I used just aren't supported :(
lexor - For using TVersity, use .m2t extension and the latest version of TVersity. Works for me.
Pretty cool stuff... I'd like to see the PS3 become more usable as a full-fledged media center. If only it supported .m4a audio files...
survivant001
27th January 2008, 02:29
D-Train
if you use the command line Atak give you with the latest x264 build patched.. it will work. don't forget.. no DTS.. and not h264info..
with that it will work. if not.. can you try it in scenarist and tell me what is the error. (mux your 264+ac3)
D-Train
27th January 2008, 17:54
Thanks survivant001, last night I did have success with some of my older encodes now too. Instead of relying on tsmuxer to set the level to 4.1, I had to strip the elementary streams and change the level with h264info. With Atak's command line of course that's not necessary, and anyways I really should start using crf instead of 2pass target bitrate which I always used before.
survivant001
27th January 2008, 18:24
I'll continue to use 2pass. easier to get to the target size
Atak_Snajpera
27th January 2008, 22:21
survivant001 will you be able to send me Bluray-structure generated by scenarists? TSRemux structure is not compatible with sony players (no sound) http://forum.doom9.org/showthread.php?p=1092401#post1092401
survivant001
27th January 2008, 23:13
no trouble. will send you one tonight
here a rar of a scenarist output. I just remove the 00000.m2ts file.
here the link
http://www.mediafire.com/?2vxezcxb1mx
bob0r
28th January 2008, 07:14
For those who care:
X264 rev 735
added patches:
x264_aq_var.47.diff
x264_hrd_pulldown.04.diff
x264_2pass_vbv.0.diff
x264.735.dark.aq.0.47-hrd_pulldown.0-2pass_vbv.0.exe (http://files.x264.nl/x264.735.dark.aq.0.47-hrd_pulldown.0-2pass_vbv.0.exe) (pthreads/mp4 = yes, made with make fprofiled)
Atak_Snajpera
28th January 2008, 08:05
I do care! Thanks bob0r. I was waiting for this !
One question. Do still I need external pthreadGC2.dll?
survivant001
thanks. BTW Will be ok if I replace (in ripbot) m2ts muxing with Blu-Ray Disc structure?
bob0r
28th January 2008, 08:07
I do care! Thanks bob0r. I was waiting for this !
One question. Do still I need external pthreadGC2.dll?
Nop, not for my builds
survivant001
28th January 2008, 12:19
survivant001
thanks. BTW Will be ok if I replace (in ripbot) m2ts muxing with Blu-Ray Disc structure?
yes it will be fine. THe user just have to take the 00000.m2ts from the folder.
lexor
28th January 2008, 21:07
For those who care:
X264 rev 735
added patches:
x264_aq_var.47.diff
x264_hrd_pulldown.04.diff
x264_2pass_vbv.0.diff
x264.735.dark.aq.0.47-hrd_pulldown.0-2pass_vbv.0.exe (http://files.x264.nl/x264.735.dark.aq.0.47-hrd_pulldown.0-2pass_vbv.0.exe) (pthreads/mp4 = yes, made with make fprofiled)
For those of us still affected by the DNS issues, what IP does http://files.x264.nl/ resolve to? The main page on x264 says that x264.nl is at http://72.21.44.163/ but I don't know how to navigate to files.x264.nl sub domain, and the files section at http://72.21.44.163/x264/ doesn't contain these builds.
Thank you.
P.S. Before someone asks how I can read the x264 main page if I have DNS issues, I use my company's proxy server (that apparently comes out somewhere in germany, since I get german google through it), but it blocks file transfer that aren't normal html pages.
J_Darnley
28th January 2008, 21:21
Try 64.85.162.133 as that is what ping -a files.x264.nl resolves to.
lexor
28th January 2008, 21:33
That worked, thank you!
bob0r
30th January 2008, 10:58
- x264 revision 736
- AQ_0.48.diff
- x264_2pass_vbv.0.diff
- x264_hrd_pulldown.04.diff
x264.736.dark.aq.0.48-2pass_vbv.0-hrd_pulldown.04.exe (http://files.x264.nl/AQ/x264.736.dark.aq.0.48-2pass_vbv.0-hrd_pulldown.04.exe) pthreads/gpac/fprofiled = yes
MatMaul
30th January 2008, 11:46
seems like a new version of the 2pass_vbv patch is available :
http://mailman.videolan.org/pipermail/x264-devel/2008-January/004015.html
bob0r
30th January 2008, 12:35
seems like a new version of the 2pass_vbv patch is available :
http://mailman.videolan.org/pipermail/x264-devel/2008-January/004015.html
Next rev or AQ it will be added :)
bob0r
1st February 2008, 02:34
seems like a new version of the 2pass_vbv patch is available :
http://mailman.videolan.org/pipermail/x264-devel/2008-January/004015.html
patch -p0 < x264_2pass_vbv.4.diff
patching file `encoder/ratecontrol.c'
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 244:
Even when convert to unix format: FAIL!
Sorry, can't add this patch for now. Test before you post??
Edit:
Email send to it's creator..... we wait.
Sharktooth
1st February 2008, 15:57
is line 244 the last line?
bob0r
1st February 2008, 16:03
is line 244 the last line?
When i remove the last line, another one is bad, someone just needs to make it correct, i have mailed the author as i said.
Sharktooh come irc please (ill try not fall asleep this time :o)
MatMaul
1st February 2008, 22:39
yes the patch is malformed but it is just a problem with the patch file itself not the code I think.
here is a good patch :
http://www.etud.insa-toulouse.fr/~mvelten/bordel/x264_2pass_vbv.4.diff
bob0r
3rd February 2008, 05:48
x264.736.modified.01.exe (http://files.x264.nl/x264.736.modified.01.exe)
General thread:
http://forum.doom9.org/showthread.php?t=130364
x264_aq_var.48.diff
http://forum.doom9.org/showthread.php?t=132760
x264.gaussian.cplxblur.01.diff
Dark Shikari: - gaussian cplxblur: gives a tiny improvement in 2pass ratecontrol
x264_me-prepass_DeathTheSheep.01.diff
http://forum.doom9.org/showthread.php?p=1093523
x264_2pass_vbv.4.MatMaul.diff
http://mailman.videolan.org/pipermail/x264-devel/2008-January/004015.html
x264_hrd_pulldown.04.diff
- HRD and pulldown for HD compatibility
csy
3rd February 2008, 07:21
@bob0r
I would like to request your next build please use the hrd/pulldown patch with the interlacing fix from dattrax, attached in the post:
http://forum.doom9.org/showpost.php?p=1047919&postcount=157
(if that is not too much trouble)
Thanks
bob0r
3rd February 2008, 16:16
@bob0r
I would like to request your next build please use the hrd/pulldown patch with the interlacing fix from dattrax, attached in the post:
http://forum.doom9.org/showpost.php?p=1047919&postcount=157
(if that is not too much trouble)
Thanks
x264.736.modified.02.exe (http://files.x264.nl/x264.736.modified.02.exe)
General thread:
http://forum.doom9.org/showthread.php?t=130364
x264_aq_var.48.diff
http://forum.doom9.org/showthread.php?t=132760
x264.gaussian.cplxblur.01.diff
Dark Shikari: - gaussian cplxblur: gives a tiny improvement in 2pass ratecontrol
x264_me-prepass_DeathTheSheep.01.diff
http://forum.doom9.org/showthread.php?p=1093523
x264_2pass_vbv.4.MatMaul.diff
http://mailman.videolan.org/pipermail/x264-devel/2008-January/004015.html
x264_hrd_pulldown.04_interlace.diff
- HRD and pulldown for HD compatibility, updated patch for interlacing
http://forum.doom9.org/showthread.php?p=1047919#post1047919
csy
5th February 2008, 04:58
:thanks:
Thanks bob0r, much appreciated!
survivant001
10th February 2008, 15:03
why do I still obtain buffer underflows event with the vbv patch ?
akupenguin
10th February 2008, 17:21
VBV is aproximate. x264 will only make an effort to comply, and warn you when it failed.
survivant001
10th February 2008, 18:19
@akupenguin
thanks.
I'm trying to figure how to avoid this problem, or which setting to tweak whent his happen
here a discusion with other person that have the problem
http://forum.doom9.org/showthread.php?p=1098148#post1098148
Sagittaire
11th February 2008, 10:49
In most time you can solve this problem if you reduce qcomp.
Try with this empirical formulation:
qcomp = 1.00 - ( average_bitrate / max_bitrate )
survivant001
11th February 2008, 12:10
thanks Sagittaire.
here my command line (mostly base on one that you posted)
"D:\DVD-tools\tools\AutoMKV095_NORIP\exe\encoder\x264.exe" --pass 2 --bitrate 7304 --stats "D:\DVD-convertion\converting\temp\.stats" --progress --keyint 14 --min-keyint 2 --bframes 3 --qpmin 5 --qpmax 51 --mixed-refs --trellis 1 --ref 3 --filter 0,0 --subme 6 --direct auto --vbv-bufsize 14745 --vbv-maxrate 30000 --me dia --level 4.1 --weightb --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --threads auto --thread-input --aud --nal-hrd --sar 1:1 --me-prepass --qcomp 0.40 --ipratio 1.10 --pbratio 1.10 --no-psnr --output "D:\DVD-convertion\converting\temp\movie.264" "D:\DVD-convertion\converting\temp\movie.avs" -v 2>pass_verbose.txt
by your formula, 0.40 should be ok.. but doesn't work.
I'll try with 0.35 (but don't know what will be the result on quality)
here my output log
http://forum.doom9.org/showthread.php?p=1098933#post1098933
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.