BD Rebuilder Beta - Bug Reports Only

[Rodger]

Hi Guys,

sadly another one with that annoying error:

----------------------
[02.15.14] BD Rebuilder v0.46.11 (beta)
[07:48:46] Source: RED_2
- Input BD size: 35,32 GB
- Approximate total content: [03:00:15.596]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[07:48:46] PHASE ONE, Encoding
- [07:48:46] Processing: VID_00027 (1 of 4)
- [07:48:46] Extracting A/V streams [VID_00027]
- [07:48:51] Reencoding video [VID_00027]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 107 frames
- [07:48:51] Reencoding: VID_00027, Pass 1 of 1
- [07:48:51] Video Encode complete
- [07:48:51] Processing audio tracks
- [07:48:51] Multiplexing M2TS
- [07:48:55] Processing: VID_00026 (2 of 4)
- [07:48:55] Extracting A/V streams [VID_00026]
- [07:49:02] Reencoding video [VID_00026]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 2.959 frames
- [07:49:02] Reencoding: VID_00026, Pass 1 of 1
- [07:49:16] Video Encode complete
- [07:49:16] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [07:49:16] Multiplexing M2TS
- [07:49:20] Processing: VID_00001 (3 of 4)
- [07:49:20] Extracting A/V streams [VID_00001]
- [07:50:08] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 49.931 frames
- Bitrate: 12.223 Kbs
- [07:50:08] Reencoding: VID_00001, Pass 1 of 1
- [07:55:44] Video Encode complete
- [07:55:44] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [07:55:44] Multiplexing M2TS
- [07:56:05] Processing: VID_00000 (4 of 4)
- [07:56:05] Extracting A/V streams [VID_00000]
- Error in attempt to extract audio/subs.
-
[07:58:22] - Failed to retrieve audio, aborted


Since ALL my Rips seems to have problem now (only in BDRB it seems) I took a shot and tried that file in tsmuxer as that is usually the problem described when that error appears.
But tsmuxer is not the problem it seems:

SmartLabs tsMuxeR. Version 1.10.6 http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
H.264 stream does not contain fps field. Muxing fps=23.976
Decoding DTS-HD stream (track 2): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 7.1 (DTS Master Audio)
Decoding DTS-HD stream (track 3): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 7.1 (DTS Master Audio)
Decoding PGS stream (track 5): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 6): Resolution: 1920:1080 Frame rate: 23.976
Processed 166993 video frames
Demux complete.
Demuxing time: 1 min 22 sec

Full BD-Backup. I´m trying Movie only to see if that helps.
Until now every time BDRB showed that message I ALWAYS was able to "save" the movie only with BDtoAVCHD.
And it shows me a working progress with VID_00000 instead of stopping with an error.
I really think this is a problem of BDRB. Whatever it is :(

see here:
[02.15.14] BD Rebuilder v0.46.11 (beta)
[08:13:32] Source: RED_2_00000
- Input BD size: 24,95 GB
- Approximate total content: [01:56:04.999]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[08:13:34] PHASE ONE, Encoding
- [08:13:34] Processing: VID_00000 (1 of 1)
- [08:13:34] Extracting A/V streams [VID_00000]
- [08:16:55] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 166.993 frames
- Bitrate: 20.916 Kbs
- [08:16:55] Reencoding: VID_00000, Pass 1 of 1


Anyone got an idea why that happens?

[inge70]

Just curious, I have noticed ever since BD-RB began using the new tsMuxer, after movie only backups to AVCHD there is two clipi and mpls files in each respective folders. One is named 00000.clpi and 00000.mpls, the other is just .clpi and .mpls.
Is there a reason for this? :confused:

is also already noticed. only I do not know if the new tsmuxer causes or BD_Rebuilder. The files 00000.clpi and 00000.mpls in the folders BMDV / Backup / CLIPINF and BDMV / Backup / playlist, and in BDMV / CLIPINF and BDMV / playlist are ok and need to be there. But there appear additional files only. Clpi and. Mpls hot, so without "00000" in the name, the wrong and the burn an AVCHD, in the acquisition, denied. these files. clpi and. mpls please delete. They are each present twice in the folders listed here.
Then, no more burning program complains rum. ;)

PS: If I use tsMuxeR solo, that does not happen when I Muxe a mkv to AVCHD. Teste just BD_Rebuilder if it happens there, as I have already noticed with these additional two files.

[colinhunt]

I bumped into something which is very likely not a bug with BD-RB, but it's vexing nevertheless. I did a full backup of The Americans disc 2 on 0.46.11, and the deleted scenes came out somewhat messed up again. The four relevant m2ts files are 00300, 00301, 00302 and 00303.

Since the backup came out a bit undersized and there was enough space for them, I decided to replace the four messed up files with the originals. So I copied the four m2ts files to the backup, followed by the .clpi and .mpls files, also named 00300, 00301, 00302 and 00303. I also replaced the backups with originals in the BDMV / Backup directory.

But all that wasn't enough, because the backup does not play correctly. Deleted scenes start in the middle, play for a second, then skip to the next one. What did I miss or mess up?

[jdobbs]

Just curious, I have noticed ever since BD-RB began using the new tsMuxer, after movie only backups to AVCHD there is two clipi and mpls files in each respective folders. One is named 00000.clpi and 00000.mpls, the other is just .clpi and .mpls.
Is there a reason for this? :confused:I've noticed it too. But can't seem to find one where they exist now. I assumed it was a bug in TSMUXER, but I'll check to find out. I don't think it hurts anything, but I'll make sure it goes away in the next release.

Can you give me a specific sequence that will cause it?

[jdobbs]

Hi Guys,

sadly another one with that annoying error:
...
Anyone got an idea why that happens?I have RED_2 on my hard drive. Post the contents of your INI file and I'll run a test. Could you also run INSPECT from the HELP menu and post the results?

[Capsbackup]

I've noticed it too. But can't seem to find one where they exist now. I assumed it was a bug in TSMUXER, but I'll check to find out. I don't think it hurts anything, but I'll make sure it goes away in the next release.

Can you give me a specific sequence that will cause it?

Seems that every movie only backup to BD5 or BD9 causes this for me.
Source is original Blu-ray rip.

[Rodger]

Hi there Jdobbs,

cleared my harddrive up su just started a new run to deliver an ini file.

INSPECT:
- Windows Version: 6.2 [9200]
- AVISYNTH Version: [2.6.0.3], not recommended version
- HAALI Splitter: [1.9.42.1], Ok
- FFDSHOW: [4504], Ok
- FFDSHOW VC-1 set incorrectly: [19]
- FFDSHOW MPEG2 set incorrectly: [19]
- FFDSHOW AVC set incorrectly: [19]
- AnyDVD settings check: Ok.
- BD-RB v0.46.0.11, not current

INFO FFDSHOW Errors = Intel Quicksync is set

==============================================
Complete Verbose Log of Project:
[02.15.14] BD Rebuilder v0.46.11 (beta)
[15:45:41] Source: RED_2_00000
- Input BD size: 24,95 GB
- Approximate total content: [01:56:04.999]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:45:41] PHASE ONE, Encoding
- [15:45:41] Processing: VID_00000 (1 of 1)
- [15:45:41] Extracting A/V streams [VID_00000]
[15:45:46]PHASE ONE aborted by user request
----------------------
[02.15.14] BD Rebuilder v0.46.11 (beta)
[15:45:53] Source: RED_2
- Input BD size: 35,32 GB
- Approximate total content: [03:00:15.596]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:45:54] PHASE ONE, Encoding
- [15:45:54] Processing: VID_00027 (1 of 4)
- [15:45:54] Extracting A/V streams [VID_00027]
- [15:45:59] Reencoding video [VID_00027]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 107 frames
- [15:45:59] Reencoding: VID_00027, Pass 1 of 1
- [15:45:59] Video Encode complete
- [15:45:59] Processing audio tracks
- [15:45:59] Multiplexing M2TS
- [15:46:03] Processing: VID_00026 (2 of 4)
- [15:46:03] Extracting A/V streams [VID_00026]
- [15:46:10] Reencoding video [VID_00026]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 2.959 frames
- [15:46:10] Reencoding: VID_00026, Pass 1 of 1
- [15:46:24] Video Encode complete
- [15:46:24] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [15:46:24] Multiplexing M2TS
- [15:46:28] Processing: VID_00001 (3 of 4)
- [15:46:28] Extracting A/V streams [VID_00001]
- [15:47:10] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 49.931 frames
- Bitrate: 12.223 Kbs
- [15:47:10] Reencoding: VID_00001, Pass 1 of 1
[02.15.14] Checking System Settings
- BD-Rebuilder v0.46.11 (beta)
- Windows Version: 6.2 [9200]
- AVISYNTH Version: 2.6.0.3, not recommended version
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set incorrectly: [19]
- FFDSHOW MPEG2 set incorrectly: [19]
- FFDSHOW AVC set incorrectly: [19]
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02.15.14] Systems Settings Check complete
- [15:52:48] Video Encode complete
- [15:52:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:52:48] Multiplexing M2TS
- [15:53:09] Processing: VID_00000 (4 of 4)
- [15:53:09] Extracting A/V streams [VID_00000]
- Error in attempt to extract audio/subs.
-
[15:55:26] - Failed to retrieve audio, aborted



TRYING MOVIE ONLY BACKUP
Completet Verbose Log:
02.15.14] BD Rebuilder v0.46.11 (beta)
[15:56:18] Source: RED_2_00000
- Input BD size: 24,95 GB
- Approximate total content: [01:56:04.999]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:56:20] PHASE ONE, Encoding
- [15:56:20] Processing: VID_00000 (1 of 1)
- [15:56:20] Extracting A/V streams [VID_00000]
- [15:59:38] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 166.993 frames
- Bitrate: 20.916 Kbs
- [15:59:38] Reencoding: VID_00000, Pass 1 of 1


NOW it is NO PROBLEM ???

[jdobbs]

The FFDSHOW settings won't really matter when you are using DGDecNV, so that's no big deal. But I'm confused as to how you could possibly get the "BD-RB v0.46.0.11, not current" message? The INSPECT in the HELP menu doesn't even check that???

What do you mean by "NOW it is NO PROBLEM"?

[Capsbackup]

@Rodger,
You need to correct the many problems displayed with "Inspect"!! :(

[jdobbs]

Seems that every movie only backup to BD5 or BD9 causes this for me.
Source is original Blu-ray rip.I was able to repeat it. I also ran the META directly from a command line and it didn't create the files... so I need to find out why it is doing it when BD-RB runs it.

[Rodger]

Sorry,

thought you´d figure it out.

The Inspect part was from the external inspect.exe
There is a inspect from inside BDRB in the Logs of my last post.

So to prevent further confusion....
[02.15.14] Checking System Settings
- BD-Rebuilder v0.46.11 (beta)
- Windows Version: 6.2 [9200]
- AVISYNTH Version: 2.6.0.3, not recommended version
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set incorrectly: [19]
- FFDSHOW MPEG2 set incorrectly: [19]
- FFDSHOW AVC set incorrectly: [19]
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02.15.14] Systems Settings Check complete


Now it is no problem was related to the fact that BDRD is unable to work with VID_00000 while making a full backup but when making a movie only backup it is obviously no problem since it started to reencode it.

See the Logs in my last post.

[jdobbs]

@RodgerPost the contents of your INI file and I'll run a test.You gave me your log and the contents of the INF file. But I need the INI file to make sure my settings match yours. It is called BDREBUILDER.INI and is located int the same folder as BDRB.EXE. In the meantime I've started a job doing a full backup of RED_2 using DGDecNV.

It also doesn't look like the structure of my disc matches yours... probably because they are different regions.

I notice that you are using the alpha version of AVISYNTH v2.6 -- which is not recommended for BD-RB. But... AVISYNTH isn't involved in the extraction of audio/subs, so I'll ignore that for now.

Do you have a copy of the AUD_00000.META file from the full backup attempt? I'd like to see if it has any anomalies. In fact, it might be useful to compare that file from both of the two attempts.

[jdobbs]

I just completed the backup of RED_2 with no issues. I'll need more information (see previous post) before I can help any more.

[Rodger]

Sorry my bad!
Didn´t read carefully enough I guess :o

You may compare the disc sizes...maybe the different disc releases are already that easy to compare.


All requested files in the new zip.
+ ERROR When BackUp MOVIE ONLY!!!
Reencoding does work but final Muxing gives error!!!
See files / Logs for Info


Since it is globally mentioned...
SHOULD I use DGdeNV or am I better off without it when processing BDs with BDRB?

MY experience is that AVIsynth 2.6.x is faster than 2.5.8 since I can use the MT tweaked version from SEt in other programs.
see here: http://forum.doom9.org/showthread.php?t=148782
+ It has been perfectly stable for me

What´s your opinion on this?



/EDIT: STOP!!! Please wait for me to give further Info via PM before waisting your time (anymore)


/EDIT: I AM SO EMBARRASSED! And so sorry for waisting your time. There is nothing in the whole world you could do but to tell the idiot (me) to check for enough space left on the harddrive.

[jdobbs]

Don't worrry about it. I've done the same thing myself -- even to the point of looking at code before checking my free space.

Have a good day. :)

[Rodger]

Thanks for your kind answer ;)

But please give me your opinion on my two questions:

SHOULD I use DGdeNV or am I better off without it when processing BDs with BDRB?

MY experience is that AVIsynth 2.6.x is faster than 2.5.8 since I can use the MT tweaked version from SEt in other programs.
see here: http://forum.doom9.org/showthread.php?t=148782
+ It has been perfectly stable for me

[Capsbackup]

I was able to repeat it. I also ran the META directly from a command line and it didn't create the files... so I need to find out why it is doing it when BD-RB runs it.

Not a "high priority" bug, more cosmetic! :)
There has never been a doubt about your finding and fixing capabilities. :D ;)

[inge70]

I've noticed it too. But can't seem to find one where they exist now. I assumed it was a bug in TSMUXER, but I'll check to find out. I don't think it hurts anything, but I'll make sure it goes away in the next release.

Can you give me a specific sequence that will cause it?

Have times tested because of the ". Cpli" and ". Mpls" files. If I use tsMuxer v2.6.12 alone (mkv to AVCHD mux) are correct, only one "00000.clpi" and "00000.mpls" created in each folder and NO ".cpli" and ".mpls" without "00000" in the name.
This happens, strangely enough, only with BD_Rebuilder currently. After completion appear "00000.clpi" and ".clpi" in CLIPINF folder. same for "00000.mpls" and ".mpls" in the playlist folder.

Why this is, I can not see from the bd_rebuilder-log and. Inf unfortunately. Everything looks normal there.

[02.15.14] BD Rebuilder v0.46.11 (beta)
[09:13:23] Source: FILME_00000
- Input BD size: 3,12 GB
- Approximate total content: [01:47:27.920]
- Target BD size: 4,36 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:13:23] PHASE ONE, Encoding
- [09:13:23] Processing: VID_00000 (1 of 1)
- [09:13:23] Extracting A/V streams [VID_00000]
- [09:14:04] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 161.198 frames
- Bitrate: 5.156 Kbs
- [09:14:04] Reencoding: VID_00000, Pass 1 of 2
- [09:46:28] Reencoding: VID_00000, Pass 2 of 2
- [11:38:33] Video Encode complete
- [11:38:33] Processing audio tracks
- Track 4352 (ger): Reencoding audio to AC3...
[11:38:55]PHASE ONE complete
[11:38:55]PHASE TWO - Rebuild Started
- [11:38:55] Rebuilding AVCHD file Structure
[11:39:48] - Encode and Rebuild complete
- WORKFILES folder removed.
[11:39:48] JOB: FILME finished.

[Status]
LABEL=FILME
VERSION=v0.46.11 (beta)
SOURCE_SIZE=3346022400
SOURCE_VIDEO_SIZE=3346022400
TARGET_SIZE=4686086144
REDUCTION=1.40049455257681
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;ger;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4686086144
RATE=5156
SPLITS=1
NSIZE=0
FLINK=0
MLINK=0


[02.15.14] Checking System Settings
- BD-Rebuilder v0.46.11 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4515, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02.15.14] Systems Settings Check complete


Maybe the error occurs when BD_rebuilder works with tsMuxeR v2.6.12 together. TsMuxeR solo does not write the additional file.
But now no test completed with tsMuxeR v1.10.6 v2.6.11 or to further isolate the error.

[jdobbs]

Thanks for your kind answer ;)

But please give me your opinion on my two questions:

SHOULD I use DGdeNV or am I better off without it when processing BDs with BDRB?

MY experience is that AVIsynth 2.6.x is faster than 2.5.8 since I can use the MT tweaked version from SEt in other programs.
see here: http://forum.doom9.org/showthread.php?t=148782
+ It has been perfectly stable for meDefinitely 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.

[jdobbs]

Maybe the error occurs when BD_rebuilder works with tsMuxeR v2.6.12 together. TsMuxeR solo does not write the additional file.
But now no test completed with tsMuxeR v1.10.6 v2.6.11 or to further isolate the error.Not a "high priority" bug, more cosmetic! :)
There has never been a doubt about your finding and fixing capabilities. :D ;)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.

[Capsbackup]

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. :D

[Rodger]

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]

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]

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]

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]

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]

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]

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.
http://i60.tinypic.com/10idzzm.gif

[Sharc]

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]

....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]

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]

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]

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 TypeI'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]

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]

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).

[HWK]

speaking of relax, you have earned it :D Perhaps go for dinner with your family as well.

[slvrsrfr]

Make sure you are running AVISYNTH v2.58. v2.6.0 is still in alpha, and if you have it installed it is probably you problem. I have no idea how it's DirectshowSource() interprets pulldown signals.

So, I just wiped my machine and did a fresh install of Window 7 Ultimate 64 bit. All I added on top of that was Avast, Office 2013, Beyond Compare, and Hypersnap.

I then went through your BDRB install steps from page 1 and then tried Season 1 of the Wire again, and The Simpsons Season 2 both 4 DVDs --> 1 BD. Both BDs have sound/video sync issues, however, it is very pronounced on The Simpsons.

jdobbs, The Wire is actually pretty close in terms of syncing. If you could just do me one more favor and check the first episode of season 1 (The target) - go to around the 50 minute mark (it's chapter 6 on my disc) where Bunk and McNulty are in a bar talking about his separation...the sound is about 1-2 seconds behind the video; is yours spot on?

FWIW, here are the batch log, settings ini, inspect log, and sample avs files from The Simpsons season 6 (my Wire files were deleted by the cleanup process).

[omegaman7]

So, I just wiped my machine and did a fresh install of Window 7 Ultimate 64 bit. All I added on top of that was Avast, Office 2013, Beyond Compare, and Hypersnap.

I then went through your BDRB install steps from page 1 and then tried Season 1 of the Wire again, and The Simpsons Season 2 both 4 DVDs --> 1 BD. Both BDs have sound/video sync issues, however, it is very pronounced on The Simpsons.

jdobbs, The Wire is actually pretty close in terms of syncing. If you could just do me one more favor and check the first episode of season 1 (The target) - go to around the 50 minute mark (it's chapter 6 on my disc) where Bunk and McNulty are in a bar talking about his separation...the sound is about 1-2 seconds behind the video; is yours spot on?

FWIW, here are the batch log, settings ini, inspect log, and sample avs files from The Simpsons season 6 (my Wire files were deleted by the cleanup process).

Didn't Jdobbs run a test on that one already(The Wire). I suspect you had a bad rip. Even if the raw/rip plays fine, encoders/rebuilder tools may find errors, where the player may not. I had to retire my ihes108 for this exact reason. It seemed to rip fine, but some encodes came out bad, due to rip/read errors.

[slvrsrfr]

Didn't Jdobbs run a test on that one already(The Wire). I suspect you had a bad rip. Even if the raw/rip plays fine, encoders/rebuilder tools may find errors, where the player may not. I had to retire my ihes108 for this exact reason. It seemed to rip fine, but some encodes came out bad, due to rip/read errors.

He did.

It would be a very strange coincidence if it was a bad rip, b/c every episode has a lag - this was across 4 DVDs. Same thing with The Wire Season 2, and The Simpsons Seasons 2, 3, and 6. 4 DVDs each/season. Further, the source videos are MPEG-2, 720x480, _Hybrid_ files.

I also did The Simpsons seasons 4 and 5 without issue, however, the total source size was < 23500, so there was no video reencoding.

So, that's 20 source DVDs, all with MPEG-2, 720x480, Hybrid files, all of which would need to have been bad rips to support that. But, right before I wiped my machine I reencoded season 4 of The Wire without issue, but these were _not_ hybrid source files. I also did 5 BD to BDs without issue, so I know my burner is OK...

[omegaman7]

I found I had to force encode on those types of sources. Don't ask me why, but it corrected Sync issues I had.

[slvrsrfr]

I found I had to force encode on those types of sources. Don't ask me why, but it corrected Sync issues I had.

I'm not sure that I follow you. These were all reencoded, except for seasons 4 and 5 of the Simpsons, which were fine.

So you set it to force encode, even when it already was encoding, to deal with hybrid mpeg2 file video/audio sync issues?

[jdobbs]

So, I just wiped my machine and did a fresh install of Window 7 Ultimate 64 bit. All I added on top of that was Avast, Office 2013, Beyond Compare, and Hypersnap.

I then went through your BDRB install steps from page 1 and then tried Season 1 of the Wire again, and The Simpsons Season 2 both 4 DVDs --> 1 BD. Both BDs have sound/video sync issues, however, it is very pronounced on The Simpsons.

jdobbs, The Wire is actually pretty close in terms of syncing. If you could just do me one more favor and check the first episode of season 1 (The target) - go to around the 50 minute mark (it's chapter 6 on my disc) where Bunk and McNulty are in a bar talking about his separation...the sound is about 1-2 seconds behind the video; is yours spot on?

FWIW, here are the batch log, settings ini, inspect log, and sample avs files from The Simpsons season 6 (my Wire files were deleted by the cleanup process).I'm running it again. One thing I meant to ask you... you mentioned that your Season 1 Collection had 4 discs consisting of 13 episodes. The one I have is 5 discs (13 episodes). I assumed it was a typo. My episodes were flagged as "Hybrid" just like yours.

[omegaman7]

I'm simply saying, that when rebuilder did not encode, there was a problem. By forcing, it corrected my issue. Thankfully, I rarely work with 480p/i sources :S

[slvrsrfr]

I'm running it again. One thing I meant to ask you... you mentioned that your Season 1 Collection had 4 discs consisting of 13 episodes. The one I have is 5 discs (13 episodes). I assumed it was a typo. My episodes were flagged as "Hybrid" just like yours.

Actually, it was a typo, sorry. There are 5 DVDs. The other series were all 4 (so, 21 bad DVD rips.....?)

Thanks for doing me this favor! :)

I'm simply saying, that when rebuilder did not encode, there was a problem. By forcing, it corrected my issue. Thankfully, I rarely work with 480p/i sources :S

This is the opposite of what I am experiencing.

[jdobbs]

I'm simply saying, that when rebuilder did not encode, there was a problem. By forcing, it corrected my issue. Thankfully, I rarely work with 480p/i sources :SThere are some issues with TSMUXER multiplexing sources with pulldown. I should probably disable the "USE_ORIGINAL" mode when it encounters them. I think some people see the issue and others don't depending upon the player.

@slvrsrfr

I don't remember if I asked this before... what player are you using?