BD-RB's TWEAK_PASS_ONE/TWEAK_PASS_TWO

[hoju3508]

Hi,

I was trying to change the preset to veryslow by using these two hidden options, but it's not taking it. I stopped the job (BD50->BD25, movie only) after a bit and looked at the LASTCMD.txt file.

[15:24:50] BD Rebuilder v0.38.04 (beta)
- Source: NOWHERE_BOY
- Input BD size: 25.18 GB
- Approximate total content: [01:39:12.988]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:24:53] PHASE ONE, Encoding
- [15:24:53] Extracting A/V streams [VID_00011]
- [15:31:41] Reencoding: VID_00011 (1 of 1)
- [15:31:41] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 142,729 frames
- Bitrate: 27,516 Kbs
- [15:31:41] Reencoding: VID_00011, Pass 1 of 2
[15:32:30]PHASE ONE aborted by user request


LASTCMD.txt
"C:\Tools\BD_Rebuilder\tools\x264.exe" "C:\BD_REBUILDER_WORK\WORKFILES\VID_00011.AVS" --preset slow --bluray-compat --ref 4 --b-adapt 1 --b-pyramid none --weightp 1 --qpmin=0 --bitrate 27516 --level 4.1 --qpfile "C:\BD_REBUILDER_WORK\WORKFILES\VID_00011.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats "C:\BD_REBUILDER_WORK\WORKFILES\VID_00011.AVS.264.stats" --pass 1 --output NUL


Perhaps I'm not using it right or the options that I'm trying to use is not allowed.

I got the x264 switches from here (http://www.x264bluray.com/home/1080i-p).

TWEAK_PASS_ONE=--preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --sar 1:1 s = X264 pass 1 command line tweak(s)(warning -- for experts only, bugs not supported)
TWEAK_PASS_TWO=--preset veryslow --tune film --bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --keyint 24 --open-gop --slices 4 --sar 1:1 s = X264 pass 2 command line tweak(s)(warning -- for experts only, bugs not supported)


Any ideas?

:thanks:

[jdobbs]

BD Rebuilder removes switches that can or might create an incompatiblity with the blu-ray or AVCHD standard. Your command line is filled with them. You've also left the comments at the end -- meaning BD-RB will attempt to add garbage to the command line ("s = X264 pass 1 command...").

Did you actually add those lines to the INI file? It almost looks like you edited the HIDDENOPTS.TXT file, which of course is only there as ain informational file to advise you of the values that can be used...

BD Rebuilder already uses the correct values for proper blu-ray encoding. My advice is to simply leave them alone.

[hoju3508]

Thanks for the reply jdobbs. I thought the HIDDENOPTS.TXT file was used by BD-RB.

[RobertM]

If you really want to play around with different encoding settings then I suggest that you do so OUTSIDE of the BD-Rebuilder application. BD-Rebuilder has constraints on what it will tell x264 to do, for good reasons. You can play around a bit with the settings by inserting the HIDDENOPS commands into the "ini" file, but you won't really be sure what the ACTUAL custom settings were until you inspect the LASTCMD.txt file to see what BD-Rebuilder, ultimately, told x264 to do.

A better idea would be to do all this manually, which prevents BD-Rebuilder from 'nannying' away all the mistakes that you are going to make. Here is a process that you could use:

1. Find some sections of a BD movies that you want to use for experimentation purposes. Not whole movies, but just short parts, maybe 10 seconds to 1 minute each. Possibly an action scene, panning scene, fading scene,... whatever you think might demonstrate how well the encode process has worked. Working with a few small sections will allow you to conduct your experiments quickly, without waiting hours to see the results of each iteration. Use tsMuxeR to snip those sections out of their parent movies and save them as separate trial files, or stitch them together into a short experimental demo movie.

2. Use tsMuxeR to strip the video out of the files; these video only streams will be your source files for your x264 experiments.

3. Copy the LASTCMD.txt file to a batch file. This will be your template for your experiments.

4. Find a reference for x264 to guide you in what settings are possible. One that I have looked at is http://mewiki.project357.com/wiki/X264_Settings".

5. Now you can edit your batch file, putting in any settings you want, and run the batch. Remember that parameters appearing later in the list may overwrite earlier parameters. So if you add in a bunch of custom settings, but they are followed by something like "--bluray-compat" then your earlier settings may have been overwritten.

6. After running the batch you may want to use tsMuxeR to stitch the new video back with its original audio. This might make reviewing the re-encoded video more pleasant.

7. Rinse and repeat.


Using a method like this will allow you to take manual control of the re-encoding process. It allows you to make lots of mistakes, to be sure, but each mistake will be over quickly and, therefore, relatively painlessly.

Now, please keep in mind that if you come up with some crazy combination of settings, and you have absolutely convinced yourself that they are the pinnacle of re-encoding perfection, don't delude yourself into believing that JDobbs will agree with you -- or, even less likely, will make any changes to BD-Rebuilder to incorporate your new-found wisdom. You may have created a non-compliant stream, you may be wrong in your perception that your result is "better", or you may just be wrong in general. Remember that you are conducting these re-encoding experiments for yourself only; other people might not be interested in hearing about any of it.

Speaking for myself, I just do "movie only" BD-25 backups using the default settings in BD-Rebuilder. ;)

[JJB]

Quote:

"Speaking for myself, I just do "movie only" BD-25 backups using the default settings in BD-Rebuilder."

Words of wisdom.:p

[setarip_old]

@RobertM, @JJB

As well intentioned as that statement is (and it's certainly your prerogative to do so), limiting your use of Bd-RB to ONLY creating "movie-only" discs is not necessarily going to provide "jdobbs" with sufficient information to COMPLETELY debug each new iteration of BD-RB...