Log in

View Full Version : Blu-Ray~DVD Backup & Conversion


Pages : 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14

laserfan
7th August 2008, 03:16
...you have to set the file name and bitrate before running (first two lines). The bitrate is calculated based upon the size (in frames) of the input...

@SET IN_TITLE=FILETITLE
@SET IN_BITRATE=5240
TIME /T
"E:\X264\x264.exe" "%IN_TITLE%.AVS" --bitrate %IN_BITRATE% --level 4.1 --sar 1:1
--aud --vbv-bufsize 14745 --vbv-maxrate 17500 --filter 0,0 --bframes 3 --direct auto
--subme 2 --analyse none --me dia --threads auto --thread-input --progress --no-psnr
--no-ssim --stats "stats2.log" --pass 1 --output NUL
TIME /T
"E:\X264\x264.exe" "%IN_TITLE%.AVS" --bitrate %IN_BITRATE% --level 4.1 --sar 1:1 --aud
--vbv-bufsize 14745 --vbv-maxrate 17500 --filter 0,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
--stats "stats2.log" --pass 2 --output "%IN_TITLE%.264"
TIME /T
PAUSE

I've tried to correlate the example above (SET IN_BITRATE=5240) to any movie-length no. of frames and must not understand the math. Can jdobbs or anyone tell me how to select a bitrate for a movie's framecount, that correlates with a DVD-5 or DVD-9? :o

jdobbs
7th August 2008, 12:28
You just work from the run time of the movie.

For example let's say you have a movie that has a run time of 2:10:14. That would be 7814 seconds. Now you have to determine the output size: a DVD+R (Dual Layer) holds 8,547,991,552 bytes or 68,383,932,416 bits. Divide that by the number of seconds and it means that, without any other considerations, you have a total of 8,751,463 bits per second (about 8751Kbs). If you assume a 6% overhead you will come to about 8400Kbs. Being the careful type I usually even take a little more off (because it takes lots of hours to encode, I don't want to oversize and have to do it twice). So let's round it down to 8200Kbs.

Now subtract the audio track. Let's say you are keeping one of the 640Kbs AC3 tracks... 8200 - 640 = 7560.

So you'd replace the 5240 with 7560 for that movie.

laserfan
7th August 2008, 16:57
You just work from the run time of the movie.

For example let's say you have a movie that has a run time of 2:10:14. That would be 7814 seconds. Now you have to determine the output size: a DVD+R (Dual Layer) holds 8,547,991,552 bytes or 68,383,932,416 bits. Divide that by the number of seconds and it means that, without any other considerations, you have a total of 8,751,463 bits per second (about 8751Kbs). If you assume a 6% overhead you will come to about 8400Kbs. Being the careful type I usually even take a little more off (because it takes lots of hours to encode, I don't want to oversize and have to do it twice). So let's round it down to 8200Kbs.

Now subtract the audio track. Let's say you are keeping one of the 640Kbs AC3 tracks... 8200 - 640 = 7560.

So you'd replace the 5240 with 7560 for that movie.Thanks very much jdobbs, for a thorough explanation even *I* can understand!!! :)

I had managed to completely confuse myself because I was using a hand calculator that erred-out on these large numbers! :scared:

:thanks:

Sharc
19th August 2008, 20:38
Has anyone tried yet to play a x264 AVC re-encoded DVD at its native resolution (720x480) on a Blue-ray standalone?
I know the resolution is not Blue-ray compliant, but upscaling does not add true details, it just takes much more time for encoding.

jdobbs
19th August 2008, 20:50
Actually 720x480 is blu-ray compliant. The only secret to that one is making sure you encode it with the right SAR. I assume you mean doing a MOVIE-ONLY disc with the blu-ray disc/file format.

Sharc
19th August 2008, 21:33
Yes, I am thinking of Movie-only "transparent" DVD backups.
I am in PAL country, so the resolution is actually 720x576, anamorphic 16:9, SAR 16:11, encoding with x264, authoring with tsmuxer. So you think this format should be playable on a standalon BD player (I don't have one yet to try myself ..... )?
With all the progress made recently, x264 with 1-pass CRF becomes more and more speedwise attractive, even on my outdated single-core PC. I re-encoded the 3-hours Wyatt Earp in 8 hours with CRF=16, original resolution, 2 language tracks, fitting easily on a DVD5, excellent quality.

jdobbs
20th August 2008, 00:48
I did that one too, but I did it in two-pass mode with x264. It is one of the few Blu-ray to DVD-5 ones that I decided to redo in DVD-9. Actually 99% of the movie looked great, but there was some blocking in dark scenes. I wonder if it would look better with CRF? I may give it a try.

I've done some 720x480 encodes in testing and they play back on my Sony standalone. I haven't done any recently. I'll run a couple through just as a comparison to MPEG-2 in DVD Format. I think an exceptionally long movie would be a good test case (like maybe Wyatt Earp or Gladiator).

Wombler
20th August 2008, 21:32
I think an exceptionally long movie would be a good test case (like maybe Wyatt Earp or Gladiator).

How about 'Saving Private Ryan'?

This was always a stern test for any of the DVD re-encoders so I'd assume the Blu-Ray to DVD would be equally challenging.


Wombler

jdobbs
21st August 2008, 02:09
Good idea.

tyee
21st August 2008, 06:48
JDobbs
Thanks for all the info you've provided here. I have been backing up my BRs to external USB Hard Drive and playing on the PS3 that way using CRF=20 one pass. I'm getting encode times of REAL TIME with x264 with my Q6600 quad core. However my command line is nowhere as full as the one you gave, and of course I cannot predict the final file size. I looks like your using constant bitrate then, does not fast motion cause problems?

I'm interested in using your command lines to try burning to DVD5 but have a question, what version of x264 do you use currently and do you keep upgrading it every time a new version comes out. What site do you get it from?

From what I gather, MANY versions are available and it is very confusing which one to use unless you follow the threads everyday.
Like here --> http://forum.doom9.org/showthread.php?t=130364

Wombler
21st August 2008, 08:36
Good idea.

Apologies JD.

Remarkably 'Saving Private Ryan' hasn't been released on Blu-ray and I'd assumed it was bound to be available.

Apparently it was originally released by one of the HD-DVD supporting studios and they haven't got their act together yet re a Blu-ray release.

Oh well. :rolleyes:


Wombler

G_M_C
21st August 2008, 09:12
I've also been backing up BR's to DVD9's. For a rule of thumb I stick to approx. 1 1/2 ~ 1 3/4 hours per DVD9 for a 1080p, simply because i want to keep as much detail as possible while retaining a resonable amount of cuts. Most movies end up in 2 parts (either DVD9 or DVD5, or a mix of those).

In my experiance it works best to keep good details, because you can use a good enough bitrate for video. I also try to use a DTS 1,5 mbps audio if possible; Sometimes it's the core-DTS track, and sometimes I make the DTS-track with EAC3To + DTS-encoder. I also mux in 1 subtitle-track; But i try to get @ 10000 kbps for 1080p video approx, depending on the source offcourse (movement, scenecuts etc.).

For encoding i use MeGUI atm, and "make my .AVS-script myself / by hand". I use the last patched x264 build (with all the psy-additions and the new b-frame decisions). I'll post my commandline tonight if you want.

EDIT:
I make these DVD's for playing on my standalone Panasonic DPM-BD30, and they play without issues. Muxed to Blu-ray structure thru tsMuxeR 1.84(b), burned both the BDMV & CERTIFICATE folders with IMGBurn.

jdobbs
21st August 2008, 11:36
I looks like your using constant bitrate then, does not fast motion cause problems? No... the command line I gave here uses VBR, but it does it in two passes rather than one (as would be true with CRF). When you've made a decision to fit HD on a DVD-5 or DVD-9 it's just better to use all the tools at your disposal. While I like CRF very much, two pass encoding is the best way to ensure you are getting the best out of your encode (as long as you have time to do so).
From what I gather, MANY versions are available and it is very confusing which one to use unless you follow the threads everyday. Yes they get released all the time. I used r777 for a long time. I recently started using r928. I go to www.x264.nl every now and then to see what's new. It can be a little confusing with all the changes -- but it's also good to know that the program is being so actively worked. I haven't starting using psyRDO yet, but it appears it may soon become the standard approach.

G_M_C
21st August 2008, 16:59
This is the commandline I use / MeGUI makes;

program --pass 2 --bitrate 10000 --stats ".stats" --level 4.1 --keyint 24 --min-keyint 1 --ref 4 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --subme 6 --trellis 2 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.3 --pbratio 1.2 --vbv-bufsize 22000 --vbv-maxrate 16000 --qcomp 0.5 --scenecut 32 --me umh --merange 24 --threads auto --thread-input --progress --no-psnr --no-ssim --output "output" "input" --mvrange 511 --aud --nal-hrd --sar 1:1 --b-adapt 2 --psy-rd 1.0

Sharc
21st August 2008, 18:51
Apologies JD.

Remarkably 'Saving Private Ryan' hasn't been released on Blu-ray and I'd assumed it was bound to be available.


Even the DVD version of SPR could be worth a test for comparison with an mpeg-2 backup on a DVD5.
I just wonder which version is compatible for playback on a standalone BD player:
Assuming original DVD PAL, 720x576, anamorphic, active picture 720x416
a) no crop, no resize => encode x264, sar 16:11
b) crop 720x416, no resize => encode x264, sar 16:11
c) crop 720x416, resize 720x576 => encode x264, sar 255:129

I would assume a) and c) should be ok because the 720x576 is BD compliant
I doubt with b) because 720x416 is not a BD compliant resolution.
Any experience?

m1482
21st August 2008, 19:14
The easiest way right now is to use the MOBILE encoding option with the "Experimental AVCHD, 1280x720" template. It will create a .TS file as output. Then just select that .TS from within TSREMUX (search DOOM9 for the TSREMUX thread) and tell it to output to Blu-ray format. Burn the contents of the output folder to DVD-R using ImgBurn in UDF 2.5 mode.

You may want to adjust the video bitrate depending on the movie size.

jdobbs:

When I burn my DVD-R using the following procedure (Blu-Ray structure created with TsRemux), when I play it back using a PS3 I don't have chapters function, only FF or Rew. However if I use the AVCHD created with Nero 8 it works correctly.
Any ideas how to make it work with your procedure?

jdobbs
21st August 2008, 19:36
That's a function of the muxing... try using TSMUXER instead (that's the one I use most often). By default it puts a chapter mark at each 5 minutes. You can also adjust it.

jdobbs
21st August 2008, 22:11
How about 'Saving Private Ryan'?

This was always a stern test for any of the DVD re-encoders so I'd assume the Blu-Ray to DVD would be equally challenging.


WomblerI'm encoding SPR right now from DVD to BD-5 format keeping the 720x480 resolution. I'll let you know how it looks when completed. I also plan to do a 1280x720 version for comparison.

Sharc
21st August 2008, 22:26
I'm encoding SPR right now from DVD to BD-5 format keeping the 720x480 resolution.
Means you don't crop the black borders, you leave them untouched in order to comply with the BD standard (720x480)?

jdobbs
21st August 2008, 23:09
I leave them untouched. Very, very few discs are 704x480 -- in fact I'm not sure I've ever seen a commercial one. They almost all are 720x480 (for NTSC). IMHO the smart strategy is to not modify their original configuration. Here are the legal formats for blu-ray:

1920 x 1080
1440 x 1080 (AVC/VC-1 only)
1280 x 720
720 x 480
720 x 576

Sharc
22nd August 2008, 05:51
For the exceptional 704x480 / 704x576 discs (eg "The Jacket" if I remember correctly) one should probably add vertical borders then, or resize horizontally to 720 and set the SAR accordingly.
I have also made an example with cropping and resizing the active picture to 720 x 576, and set the sar to 255:129 in that case. The resizing of course doesn't add real details, it rather blows up the file size (CRF encoding) and takes longer to encode.

Wombler
22nd August 2008, 09:11
I'm encoding SPR right now from DVD to BD-5 format keeping the 720x480 resolution. I'll let you know how it looks when completed. I also plan to do a 1280x720 version for comparison.

Ahh good.

So I didn't lead you entirely astray then. :)

It'll be very interesting though to hear your results.


Wombler

jdobbs
22nd August 2008, 11:53
The 720x480 encode went well, it took much less time of course than a BD movie, and the playback looks identical to the original.

tyee
23rd August 2008, 06:17
jdobbs
I tried your 2pass bat file last night and it came out great. Boy I sure didn't have much room for error, I had about 23 MB left to spare after muxing in the 448kbps audio!

Pass 1 took about 1.5hrs (36fps) Pass 2 took about 3.5 hrs (17fps).

I then decided to try one pass CRF=23 and it took about 2 hrs at 27fps. Comparing them just now on my Dell 30", I can't really see a difference, and the one pass was about 700MB smaller!

I noticed in the early discussion in this thread that you tried CRF too but now use 2pass, is this correct? How come the switch? I think I'm going to go with one pass CRF. I like the speed!

Sharc
23rd August 2008, 08:00
With my outdated and slow single core system 1-pass CRF has become my choice for x264 "overnight encodes". There is of course the file size issue with 1-pass. However, using CRF16 for DVD backups (in original resolution) of up to 3 hours duration seem to fit on a DVD5 including 2 original AC3 soundtracks + subtitles. With CRF16 I would say the backup is indistinguishable from the original. CRF18 is almost equally good, if one wants to be on the very safe side with the file size. I have noticed little blurring/softening/loss of details in dark scenes in a direct frame-by-frame comparison with the original - but hardly noticeable when watching the movie.

jdobbs
23rd August 2008, 12:07
jdobbs
I tried your 2pass bat file last night and it came out great. Boy I sure didn't have much room for error, I had about 23 MB left to spare after muxing in the 448kbps audio!

Pass 1 took about 1.5hrs (36fps) Pass 2 took about 3.5 hrs (17fps).

I then decided to try one pass CRF=23 and it took about 2 hrs at 27fps. Comparing them just now on my Dell 30", I can't really see a difference, and the one pass was about 700MB smaller!

I noticed in the early discussion in this thread that you tried CRF too but now use 2pass, is this correct? How come the switch? I think I'm going to go with one pass CRF. I like the speed! I've used CRF, and it looks good. But I noticed some occasional blocking (especially in dark scenes) that went away when I used 2 pass. The fact is that two pass will always do better. But when you can't see it, it doesn't mean a thing. :)

What kind of processor are you using. 1.5 and 3.5 are pretty good times with the settings I proposed (they are meant for extremely high quality on pass-2).

tyee
23rd August 2008, 15:49
I have a Q6600 2.4GHz o/c to 3GHz, not too bad.

jdobbs
23rd August 2008, 20:14
My Quad-Core Phenom 9500 is lame compared to your Q6600. How long was the movie?

Wombler
24th August 2008, 22:39
The 720x480 encode went well, it took much less time of course than a BD movie, and the playback looks identical to the original.

Excellent.

If you want the ultimate test though try Rammstein's 'Volkerball' DVD.

I tried this one with various encoders and couldn't even get what I'd regard as passable results no matter what settings I played with.

I reckon this one's impossible with normal DVD codecs.


Wombler

G_M_C
25th August 2008, 11:32
Excellent.

If you want the ultimate test though try Rammstein's 'Volkerball' DVD.

I tried this one with various encoders and couldn't even get what I'd regard as passable results no matter what settings I played with.

I reckon this one's impossible with normal DVD codecs.


Wombler

(Re)Encoding live music DVD's is often difficult. Often it is best to set higher number of keyframe-interval and instead use a lower/more sensitive scenechange-detection. If you get that right, then i-frames will be placed based more on scene-change (flashing lights for instance) in stead of just on a regular x-frame basis; But you'll still need a higher bitrate than normal, because there is much more movement / scene-changes compared to movies.

BUT (there is allways a but isn't there) the BR-specs describe a keyframe-interval of max 1 second (so keyframe-interval == framerate, rounded off). So you can only try to lower the --scenecut parameter of x264 (considerably).

Try these options (for use with this build: http://forum.doom9.org/showthread.php?p=1172251#post1172251. Use that one, some of the newer ones dont work right);

--level 4.1 --keyint 24 --min-keyint 1 --ref 4 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --subme 6 --trellis 2 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.3 --pbratio 1.2 --vbv-bufsize 22000 --vbv-maxrate 16000 --qcomp 0.5 --scenecut << set lower, maybe even down to 16 or 20 >> --me umh --merange 24 --threads auto --thread-input --progress --no-psnr --no-ssim --mvrange 511 --aud --nal-hrd --sar 1:1 --b-adapt 2 --psy-rd 1.0

Wombler
25th August 2008, 16:01
Thanks for that G_M_C but I'm afraid I haven't dabbled with x.264 yet as I haven't yet bought a Blu-ray player.

Jdobbs may find this useful ATM but I'd also like to start playing around with this stuff myself at some stage.

If you don't mind me asking, are you using a GUI with x.264 and if so, which one?


Wombler

G_M_C
26th August 2008, 07:02
[...]
If you don't mind me asking, are you using a GUI with x.264 and if so, which one?


Wombler

Atm I use Megui, and configure x264 from there. You can also set the more " expirimental" options in the custom commandline-field of Megui. Decrypting, creating AVS-scripts etc. i do myself by AvsP or by hand if it's only opening.

Actually, coming back to (re)encoding "very active" live music video's/concert recordings; The fact that you need more bitrate than average, and could try to tweak the scene-changesettings, should count for all formats / codecs.

Wombler
26th August 2008, 21:08
Actually, coming back to (re)encoding "very active" live music video's/concert recordings; The fact that you need more bitrate than average, and could try to tweak the scene-changesettings, should count for all formats / codecs.

Absolutely but I think that the original disc in this particular case is already so highly optimised that there's not enough scope to compress to DVD5 within the constraints of normal DVD codecs.

Or in other words in this extreme case adjusting the settings will make some improvement but nothing like enough to produce even a barely adequate DVD5 version.

That's why I thought it would be a good test for x264 as out of hundreds of DVDs I've never experienced anything that's even as remotely severe a test as this particular disc.


Wombler

G_M_C
27th August 2008, 00:18
Absolutely but I think that the original disc in this particular case is already so highly optimised that there's not enough scope to compress to DVD5 within the constraints of normal DVD codecs.

Or in other words in this extreme case adjusting the settings will make some improvement but nothing like enough to produce even a barely adequate DVD5 version.

That's why I thought it would be a good test for x264 as out of hundreds of DVDs I've never experienced anything that's even as remotely severe a test as this particular disc.


Wombler

I dont have that DVD, and i dont know if jdobbs has it. So i say Try it ! It's not that much different from other (re)encoding stuff. Just decrypt the DVD, run it through DGIndex, make an AVS with MPEG2Source() and open that in Megui.

The only thing you need to look at is that you have the right build of x264 for use with the commandline i gave. Megui has a bitratecalculator and can mux to mkv, so you should be able to work out how it works quite easily :)

After finishing you can try to compare with the original on you PC !

Sophocles
27th August 2008, 01:15
I’ve been backing Blu-Ray to type 5 and 9 DVD-/+R discs with no issue as of yet. I don’t use a home BD player but then I don’t expect to own one either since I prefer using an HTPC for media playback. Then I got into converting HD DVD to BD compatible type single and dual layer and that also worked like a charm in my BD player. After having done several successful encodes I decided to try the HD DVD of the new version of King Kong which is a 3 hour and 7 minute movie. Because of its 3 hour plus length I naturally decided to shoot for a dual layer disc.

The final result came in at 7.95 Gigabytes. I began playing it and the video quality was excellent and so was the sound, or so I thought. The sound and video both were excellent to about half way through the movie and then the audio turned into a reverberating metallic sounding noise. Since HD DVD’s unlike all the BD movies I’ve seen are recorded to two main files labeled “feature 1 and feature 2” my best guess is that for some reason the second feature file is not muxing properly. Any ideas?

Sharc
27th August 2008, 11:05
Have you tried to remux the original sound track(s)? It may be safer than transcoding the format.

Sophocles
27th August 2008, 22:17
Have you tried to remux the original sound track(s)? It may be safer than transcoding the format.

I think I left the original 448 KHz track in tact but now you've got me thinking that I might have inadvertently chosen to transcode. I have a new L GGW-H20L multi drive coming in today so after I move HD DVD and Lite-On BD drive to another computer I'll be able to experiment a little more often. King Kong took twice as long as any other movie I've attempted (16 hours).

jdobbs
27th August 2008, 23:24
Any chance it was True-HD or one of the other extended formats? Sometimes you have to tell TSMUXER to remove the extended part. I know when I try to play them back without down-converting I get terrible squealing on my PC.

Sophocles
28th August 2008, 00:49
I just went back and reviewed the soundtrack. It has a single 448 kbps Dolby Digital plus sound track for each of three languages.

The funny thing is that the first 60 to 70 minutes of the encodes playback audio is perfect, and then out of the blue it goes sour with a metallic buzzing sound. This is why I thought that perhaps the second feature file failed to mux properly. The video was perfect all the way through. I'm setting up a couple of rigs just for BD encoding this weekend. One to encode HD DVD to BD and another for BD to BD only. Then I'll give it another try since the 16 hours won't tie things up. LOL

laserfan
1st September 2008, 23:39
Is there any magic to using DL DVD+R discs with the BR structure i.e. any "layer break" issues to deal with?

jdobbs
1st September 2008, 23:40
I haven't had any "issues" -- but sometimes you see the pause when it hits the layer break.

tyee
2nd September 2008, 01:57
My Quad-Core Phenom 9500 is lame compared to your Q6600. How long was the movie?

Sorry for the late reply, I was on holidays. I believe the movie was 2hr. 20min. The big robot movie!

BTW, what brand of DL discs would you recommend? I see that there are few DVD-R DL but quite a few DVD+R DL?

jdobbs
2nd September 2008, 12:18
I find Verbatim to be a good disc. I use the inkjet printable DVD+R DL.

G_M_C
2nd September 2008, 12:33
I haven't had any "issues" -- but sometimes you see the pause when it hits the layer break.

Depends on the buffer in the player i think. Havent had pause with my BR-player (Panasonic db30), playing DIY BD9's (DVD9 with Bluray-structure, made by tsMuxeR).

jdobbs
2nd September 2008, 12:53
What value do you use for "--keyint", anything?

EDIT: Never mind. I see from the previous page that you use "--keyint 24". Is there a blu-ray limit/suggestion on the keyint value? I've been using the default (250) and it works -- but I wonder if it is the reason for the pause at layer break.

G_M_C
2nd September 2008, 13:47
What value do you use for "--keyint", anything?

EDIT: Never mind. I see from the previous page that you use "--keyint 24". Is there a blu-ray limit/suggestion on the keyint value? I've been using the default (250) and it works -- but I wonder if it is the reason for the pause at layer break.

Just had a disscusion about that elswhere on the board; Bluray specs say that a GOP can be max 1 sec long. Based on that I set my --keyint equal to the framerate, rounded off.

See also this thread: http://forum.doom9.org/showthread.php?t=140741

My posting (and further discussion about --keyint): http://forum.doom9.org/showthread.php?p=1178039#post1178039

jdobbs
2nd September 2008, 14:03
Good to know. Thanks. Interestingly my Sony BDP-S301 Player doesn't seem to have a problem with large GOPs. I'll modify my recommended command line in this thread to include the limited keyint.

Do you know if there is a summary of blu-ray constaints online anywhere?

Also, do you know if there is a site or document that outlines the formats for .mpls and .clpi files anywhere online? I've been dumping them out and have gathered some info -- but it is really tedious.

G_M_C
2nd September 2008, 14:35
Good to know. Thanks. Interestingly my Sony BDP-S301 Player doesn't seem to have a problem with large GOPs. I'll modify my recommended command line in this thread to include the limited keyint.

Do you know if there is a summary of blu-ray constaints online anywhere?

Also, do you know if there is a site or document that outlines the formats for .mpls and .clpi files anywhere online? I've been dumping them out and have gathered some info -- but it is really tedious.

No i have not seen a site where all the required info can be found, only bits and pieces here (on this forum) and there ; And I think there are people on this board that might be able help you further. The only thing i know of are the whitepapers on the Blu-ray Disc Association site.

laserfan
3rd September 2008, 19:27
Do you know if there is a summary of blu-ray constaints online anywhere?Not sure how all of these translate to the x264 command line, but Sharktooth has published a BR standalone profile for MeGUI over here (http://forum.doom9.org/showthread.php?t=139765) which looks like this:

<Name>Standalone-Blu-ray</Name>
<Settings>
<EncodingMode>4</EncodingMode>
<BitrateQuantizer>8000</BitrateQuantizer>
<KeyframeInterval>24</KeyframeInterval>
<NbBframes>3</NbBframes>
<MinQuantizer>10</MinQuantizer>
<MaxQuantizer>51</MaxQuantizer>
<Turbo>true</Turbo>
<V4MV>false</V4MV>
<QPel>false</QPel>
<Trellis>false</Trellis>
<CreditsQuantizer>40</CreditsQuantizer>
<Logfile>.stats</Logfile>
<CustomEncoderOptions>--mvrange 511 --aud --nal-hrd --sar 1:1</CustomEncoderOptions>
<FourCC>1</FourCC>
<MaxNumberOfPasses>3</MaxNumberOfPasses>
<NbThreads>0</NbThreads>
<QuantizerCRF>8000</QuantizerCRF>
<EncodeInterlaced>false</EncodeInterlaced>
<NoDCTDecimate>false</NoDCTDecimate>
<PSNRCalculation>false</PSNRCalculation>
<noFastPSkip>false</noFastPSkip>
<NoiseReduction>0</NoiseReduction>
<MixedRefs>true</MixedRefs>
<X264Trellis>2</X264Trellis>
<NbRefFrames>3</NbRefFrames>
<AlphaDeblock>-1</AlphaDeblock>
<BetaDeblock>-1</BetaDeblock>
<SubPelRefinement>5</SubPelRefinement>
<MaxQuantDelta>4</MaxQuantDelta>
<TempQuantBlur>0</TempQuantBlur>
<BframePredictionMode>3</BframePredictionMode>
<VBVBufferSize>30000</VBVBufferSize>
<VBVMaxBitrate>40000</VBVMaxBitrate>
<METype>2</METype>
<MERange>16</MERange>
<MinGOPSize>2</MinGOPSize>
<Profile>2</Profile>
<Level>11</Level>
<IPFactor>1.1</IPFactor>
<PBFactor>1.1</PBFactor>
<ChromaQPOffset>0</ChromaQPOffset>
<VBVInitialBuffer>0.9</VBVInitialBuffer>
<BitrateVariance>1.0</BitrateVariance>
<QuantCompression>0.5</QuantCompression>
<TempComplexityBlur>20</TempComplexityBlur>
<TempQuanBlurCC>0.5</TempQuanBlurCC>
<SCDSensitivity>40</SCDSensitivity>
<BframeBias>0</BframeBias>
<Deblock>true</Deblock>
<Cabac>true</Cabac>
<WeightedBPrediction>true</WeightedBPrediction>
<AdaptiveBFrames>true</AdaptiveBFrames>
<BFramePyramid>false</BFramePyramid>
<BRDO>true</BRDO>
<biME>true</biME>
<ChromaME>true</ChromaME>
<P8x8mv>true</P8x8mv>
<B8x8mv>true</B8x8mv>
<I4x4mv>true</I4x4mv>
<I8x8mv>true</I8x8mv>
<P4x4mv>false</P4x4mv>
<AdaptiveDCT>true</AdaptiveDCT>
<SSIMCalculation>false</SSIMCalculation>
<Lossless>false</Lossless>
<QuantizerMatrix>Flat (none)</QuantizerMatrix>
<QuantizerMatrixType>0</QuantizerMatrixType>
<DeadZoneInter>21</DeadZoneInter>
<DeadZoneIntra>11</DeadZoneIntra>
<AQmode>2</AQmode>
<AQstrength>1.0</AQstrength>


Not sure if this is "be-all, end-all" info but at least it corroborates the KeyInt of 24.

BTW I did my first BU today using your BAT file and it all worked--pretty amazing to see, though it did take my P4 fully 40 hours to complete! :eek:

I'm underwhelmed by the result, a little blocky, but I did a 2h8m movie for DVD+5 and wasn't expecting too much from the 4000kbps bitrate used. Next time I'll try a DL, or maybe downsize to 720p.

jdobbs
3rd September 2008, 19:37
If you're underwhelmed -- then something is wrong. A 2h8m movie should be very easy for x264 to encode for DVD-5. None of the ones I've done that size have any blocks at all. I'm talking "perfect". Are you sure the original wasn't blocky? Did you do two passes?

Don't know if I would have the patience for 40 hours. I'm getting down to about 8 hours now for a two pass encode now -- and that is barely tolerable.

Also -- watch out for the maximum bitrate in the profile you posted if you're writing to DVD-5 or 9, the maximum bitrate is too high for those.