BD Rebuilder Beta - Bug Reports Only

[MikeyBK]

I've just updated the first post of this thread with a new version of BD Rebuilder (v0.20.01).

Thanks JD, looking forward to running it tonite...

Just an FYI.... version 0.19.06 was extremely successful for me on my system, 100% success on nearly ten encodes.... so I'm sure version 0.20.01 will be just as great...
:thanks:

[turbojet]

Thanks, already got an encode running to check size, will update my 'size' post with new results.

[DIVX2009]

New version of tsMuxer 1.8.19b

[jdobbs]

Thanks, already got an encode running to check size, will update my 'size' post with new results.
I only made about a 1% upward adjustment, so I wouldn't get too excited. Give me a couple more versions and we'll get it right on the money.

[setarip_old]

@jdobbs

I notice that the latest update includes "tsMuxeR v.1.8.18".

In light of the following (That I posted in a "tsMuxeR"-specific thread), which may be indicative of yet other unreported problems, you may want to reconsider:Take care when using v.1.8.18 (beta)

In addition to another poster's earlier noted problem when trying to use the "Split" function, I've just come upon another apparent bug in this version - It claimed it couldn't determine the format of an AVC videostream in an M2TS file created by an earlier version of tsMuxeR.

Both earlier versions, 1.8.8 and 1.8.4 had no such difficulty.

Version 1.8.18, however, had no such difficulty with a similar M2TS file that it had created.

It would be good to find out if the problems lie with v.1.8.18 itself, or if they are a consequence of using the v.1.8.8 GUI (Presently there is no v.1.8.18 GUI) with this newer .EXE...

[jdobbs]

Hmmm... well I guess I'll be hearing from everyone soon enough if it has problems... :( I guess I should have tested/read more before deciding to move to that version.

[MikeyBK]

@jdobbs

I notice that the latest update includes "tsMuxeR v.1.8.18".

In light of the following (That I posted in a "tsMuxeR"-specific thread), which may be indicative of yet other unreported problems, you may want to reconsider:
Take care when using v.1.8.18 (beta)

In addition to another poster's earlier noted problem when trying to use the "Split" function, I've just come upon another apparent bug in this version - It claimed it couldn't determine the format of an AVC videostream in an M2TS file created by an earlier version of tsMuxeR.

Both earlier versions, 1.8.8 and 1.8.4 had no such difficulty.

Version 1.8.18, however, had no such difficulty with a similar M2TS file that it had created.

It would be good to find out if the problems lie with v.1.8.18 itself, or if they are a consequence of using the v.1.8.8 GUI (Presently there is no v.1.8.18 GUI) with this newer .EXE...


I also overwrote the 1.8.8 exe with the 1.8.18 exe in the TSMuxer 1.8.8 folder, and used the 1.8.8 GUI with that 1.8.18 exe... and every one of the movie only m2ts files I had done previously opens with 1.8.18... as do all of the BD-RB m2ts files on my harddrive...

So I'm not too sure it's even 1.8.18 as being the problem...

[Capsbackup]

@jdobbs,
just tried a rebuild of Nights In Rodanthe with the new BD-RB v0.20.01, but I still get the "CorrectMPLS() 00009 5" error. This was on a previous encode with v 0.19.06 that I kept on my hard drive, not a new complete project. If you think it can make a difference, I can redo the whole movie. I just copied over the old BD-RB .exe with the new one. This was a full backup that gives the error, but the movie only was successful.

[drmih]

For information I have had issues where a rip has either reported that each segment was 4 GB and was therefore too big to be done, or the file structure looked okay but rebuilder still said it was too big. I have re-ripped the discs to images and mounted rather than from a file structure on the HDD and they are now fine. This isn't a correction in bd-rebuilder as that still gives the message with the files with the new version but hopefully assists others who have seen this problem.

For those of you who have 'lost' the original disc, you can use imgburn to create an image of the files which also works.

[jdobbs]

@jdobbs,
just tried a rebuild of Nights In Rodanthe with the new BD-RB v0.20.01, but I still get the "CorrectMPLS() 00009 5" error. This was on a previous encode with v 0.19.06 that I kept on my hard drive, not a new complete project. If you think it can make a difference, I can redo the whole movie. I just copied over the old BD-RB .exe with the new one. This was a full backup that gives the error, but the movie only was successful.
Just to be clear, you got that same error with 0.19.6, right?

[GaPony]

It seems to me like you would want to start over again from scratch. Surely any problem from 19.06 would be transferred forward if using a previously processed project as your source for 20.01.

[jdobbs]

Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.

[Capsbackup]

@jdobbs,
Just to be clear, you got that same error with 0.19.6, right?
Yes that is correct.

[Sharc]

Just a note on target size using the latest version:
v0.20.01 / movie only / 2 audio tracks / 2 subtitles.
With custom TARGET_SIZE=4440 it ended up with 3% undersize on a BD5.
Considering that the custom size 4440 includes already a 1% margin, the actual "undersize" is 2% only.

[turbojet]

@jdobbs,
just tried a rebuild of Nights In Rodanthe with the new BD-RB v0.20.01, but I still get the "CorrectMPLS() 00009 5" error. This was on a previous encode with v 0.19.06 that I kept on my hard drive, not a new complete project. If you think it can make a difference, I can redo the whole movie. I just copied over the old BD-RB .exe with the new one. This was a full backup that gives the error, but the movie only was successful.

Same here with a brand new project and 0.20.1

[turbojet]

Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.

I'll try testing it later today

[turbojet]

X FIles 2 movie only drifted way out of sync and this is why

a04 Audio overlaps for 11ms at playtime 0:02:47.
a04 Audio overlaps for 11ms at playtime 0:05:17.
a04 Audio overlaps for 10ms at playtime 0:25:29.
a04 Audio overlaps for 13ms at playtime 0:27:47.
a04 Audio overlaps for 16ms at playtime 0:36:23.
a04 Audio overlaps for 21ms at playtime 0:49:25.
a04 Audio overlaps for 19ms at playtime 0:52:18.
a04 Audio overlaps for 13ms at playtime 1:08:41.
a04 Audio overlaps for 11ms at playtime 1:12:16.
a04 Audio overlaps for 11ms at playtime 1:15:14.
a04 Audio overlaps for 12ms at playtime 1:17:18.
a04 Audio overlaps for 9ms at playtime 1:24:20.
a04 Audio overlaps for 8ms at playtime 1:36:09.
a04 Audio overlaps for 14ms at playtime 1:38:23.
Reported by eac3to.

I think the only way to solve the movie only problem with seamless branching is demuxing the audio with eac3to or TSsplitter or some homebrew demuxer at least until tsmuxer gets fixed if it ever does.

I don't know about full backup, it might be best to keep the delays, is that what you tested jdobbs?

[jdobbs]

X FIles 2 movie only drifted way out of sync and this is why

a04 Audio overlaps for 11ms at playtime 0:02:47.
a04 Audio overlaps for 11ms at playtime 0:05:17.
a04 Audio overlaps for 10ms at playtime 0:25:29.
a04 Audio overlaps for 13ms at playtime 0:27:47.
a04 Audio overlaps for 16ms at playtime 0:36:23.
a04 Audio overlaps for 21ms at playtime 0:49:25.
a04 Audio overlaps for 19ms at playtime 0:52:18.
a04 Audio overlaps for 13ms at playtime 1:08:41.
a04 Audio overlaps for 11ms at playtime 1:12:16.
a04 Audio overlaps for 11ms at playtime 1:15:14.
a04 Audio overlaps for 12ms at playtime 1:17:18.
a04 Audio overlaps for 9ms at playtime 1:24:20.
a04 Audio overlaps for 8ms at playtime 1:36:09.
a04 Audio overlaps for 14ms at playtime 1:38:23.
Reported by eac3to.

I think the only way to solve the movie only problem with seamless branching is demuxing the audio with eac3to or TSsplitter or some homebrew demuxer at least until tsmuxer gets fixed if it ever does.

I don't know about full backup, it might be best to keep the delays, is that what you tested jdobbs?
Are you letting BD-RB do it's job alone, or are you massaging some of it? I've done that disc many times in testing (movie-only and full). The audio drift (in movie-only) was corrected several versions ago.

[turbojet]

Letting BD-RB do it's job except for getting around that mkv issue.
- Demuxes DTS core from DTSMA / sups from 00004.mpls (appending the correct order)
- Encodes each m2ts separately
- Muxes each m2ts encode to new m2ts video only
- Errors out when trying to append mkv's
- I changed meta to append m2ts instead and double checked the order, it was correct
- Used TSMuxer with the edited meta.

It doesn't end up very far out of sync but it does end up out of sync. eac3to's report I think is pretty accurate about 300ms out of sync at the end.

[jdobbs]

You can't append the M2TSs, that was what I had to fix in the original audio-sync problem. Apparently TSMUXER has issues working with its own M2TS creations. I had to change it so it muxes the .264 files.

[turbojet]

Do you have any idea how to work around it using mkv intermediate files?

I'm going to try what I mentioned yesterday about appending all the files in avisynth.

[turbojet]

Appending a bunch of directshowsource in an avs is impractical at least for 1080p sources, with Q6600 and 2GB of RAM x264 lasted about a minute before it froze, maybe it's an x264 bug, I'm not sure. But in the meantime I'll just scream (again) in the MPC-HC threads about the m2ts from .264 issue and hopefully someone will hear me.

[Capsbackup]

@jdobbs,
As turbojet reported, I also have the same error again with BD-RB v0.20.01 on Nights in Rodanthe. "CorrectMPLS() 00009 5"

[jdobbs]

Do you have any idea how to work around it using mkv intermediate files?

I'm going to try what I mentioned yesterday about appending all the files in avisynth. That was the way I did it originally -- but on some sources it brought up so many FFDSHOW CODEC instances that it crashed the computer. It'll do one for each...

[jdobbs]

@jdobbs,
As turbojet reported, I also have the same error again with BD-RB v0.20.01 on Nights in Rodanthe. "CorrectMPLS() 00009 5" I guess I'm going to have to go out and buy that one.

[jdobbs]

Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.Anyone?

[turbojet]

I could not reproduce my aften hanging bug outside of BD-RB. I just did the problem one again in BD-RB with aften 0.0.8 (dated a month after current BD-RB aften svn version) and it worked. So the two times (all attempted) it didn't work it must have been some thing in between BD-RB and aften.

jdobbs I'll be checking BD30 soon... have you had a chance to look at the 720p sup issue I had?
Turns out that's the only movie I've done that has them falling off the screen, I've seen some other subs not centered though and all seem to be fairly big.

Also my output sizes (http://forum.doom9.org/showthread.php?p=1256045#post1256045) are ending up a little better since v0.20.01

[jdobbs]

The subs seem larger because I'm not resizing the graphics themselves, just repositioning them. The ones I've tested have been positioned correctly, but I honestly haven't spent a lot of time on it.

There are subs that aren't meant to be centered... usually they put them to one side or the other on the screen near the origin (or even above the origin).

[isoss]

hoi jdobbs

i hav downloaded the latest version 20.01 bud i have a quastion. what do i need to get the best result (software)

isoss

[jdobbs]

Not sure what you mean. I recommend you read the first post in this thread. Personally I would leave all the settings to the defaults, as they have been selected to give a good balance of speed/quality.

[turbojet]

The subs seem larger because I'm not resizing the graphics themselves, just repositioning them. The ones I've tested have been positioned correctly, but I honestly haven't spent a lot of time on it.

There are subs that aren't meant to be centered... usually they put them to one side or the other on the screen near the origin (or even above the origin).

Ya I know the type but I'm pretty sure some of these are supposed to be centered because I've seen instances where someone is talking near the middle of the screen, centered subtitles then it goes off to the right a bit for one entry, then back to center again. I'd say it's much more often off to the right maybe 30 pixels then misplaced anywhere else.

I see anydvd directories (ANY!/ANYM) are moved over to the output directory, should they be? Are the calculated into the size?

Also I found out newest cyberlink vc-1 decoder can decode streams wmv9 can't, is there any chance of doing some kind of a failover to cyberlink if wmv9 fails?

I don't think I'll be able to test BD30 today, guy isn't home yet probably tomorrow though.

[jdobbs]

No, the anydvd directories are virtual. I just copy over the BDMV and CERTIFICATE folders to my hard drive.

[tyau]

I notice that while encoding a blu-ray using BD-Rebulider, the user is able to change the encoding settings between Good, Better, High Quality, and Highest. Does changing this setting actually take effect during the encoding process?

[turbojet]

If they exist, like if you make image with anydvd, BD-RB copies them over unintentionally.

[jdobbs]

Oh, I see. I always copy discs to my hard drive so I never gave it any thought. Hmm... I guess I should look and see how big they are, I've never paid much attention to them. Maybe I can put some code in to just include the BDMV and CERTIFICATE folders.

[turbojet]

This one I recently did has 127 MB of stuff in the anydvd directories, I don't think it was calculated in when judging the size.

[Shuttle99]

Answer to

"Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.)

I have tested a couple with 20.01 on a Panasonic DMP-BD55 and no problems. I am not sure about FIX_CLPI=0 I just used the default settings and it worked fine.

[isoss]

answer to

i have a panasonic DMP-BD30 and im rebuilding on this moment to see that this version is better. but can anyone please say if its not good how to use FIX_CLPI=0

greatings

[smnckl]

@all

Has anyone had issues with playing back rebuilds done using 0.20.01 on mpc-hc?
I usually test the rebuilds before I burn to disc and with v0.20.01 mpc-hc displays just a black screen. Does not matter whether I open the m2ts file in the STREAM folder or use "Open directory" and point to the BDMV folder.

Could it be due to the new 1.8.18 txMuxeR executable?

The 0.20.01 rebuild process runs fine otherwise.

Sorry if this is OT, just wanted to check.

[MikeyBK]

@all

Has anyone had issues with playing back rebuilds done using 0.20.01 on mpc-hc?
I usually test the rebuilds before I burn to disc and with v0.20.01 mpc-hc displays just a black screen. Does not matter whether I open the m2ts file in the STREAM folder or use "Open directory" and point to the BDMV folder.

Could it be due to the new 1.8.18 txMuxeR executable?

The 0.20.01 rebuild process runs fine otherwise.

Sorry if this is OT, just wanted to check.



Yeah, you're right. The movie I did last night with BD-RB 0.20.01 doesn't open in MPC-HC... but it plays perfectly on VLC, WMP 11, & Arcsoft TMT.
I'll check to see if it's TSMuxer 1.8.18 that might be causing that... but I think it's more of an issue for MPC-HC than TSMuxer, considering the other players all play it fine.

EDIT: Yep, it's the TSMuxer 1.8.18 outputs that won't play on MPC-HC. I just tested an audio comparison m2ts that I did earlier with 1.8.18 and it does the same... black screen only.

Plays fine in all the other players I mentioned though...

[GaPony]

I've had all sorts of problems with the last couple of versions... pixelated playback (in testing from the HDD), x264 crashing like crazy, other things... I'm hesitant to report it as a bug because it was working so well before, and its more than one thing going wrong.

Are Gremlins bugs??? :eek: :)

[MikeyBK]

I've had all sorts of problems with the last couple of versions... pixelated playback (in testing from the HDD), x264 crashing like crazy, other things... I'm hesitant to report it as a bug because it was working so well before, and its more than one thing going wrong.

Are Gremlins bugs??? :eek: :)

Versions 0.19.06 and 0.20.01 have been smooth as butter for me... not as fast as that vewrsion of x264 which did haave that crash bug, but still pretty fast enough.

And the 0.20.01 output m2ts not playing in MPC-HC can't really be considered an issue of either BD-RB or TSMuxer, because it plays perfect on VLC, WMP 11, & TMT... as I mentioned.

[Chefkoch_ico]

Versions 0.19.06 and 0.20.01 have been smooth as butter for me... not as fast as that vewrsion of x264 which did haave that crash bug, but still pretty fast enough.

And the 0.20.01 output m2ts not playing in MPC-HC can't really be considered an issue of either BD-RB or TSMuxer, because it plays perfect on VLC, WMP 11, & TMT... as I mentioned.

Hi!

TSMuxer from 0.20.01 gives me black screens on a lot of extras in PowerDVD 7.3 (incl latest updates). Also on the main movie when skipping chapters, it always plays from the beginning, even though the time shows to be where the chapters really are. Strange.

However, I deleted the output folder, copied tsmuxer from 0.19.06 and started a rebuild with 0.20.01.

That fixed the problem.

So, IMO the new tsmuxer has a serious problem.

Bye

[MikeyBK]

Hi!

TSMuxer from 0.20.01 gives me black screens on a lot of extras in PowerDVD 7.3 (incl latest updates). Also on the main movie when skipping chapters, it always plays from the beginning, even though the time shows to be where the chapters really are. Strange.

However, I deleted the output folder, copied tsmuxer from 0.19.06 and started a rebuild with 0.20.01.

That fixed the problem.

So, IMO the new tsmuxer has a serious problem.

Bye

Not sure how it is TSMuxer as having a 'serious problem', when they all play perfectly with TMT, VLC, & even WMP 11...
I could understand if a BD-9 or BD-25 won't play on most Bluray players or the PS3, but that's more than likely not the case.

If JD starts hearing about playback issues on the standalone players or PS3s, then OK.

Just my .02 cents

[Chefkoch_ico]

PowerDVD is the standard BluRay player on PCs. So when there are issues with it, its serious.

Previously, all players were working, now 2 are not. So one can conclude that others also will not work correctly.

At least, the easy fix for me is to use the old tsmuxer, but I am trying the newest version 0.18.19 in a few hours (only remux).

Bye

[MikeyBK]

PowerDVD is the standard BluRay player on PCs. So when there are issues with it, its serious.

Previously, all players were working, now 2 are not. So one can conclude that others also will not work correctly.

I had PowerDVD, but deleted it off my system because of it's just isn't that great of a Bluray playback software, IMHO...

My 0.20.01 encoded BD-9 plays perfect on my Sony BDP-BX1, haven't had a chance to test it on a PS3 yet, but am confident it will play on it without issues as well.

[Furiousflea]

I had PowerDVD, but deleted it off my system because of it's just isn't that great of a Bluray playback software, IMHO...

My 0.20.01 encoded BD-9 plays perfect on my Sony BDP-BX1, haven't had a chance to test it on a PS3 yet, but am confident it will play on it without issues as well.

Let's try and be helpful :) This post adds nothing to the discussion whatsoever.

[Furiousflea]

Hi!

TSMuxer from 0.20.01 gives me black screens on a lot of extras in PowerDVD 7.3 (incl latest updates). Also on the main movie when skipping chapters, it always plays from the beginning, even though the time shows to be where the chapters really are. Strange.

However, I deleted the output folder, copied tsmuxer from 0.19.06 and started a rebuild with 0.20.01.

That fixed the problem.

So, IMO the new tsmuxer has a serious problem.

Bye

You might want to just confirm this isn't a codec issue. I've had problems in the past with software players where say for example the main feature would play and the extras would not. This is because extras are often encoded with different codec that was playing up on my setup.

You say when it was rebuilt with .20.01 it worked fine. Are you sure this was immediately afterwards. Just to make sure :)

[MikeyBK]

Why are you referring to things he hasn't questioned as bugs? He said PowerDVD isn't working with latest release what has that got to do with your PS3\BDP-BX1. We're trying to correct problems here. If you want to just kiss booty go in another thread. PowerDVd is the defacto standard for players on the PC. Whether you like it or not really isn't the discussion here.


Dude, I'm gonna ask you to lighten up.

smnckl posted that the newly encoded files with BD-RB 0.20.01 doesn't open with MPC-HC, and subsequently blamed TSMuxer as the problem. I merely replied that though it doesn't open with MPC-HC, it does with VLC, TMT, & WMP 11.

That's when Chefkoch_ico stated that he was having similar issues with PowerDVD, and went as far as replacing the version of TSMuxer with the EXE from BD-RB 0.19.06.

That's when I stated that it does open with the other playback software I mentioned, and also voiced my dislike of PowerDVD.

So in essence they are trying to say that it may be a bug with BD-RB 0.20.01 and the TSMuxer version . I'm just saying that the burned discs plays fine for me on my BD player, and hadn't yet tested to see if the BD-9 plays on the PS3 yet.

What part of that isn't related to smnckl's original possible bug??

And JD has already asked that people stop using other versions of included EXEs to help him fix the issues unilaterally.

[Chefkoch_ico]

You might want to just confirm this isn't a codec issue. I've had problems in the past with software players where say for example the main feature would play and the extras would not. This is because extras are often encoded with different codec that was playing up on my setup.

You say when it was rebuilt with .20.01 it worked fine. Are you sure this was immediately afterwards. Just to make sure :)

Hi.

PowerDVD uses always its own codecs, so no problem there.

And yes, I am sure its the same encodings, encode and build = 24 hrs, rebuild only 10 minutes.

Bye