BD Rebuilder Beta - Bug Reports Only

[Category 5]

2.05 worked for Kill Bill 1 but the subtitles need to be turned on manually. is there a way to make the second subtitle track forced (1st is whole movie, second is only foreign language subs)?

I will try 2.08 now, with the old file from 2.05

[Furiousflea]

0.20.08 is SCREWED

EDIT - Not screwed...see post below...;)

[turbojet]

I just loaded 8 retail BD iso's just fine here. I think it's something besides BD-Rebuilder or maybe an option that breaks it, like movie only did in 0.28.07

[MILLZY]

0.20.08 is SCREWED

Just attempting to load a bluray structure from the hard drive that works perfectly fine on all previous releases...

A dialogue box appears...

"Stop Statement Encountered"....


Jdobbs, it's a faulty release good man.... :)


EDIT - IT won't load ANYTHING at all.

Just loaded a few bluray folders with no problems.Trying bedtime stories again at fast encode to see if i have the same probs as last time.(full backup)

[Furiousflea]

I just loaded 8 retail BD iso's just fine here. I think it's something besides BD-Rebuilder or maybe an option that breaks it, like movie only did in 0.28.07

Weird, I just tried a load of old versions...no problem.

This version...default options...get that dialogue every time.

[Furiousflea]

0.20.08 is SCREWED

Just attempting to load a bluray structure from the hard drive that works perfectly fine on all previous releases...

A dialogue box appears...

"Stop Statement Encountered"....


Jdobbs, it's a faulty release good man.... :)


EDIT - IT won't load ANYTHING at all.

Found the problem, and the problem is with BDRB not my system.

1. If I did a copied BDRB to a "fresh" folder (not overwriting) and don't chane ANY options before loading a bluray folder, you will get the error...try it and see ;)

2. If you do it to a "fresh" folder...go into the options first and change the settings then save them...It will load fine :)

...Something to do with loading the settings from the ini before the options are present...I think.

So it's working fine now, but might want to chance the way it goes on the first run jdobbs...

[GaPony]

You're talking about the program files, right? Such as creating a new folder like... C:\BD_R-2008 instead of overwriting existing program files in a C:\BD_Rebuilder folder.

It would make sense that a new release of BD-Rebuilder would come without an .ini file and the old one from the previous version would cause a problem. I always create a new folder for each release, so I haven't seen the problem you mentioned.

I'm glad you got it sorted, but your "0.20.08 is screwed" comment made me a bit gunshy to even check out the new release. You might want to edit those posts for a bit less panicky initial response to the new release. :)

[turbojet]

Found the problem, and the problem is with BDRB not my system.

1. If I did a copied BDRB to a "fresh" folder (not overwriting) and don't chane ANY options before loading a bluray folder, you will get the error...try it and see ;)

2. If you do it to a "fresh" folder...go into the options first and change the settings then save them...It will load fine :)

...Something to do with loading the settings from the ini before the options are present...I think.

So it's working fine now, but might want to chance the way it goes on the first run jdobbs...

I can't reproduce this with the pesky ini or deleting the ini and letting it make it's own. Does C:\ exist on your computer?

I really wish the ini wasn't included in the pack as it doesn't really do anything except sets idle priority which could just as well be done on first load if no ini.

I've already requested this as well as 2 fairly big but easy to fix bugs and I've offered solutions but it's getting awfully frustrating when the developer doesn't reply.

[jdobbs]

I found it. I'd left a STOP statement in for the work I'm doing on secondary audio/video tracks. It happens when the stream type is not one of the standard values. I'll fix it and repost. I just found another error doing "300" that I need to fix also.

[jdobbs]

I can't reproduce this with the pesky ini or deleting the ini and letting it make it's own. Does C:\ exist on your computer?

I really wish the ini wasn't included in the pack as it doesn't really do anything except sets idle priority which could just as well be done on first load if no ini.

I've already requested this as well as 2 fairly big but easy to fix bugs and I've offered solutions but it's getting awfully frustrating when the developer doesn't reply.Of course the developer could also just turn this whole project off because he also has to make a living. You know what is frustrating? Trying to build something for the convenience of others -- with virtually nothing in return -- and still having to take criticism from those you are helping because you're not moving fast enough.

[Capsbackup]

Of course the developer could also just turn this whole project off because he also has to make a living.

Free pie is hard to complain about.
I HEAR you loud and clear!! I agree completely. But I hope you consider the majority then the few when it comes to appreciation. Beta software, lets not forget.
Thanks again for your generosity and time you spend developing this software. :thanks:

[turbojet]

Back in February you said you'd look into the 720 sup problem. Now since there is a solution you seem to be ignoring me completely on the matter but keep on pumping out versions fixing bugs from other people in this thread even if it only affects 1 BD. These 3 issues I talk about affect every BD depending on the options. I understand being busy but the least you could say is 'I'll look into it' or 'I don't plan on fixing the problem'. Hopefully you are thinking the former but I'm under the assumption it's the latter as I don't get any replies about it after 3 months.

A few weeks ago I posted about --bluray changing and to not use it with new tsmuxer, I was obviously ignored and now you are facing more bug reports. But now that it's being used I'm giving you ways to fix it, already been ignored once on this, let's see if it happens again.

Also a few weeks ago I posted that disabled streams weren't being removed from mpls and I included a fixed version but also got not one reply about it.

I'm here to help the program but is it any use when the other side seems to ignore the help?

[jdobbs]

I do what I can do with the time I have. You can't make the assumption that I've read every post you have put here. I was away for several weeks and there's no way I can catch up.

If that isn't a good enough answer... then screw it.

A few weeks ago I posted about --bluray changing and to not use it with new tsmuxer...Is this still an issue with v1.10.1?

...disabled streams weren't being removed from mpls... They never were meant to be -- doing so causes more issues than it corrects. Instead they should still exist, but point to a PID that is kept.

...you'd look into the 720 sup problem... It isn't really a "problem" -- the subs show large on the screen because the picture resolution was reduced. As I said before, I'll look at it. But I think it is more important to fix the problems that cause discs not to work before attacking the cosmetic problems.

[turbojet]

Since I have your attentino now. For all 3 can you answer if you plan on fixing it, don't plan on fixing ir or don't understand the issue?

[archaeo]

Of course the developer could also just turn this whole project off because he also has to make a living. You know what is frustrating? Trying to build something for the convenience of others -- with virtually nothing in return -- and still having to take criticism from those you are helping.

Just my two cents - I do have to say that the tone here seems more demanding (and critical) than what I'd seen during the years of development of DVDRB... I've followed the development of jdobbs Rebuilder proggies since somewhere around v.50, and it's been kind of an eye opener at times to hear the tone in this thread. Really, sometimes one has to step back and realize three things: 1) It's a beta 2) he's doing it on his own time, and 3) there's a difference between constructive feedback and criticism

[MILLZY]

Back in February you said you'd look into the 720 sup problem. Now since there is a solution you seem to be ignoring me completely on the matter but keep on pumping out versions fixing bugs from other people in this thread even if it only affects 1 BD. These 3 issues I talk about affect every BD depending on the options. I understand being busy but the least you could say is 'I'll look into it' or 'I don't plan on fixing the problem'. Hopefully you are thinking the former but I'm under the assumption it's the latter as I don't get any replies about it after 3 months.

A few weeks ago I posted about --bluray changing and to not use it with new tsmuxer, I was obviously ignored and now you are facing more bug reports. But now that it's being used I'm giving you ways to fix it, already been ignored once on this, let's see if it happens again.

Also a few weeks ago I posted that disabled streams weren't being removed from mpls and I included a fixed version but also got not one reply about it.

I'm here to help the program but is it any use when the other side seems to ignore the help?

There are plenty of posts that jdobbs does not reply too.How about giving the guy a break and letting him get on with it instead of bitching about all the comments that he has not answered.He does have a life at the end of the day away from this.

[turbojet]

I must be really unlucky then because as he's been replying to almost everyone else's legitimate bug reports. He hasn't replied to any of mine since February except for when I said that it might take 3 lines of code to use an external program that requires 1 command line. Even then he didn't reply about the real issue, 720p subs, but instead said he hasn't seen anything that would only require 3 lines of code.

I'll give him a break by not posting any bug reports until he acknowledges the current ones.

[laserfan]

Of course the developer could also just turn this whole project off because he also has to make a living.I for one would not blame you one iota if you did this--heck I might even *admire* you for it! It appears to me that BD backups are sufficiently complex, what with the myriad of codecs supported, and extras, and pop-ups, and PIPs, and... well lets just say it's at least an order-of-magnitude more complex than DVD, and unlikely to be anything but a huge support issue well into the future. Gosh it took a few years to get DVD Rebuilder "perfect" (and it is), but you gotta wonder about BR discs given what an ugly mess they are.

If it were me I'd have likely given-up (a public release that is, vs. for my own personal amusement) long ago! :eek:

[MILLZY]

I have just tried a previous backup again that failed at the rebuild process on all beta releases aswell as v0.20.08.I presume it is just one that will not backup, here`s the log:

[10:13:45] BD Rebuilder v0.20.08 (beta)
- Source: BEDTIME STORIES
- Input BD size: 30.01 GB
- Approximate total content: [02:21:51.461]
- Target BD size: 22.46 GB
[10:13:46] PHASE ONE, Encoding
- [10:13:46] Extracting audio/subs [VID_00044]
- [10:13:47] Reencoding: VID_00044 (1 of 16)
- [10:14:04] Extracting audio/subs [VID_00047]
- [10:14:05] Reencoding: VID_00047 (2 of 16)
- [10:14:19] Extracting audio/subs [VID_00042]
- [10:14:22] Reencoding: VID_00042 (3 of 16)
- [10:15:22] Extracting audio/subs [VID_00003]
- [10:15:22] Reencoding: VID_00003 (4 of 16)
- [10:16:57] Extracting audio/subs [VID_00040]
- [10:17:05] Reencoding: VID_00040 (5 of 16)
- [10:19:21] Extracting audio/subs [VID_00002]
- [10:19:29] Reencoding: VID_00002 (6 of 16)
- [10:21:49] Extracting audio/subs [VID_00016]
- [10:21:58] Reencoding: VID_00016 (7 of 16)
- [10:23:38] Extracting audio/subs [VID_00043]
- [10:23:48] Reencoding: VID_00043 (8 of 16)
- [10:26:01] Extracting audio/subs [VID_00045]
- [10:26:13] Reencoding: VID_00045 (9 of 16)
- [10:29:00] Extracting audio/subs [VID_00041]
- [10:29:15] Reencoding: VID_00041 (10 of 16)
- [10:32:53] Extracting audio/subs [VID_00006]
- [10:33:16] Reencoding: VID_00006 (11 of 16)
- [10:40:59] Extracting audio/subs [VID_00009]
- [10:41:24] Reencoding: VID_00009 (12 of 16)
- [10:47:48] Extracting audio/subs [VID_00008]
- [10:48:19] Reencoding: VID_00008 (13 of 16)
- [10:58:19] Extracting audio/subs [VID_00010]
- [10:58:58] Reencoding: VID_00010 (14 of 16)
- [11:11:08] Extracting audio/subs [VID_00011]
- [11:12:29] Reencoding: VID_00011 (15 of 16)
- [11:29:48] Extracting audio/subs [VID_00000]
- [11:45:32] Reencoding: VID_00000 (16 of 16)
[15:38:07]PHASE ONE complete
[15:38:07]PHASE TWO - Rebuild Started
- [15:38:07] Rebuilding BD file Structure
- [15:38:31] RebuildBDFiles() 00076 220

Did this backup at fast encode just to try.

[pbeumer2001]

I just wanna say that I`m verry pleased with this prog. Made severel backups without any problem.


So JDobbs Thanx for this Prog!!!!

[turbojet]

I do what I can do with the time I have. You can't make the assumption that I've read every post you have put here. I was away for several weeks and there's no way I can catch up.

If that isn't a good enough answer... then screw it.

Is this still an issue with v1.10.1?

Thanks for answering, yes --bluray is really only there now for VC-1 on Panasonic BD35 but it hasn't been reported if it works or not. It should theoretically work well if burning on BDR but it's not well tested.

What I wrote earlier about --avchd w/stricter AVCHD option removing BBMV/AUXDATA and w/0 stricter AVCHD you probably could leave output alone but older versions had BDMV/BDJO and BDMV/META files is how it used to be and I believe what's to be intended.

They never were meant to be -- doing so causes more issues than it corrects. Instead they should still exist, but point to a PID that is kept.

Is the issue with disabling stream 1 while keeping stream 2?

It isn't really a "problem" -- the subs show large on the screen because the picture resolution was reduced. As I said before, I'll look at it. But I think it is more important to fix the problems that cause discs not to work before attacking the cosmetic problems.

While the larger size isn't pleasant the bigger problem is it misaligns some subs and these often fall off the screen.

[jdobbs]

1. Yes BD25 default set - not changed.

2. MIN_M2TS_SIZE=4000
I found the bug that caused the issue you reported in "300". It was caused by the fact that 00004.M2TS was larger than 2GB and my routine had a bug. It only shows when MIN_M2TS_SIZE is set larger than 2GB and there are files larger than that being copied. I'm fixing it.

[Furiousflea]

You're talking about the program files, right? Such as creating a new folder like... C:\BD_R-2008 instead of overwriting existing program files in a C:\BD_Rebuilder folder.

It would make sense that a new release of BD-Rebuilder would come without an .ini file and the old one from the previous version would cause a problem. I always create a new folder for each release, so I haven't seen the problem you mentioned.
I'm glad you got it sorted, but your "0.20.08 is screwed" comment made me a bit gunshy to even check out the new release. You might want to edit those posts for a bit less panicky initial response to the new release. :)

You got it the wrong way round. Of course I completely agree with you...Can't stand stupid people just overwriting stuff and expecting it to work. That is not what I'm doing...The problem arises when you DO create a new folder from scratch and load a bluray folder without changing ANY options.

Give it a go and see...

No other version does it...Well, not the last few lol. I think it's because no ini is created until some options are set. The ini is needed to load the bluray folder for it's paremeters...

something like that ;) prolly :)

I editied my post already to tell people to read the bit giving more info, but I do think it was warranted. It is screwed if you were a noob and didn't know to change the options first etc...well not screwed...but a bug for sure.

[Furiousflea]

lol at the hissy fits the last couple of pages...

The problem here is that BDRB is in a very early stage where there are lots of problems with each release, of course. However there are technically minded people who just say it how it is (turbojet). Then there are the parasites who are just here for a free lunch, don't contribute any meaningful bug reports but are "ever so greatful to the god that is jdobbs". It's you guys who need to sort your act out and provide proper bug reports etc and not the usual crap that 9\10 people post. turbojet and tekmobile are basically the only 2 people here that give decent bug reports etc.

Also yeah sure it was much more chilled with DVDRB, but that was very simple, very few bugs except for complex discs and advanced features. Personally, I've spent a lot of time testing discs out to HELP, not just do all my backups then sod off like the rest of you crawlers do. So yeah sure, you people who worship jdobbs have you provided 1 decent bug report...

I rest my case and you should zip it and try understand that constructive critisism in intellectual circles is A-OK. Go flush your ego down the toilet because it's not needed.

jdobbs cheers for lukin into the issue with 300, look forward to having a good backup.

[Furiousflea]

I found the bug that caused the issue you reported in "300". It was caused by the fact that 00004.M2TS was larger than 2GB and my routine had a bug. It only shows when MIN_M2TS_SIZE is set larger than 2GB and there are files larger than that being copied. I'm fixing it.

Cheers :)

[MILLZY]

lol at the hissy fits the last couple of pages...

The problem here is that BDRB is in a very early stage where there are lots of problems with each release, of course. However there are technically minded people who just say it how it is (turbojet). Then there are the parasites who are just here for a free lunch, don't contribute any meaningful bug reports but are "ever so greatful to the god that is jdobbs". It's you guys who need to sort your act out and provide proper bug reports etc and not the usual crap that 9\10 people post. turbojet and tekmobile are basically the only 2 people here that give decent bug reports etc.

Also yeah sure it was much more chilled with DVDRB, but that was very simple, very few bugs except for complex discs and advanced features. Personally, I've spent a lot of time testing discs out to HELP, not just do all my backups then sod off like the rest of you crawlers do. So yeah sure, you people who worship jdobbs have you provided 1 decent bug report...

I rest my case and you should zip it and try understand that constructive critisism in intellectual circles is A-OK. Go flush your ego down the toilet because it's not needed.

jdobbs cheers for lukin into the issue with 300, look forward to having a good backup.

We have got a little chip on our shoulder havent we,Talk about blowing your own trumpet!As you say this is about bug reports and yes most of us are not technically minded but we are still trying to help out.I myself have spent many hours testing many a disc to try a help out.At the end of the day this is a forum were people technically minded or not try to help out.

[archaeo]

lol at the hissy fits the last couple of pages...

The problem here is that BDRB is in a very early stage where there are lots of problems with each release, of course. However there are technically minded people who just say it how it is (turbojet). Then there are the parasites who are just here for a free lunch, don't contribute any meaningful bug reports but are "ever so greatful to the god that is jdobbs". It's you guys who need to sort your act out and provide proper bug reports etc and not the usual crap that 9\10 people post. turbojet and tekmobile are basically the only 2 people here that give decent bug reports etc.

Also yeah sure it was much more chilled with DVDRB, but that was very simple, very few bugs except for complex discs and advanced features. Personally, I've spent a lot of time testing discs out to HELP, not just do all my backups then sod off like the rest of you crawlers do. So yeah sure, you people who worship jdobbs have you provided 1 decent bug report...

I rest my case and you should zip it and try understand that constructive critisism in intellectual circles is A-OK. Go flush your ego down the toilet because it's not needed.

jdobbs cheers for lukin into the issue with 300, look forward to having a good backup.

Hmmm... So how constructive is this comment 'intellectually'?

rule #4

Edit: Furiousflea: I do want to say that you have been a help to myself and others on this forum, and there's no doubt you have contributed to the development of BDRB... But c'mon - sometimes you really cross the line into outright insults to others.

[MikeyBK]

Whoa guys... you need to relax A Bit... :cool:

It's one thing to report bugs to try and help 'the developer' of a Beta software, but completely a different thing when you come accross as if you can produce a better software.... which I know you can't. So come on guys, RELAX!!

Just because most of the users of BD-Rebuilder are appreciative towards JDobbs, that doesn't constitute that they'll be building him a shrine-temple anytime soon!! LOL... What's wrong with being thankful towards him for his time and efforts?

I for one, have had success after success in the last 50 some Blurays using BD-RB... so either I'm the luckiest bastard on the planet or you aren't as super-tech as you claim to be...because you seem to have a shietload of problems using BD-RB when many barely have some of the issues you mention??


Just because I don't test every Bluray in 9 different BD-Rebuilder configurations per disc nowadays makes me supposedly here for a 'free lunch'?? or don't contribute anything? I've reported any bugs that I encountered previously, but just haven't run into any since, can't remember when...

put your money where your mouth is furiousflea..and contribute some more $$ to JD, I have.... as has many others already. And if you haven't contributed anything, contribute whatever you can... let's help the brother out...

[drmih]

I found the bug that caused the issue you reported in "300". It was caused by the fact that 00004.M2TS was larger than 2GB and my routine had a bug. It only shows when MIN_M2TS_SIZE is set larger than 2GB and there are files larger than that being copied. I'm fixing it.

This is also the issue with The Mummy 3 so I'll retry that when you've updated it.
Thanks

[drmih]

I think most of the 'attitude' issues are caused by the size of this thread. It really needs closing and a new one starting with the discs which can't currently be done updated at the top with the problems catagorised and work arounds shown where known. This would prevent repetitive posts and also give jdobbs a way of bracketing typical problems (such as extras which x264 can't handle, pip issues).

[MikeyBK]

I think most of the 'attitude' issues are caused by the size of this thread. It really needs closing and a new one starting with the discs which can't currently be done updated at the top with the problems catagorised and work arounds shown where known. This would prevent repetitive posts and also give jdobbs a way of bracketing typical problems (such as extras which x264 can't handle, pip issues).


Very decent suggestion Bro...

[turbojet]

I think most of the 'attitude' issues are caused by the size of this thread. It really needs closing and a new one starting with the discs which can't currently be done updated at the top with the problems catagorised and work arounds shown where known. This would prevent repetitive posts and also give jdobbs a way of bracketing typical problems (such as extras which x264 can't handle, pip issues).

I agree the lenght of this thread is a problem. I have suggested having a known bug list in the original post a few times so they don't keep getting reported. I've also posted a workaround for VC-1 interlaced decoding issues which so far has been the only type of stream that's confirmed to have decoding problems and this is not a BD-RB issue but basic lack of a decent VC-1 decoder. If both of these were in the original post the thread would probably be less than half of what it is and the same thing wouldn't have to be repeated a bunch of times. In turn maybe my posts would have gotten recognized like they were the first 3 months of the program and not posted around like they have been the past 3 months.

My criticism finally got what I had been looking for the past 3 months, a reply to my legitimate bug reports. I think jdobbs will survive just fine and personally I don't see how someone mentioning they are frustrated because they are getting ignored could be taken as offensive but to each his own. All I can hope is that he pays attention to real bug reports like he used to and that I or someone else doesn't get frustrated enough to mention it again. I think 3 months of reporting the bug about every 2 weeks is more patience then most would have.

[Shuttle99]

Did the txmuxer problem get fixed where it was not writing the correct avchd format to play on panasonic players?

[datman]

I'm guessing I had a problem ripping the movie, because I was also unable to run tsmuxer from either rip or iso-rip. I just ran tsmuxer off the disc and it worked fine. Tonight I will try encoding it again:thanks:

yes I sucessfully encoded using the tsmuxer copy:)

[GaPony]

Given the tone of the past few pages... Yea, I'd start a new bug thread. I'd probably require a properly composed, pre-formatted, on-line form and if it didn't meet the strict standards, reject it.... but that's just me. jdobbs is working to provide the world with the first (so far as I know) real comprehensive Blu-Ray backup program, already supports a DVD copying program, and has to travel extensively as part of the job that actually feeds his family.

Give it a rest! If you have a bug, report it. Nobody needs to hear how the bug is wasting your time or upsetting you.

If you have another issue, or question, you can easily post it someplace else on here. There are other bright people who can, and I'm sure will be glad to help for most other non-bug things.... like TXMuxer problems, x264 issues, etc. Fewer posts in this section might give jdobbs time to read the important ones. I totally understand why he'd like to have all the bug reports in one thread.

Just a suggestion.

[turbojet]

Did the txmuxer problem get fixed where it was not writing the correct avchd format to play on panasonic players?

Broken in 0.20.07.
Works with 0.20.06 and before.
In 0.20.08 you need to enable strict avchd option but it breaks playback in Samsung players (AUXDATA exists).

Hopefully next version it will be fixed so without the strict avchd option enabled it will play on all but Samsung players and enable strict avchd will allow Samsung to play the output again.

[GaPony]

Broken in 0.20.07.
Works with 0.20.06 and before.
In 0.20.08 you need to enable strict avchd option but it breaks playback in Samsung players (AUXDATA exists).

Hopefully next version it will be fixed so without the strict avchd option enabled it will play on all but Samsung players and enable strict avchd will allow Samsung to play the output again.

So just remove the AUXDATA folder before burning, as we did several versions back, and all is ok again?

[Shuttle99]

Broken in 0.20.07.
Works with 0.20.06 and before.
In 0.20.08 you need to enable strict avchd option but it breaks playback in Samsung players (AUXDATA exists).

Hopefully next version it will be fixed so without the strict avchd option enabled it will play on all but Samsung players and enable strict avchd will allow Samsung to play the output again.

Great, thanks for the update I will try it.

[turbojet]

So just remove the AUXDATA folder before burning, as we did several versions back, and all is ok again?

Yes, with v0.20.08 movie only w/strict avchd and full backup modes with Samsung players. Unfortunately Denon and Phillips players need the AUXDATA directory to play. On all other players tested so far the AUXDATA directory has no meaning. This post (http://forum.doom9.org/showthread.php?t=146339) has playable and unplayable results.

[jdobbs]

It would sure be nice if there was some standardization between players... there are more exceptions than there are rules.

[MikeyBK]

Well I double checked the Movie-Only BD9s that I created with 0.20.07 & 0.20.08 and they won't autoplay on PS3s... they play pefectly fine on my Sony BDP-BX1 player though.

It appears that the newer TSMuxers output an m12ts file that is 0000.m2ts, whereas it had always been 0001.m2ts prior.... not sure if this is why PS3s no longer can autoplay these BD9s any longer. All those I did with BD-RB 0.20.05 work pefectly on my Sony and my kids' PS3s.

I'm not quite certain if this was mentioned the way I have, earlier in this thread... I do rmember someone mentioning that it didn't autoplay on their PS3, but not sure if they mentioned what the differencces were from prior TSMuxers in BD-RB 0.20.05 & before.

[turbojet]

It would sure be nice if there was some standardization between players... there are more exceptions than there are rules.

deank may have found a one for all solution with multiAVCHD's AVCHD output but it needs confirmation to work on Phillips, Denons and any other unknown player that needs BDMV/AUXDATA directory.

Well I double checked the Movie-Only BD9s that I created with 0.20.07 & 0.20.08 and they won't autoplay on PS3s... they play pefectly fine on my Sony BDP-BX1 player though.

It appears that the newer TSMuxers output an m12ts file that is 0000.m2ts, whereas it had always been 0001.m2ts prior.... not sure if this is why PS3s no longer can autoplay these BD9s any longer. All those I did with BD-RB 0.20.05 work pefectly on my Sony and my kids' PS3s.

I'm not quite certain if this was mentioned the way I have, earlier in this thread... I do rmember someone mentioning that it didn't autoplay on their PS3, but not sure if they mentioned what the differencces were from prior TSMuxers in BD-RB 0.20.05 & before.

From what I learned from deank's posts the issue involves index.bdmv.
With --bluray it produces V0200 without IDEX which is what all retail BD's use.
With --avchd it produces V0100 with IDEX which is what AVCHD software produce however it goes beyond that but I don't know what that is, deank knows though.

Thanks for the BX1 report, I added NEWBD as playable in the table.

[Jake802]

Hello! I got The Spirit to work with the newest version of BDRebuilder(V 0.20.08).Also checked the stream files and they played with sound. I did full backup BD25.I am setting up to burn now.The BD-RE I am using is only 2x though.Once it is finished Ill let you guys know if it plays correctly on PS3 and my LG Player! Thanks Again JDobbs! I get paid next and I am going to attempt to send you a donation then.I apologize for it not being done sooner,money has been tight lately!

[tekmobile]

Im having problems with Tenacious D: The Complete Masterworks Vol 2

I've done this disc many times in both movie only and full disc with every BD-RB version since 0.20.05 to the latest and always have the same problem.

It works perfect through total media theatre but for some reason it always locks up my SONY BDP-S350 in the exact same place at the start of the concert ive tried different versions of TsMuxer and different versions of x264 with no change.

The original disc plays fine on the BDP-S350

[Tongariro]

I have "The Spirit" (bought it today) but haven't tried it yet. I'll do it after "300" finishes. Can you try reencoding the DTS HD to AC3 and see how it works?

jdobbs

I did as you requested, the spirit that convert DTS to Ac3 and as expected the output works perfect.
I did some testing using the latest tsMuxer:

Muxed to m2ts the h264 with sub and with DTS Master- not working (freezez)

Muxed to m2ts the h264 with sub and the AC3 from the workfile - working perfect

So it seems the problem is the DTS Master.
The file.dts by it self works O.K on my pc(using powerDvd).

Any idea what is going on??

[cyberdoggy]

Did a Movie-only backup with v0.20.08 with Stricter AVCHD and I am glad to say it went perfect for my Panasonic standalone, played perfectly. Good job Jdobbs ;) That seems to have fixed the problem with the newer tsmuxer.exe.

[Furiousflea]

I'm getting that "Stop Statement" dialogue box then BDRB automatically closing when I click "OK" on the dialogue box when i set min m2ts to =0 with...

Kung Fu Panda - UK\EU version.
Royal Space Force - The Wings of Honneamise - Jap import.

...Setting it to =10 and I don't get it...defo something wrong there...

[Chefkoch_ico]

@jdobbs:
beside your Sony Player, do you have PowerDVD available for testing?

Full Backups of most european Universal titles (for example The mummy 3, Bourne Triology), dont work with PowerDVD and some Panasonic Players.

The menu starts fine, but pressing "Play Movie" menu item results in black screen ( I waited more than 1 hour ).

For other players, its OK. Anyway, I assume other players will have this problem too.

Bye

[setarip_old]

@Chefkoch_ico

Hi!do you have PowerDVD available for testing?That's too general a question, as there are a multitude of versions of PowerDVD.

I have found that my intentionally NOT updated version of Power DVD v.7.3 successfully plays all BD-RB conversions...

[turbojet]

When using quick extras --stats parameter is unnecessary.

Also not deinterlacing may allow playback in more players because most menus are 30i and 30p isn't BD standard at the least they will look better at around the same size/effeciency but must use --tff and --bff in x264.