BD Rebuilder Beta - Bug Reports Only

[MrVideo]

It was only meant to show the bitrate distribution, but please tell me what is wrong with it, the NTSC label?

Yep. As noted, the program is 5 years old. Many more people described digital video incorrectly then. Education has brought that number down. Unfortunately, a lack of an update is propagating the use of improper use of NTSC/PAL labels with digital video. Oh well.

[MrVideo]

No, no, it was an excellent example demonstrating exactly what I was wondering about how the bitrate was distributed.

I installed the program and have attached three samples. The first one is of a MPEG-2 sat feed. The mux is 44.7 Mbps. It surprises me that the peak video of said capture is higher that the mux bitrate.

The 2nd one is the 4 Mbps H.264 recode using the x264 parameters previously posted (4 Mbps avg bitrate). The last one is an expanded view of 400 samples showing the distribution of the bits, with the GOP I-frame getting the most (which is what is supposed to happen).

Unfortunately that damn V3 message is on the screen. I somehow doubt that V3 will be arriving any time soon.

[Sharc]

Yep! I will definitely give that another try. Unfortunately though, that seems to trigger the same error when I use DirectShow every time I use it. But, I still need to get off my but and reinstall the DirectShow filters and give it another try! I don't think I've actually tried the ARCHIVE_CRF=18 specifically in the ini yet. Hang on a minute...! You said here FORCE_CRF=18 but the hidden opts text says FIXED_CRF=18...??? Did I get this wrong...?

FIXED_CRF is correct.

[Sharc]

I installed the program and have attached three samples. The first one is of a MPEG-2 sat feed. The mux is 44.7 Mbps. It surprises me that the peak video of said capture is higher that the mux bitrate.......
.

I think it depends how the local bitrate is defined and measured, e.g. averaged over 1 second intervals or averaged over 1 GOP or averaged over 1 frame duration, sliding window or not etc.

[Lathe]

FIXED_CRF is correct.

Thanks Sharc. Bummer... I was hoping for a nice, easy fix...

[Sharc]

...Unfortunately though, that seems to trigger the same error when I use DirectShow every time I use it. But, I still need to get off my but and reinstall the DirectShow filters and give it another try! .....
Re-install DirectShow etc., but remember that it wouldn't solve issues which actually have its roots in sources of doubtful origin.

[Lathe]

Re-install DirectShow etc., but remember that it wouldn't solve issues which actually have its roots in sources of doubtful origin.

Heh... you must be related to Ch3vr0n... :)

Guys, go ahead and slander to your heart's content. I am truly weary of stating until I die that I am using Blu-rays.

Please, no more... I am DONE with this issue...

[Sharc]

........
Guys, go ahead and slander to your heart's content. I am truly weary of stating until I die that I am using Blu-rays.
...........

Ohhh, I see, you are improving ...... :p
No offense! I really don't care what people have on their HD. I would just find it unfair (against jdobbs and others trying to help) if this BDRB bug report thread would be used for seeking help on issues which may eventually have been caused by doubtful source material.
Apparently a general, unnecessary reminder, no less and no more :)

[gonca]

Yep. As noted, the program is 5 years old. Many more people described digital video incorrectly then. Education has brought that number down. Unfortunately, a lack of an update is propagating the use of improper use of NTSC/PAL labels with digital video. Oh well.

Oy Vey!!!

[jdobbs]

FIXED_CRF is correct.My mistake. Yes, it's FIXED_CRF.

[lauguru]

jdobbs@
It is possible to add in setup bdrebuilder use DGDecNV x64 , only suport 32 bits.

the DGDecNV build 2052 suport x64

thanks

http://image.prntscr.com/image/9147badb0ace4023a4107c7c14738238.png

[DoctorM]

AFAIK, the only 64-bit method currently supported is using x264's internal LAVfilter.

[Sharc]

@jdobbs
Did you already come to any conclusions on this? Is it a bug?
http://forum.doom9.org/showpost.php?p=1775637&postcount=24629

[Lathe]

Ah, there we go...

I just simply chose the FRIM frame server (which I NEVER USE) and BINGO! no more AnyDVD errors... Gee, how about that...? The only thing though is that although it IS re-encoding, it is doing so at a CRF of 23 instead of 18, but HEY that IS progress! :)

Here is the .264 stats of the currently re-encoding file in the workfiles:

cabac=1 / ref=4 / deblock=1:-2:-2 / analyse=0x3:0x113 / me=umh / subme=8 / psy=1 / psy_rd=1.00:0.20 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=6 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=1 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.50 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=15000 / vbv_bufsize=13000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / aq=1:1.00

Here is the log:

[07/30/16] BD Rebuilder v0.50.17
[21:02:50] Source: __VID00000
- Input BD size: 15.11 GB
- Approximate total content: [01:33:34.859]
- Windows Version: 6.2 [9200]
- Archive Backup (AVC/AC3) mode enabled
- Quality: High Quality (Default)
- X264 Tweak(s) enabled
- Decoding/Frame serving: FRIMSource
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[21:02:51] PHASE ONE, Encoding
- [21:02:51] Processing: VID_00000 (1 of 1)
- [21:02:51] Extracting A/V streams [VID_00000]
- [21:04:31] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 134,622 frames
- [21:04:31] Reencoding: VID_00000, Pass 1 of 1

(No AnyDVD error... GEE, how about that...)

Here is my ini, which is still the same as it has been:


VERSION=0.50.0.17
ENCODER=0
MODE=4
ENCODE_QUALITY=2
ONEPASS_ENCODING=1
AUTO_QUALITY=0
FIXED_CRF=18
AVSFilter01=tweak(cont=1.40, bright=1, Sat=1.3, startHue=325, endHue=15, maxSat=75)
TWEAK_PASS_ONE=--direct auto --qcomp 0.50
TWEAK_PASS_TWO=--ref 4 --deblock -2:-2 --psy-rd 1.00:0.20 --me umh --subme 8 --trellis 2 --direct auto --qcomp 0.50
AUTO_BIAS=3
B_PYRAMID=1
QUICK_CRF=24
ENABLE_TEST=1
ENABLE_BLANKING=1
ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ARCHIVE_265=0
ARCHIVE_AUDIO_100
KEEP_HD_LPCM=1
USE_ZLIB=0

ALTERNATE_BLURAY=0
ENCODER_MENU=1
MBTREE=1

MENU_BACKGROUND=D:\EXECUTABLES\BD-RBV05017\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=D:\EXECUTABLES\BD-RBV05017\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1

AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=1
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=4
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
[Paths]
WORKING_PATH=C:\_______MEDIA\_BDRB\
SOURCE_PATH=C:\_______MEDIA\__TSMUXER\

So, if anyone can see why it is encoding the archive at CRF 23 instead of 18 that would be great!

[Lathe]

Hmmm... I thought simply adding '--crf 18' to the 2nd pass tweaks would do it, but it is still encoding at 23... I wonder why?

[Sharc]

Hmmm... I thought simply adding '--crf 18' to the 2nd pass tweaks would do it, but it is still encoding at 23... I wonder why?
CRF is 1-pass. Adding anything to the 2nd pass tweaks has no effect as there is no 2nd pass.
But as jdobbs has written to you few posts before, you have to put ARCHIVE_CRF= when using archive mode.
FIXED_CRF= applies for the regular 1-pass (non-archive) modes.
Looks like people are wasting their breath ..... :rolleyes:

[gonca]

From HIDDENOPTS file

ARCHIVE_CRF n = 10-50 X265 CRF value to use for ARCHIVE mode (default=23)

[jdobbs]

@Lathe All you have to do is set ARCHIVE_ENABLE=1 and ARCHIVE_CRF=18 in the INI and you can do ARCHIVE backups using CRF. It's almost the same as what you get with FIXED_CRF.

See gonca's comment. FIXED_CRF is for a different mode. ARCHIVE_CRF is what you use when doing an ARCHIVE backup.

[jdobbs]

@jdobbs
Did you already come to any conclusions on this? Is it a bug?
http://forum.doom9.org/showpost.php?p=1775637&postcount=24629Sorry. But I still haven't looked at it.

[Sharc]

Sorry. But I still haven't looked at it.
Thanks, no problem. I was afraid that you may have forgotten or not seen it :)

[Lathe]

@Lathe

See gonca's comment. FIXED_CRF is for a different mode. ARCHIVE_CRF is what you use when doing an ARCHIVE backup.

Awesome! Thanks you guys :)

[emilio99]

One Question: When using alternative ouput with e.g. convert to 1080p mkv then I can use "Two Pass Encoding" but the bitrate is already set a value which is not changeable (entry is read only grey).

Why this is not changeable and where this value comes from?

[jdobbs]

One Question: When using alternative ouput with e.g. convert to 1080p mkv then I can use "Two Pass Encoding" but the bitrate is already set a value which is not changeable (entry is read only grey).

Why this is not changeable and where this value comes from?Look in BD Rebuilder's MISC folder. The file ALTERNATE.TXT contains all the presets that show up when you're selecting ALTERNATE output. You can modify any of them, or add more. There is text at the top of the file that explains all the settings. If you modify it while BD-RB is running, make sure you exit and reenter the program to see any changes.

[emilio99]

Look in BD Rebuilder's MISC folder. The file ALTERNATE.TXT contains all the presets that show up when you're selecting ALTERNATE output. You can modify any of them, or add more. There is text at the top of the file that explains all the settings. If you modify it while BD-RB is running, make sure you exit and reenter the program to see any changes.

Wow, cool! Thanks, will take a look :D

[DoctorM]

Is there a simpler way to set X264's tune or is the only method:
TWEAK_PASS_ONE=--tune animation
TWEAK_PASS_TWO=--tune animation

I'm working with an old Lupin the Third film and most sources suggest this should provide an improvement when re-encoding.

[jdobbs]

Is there a simpler way to set X264's tune or is the only method:
TWEAK_PASS_ONE=--tune animation
TWEAK_PASS_TWO=--tune animation

I'm working with an old Lupin the Third film and most sources suggest this should provide an improvement when re-encoding.Nope, that's it.

[DoctorM]

Nope, that's it.

Thanks. Encoded both ways and in just the first few second the tuned version was visibly inferior.

I really need to just trust your settings.

[Lathe]

Thanks. Encoded both ways and in just the first few second the tuned version was visibly inferior.

I really need to just trust your settings.

Careful...

JD's gonna get a big head again, and you KNOW what happened last time...

[jdobbs]

Careful...

JD's gonna get a big head again, and you KNOW what happened last time...Hmm... I don't remember that. What did that jerk JD do last time?

[gonca]

Hmm... I don't remember that. What did that jerk JD do last time?

Lost his balance and fell off a roof.
You, on the other hand, are a very humble person, one of the greats.:D:D

[Lathe]

hmm... I don't remember that. What did that jerk jd do last time?
.


:)

[Lathe]

Lost his balance and fell off a roof.
You, on the other hand, are a very humble person, one of the greats.:D:D

Suckup... :devil:

[gonca]

:eek::eek::sly:

[jdobbs]

Lost his balance and fell off a roof.
You, on the other hand, are a very humble person, one of the greats.:D:DWow. You remember that, eh? I'm lucky I didn't break my neck.

[Lathe]

Wow. You remember that, eh? I'm lucky I didn't break my neck.

Yeah... but with all the new information about concussions...

And, how do we know that that was the FIRST time you fell off the roof...? :eek:

[RobertM]

I think I speak for the whole crowd when I say that we're ALL happy that you didn't do that ;)

Wow. You remember that, eh? I'm lucky I didn't break my neck.

[jdobbs]

I think I speak for the whole crowd when I say that we're ALL happy that you didn't do that ;)There are some who might disagree with you. :)

[gonca]

Who cares what Toilet Duck (or his alias) thinks

[Lathe]

Who cares what Toilet Duck (or his alias) thinks

(...beginning the incantation to invoke Toilet Duck...) :devil:

[gonca]

(...beginning the incantation to invoke Toilet Duck...) :devil:
Don't forget his alter ego >>> Metagondria

[DoctorM]

Don't forget his alter ego >>> Metagondria

You can take penicillin for that.

[Lathe]

You can take penicillin for that.

... or use protection.

[Lathe]

So, what exactly IS this for again...?

NEW_CRF_PREDICTION=1

And, how do you use it?

[jdobbs]

So, what exactly IS this for again...?

NEW_CRF_PREDICTION=1

And, how do you use it?Wow. I'd forgotten about that. It chooses a newer prediction algorithm that I'd created. It finds the desired CRF in fewer passes. I've been using it for a long time and it should have been set as the default a long time ago. I recommend you set it to 1. I'll make it the default in the next release.

[Sharc]

Wow. I'd forgotten about that. It chooses a newer prediction algorithm that I'd created. It finds the desired CRF in fewer passes. I've been using it for a long time and it should have been set as the default a long time ago. I recommend you set it to 1. I'll make it the default in the next release.

Maybe you keep an eye on this. I had NEW_CRF_PREDICTION enabled:
http://forum.doom9.org/showpost.php?p=1770564&postcount=24334

[Lathe]

Wow. I'd forgotten about that. It chooses a newer prediction algorithm that I'd created. It finds the desired CRF in fewer passes. I've been using it for a long time and it should have been set as the default a long time ago. I recommend you set it to 1. I'll make it the default in the next release.

Oh good, thanks!

I did set it to '1', but, uh, how do I use it...? Is that how you figured out the CRF value when you told me what it would be for a film if you filled out a BD-25 (I think you said it was a CRF of around 12.5) as opposed to if you used CRF-18 (which I was asking you about at the time) then the size came out to about 5.5 Gigs.

Is there a way I can use it to figure that out too? How do I use it?

[DoctorM]

I was taking a look at Big Buck Bunny today and saw that all Stereoscopic 3D formats are either full HD over-under or UHD over-under (yup 3840x4320 video).
Is it possible to convert either the HD or UHD over-under to 3DBD with Rebuilder?

I see you can import SBS, but I'm not even sure it would downscale.

[gonca]

@Lathe
BD output >>> fixed size >>> one pass CRF, from settings -- encoder settings

[Lathe]

@Lathe
BD output >>> fixed size >>> one pass CRF, from settings -- encoder settings

Thanks kindly, but I don't understand how that helps me utilize that function in any way. Those are the settings that have been giving me trouble to re-encode anyway (as I've mentioned exhaustively already, using a 1-pass CRF encode with DirectShow ALWAYS gives me an AnyDVD error regardless of source. Or, if I set it for FRIM frame server I THINK that will run)

But, that doesn't tell me how to use this new function though. HOW, do I use it or use it to tell me what the CRF will be at a certain size, etc...?

[jdobbs]

I was taking a look at Big Buck Bunny today and saw that all Stereoscopic 3D formats are either full HD over-under or UHD over-under (yup 3840x4320 video).
Is it possible to convert either the HD or UHD over-under to 3DBD with Rebuilder?

I see you can import SBS, but I'm not even sure it would downscale.You can import half or full SBS -- and it will create a 3DBD (after reencoding). You can also use ALTERNATE output to convert it to half SBS. Right now BD-RB only supports SBS, but I guess over-under wouldn't be that hard to add.

3840x4320?