BD Rebuilder Beta - Bug Reports Only

[Sharc]

v0.24.04 / full backup including secondary video on BD-5 / resize 720 / audio re-encoded to AC3 448 / 1-pass CRF.

Everything perfect and the quality is amazingly good, but final size was 4.74 GB which exceeds the disc capacity of the DVD5 by about 8%. I am aware of the sizing risk with 1-pass, so it's probably not a bug. Just wondering a little about the +8% oversize, because previous backups ended up at perfect 96 .... 98% of the disc capacity.

[Groucho2004]

Yeah. It's a problem I've been working on for a long time. Occasionally when BD-RB tries to find the X264 window (to get the handle so it can update its display) the operating system just doesn't seem to return it -- even though it is running.

How do you try to get the window handle? FindWindow()?

I wrote a couple of programs that retrieve the window handle from a console window. I use EnumWindows() periodically to enumerate all windows and have a callback function (EnumWindowsProc()) that checks the properties of the windows (GetWindowText(), for example). This never failed to retrieve the window handle I need.

You may already do it the same way but if not you might give it a try...

[shamoo]

It can affect the output and cause unknown errors. BD-RB is meant to used on an unaltered Retail Disc that was ripped to the hard drive for backup of retail owned Bluray, not for piracy.

I backed up again using the original folder and it worked, although the folder is 50gb, let me explain,.. in the iron-man folder there are 2 folders, "workfiles" & "iron-man" in workfiles there is 36gb of stuff in there and in the iron-man folder is the BDMV & CERTIFICATE folders, why is it putting a workfiles folder in it and can i delete it?

also thanks for your help :D

[jdobbs]

How do you try to get the window handle? FindWindow()?

I wrote a couple of programs that retrieve the window handle from a console window. I use EnumWindows() periodically to enumerate all windows and have a callback function (EnumWindowsProc()) that checks the properties of the windows (GetWindowText(), for example). This never failed to retrieve the window handle I need.

You may already do it the same way but if not you might give it a try... Thanks for the tip. Yes, I'm using FindWindow(). I'll switch over to EnumWindow() and see if that serves me better. Much appreciated.

[jdobbs]

v0.24.04 / full backup including secondary video on BD-5 / resize 720 / audio re-encoded to AC3 448 / 1-pass CRF.

Everything perfect and the quality is amazingly good, but final size was 4.74 GB which exceeds the disc capacity of the DVD5 by about 8%. I am aware of the sizing risk with 1-pass, so it's probably not a bug. Just wondering a little about the +8% oversize, because previous backups ended up at perfect 96 .... 98% of the disc capacity. I assume you meant v0.28.4. Yes, I've noticed that the sizing has started going over as well with one pass CRF. The same thing happened to me on an encode recently. I think it is related to the recent change I added to prevent the looping, but I'm not sure. I'm looking at it to see why that would do it. Odd for sure, that something like that could cause an oversize -- but since it started happening right afterwards, the chances are high that it is related.

[jdobbs]

I backed up again using the original folder and it worked, although the folder is 50gb, let me explain,.. in the iron-man folder there are 2 folders, "workfiles" & "iron-man" in workfiles there is 36gb of stuff in there and in the iron-man folder is the BDMV & CERTIFICATE folders, why is it putting a workfiles folder in it and can i delete it?

also thanks for your help :D Workfiles is where BD-RB does all it's extracting, encoding, converting, etc. The other (in this case IRON-MAN) folder is the actual output that is meant to be written to disc. You can delete the WORKFILES folder, but not until the rebuild is complete. The reason BD-Rebuilder doesn't delete it automatically is so if something goes wrong, expert users can manually make corrections and continue without having to start from scratch.

At some point, when everything is working more reliably I'll probably make automatic removal of the WORKING folder the default. For right now you can go into the SETUP dialog and click on "Remove WORKFILES after Rebuild" and it will do so.

[pbeumer2001]

Hi all,

I have tried a movie only back up of `The Siege` to BD-25. In order to get a maximum bit rate I wanted to get as close as possible to the BD-25 maximum size of 23.2 GB.

Therefore I have set the target to 24.41 GB and even to 29.39 GB with different versions and speed settings:

20:50:24] BD Rebuilder v0.28.04 (beta)
- Source: AUSNAHME_DT
- Input BD size: 29,73 GB
- Approximate total content: [01:56:05.823]
- Target BD size: 24,41 GB

-----------------------
[21:40:43] BD Rebuilder v0.26.01 (beta)
- Source: AUSNAHME_DT
- Input BD size: 29,73 GB
- Approximate total content: [01:56:05.823]
- Target BD size: 29,39 GB


But no matter what I have tried, the maximum output size was no more than 21.9 GB, still a waste of 1.3 GB.

Is there anything I can do to increase the output size?

Is it because the maximum bit rate is limited?
(The original bit rate of the movie is around 34500 kbps)



Thanks.

Are you sure it`s encoding? Seems like it`s not necessary to encode and that the main movie file stays intact.

[jdobbs]

Are you sure it`s encoding? Seems like it`s not necessary to encode and that the main movie file stays intact. Hah! Good point. I should have noticed that. It has nothing to do with saturation -- it's staying the same size because it doesn't need to reencode and isn't doing so. There's no "wasted space" when you keep the original -- because no reencode is ever better than the original (ignoring filtering for cleanup).

@hudsucker
If you're determined to fill the disc at the expense of quality, you should be able to add:

FORCE_ENCODE=1

to the "[Options]" are of the INI and BD-RB will reencode anyway. I wouldn't recommend it, though.

[MikeyBK]

Wonder if anyone is having some chapter navigation issues when using the batch encoding? v0.28.04

I set up three BDs to BD-9, movie only.... and only the first one runs properly. The second jumps back to the beginning of the movie when trying to jump to next chapter, and the third doesn't do anything when pressing to jump forward. Both jumps backwards to the beginning like normal.

-----------------------
[23:45:18] PROCESSING BATCH FILE [1]
-----------------------
[23:45:18] BD Rebuilder v0.28.04 (beta)
- Source: ADVENTURELAND
- Input BD size: 29.65 GB
- Approximate total content: [01:46:54.866]
- Target BD size: 8.15 GB
- MOVIE-ONLY mode enabled
[23:45:18] PHASE ONE, Encoding
- [23:45:18] Extracting A/V streams [VID_00069]
- [23:52:49] Reencoding: VID_00069 (1 of 1)
[04:36:08]PHASE ONE complete
[04:36:08]PHASE TWO - Rebuild Started
- [04:36:08] Rebuilding BD file Structure
[04:41:04] - Encode and Rebuild complete
[04:41:04]JOB: ADVENTURELAND finished.
-----------------------
[04:41:04] PROCESSING BATCH FILE [2]
-----------------------
[04:41:06] BD Rebuilder v0.28.04 (beta)
- Source: DUPLICITY
- Input BD size: 21.90 GB
- Approximate total content: [02:05:02.494]
- Target BD size: 8.15 GB
- MOVIE-ONLY mode enabled
[04:41:06] PHASE ONE, Encoding
- [04:41:06] Extracting A/V streams [VID_00010]
- [04:47:51] Reencoding: VID_00010 (1 of 1)
[10:03:52]PHASE ONE complete
[10:03:52]PHASE TWO - Rebuild Started
- [10:03:52] Rebuilding BD file Structure
[10:08:57] - Encode and Rebuild complete
[10:08:57]JOB: DUPLICITY finished.
-----------------------
[10:08:57] PROCESSING BATCH FILE [3]
-----------------------
[10:08:59] BD Rebuilder v0.28.04 (beta)
- Source: FIGHTING
- Input BD size: 21.51 GB
- Approximate total content: [01:44:56.707]
- Target BD size: 8.15 GB
- MOVIE-ONLY mode enabled
[10:08:59] PHASE ONE, Encoding
- [10:08:59] Extracting A/V streams [VID_00082]
- [10:15:11] Reencoding: VID_00082 (1 of 1)
[15:07:41]PHASE ONE complete
[15:07:41]PHASE TWO - Rebuild Started
- [15:07:41] Rebuilding BD file Structure
[15:12:44] - Encode and Rebuild complete
[15:12:44]JOB: FIGHTING finished.
==========================
[15:12:44] END - BATCH SEQUENCE
==========================

[Status]
LABEL=ADVENTURELAND
VERSION=v0.28.04 (beta)
SOURCE_SIZE=31840014336
SOURCE_VIDEO_SIZE=31840014336
TARGET_SIZE=8755609600
REDUCTION=.274987614879948
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00069]
AUDIO=10000
PGS=1000000000000000000
M2TS_TARGET=8755609600
RATE=9394
NSIZE=7868467200
FLINK=0
MLINK=0


[Status]
LABEL=DUPLICITY
VERSION=v0.28.04 (beta)
SOURCE_SIZE=23518513152
SOURCE_VIDEO_SIZE=23518513152
TARGET_SIZE=8755609600
REDUCTION=.372285847468866
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00010]
AUDIO=1000
PGS=10000
M2TS_TARGET=8755609600
RATE=7911
NSIZE=7795052544
FLINK=0
MLINK=0


[Status]
LABEL=FIGHTING
VERSION=v0.28.04 (beta)
SOURCE_SIZE=23098546176
SOURCE_VIDEO_SIZE=23098546176
TARGET_SIZE=8755609600
REDUCTION=.379054574832823
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00082]
AUDIO=100
PGS=10000
M2TS_TARGET=8755609600
RATE=9578
NSIZE=7908446208
FLINK=0
MLINK=0

[MikeyBK]

Actually, it might be an issue with the version and not just the Batch encoding. I actually redid Fighting because I did the theatrical version with the batch process, but the unrated version which I did seperately also has the same chapter jumping issue... press to jump forward and it returns to the beginning of the movie instead.

[worknstiff]

Hi Mikey, I had the same problem with a couple of movie only BDRB backups to BD9. The two movies I had that would either freeze up or go back to the start would also not fast forward. Both of the movies had mutiple .mpls files and somehow that messes with the original chapter locations. (I think) As a solution someone told me to use Clown BD and have it rebuild the .mpls into one large .mpls and use BD_Rebuilder on it instead of the original rip. That fixed the one movie (12 Rounds) but not Watchman. Still can't figure it out. BTW is your player a Panasonic? Mine is an old BD-30. and plays all BDRB BD-9 movies except those two. I did try them on a couple of Sony's but it did the same freeze up.

[setarip_old]

@worknstiff

Hi!

If you're willing to do something a bit differently, in order to get a successful movie-only of "Watchmen", try the following:

1) Use "MakeMKV" (Do NOT use "AnyDVDHD" with it) to both rip the original BluRay disc and convert it to an MKV

2) Load the MKV into "tsMuxeR" and save as "BluRay"

3) Load this NEW BluRay "package" into BD-RB and process as "Movie-only" - Yes, you'll have correct chaptering ;>}

[MikeyBK]

Hi Mikey, I had the same problem with a couple of movie only BDRB backups to BD9. The two movies I had that would either freeze up or go back to the start would also not fast forward. Both of the movies had mutiple .mpls files and somehow that messes with the original chapter locations. (I think) As a solution someone told me to use Clown BD and have it rebuild the .mpls into one large .mpls and use BD_Rebuilder on it instead of the original rip. That fixed the one movie (12 Rounds) but not Watchman. Still can't figure it out. BTW is your player a Panasonic? Mine is an old BD-30. and plays all BDRB BD-9 movies except those two. I did try them on a couple of Sony's but it did the same freeze up.

Well first, as you can see in my posted logs, they are all single m2ts file movie-onlys.
And this chapter navigation issue only surfaced with this latest version of BD-RB, both when played from the HDD with Arcsoft TMT player or from BD-9 disc on my Sony BDP-BX1.

I'm certain this is related to the rebuild stage, and due to it being VC-1. But will wait for JD to inject his thoughts.+

Oh BTW... I had no issues whatsoever with Watchmen..


[23:51:15] BD Rebuilder v0.25.04 (beta)
- Source: WATCHMEN
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Target BD size: 8.15 GB
- MOVIE-ONLY mode enabled
[23:51:15] PHASE ONE, Encoding
- [23:51:15] Extracting A/V streams [VID_00500]
- [23:58:07] Reencoding: VID_00500 (1 of 25)
- [00:03:13] Extracting A/V streams [VID_00501]
- [00:03:14] Reencoding: VID_00501 (2 of 25)
- [00:04:31] Extracting A/V streams [VID_00502]
- [00:04:37] Reencoding: VID_00502 (3 of 25)
- [00:07:50] Extracting A/V streams [VID_00503]
- [00:07:57] Reencoding: VID_00503 (4 of 25)
- [00:13:10] Extracting A/V streams [VID_00504]
- [00:13:43] Reencoding: VID_00504 (5 of 25)
- [00:38:44] Extracting A/V streams [VID_00505]
- [00:38:50] Reencoding: VID_00505 (6 of 25)
- [00:43:36] Extracting A/V streams [VID_00506]
- [00:44:26] Reencoding: VID_00506 (7 of 25)
- [01:22:03] Extracting A/V streams [VID_00507]
- [01:22:09] Reencoding: VID_00507 (8 of 25)
- [01:26:25] Extracting A/V streams [VID_00508]
- [01:26:38] Reencoding: VID_00508 (9 of 25)
- [01:35:08] Extracting A/V streams [VID_00509]
- [01:35:12] Reencoding: VID_00509 (10 of 25)
- [01:38:27] Extracting A/V streams [VID_00510]
- [01:38:36] Reencoding: VID_00510 (11 of 25)
- [01:45:14] Extracting A/V streams [VID_00511]
- [01:45:20] Reencoding: VID_00511 (12 of 25)
- [01:50:01] Extracting A/V streams [VID_00512]
- [01:50:54] Reencoding: VID_00512 (13 of 25)
- [02:30:48] Extracting A/V streams [VID_00513]
- [02:30:54] Reencoding: VID_00513 (14 of 25)
- [02:34:24] Extracting A/V streams [VID_00514]
- [02:35:35] Reencoding: VID_00514 (15 of 25)
- [03:27:58] Extracting A/V streams [VID_00515]
- [03:28:06] Reencoding: VID_00515 (16 of 25)
- [03:34:11] Extracting A/V streams [VID_00516]
- [03:34:56] Reencoding: VID_00516 (17 of 25)
- [04:06:06] Extracting A/V streams [VID_00517]
- [04:06:12] Reencoding: VID_00517 (18 of 25)
- [04:11:11] Extracting A/V streams [VID_00518]
- [04:11:42] Reencoding: VID_00518 (19 of 25)
- [04:33:33] Extracting A/V streams [VID_00519]
- [04:33:39] Reencoding: VID_00519 (20 of 25)
- [04:38:44] Extracting A/V streams [VID_00520]
- [04:38:53] Reencoding: VID_00520 (21 of 25)
- [04:45:09] Extracting A/V streams [VID_00521]
- [04:45:16] Reencoding: VID_00521 (22 of 25)
- [04:49:29] Extracting A/V streams [VID_00522]
- [04:50:01] Reencoding: VID_00522 (23 of 25)
- [05:16:17] Extracting A/V streams [VID_00523]
- [05:16:25] Reencoding: VID_00523 (24 of 25)
- [05:23:05] Extracting A/V streams [VID_00524]
- [05:23:06] Reencoding: VID_00524 (25 of 25)
[05:23:08]PHASE ONE complete
[05:23:08]PHASE TWO - Rebuild Started
- [05:23:08] Rebuilding BD file Structure
[05:31:27] - Encode and Rebuild complete
[05:31:27]JOB: WATCHMEN finished.

[jdobbs]

I don't think it has anything to do with the BD-RB version... but I can say that I have the same problem with Watchmen (Region A) and I'm still trying to figure it out. I can do a complete backup and there are no issues, but if I do a movie-only, it will play fine as long as you don't jump chapters, but if you go a couple of chapter jumps into the film it locks and you only get sound.

I'm pretty sure it is a TSMUXER issue. Because the only thing I could imagine that would cause that is the CLPI file. If you look at the .META file used for muxing it looks correctly structured to me (but very long with lots of combined parts). I even removed the chaptering and used 5 minute defaults with no joy. On movie-only rebuilding, the TSMUXER output isn't modified after completion.

@MikeyBK

If it worked for you, can you send me your settings? Maybe it has something to do with audio or subs kept...

[MikeyBK]

I don't think it has anything to do with the BD-RB version... but I can say that I have the same problem with Watchmen (Region A) and I'm still trying to figure it out. I can do a complete backup and there are no issues, but if I do a movie-only, it will play fine as long as you don't jump chapters, but if you go a couple of chapter jumps into the film it locks and you only get sound.

I'm pretty sure it is a TSMUXER issue. Because the only thing I could imagine that would cause that is the CLPI file. If you look at the .META file used for muxing it looks correctly structured to me (but very long with lots of combined parts). I even removed the chaptering and used 5 minute defaults with no joy. On movie-only rebuilding, the TSMUXER output isn't modified after completion.

@MikeyBK

If it worked for you, can you send me your settings? Maybe it has something to do with audio or subs kept...

For Watchmen I didn't save the inf, I had it set to output custom BD-9 size of 8350 MBs, Keeping only one English audio and one PGS, also selecting an alternative movie-only playlist. High Quality setting but I'm sure that had nothing to do with it. Also did not resize.
Seems TSMuxer is having some issues with certain BDs on the rebuild, and especially I guess with alternative movie-only playlist or multi-m2ts movies.

[Capsbackup]

The first time I tried Watchmen, I also experienced this. However, I tried it again, but first ran the original rip thru ClownBD, letting it strip the unnecessary audio and subtitle tracks, and creating a new Blu-Ray with one .m2ts ( Of course, movie only ). I'm not sure why, but this new Blu-Ray was selected as my source with BD-RB, and after BD-RB reencoded to BD-9, the outcome came out perfect, no more video stopping but audio still playing. Chapter advance worked, both forward and backward.
So I'm not sure what ClownBD, along with eac3to and tsMuxeR, does differently that BD-RD does on its own, but the outcome did work this way and not with BD-RB all by itself.
I know this is considered preprocessing, and I normally will not preprocess my movies unless there is an issue like this. ( which has been rare )
I am NOT recommending this procedure, but did want to share my experience and results with this movie.
I have tried eac3to on occasion, and it does seem to be an excellent program, very usefull at times. However, I do not know if this is the reason I was successful with backing up Watchmen. Maybe the second time thru tsMuxeR, once with ClownBD/eac3to and then again with BD-RB, had something to do with it. :confused:

[Sharc]

..... I have tried eac3to on occasion, and it does seem to be an excellent program, very usefull at times. However, I do not know if this is the reason I was successful with backing up Watchmen. Maybe the second time thru tsMuxeR, once with ClownBD/eac3to and then again with BD-RB, had something to do with it. :confused:
Just to add: I had an issue with BD-RB producing audio/video out of sync (movie only) in one case. Using eac3to for the demuxing and for audio conversion solved it.

[MikeyBK]

I've run the movie only m2ts from Fighting through TSMuxer version that is in BD-RB v0.28.04, and will run the resulting Bluray files thru BD-RB tonite... will see if that makes a difference with the chapter navigational issue on this title.

Couple more tests I ran... I ran the BD-9 files that was output from BD-RB and was having navigational issues, thru TSMuxer (both an older version of TSMuxer and the version in BD-RB v0.28.04), and both resulting BD-9 files have proper chapter jumping capabilities now.
I also checked the files that I ran thru TSMuxer (two versions again), directly from the full Bluray itself, to a movie-only 20 GB Bluray... and they both chapter navigate properly.

Not sure if any of this info helps, but wonder if something else is causing the issue somewhere between x264 and TSMuxer?

[worknstiff]

Not sure if this is helpful or not but when I did Watchman all the rips and reencodes that I tried would play great on computer but it was only after burning to disk and playing on my BD-30 that I had problems.

[DK]

I'm having the same "jump forward" issues with BD-9 - the picture freezes, sounds come out normal.

Will any log or inf help?

++++

Not sure if this is helpful or not but when I did Watchman all the rips and reencodes that I tried would play great on computer but it was only after burning to disk and playing on my BD-30 that I had problems.

Similar here: playing the title from HDD AND from DVD-DL with TMT3 the picture does NOT freeze.

[hudsucker]

Are you sure it`s encoding? Seems like it`s not necessary to encode and that the main movie file stays intact.


Hah! Good point. I should have noticed that. It has nothing to do with saturation -- it's staying the same size because it doesn't need to reencode and isn't doing so. There's no "wasted space" when you keep the original -- because no reencode is ever better than the original (ignoring filtering for cleanup).

@hudsucker
If you're determined to fill the disc at the expense of quality, you should be able to add:

FORCE_ENCODE=1

to the "[Options]" are of the INI and BD-RB will reencode anyway. I wouldn't recommend it, though.


Yes, I´m sure it went through the encoding process.

I should have mentioned that I always use TsMuxer before to check if the movie fits to BD-25 without encoding.

So the input size of 29.43 GB is the size of the movie with german audio only. I simply was surprised that the smallest reduction in size with best quality settings has always been below the BD-25 size of 23.2 GB. If it is because of `encoder saturation` of x264 it is ok because I know I will have the best possible quality. I just wanted to be sure to have not wasted any bit rate improvement. I use a projector with 100" screen size for viewing, so a maximum of quality is all I want on my BD-25.

Anyway, thanks for your comments, very much appreciated.

(Now I might add english audio to BD-25 without loss of video quality to fill up the disc to the maximum of 23.2GB)

[jdobbs]

I've run the movie only m2ts from Fighting through TSMuxer version that is in BD-RB v0.28.04, and will run the resulting Bluray files thru BD-RB tonite... will see if that makes a difference with the chapter navigational issue on this title.

Couple more tests I ran... I ran the BD-9 files that was output from BD-RB and was having navigational issues, thru TSMuxer (both an older version of TSMuxer and the version in BD-RB v0.28.04), and both resulting BD-9 files have proper chapter jumping capabilities now.
I also checked the files that I ran thru TSMuxer (two versions again), directly from the full Bluray itself, to a movie-only 20 GB Bluray... and they both chapter navigate properly.

Not sure if any of this info helps, but wonder if something else is causing the issue somewhere between x264 and TSMuxer?Can you send me the .META files from each of the two muxes (the one from BD-RB and from TSMUXER)? Obviously there is some difference and if I can see what it is I can fix it.

[jdobbs]

Yes, I´m sure it went through the encoding process.

I should have mentioned that I always use TsMuxer before to check if the movie fits to BD-25 without encoding.

So the input size of 29.43 GB is the size of the movie with german audio only. I simply was surprised that the smallest reduction in size with best quality settings has always been below the BD-25 size of 23.2 GB. If it is because of `encoder saturation` of x264 it is ok because I know I will have the best possible quality. I just wanted to be sure to have not wasted any bit rate improvement. I use a projector with 100" screen size for viewing, so a maximum of quality is all I want on my BD-25.

Anyway, thanks for your comments, very much appreciated.

(Now I might add english audio to BD-25 without loss of video quality to fill up the disc to the maximum of 23.2GB) So you're saying the source was preprocessed? Please, please, please don't use preprocessed sources with BD-RB. I can't guarantee anything nor can I accept bug reports on sources that have been "adjusted" before it gets to BD-RB. I have no idea what could have happened in the preprocessing, and a lot of people (not necessarily you) think they know a lot more about the standard than they really do. What I CAN be sure of is that TSMUXER can create a non-compliant source because it is powerful and lets people do whatever they want.

If you try TSMUXER first, that's fine... but if it doesn't fit -- don't use the TSMUXER output for BD-RB, point BD-RB to the original.

[jdobbs]

I've run the movie only m2ts from Fighting through TSMuxer version that is in BD-RB v0.28.04, and will run the resulting Bluray files thru BD-RB tonite... will see if that makes a difference with the chapter navigational issue on this title.

Couple more tests I ran... I ran the BD-9 files that was output from BD-RB and was having navigational issues, thru TSMuxer (both an older version of TSMuxer and the version in BD-RB v0.28.04), and both resulting BD-9 files have proper chapter jumping capabilities now.
I also checked the files that I ran thru TSMuxer (two versions again), directly from the full Bluray itself, to a movie-only 20 GB Bluray... and they both chapter navigate properly.

Not sure if any of this info helps, but wonder if something else is causing the issue somewhere between x264 and TSMuxer? I'm going to run WATCHMEN again today. I'll then try manually linking all the files through TSMUXER and see if I get a good result. If it works, then obviously BD-RB is doing something wrong.

[SuSELinux]

Hello,

it's some time ago i reencode some BD's. So i updated to version 28.04. I reencode 3 movies (movie only) in the batch Queue. All with german audio and german subtitles selected.
But all three movies have NO audio and NO subtitles. Have this anything to do with batch? I never had this problem before. (First time i use batch with the new version)

Anyone have a idea? Or did i something wrong?

Thanks!

[MikeyBK]

Can you send me the .META files from each of the two muxes (the one from BD-RB and from TSMUXER)? Obviously there is some difference and if I can see what it is I can fix it.

I'm going to run WATCHMEN again today. I'll then try manually linking all the files through TSMUXER and see if I get a good result. If it works, then obviously BD-RB is doing something wrong.

I don't have the Meta files from the the Bluray straight thru BD-RB anymore, I erased those workfiles (I'd have to run it again straight from the disc thru BD-RB later tonite)....and the TSMuxer output didn't create one.

But the TSMuxer movie-only output that I ran thru BD-RB last night came out fine with proper chapter navigation. Not sure if that info helps you any.
I'll save the meta from this TSMuxere-to-BD-RB job, and I'll run it straight from the Bluray again, then send you both sets of Meta files.... from the work folders right?

[Capsbackup]

I don't think it has anything to do with the BD-RB version... but I can say that I have the same problem with Watchmen (Region A) and I'm still trying to figure it out. I can do a complete backup and there are no issues, but if I do a movie-only, it will play fine as long as you don't jump chapters, but if you go a couple of chapter jumps into the film it locks and you only get sound.

I'm pretty sure it is a TSMUXER issue. Because the only thing I could imagine that would cause that is the CLPI file. If you look at the .META file used for muxing it looks correctly structured to me (but very long with lots of combined parts). I even removed the chaptering and used 5 minute defaults with no joy. On movie-only rebuilding, the TSMUXER output isn't modified after completion.

If the resulting files from the output from ClownBD, which uses tsMuxeR for the output of the new Blu-Ray, could be of benefit to you, I will run it again and provide it for you ( or you may wish to run it yourself to control the parameters better ).
The tsMuxeR version used with ClownBD is also 1.10.6.
This step did seem to correct the chapter advance issue.

[MikeyBK]

If the resulting files from the output from ClownBD, which uses tsMuxeR for the output of the new Blu-Ray, could be of benefit to you, I will run it again and provide it for you ( or you may wish to run it yourself to control the parameters better ).
The tsMuxeR version used with ClownBD is also 1.10.6.
This step did seem to correct the chapter advance issue.

ClownBD does not need to be involved at all IMHO... I used TSMuxer 1.10.6 on it's own, then ran that output thru BD-RB and it's all good.
Just gotta sort out why TSMuxer 1.10.6 doesn't remux correctly within BD-RB.

[Capsbackup]

ClownBD does not need to be involved at all IMHO... I used TSMuxer 1.10.6 on it's own, then ran that output thru BD-RB and it's all good.
Just gotta sort out why TSMuxer 1.10.6 doesn't remux correctly within BD-RB.

That is possible, but I did not try it that way. Besides, ClownBD also uses eac3to, so I wanted that known too, just in case jdobbs wants an additional way to test the output, in the outside chance the results were different.
I really hate even reporting to preprocessing, since I know the potential problems that can bring! But for this instance, and movie, this is what I did to make it work.
So the info is there, be it of value or not.
My intentions are not for jdobbs to spend any additional time on this method, but to disclose what seemed to work for this movie, and if there could be a discovery of some benefit to BD-RB, we all will benefit too. ;)

[jdobbs]

ClownBD does not need to be involved at all IMHO... I used TSMuxer 1.10.6 on it's own, then ran that output thru BD-RB and it's all good.
Just gotta sort out why TSMuxer 1.10.6 doesn't remux correctly within BD-RB. I just used TSMUXER on its own and it showed the exact same problem. I'm now burning in Blu-Ray format rather than AVCHD to see if that make a difference. Next I will use .264 files instead of MKV. Then I will try encoding using something other than "Fastest". Eventually I will find what TSMUXER is tripping over.

As I said earlier, BD-RB doesn't build the CLPI file for movie-only, it uses what is created by TSMUXER. In this case the problem has to be TSMUXER. All the fast-forwarding and chapter jumping is handled via tables in the CLPI. I'm looking for a workaround -- but I want to be clear... it HAS TO BE TSMUXER or it wouldn't happen when I take BD-RB out of the picture. Period, end of story, fact, absolute, no doubt, concrete, solid, positive, no room for debate.

The reason the ClownBD version worked is probably because it was combined (not building from multiple sources) when fed to BD-RB. You could probably do the same thing by running BD-RB twice on the same source, do movie-only and then use the movie-only output as source and do it again (I haven't tried it, but at some point I'm sure I will).

I'll work it out.

[MikeyBK]

I just used TSMUXER on its own and it showed the exact same problem. I'm now burning in Blu-Ray format rather than AVCHD to see if that make a difference. Next I will use .264 files instead of MKV. Then I will try encoding using something other than "Fastest". Eventually I will find what TSMUXER is tripping over.

As I said earlier, BD-RB doesn't build the CLPI file for movie-only, it uses what is created by TSMUXER. In this case the problem has to be TSMUXER. All the fast-forwarding and chapter jumping is handled via tables in the CLPI. I'm looking for a workaround -- but I want to be clear... it HAS TO BE TSMUXER or it wouldn't happen when I take BD-RB out of the picture. Period, end of story, fact, absolute, no doubt, concrete, solid, positive, no room for debate.

The reason the ClownBD version worked is probably because it was combined (not building from multiple sources) when fed to BD-RB. You could probably do the same thing by running BD-RB twice on the same source, do movie-only and then use the movie-only output as source and do it again (I haven't tried it, but at some point I'm sure I will).

I'll work it out.

One question about something else I kinda noticed... would the size of the playlist .mpls file have any impact on the chapter navigation? The reason I'm asking is that, from the two BD-9s I created... the first from the Bluray itself, and the second from the TSMuxered movie-only source.... the only difference is the size of the mpls file. Everything else seems exactly the same.
In fact, the other movie that I just experienced the issue out of the three, Dup[licity, also has a smaller than normal mpls file.
The only working movie out of the three, Adventureland, has the normal size mpls file...about 480 bytes. As does the TSMuxered version of Fighting (as has 'all' the other BD-9s I've made in the past with BD-RB), but the problemic copy of Fighting and Duplicity, both have only mpls sizes of 200 bytes or 186 bytes.

Not sure if that has anything to do with the TSMuxer issue, but just thought I'd mention it since it seems to be the only difference from the two BD-9's I made of Fighting, one that works properly and one that doesn't.

[jdobbs]

One question about something else I kinda noticed... would the size of the playlist .mpls file have any impact on the chapter navigation? The reason I'm asking is that, from the two BD-9s I created... the first from the Bluray itself, and the second from the TSMuxered movie-only source.... the only difference is the size of the mpls file. Everything else seems exactly the same.
In fact, the other movie that I just experienced the issue out of the three, Dup[licity, also has a smaller than normal mpls file.
The only working movie out of the three, Adventureland, has the normal size mpls file...about 480 bytes. As does the TSMuxered version of Fighting (as has 'all' the other BD-9s I've made in the past with BD-RB), but the problemic copy of Fighting and Duplicity, both have only mpls sizes of 200 bytes or 186 bytes.

Not sure if that has anything to do with the TSMuxer issue, but just thought I'd mention it since it seems to be the only difference from the two BD-9's I made of Fighting, one that works properly and one that doesn't. The MPLS does contain the PlayListMark table which defines at what point the chapters start (in terms of time) -- but the specific offset into the M2TS is stored in the CLPI. I also can't think of anything in the MPLS that would be related to FF/RW -- that's also in the CLPI.

Your MPLS is shorter because you don't have a lot of PlayItems anymore -- in Movie-Only you'll only have one as opposed to the 25 or so you might have in the original. There's all so additional information for the multiple angles in the original "WATCHMEN".

I did a compare of the MPLS and CLPI from the BD-RB directed mux and using TSMUXER alone. They were bit identical.

[MikeyBK]

Well I can confirm that swapping those mpls files had an impact on the respective BD-9s...

I took the 200 byte mpls file from the copy of Fighting that wasn't properly chapter jumping, and put it into the working copies Playlist folder, and now that copy had the same chapter navigation issue...
And the same vice versa... taking the 480 byte mpls from the working copies playlist folder and putting that into the other copies playlist folder in place of the smaller 200 byte mpls file, then made that BD-9 chapter navigate properly..

Hopefully that helps you narrow down what's going wrong with TSMuxer when it processed within BD-RB's call-up commands. Well, at least I hope that helps you some.... I wouldn't know, but thought it might be valuable info for you JD.

[jdobbs]

Well I can confirm that swapping those mpls files had an impact on the respective BD-9s...

I took the 200 byte mpls file from the copy of Fighting that wasn't properly chapter jumping, and put it into the working copies Playlist folder, and now that copy had the same chapter navigation issue...
And the same vice versa... taking the 480 byte mpls from the working copies playlist folder and putting that into the other copies playlist folder in place of the smaller 200 byte mpls file, then made that BD-9 chapter navigate properly..

Hopefully that helps you narrow down what's going wrong with TSMuxer when it processed within BD-RB's call-up commands. Well, at least I hope that helps you some.... I wouldn't know, but thought it might be valuable info for you JD. I wouldn't think you could just swap them -- but I guess if they were the same in every other way... by the way -- the MPLS is created by TSMUXER in Movie-Only mode also.

[MikeyBK]

Would sending you the CLPI and MPLS files of both working and non-working copies help you in any way?

I'll just attach it and you can look if it'd help.

[jdobbs]

Well I can confirm that swapping those mpls files had an impact on the respective BD-9s...

I took the 200 byte mpls file from the copy of Fighting that wasn't properly chapter jumping, and put it into the working copies Playlist folder, and now that copy had the same chapter navigation issue...
And the same vice versa... taking the 480 byte mpls from the working copies playlist folder and putting that into the other copies playlist folder in place of the smaller 200 byte mpls file, then made that BD-9 chapter navigate properly..

Hopefully that helps you narrow down what's going wrong with TSMuxer when it processed within BD-RB's call-up commands. Well, at least I hope that helps you some.... I wouldn't know, but thought it might be valuable info for you JD. I guess I should have checked this out earlier... you can't even jump through the M2TS file of WATCHMENT when playing it back in MPC. Since that doesn't use the CLPI or the MPLS, I guess the problem has to be in the M2TS. Weird.

[jdobbs]

Would sending you the CLPI and MPLS files of both working and non-working copies help you in any way?

I'll just attach it and you can look if it'd help. You never know.

[jdobbs]

@MikeyK

Did you use the "High-Speed Option (BD-25)" when you did "Fighting"?

[MikeyBK]

@MikeyK

Did you use the "High-Speed Option (BD-25)" when you did "Fighting"?

I used the High Quality/ Default setting to BD-9.

[jdobbs]

I used the High Quality/ Default setting to BD-9.Thanks. I found it. When you have multiple MKV intermediate files TSMUXER has problems merging them together into a single M2TS (at least on this disc). If I use the exact same X264 output as a .264 or .M2TS the problem goes away and the disc works fine.

I'll change the next version so it doesn't use MKVs for multipart movie-only multiplexing.

[MikeyBK]

Both Fighting and Duplicity are single m2ts movie-only files.... so didn't have the multipart multiplexing need as Watchmen did.
Not sure why these two Blurays had the issue, but will run Fighting again now, but won't get any results for 4-5 hours from now.... if you need, or I'll just wait til your next version instead.

[jdobbs]

Both Fighting and Duplicity are single m2ts movie-only files.... so didn't have the multipart multiplexing need as Watchmen did.
Not sure why these two Blurays had the issue, but will run Fighting again now, but won't get any results for 4-5 hours from now.... if you need, or I'll just wait til your next version instead. If that's the case, we may be chasing two different problems...

[Capsbackup]

Thanks. I found it. When you have multiple MKV intermediate files TSMUXER has problems merging them together into a single M2TS (at least on this disc). If I use the exact same X264 output as a .264 or .M2TS the problem goes away and the disc works fine.

I'll change the next version so it doesn't use MKVs for multipart movie-only multiplexing.

Good find! I believe I used BD-RB v0.25.04 on Watchmen when I experienced this problem. Was that version similar to this latest version regarding multiple MKV intermediate files?
I did a BD5 backup of Duplicity and it worked perfectly, no issues with this movie. FF/RW and chapter advance works fine.

[MikeyBK]

Good find! I believe I used BD-RB v0.25.04 on Watchmen when I experienced this problem. Was that version similar to this latest version regarding multiple MKV intermediate files?
I did a BD5 backup of Duplicity and it worked perfectly, no issues with this movie. FF/RW and chapter advance works fine.

US Region? Also how many bytes is your MPLS file (of the BD-5)? Could you ZIP up that mpls file from your BD-5 of Duplicity and I can test it with my BD-9?

I'm currently running Fighting again, just to save the working files from it.

[MikeyBK]

If that's the case, we may be chasing two different problems...

Possible, I'm not experiencing any stalling, just that the chapter forward command returns the movie back to the beginning on Fighting, and chapter foward does nothing on Duplicity.

[Capsbackup]

US Region? Also how many bytes is your MPLS file (of the BD-5)? Could you ZIP up that mpls file from your BD-5 of Duplicity and I can test it with my BD-9?

I'm currently running Fighting again, just to save the working files from it.

US Region A.
452 bytes

[MikeyBK]

US Region A.
452 bytes

Thanks Bro, my mpls file was only 186 bytes (200 bytes for the non-working Fighting). All the other outputs from BD-RB (all versions) has mpls files in that 450+ byte range... so I think that may have something to do with why these two BD-9s are having problems with chapter navigation.

[MikeyBK]

I just re-did Fighting again, but this time it cam out fine...with the mpls file being 466 bytes. This title does have 4 separate play lists, two for theatrical and two for extended.. I think I selected the different extended playlist than the one that didn't chapter jump correctly...

Strange... but I hope what you found in Watchmen will correct whatever was going wrong with my two... thanks JD....

[DaMacFunkin]

I havn't had a bug to report for a while ;-) ... but region b of 50 dead men walking has a bug with latest version, during full back up to BD25, some of the extras work fine, but some only play back with sound, no picture. I'm not sure what other info you need dudes so let me know.
Thanks.

[drmih]

I havn't had a bug to report for a while ;-) ... but region b of 50 dead men walking has a bug with latest version, during full back up to BD25, some of the extras work fine, but some only play back with sound, no picture. I'm not sure what other info you need dudes so let me know.
Thanks.

Are they actually blanked? There is a setting to treat field based sources via mkvmerge but if this is not the default then any sources will be blanked.