BD Rebuilder Beta - Bug Reports Only

[Capsbackup]

Originally Posted by jdobbs

I fixed it. Actually it was caused by BD-RB and was an indicator of an actual bug that had been reported a while back... so I'm glad you asked me to address it. Two bugs killed with one stone.

Well that was fast!
And a bonus swat can always bring on a smile.

[Rodger]

Originally Posted by jdobbs

Definitely use DGDecNV. It is faster and reduces the processing necessary for several functions.

It's up to you with AVISYNTH, but you'll find I'm very hesitant to respond to bug reports when alpha software is in use that might be the cause, and may require a switch to v2.58 before accepting it as a bug.

THANKS for your heads up.

100% understand your thinking about unverified software.
But I´d say it´s beyond alpha state....even beyond beta state thanks to SEt. More like a RC. SEt fixed a lot of glitches and errors. But I can´t speak for the whole community of video encoders since I don´t use many filters.

[Sharc]

Originally Posted by jdobbs

That's really weird.

The truncated strings will have no effect -- they're just shortened because of the maximum width of the menu text at the given font size.

I am also surprised to find sometimes the generated menu background clip -- the default stars picture -- included as an "Extra" in the Quick-Menu list (titles.inf), although the thresholds are set to 10 or higher. I have to deselect it and save again to remove it from the Quick Menu. It does not happen every time though.

[Rodger]

I have never seen BDRB as a tool backup BDs to BD5/9 as a AVCHD.
Most probably because I was using "BDtoAVCHD" befor knowing of BDRB.

So I like a lot about BDRB which makes me think of BDRB replacing the other tool for BD5/9 Discs.

But BD-RB seems to be very wasterful with the possible disc space.
BDtoAVCHD makes a special run though the bitrates to be able to make a better encode-bitrate prediction.
So it is able to ALWAYS stay over 7,9GB in size making the best of the space available on BD9.

My first attempt with BDRB is 6,86GB. Over 1GB wasted.
So I´d like to know/find out is it my fault...do I need to learn how to tweak BDRB to use the space available better.

[Patrick]

An easy to reproduce bug: select some streams to be blanked and add the project to the batch queue. There is an entry about blanking attached to each queue entry (a bit vector I suppose), but the batch processor ignores all blanking requests...

[HWK]

Originally Posted by Rodger

I have never seen BDRB as a tool backup BDs to BD5/9 as a AVCHD.
Most probably because I was using "BDtoAVCHD" befor knowing of BDRB.

So I like a lot about BDRB which makes me think of BDRB replacing the other tool for BD5/9 Discs.

But BD-RB seems to be very wasterful with the possible disc space.
BDtoAVCHD makes a special run though the bitrates to be able to make a better encode-bitrate prediction.
So it is able to ALWAYS stay over 7,9GB in size making the best of the space available on BD9.

My first attempt with BDRB is 6,86GB. Over 1GB wasted.
So I´d like to know/find out is it my fault...do I need to learn how to tweak BDRB to use the space available better.

I am assuming you are using default setting in BD-RB. If so you need to enable 2-pass encoding which will encoder meet target size and provide better quality.

Also Jdobbs has reserved some space, however not as much you are seeing.

[jdobbs]

Originally Posted by Rodger

I have never seen BDRB as a tool backup BDs to BD5/9 as a AVCHD.
Most probably because I was using "BDtoAVCHD" befor knowing of BDRB.

So I like a lot about BDRB which makes me think of BDRB replacing the other tool for BD5/9 Discs.

But BD-RB seems to be very wasterful with the possible disc space.
BDtoAVCHD makes a special run though the bitrates to be able to make a better encode-bitrate prediction.
So it is able to ALWAYS stay over 7,9GB in size making the best of the space available on BD9.

My first attempt with BDRB is 6,86GB. Over 1GB wasted.
So I´d like to know/find out is it my fault...do I need to learn how to tweak BDRB to use the space available better.

All DVD+-Rs I have used/tested (even the very high grade ones) are susceptible to problems on the outer tracks. So I've reduced the output size to avoid that area. But yours is undersized by quite a bit more than that. You can adjust target sizes as you see fit with undocumented settings. Here they are with their defaults:

BD5_SIZE=4469
BD9_SIZE=8032
BD25_SIZE=23500
BD50_SIZE=47366

(Actual output target size in bytes would be this number * 1024 * 1024 using true binary numbers). So a perfectly sized BD-9 output would be 8,422,162,432 bytes in size. A DVD+R DL will hold 8,547,991,552 bytes. So in true GB size, a BD-9 will only hold 7.96GB. When getting sizes as small as you are reporting there is usually one of two things happening. 1. The original was small enough to fit without reencoding so it is keeping it's original size (you can never reencode to a better picture than the original). 2. The bitrate required to hit the target size (when adding in the audio/subtitle requirements) would be higher than the maximum transfer rate allowable under the BD-5/9 standard.

There's really no 100% accurate way to predict output size, because the muxing in BD format is fairly unpredictable. Each audio type, for example has different percentages of muxing overhead. Also, there is no perfect encoder that will always hit exactly.

You can also set a custom size.

[HWK]

Originally Posted by jdobbs

Yeah. All DVD+-Rs I have used/tested (even the very high grade ones) are susceptible to problems on the outer tracks.

What do you think of M-Disc?

[jdobbs]

Originally Posted by HWK

What do you think of M-Disc?

Don't know much about it -- and I think it requires a special burner. So obviously I haven't tested it.

[HWK]

Originally Posted by jdobbs

Don't know much about it -- and I think it requires a special burner. So obviously I haven't tested it.

I will tell you, indeed it does require a special burner, which I have it. Since they have no dye layer on disc, a high power laser is used to engrave data on disc surface.

Just for info this is how disc looks, notice how transparent are they.

[Sharc]

Originally Posted by jdobbs

There's really no 100% accurate way to predict output size, because the muxing in BD format is fairly unpredictable. Each audio type, for example has different percentages of muxing overhead. Also, there is no perfect encoder that will always hit exactly.

You can also set a custom size.

Very true. For video + 2 x audio 2.0 192kbps ac3 (my old SVCD) I have to set the custom size to 4400 for BD5 which fills the disc 98%.

[HWK]

Originally Posted by mparade

....just have sent 100 bucks for this fantastic program and for further improvements on the 3D feature. Keep it up!

I couldn't have said any better myself. So for me donation payment is by 2x.

[inge70]

Originally Posted by jdobbs

I fixed it. Actually it was caused by BD-RB and was an indicator of an actual bug that had been reported a while back... so I'm glad you asked me to address it. Two bugs killed with one stone.

you're the best .. thank you

[Rodger]

Thanks for the info.

So I changed "hiddenopts.txt" as following:

BD5_SIZE=n n = Change the output size (in one megabyte units) for BD-5 writes -- default = 4480
BD9_SIZE=n n = Change the output size (in one megabyte units) for BD-9 writes -- default = 8125
BD25_SIZE=n n = Change the output size (in one megabyte units) for BD-25 writes -- default = 24500

ALWAYS use Verbatim is what I only can say. I copy the experience of jdobbs and admire him for thinking of what many users don´t know or think.
The only brand to expect stable results is verbatim. Tried so many others and always got disappointed.
TDK has/had decent ones too...but too expensive not to directly use the reference from verbatim.
And STAY AWAY from LTH types!!! Some burnerse don´t like them at all, others burn them with degraded write speeds. I don´t even fully trust the ones from verbatim.
I have burned and played them all without a single loss but time will tell if they can live up the the expectations I have with verbatim medias.
MY burners are PIONEER BDR-206 and PIONEER BDR-S08

Watch out for the media codes:
BD9 = MCC03RG20 DVD-R DL / MKM-003-00 DVD+R DL
BD25 = VERBAT-IMu-000 = LTY Type / CMCMAG-BA5-000 = Normal Type

[Sharc]

See also:
http://www.digitalfaq.com/reviews/dvd-media.htm

[jdobbs]

Originally Posted by HWK

I couldn't have said any better myself. So for me donation payment is by 2x.

Wow. What can I say? It is appreciated very much.

[jdobbs]

Originally Posted by Rodger

Thanks for the info.

So I changed "hiddenopts.txt" as following:

BD5_SIZE=n n = Change the output size (in one megabyte units) for BD-5 writes -- default = 4480
BD9_SIZE=n n = Change the output size (in one megabyte units) for BD-9 writes -- default = 8125
BD25_SIZE=n n = Change the output size (in one megabyte units) for BD-25 writes -- default = 24500

ALWAYS use Verbatim is what I only can say. I copy the experience of jdobbs and admire him for thinking of what many users don´t know or think.
The only brand to expect stable results is verbatim. Tried so many others and always got disappointed.
TDK has/had decent ones too...but too expensive not to directly use the reference from verbatim.
And STAY AWAY from LTH types!!! Some burnerse don´t like them at all, others burn them with degraded write speeds. I don´t even fully trust the ones from verbatim.
I have burned and played them all without a single loss but time will tell if they can live up the the expectations I have with verbatim medias.
MY burners are PIONEER BDR-206 and PIONEER BDR-S08

Watch out for the media codes:
BD9 = MCC03RG20 DVD-R DL / MKM-003-00 DVD+R DL
BD25 = VERBAT-IMu-000 = LTY Type / CMCMAG-BA5-000 = Normal Type

I'm sure you already know this, but for others who may be reading -- HIDDENOPTS.TXT is just documentation. The actual changes are added to BDREBUILDER.INI.

By the way, Verbatims are very good discs and I have a stack of them in front of me -- but they (the DVD+-R discs) are prone to errors on the outside tracks as well. It's probably less-likely than cheap discs, but it's still there. The same is true for BD-R, errors are more likely in the outer tracks -- but the issue seems much less pronounced than on DVD (I really don't know why).

[jdobbs]

Originally Posted by Patrick

An easy to reproduce bug: select some streams to be blanked and add the project to the batch queue. There is an entry about blanking attached to each queue entry (a bit vector I suppose), but the batch processor ignores all blanking requests...

I'll look at it.

[gonca]

In view of the Toronto connection, HWK, $100 on the way. Jdobbs, buy the spouse some flowers amd relax for a day.

[jdobbs]

Originally Posted by gonca

In view of the Toronto connection, HWK, $100 on the way. Jdobbs, buy the spouse some flowers amd relax for a day.

I will do just that. Thanks for the support (again).