BD Rebuilder Beta - Bug Reports Only

[laserfan]

Originally Posted by jdobbs

I use the "ancient" version of TSMUXER because all the new ones introduce new bugs -- including crashes. I'll stay "ancient" because it works...

I've used 1.8.8 mostly, but every newer one as well, and they have never ever "crashed" or otherwise caused any problems whatsoever, except of course for the "chapter landing" issue that fixclpi helps to resolve for me.

But, I'm speaking in terms of tsMuxeR.exe standalone, and not in the context BD-RB which I have only tried a handful of times.

[Dark Shikari]

Originally Posted by Atak_Snajpera

25mbps is maximum for high 4.0 profile
62.5mbps is maximum for high 4.1 profile
http://en.wikipedia.org/wiki/H.264#Levels

But Blu-ray has its own restrictions on top of H.264 profiles.

[Atak_Snajpera]

according to this site http://www.blu-ray.com/faq/
max bitrate for blu-ray is 40 mbps but for unknown reason BD-RD uses only 25Mbps

[Dark Shikari]

Originally Posted by Atak_Snajpera

according to this site http://www.blu-ray.com/faq/
max bitrate for blu-ray is 40 mbps but for unknown reason BD-RD uses only 25Mbps

Blu-ray has restrictions beyond that, as well as for BD9/BD5. Check the spec

[Atak_Snajpera]

Blu-ray has restrictions beyond that, as well as for BD9/BD5. Check the spec

Do you really think that movie industry care about those spec?
http://forum.blu-ray.com/showpost.ph...4&postcount=16

[Dark Shikari]

Originally Posted by Atak_Snajpera

Do you really think that movie industry care about those spec?
http://forum.blu-ray.com/showpost.ph...4&postcount=16

And? Just because they don't care about it playing right doesn't mean we shouldn't.

[archie_here]

I tried to compress Few Good Men and the audio extraction worked fine but this is what i got for video. For some reason, my encoding doesn't start. I have the latest ffdshow with all video decoder config set as needed.

-----------------------
[19:59:47] BD Rebuilder v0.20.03 (beta)
- Source: 35990120_FEWGOODMEN
- Input BD size: 36.83 GB
- Approximate total content: [02:18:01.272]
- Target BD size: 4.27 GB
- MOVIE-ONLY mode enabled
- Resuming from previously started job.
[19:59:48] PHASE ONE, Encoding
- [19:59:48] Reencoding: VID_00141 (1 of 1)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[19:59:51] - Failed video encode, aborted

what am i missing?

[m1482]

Originally Posted by Atak_Snajpera

@jdobbs
ftp://213.221.6.90/tsMuxer/
Do we still need fixcpli with .21?

There is also a new TsMuxer 1.8.22 with new gui !!!

[NexGen76]

LOG:


[20:49:27] BD Rebuilder v0.20.03 (beta)
- Source: BANGKOK_DANGEROUS
- Input BD size: 38.48 GB
- Approximate total content: [02:30:50.708]
- Target BD size: 22.90 GB
[20:49:33] PHASE ONE, Encoding
- [20:49:33] Extracting audio/subs [VID_00028]
- [20:49:38] Reencoding: VID_00028 (1 of 11)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[20:49:54] - Failed video encode, aborted


Config:


[Options]
MODE=0
QUICK_EXTRAS=1
PRIORITY_CLASS=0
RESIZE=0
TARGET_SIZE=23450
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
TRELLIS=1
COLOR_BOOST=1
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=1
AC3_640=0
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
[Paths]
SOURCE_PATH=C:\BANG\BANGKOK_DANGEROUS\
WORKING_PATH=C:\BD_RB WORK\

[NexGen76]

Originally Posted by NexGen76

LOG:


[20:49:27] BD Rebuilder v0.20.03 (beta)
- Source: BANGKOK_DANGEROUS
- Input BD size: 38.48 GB
- Approximate total content: [02:30:50.708]
- Target BD size: 22.90 GB
[20:49:33] PHASE ONE, Encoding
- [20:49:33] Extracting audio/subs [VID_00028]
- [20:49:38] Reencoding: VID_00028 (1 of 11)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[20:49:54] - Failed video encode, aborted


Config:


[Options]
MODE=0
QUICK_EXTRAS=1
PRIORITY_CLASS=0
RESIZE=0
TARGET_SIZE=23450
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
TRELLIS=1
COLOR_BOOST=1
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=1
AC3_640=0
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
[Paths]
SOURCE_PATH=C:\BANG\BANGKOK_DANGEROUS\
WORKING_PATH=C:\BD_RB WORK\

Okay i think i have fixed this issue that might have been my fault...I went into ffdshow video decoder & enable mpeg2.Now its working so far....Thxs

[archie_here]

^ mine is already enabled. Still having the same error.

[22:13:37] BD Rebuilder v0.20.03 (beta)
- Source: 35990120_FEWGOODMEN
- Input BD size: 36.83 GB
- Approximate total content: [02:18:01.272]
- Target BD size: 4.27 GB
- MOVIE-ONLY mode enabled
- Resuming from previously started job.
[22:13:38] PHASE ONE, Encoding
- [22:13:38] Reencoding: VID_00141 (1 of 1)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[22:13:41] - Failed video encode, aborted

[Options]
MODE=1
QUICK_EXTRAS=0
PRIORITY_CLASS=1
RESIZE=0
TARGET_SIZE=4369
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=1
AC3_640=0
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
ENCODER=0
VERBOSE_STATUS=0
[Paths]
SOURCE_PATH=E:\FGM\35990120_FEWGOODMEN\
WORKING_PATH=E:\WORKING\

[rmeyers]

Originally Posted by rmeyers

i have found a bug. its on the extended version of King Kong. i dont think anyone has mentioned it yet.

using the latest version, 0.20.02, the extended version doesn't play. at all. might be some sort of rebuilding/bd-structure mishap. theatrical version plays perfectly, as does bd-live. the extended version plays on the orignal rip on my hdd, so do the picture-in-picture extras. but in the bd-rb rip, these dont work. the counter goes to 0:00:00 and stays there. i am playing the bd .iso files in the latest powerdvd 8.

everything on the original rip is progressive VC-1. it is a multiple file playlist. not sure what else i can provide. here are my files. fyi, i did a fast encode, and i had to abort it and resume it.

also, i tried with and without Quick Encode Extras to see if there was a problem there. but the same result. just when it should play the extended movie, it stops working.

i started troubleshooting by looking to see if all the files that are in the original rip are in the shrunken one, which they are. 414 files in both. then i looked into BDedit to see if i could spot some differences to see where the mishap in the structure is. i think i found something. not knowledgeable enough in this stuff to know for sure.

the one on the right is the original rip of the extended edition playlist, the one on the left is the BD-RB rip of the same playlist. as you can see, there are differences in the IN Time and OUT Time of the Playlist and PlaylistMark headings. not sure if they are supposed to be different.

and just for clarification, there are two menus on the BD. one is for the theatrical version, one for the extended version. you can only play the extended version, from the correct main menu. and you can switch back and forth between the theatrical edition menu, and the extended edition menu.

as of right now, i am making another rip, this time including all audio and subtitles to see if it makes any difference.

[Capsbackup]

Looks like the " CorrectMPLS() 00009 5" problem on rebuild was corrected with the new version BD-RBV02003, but a new issue has developed. The burned disc does play, but I now hear a "seeking/cycling" sound from my Sony BDP-BX1 while playing, as if it is struggling to play. So if I try to fast forward the player freezes for several seconds, and if I change chapters, the same happens but then the player does not recover from the still image/freeze. I then have to press stop just to get the player to respond.
This was a full movie backup to BD-5, resize to 720P, default audio re-encode to 448kbps on Nights In Rodanthe.

[jdobbs]

Originally Posted by Atak_Snajpera

according to this site http://www.blu-ray.com/faq/
max bitrate for blu-ray is 40 mbps but for unknown reason BD-RD uses only 25Mbps

I understand it is the maximum for the profile. The limitation isn't really the spec -- but the spin speed of a BD-5/9 disc and the combination of video/audio/PGS/muxing overhead. You should be right on the edge, and if a couple of HD audio streams are kept, you can go over. I just like to keep it safe.

[jdobbs]

Originally Posted by rmeyers

i started troubleshooting by looking to see if all the files that are in the original rip are in the shrunken one, which they are. 414 files in both. then i looked into BDedit to see if i could spot some differences to see where the mishap in the structure is. i think i found something. not knowledgeable enough in this stuff to know for sure.

the one on the right is the original rip of the extended edition playlist, the one on the left is the BD-RB rip of the same playlist. as you can see, there are differences in the IN Time and OUT Time of the Playlist and PlaylistMark headings. not sure if they are supposed to be different.

and just for clarification, there are two menus on the BD. one is for the theatrical version, one for the extended version. you can only play the extended version, from the correct main menu. and you can switch back and forth between the theatrical edition menu, and the extended edition menu.

as of right now, i am making another rip, this time including all audio and subtitles to see if it makes any difference.

TSMUXER uses a different time base. BD-RB updates the MPLS/CLPI to correct for it. This is ok.

[jdobbs]

Originally Posted by Capsbackup

Looks like the " CorrectMPLS() 00009 5" problem on rebuild was corrected with the new version BD-RBV02003, but a new issue has developed. The burned disc does play, but I now hear a "seeking/cycling" sound from my Sony BDP-BX1 while playing, as if it is struggling to play. So if I try to fast forward the player freezes for several seconds, and if I change chapters, the same happens but then the player does not recover from the still image/freeze. I then have to press stop just to get the player to respond.
This was a full movie backup to BD-5, resize to 720P, default audio re-encode to 448kbps on Nights In Rodanthe.

I'm aware of issues in that one -- it has a secondary video track that BD-RB isn't reencoding. I also have to change the default PID for the secondary audio track in the M2TS.

[jdobbs]

Originally Posted by Atak_Snajpera

@jdobbs
ftp://213.221.6.90/tsMuxer/
Do we still need fixcpli with .21?

I just tested .22 and it is still needed. The packet count issue seems to be corrected, but the COARSE tables still aren't being updated for SPN rollover.

[Edit] I've noticed, though, that if someone uses splitting in TSMUXER the packet count issue is still there.

[laserfan]

Originally Posted by jdobbs

The 25000 is too high (in MHO) -- I use 17500 for BD-5/9 and 25000 for BD-25, but that wouldn't make a difference. The --nal-hrd I'll have to check out.

Not to re-hash an old argument, and I don't think this has anything to do with "stuttering playback", but the "25000 vs. 17500" question may have something to do also with booktype of the BD-5/9. I have learned for example that in making an HD-DVD you have to burn as booktype DVD+R or DVD+R DL, because if the booktype is DVD-ROM the player thinks it can spin only at 1x. If burned as DVD+R instead, it can spin at 3x. I have a Pioneer burner which can't do anything but booktype DVD-ROM with a DVD+R DL, and I *think* I've burned a BD-9 on that burner, so maybe this "rule of HD DVD" does not apply to BD, or perhaps it's just that my player doesn't care, but there you go--another variable in the equation.

I suppose tho if some folks are burning BD-5/9 as booktype DVD-ROM, and their SAP plays it but refuses to spin at >1x, this could cause stops & starts huh.

P.S. I've used 25000/25000 and then 17500/14745 and now the other day I encountered "buffer underflows" in x264 for the first time. Changing to 25000 fixed that and I'm going to leave it there as at least my player works great w/25000/25000.

[jdobbs]

@rmeyers

The BDEdit displays you are showing are correct. TSMUXER uses a fixed PTS starting value (00:10:00.000) that may be (and usually is) different than the original. Most commercial discs use a value of 00:00:11.650. BD Rebuilder updates the CLPI and MPLS so the values match the new PTS values. The fact that it shows in the tables of BDEdit is just proof that they have been correctly updated. The alternative is to scan through the M2TS and change all the clock values, but it takes too much time that way, and you reach the same result either way. You just have to make sure the M2TS and CLPI/MPLS combinations match.

Actually BD Rebuilder does do the scan/correction of DTS/PTS and other clock values in the M2TS stream for certain types of files, but they are typically much smaller.

[laserfan]

Originally Posted by jdobbs

TSMUXER uses a different time base. BD-RB updates the MPLS/CLPI to correct for it. This is ok.

I noticed a couple times with BDEdit that the "entry point" for movie-only discs was 10 minutes!? Since the discs play and report run-time accurately I paid no mind to this--I wonder if it's a tsMuxeR bug...

Oh, my--you were typing the answer as I was typing my question!