BD Rebuilder Beta - Bug Reports Only

[turbojet]

Originally Posted by jdobbs

I said I wouldn't comment -- but since you can't let anything go...

I tried to explain the reasoning but you're too bullheaded to back off. Bottom line: It's my damn program and I'll do it the way I think best, if you don't like it use something else.

Sigh, you completely misunderstand me.

Anyhow I see you are showing the same type of behavior you showed with encoding audio insisting for months that it must be done, so I'll just let it runs it's course.

Originally Posted by Capsbackup

I was referring to changing the original .m2ts to 23.976fps before using BD-RB on it. I know it is a long shot, but it did work for me on Terminator 3, region A. This troublesome disc had no audio sync from the very beginning and got worse as it played. But after this change, audio sync was perfect and BD-RB reencoded it to BD-5 perfectly.

Wasn't this also fixable by keeping it interlaced?

[jdobbs]

@turbojet

See my comment in the X264 thread.

If X264 is outputing a rate of 23.975986, and my calculations are correct you would be off by one frame (1/24th of a second) every 7.3 hours of contiguously encoded video.

If anybody can detect that, they'd better be wearing a cape.

[kooibosmania]

hi JDobbs

Great work i love ur app

bug Report

on all the movies from startrek the extra's have a trailing m2ts file of 230MB

this m2ts file becomes the first to be reencoded and it fails.
i dont know what this track is but has many audio and subs but is very short ( 0007FFF8 - 00082329 ) i have been struggeling with this.
Maby it is an option to let the user select the faulty m2ts and remove it from the qeue.
but as it is part of an mpls file i dont know if it is possible to implement in ur programming.

i know it is very difficult to programmaticly determine whats what

adding the min m2ts size does not remove this m2ts from qeue

-----------------------
[16:25:20] BD Rebuilder v0.22.02 (beta)
- Source: STAR_TREK_III_THE_SEARCH_FOR_SPOCK
- Input BD size: 42,95 GB
- Approximate total content: [04:26:34.144]
- Target BD size: 22,71 GB
[16:25:22] PHASE ONE, Encoding
- [16:25:22] Extracting audio/subs [VID_00064]
- [16:25:22] Reencoding: VID_00064 (1 of 13)
- Error in attempt to multiplex: MUX_00064.meta
[16:25:23] - Failed to build structure, aborted

Thanks and keep up the good work

[Capsbackup]

@turbojet;

Wasn't this also fixable by keeping it interlaced?

No, not by BD-RB. That is why I opened a new thread, to try to see if it would be more noticeable. It was not given much response. Apparently just a rare disc and authoring. Oh well, just trying to present experiences and results, so I just brought it up again in case it might help someone or this topic.

[jdobbs]

Originally Posted by Capsbackup

I was referring to changing the original .m2ts to 23.976fps before using BD-RB on it. I know it is a long shot, but it did work for me on Terminator 3, region A. This troublesome disc had no audio sync from the very beginning and got worse as it played. But after this change, audio sync was perfect and BD-RB reencoded it to BD-5 perfectly.

So you're saying that demuxing it first using the fps parameter rather than encoding from the original stream (using the framerate tagged to the stream) actually resulted in a different outcome?

That's just scary.

[Capsbackup]

Originally Posted by jdobbs

So you're saying that demuxing it first using the fps parameter rather than encoding from the original stream (using the framerate tagged to the stream) actually resulted in a different outcome?

That's just scary.

That is correct. If your curious, try Terminator 3, Region A.
And from a previous post:http://forum.doom9.org/showthread.php?t=146884
Maybe rare, but it worked.

[jdobbs]

Originally Posted by kilbowie54

Hi again.
Installed Windows 7's VC-1 decoder in vista but x246.exe stopped working at 0.40% on the video re-encode. Tried the PowerDVD decoder - same problem at 0.70% this time.
Is this "VC-1 1080i" a problem that's unfixable at present? I have the same build of BD-RB running at present on another quad core PC (Vista 64 bit) working with a VC-1 file that's 1080p and it's doing OK - at 37% and no problems.
Maybe I should just be grateful for what I can get to work!
If anyone's got any other ideas, I'd like to try them anyway.

Thanks again for all your help.

This whole hybrid VC-1 source issue is just a pain... unfortunately there is currently no fix for BD-5/9 output, because it has to be reencoded to get the bitrate down to the required level. As for BD-25, I'll look into ways of detecting it so I can automatically just keep it intact (assuming it isn't so large a source stream as to cause space issues).

[Capsbackup]

Originally Posted by jdobbs

This whole hybrid VC-1 source issue is just a pain... unfortunately there is currently no fix for BD-5/9 output, because it has to be reencoded to get the bitrate down to the required level. As for BD-25, I'll look into ways of detecting it so I can automatically just keep it intact (assuming it isn't so large a source stream as to cause space issues).

This method would work on Terminator 3, but again, probably a rare disc.

[jdobbs]

Originally Posted by turbojet

Anyhow I see you are showing the same type of behavior you showed with encoding audio insisting for months that it must be done, so I'll just let it runs it's course.

Sigh...

You know, between the two of us I think we know just about everything there is to know.

You seem to know everything except that you're wrong -- and I know that.

[jdobbs]

Originally Posted by kooibosmania

hi JDobbs

Great work i love ur app

bug Report

on all the movies from startrek the extra's have a trailing m2ts file of 230MB

this m2ts file becomes the first to be reencoded and it fails.
i dont know what this track is but has many audio and subs but is very short ( 0007FFF8 - 00082329 ) i have been struggeling with this.
Maby it is an option to let the user select the faulty m2ts and remove it from the qeue.
but as it is part of an mpls file i dont know if it is possible to implement in ur programming.

i know it is very difficult to programmaticly determine whats what

adding the min m2ts size does not remove this m2ts from qeue

-----------------------
[16:25:20] BD Rebuilder v0.22.02 (beta)
- Source: STAR_TREK_III_THE_SEARCH_FOR_SPOCK
- Input BD size: 42,95 GB
- Approximate total content: [04:26:34.144]
- Target BD size: 22,71 GB
[16:25:22] PHASE ONE, Encoding
- [16:25:22] Extracting audio/subs [VID_00064]
- [16:25:22] Reencoding: VID_00064 (1 of 13)
- Error in attempt to multiplex: MUX_00064.meta
[16:25:23] - Failed to build structure, aborted

Thanks and keep up the good work

Can you post the contents of MUX_00064.meta?

I'll pick up a copy of that disc. I've been meaning to get the BD versions of the STAR TREK movies anyway.

[turbojet]

Originally Posted by jdobbs

Sigh...

You know, between the two of us I think we know just about everything there is to know.

You seem to know everything except that you're wrong -- and I know that.

You must know mostly everything then as I've never claimed to know much. When I am wrong I can and do admit it.

Since you already stated that the .stats files are pretty much worthless you are basically arguing with yourself.

Anyhow you have tested my patience long enough and since I'm wrong all the time I'll get rid of all the 'wrong' info I provided to support BD-RB unless things change.

In the mean time can you give me some ideas of other tools to mess with that create a bunch of useless files?

I kind of regret the $260 I've contributed to DVD-RB / BD-RB over the years. But oh well I've probably gotten my money's worth from the programs just wasn't expecting support to get as disrespectful as it has been over the past couple of months.

[jdobbs]

You are very possibly the most dense person I have ever encountered. Useless files -- can you not read????

You have a lot to learn about disrespect. Frankly, I'm tired of your attitude. I appreciate any bug reports -- but when someone starts telling me how to write my own programs, makes rude remarks, and refuses to accept decisions that are quite clearly mine to make -- I don't need him around.

Don't go away mad. Just go away.

BTW... $260 is far more than the entire amount I've received in BD-RB donations since I first posted it back in December -- and I've put hundreds of hours into it -- so trying to guilt me about money is far from effective. It obviously isn't the driver for my efforts.

[michael1971]

Originally Posted by jdobbs

BTW... $260 is far more than the entire amount I've received in BD-RB donations since I first posted it back in December -- and I've put hundreds of hours into it -- so trying to guilt me about money is far from effective. It obviously isn't the driver for my efforts.

your application is so powerful that I just donate you twice.
Another big thank you for bd-rb!
Excuse my bad english
Michael

[jdobbs]

Thanks. You're a generous man. I'll do my best to make sure you get your money's worth.

[MILLZY]

Originally Posted by jdobbs

You are very possibly the most dense person I have ever encountered. Useless files -- can you not read????

You have a lot to learn about disrespect. Frankly, I'm tired of your attitude. I appreciate any bug reports -- but when someone starts telling me how to write my own programs, makes rude remarks, and refuses to accept decisions that are quite clearly mine to make -- I don't need him around.

Don't go away mad. Just go away

Well Said M8.............

[turbojet]

Originally Posted by jdobbs

You are very possibly the most dense person I have ever encountered. Useless files -- can you not read????

You have a lot to learn about disrespect. Frankly, I'm tired of your attitude. I appreciate any bug reports -- but when someone starts telling me how to write my own programs, makes rude remarks, and refuses to accept decisions that are quite clearly mine to make -- I don't need him around.

Don't go away mad. Just go away.

Nice example you are setting for the rest of the forum, isn't personal attacks against the forum rules or are you above that?

The .stats files I asked for an option to remove ARE NOT USED AND YOU KNOW THAT. Surprisingly the option to delete all files that are used you accepted within hours of you calling me completely wrong and the densest person you know, it all makes sense to me now. Unlike every bug/feature request I've brought up over the past few months you replied the first time it was asked, you didn't ask a bunch of questions or try to prove him wrong. I took this as disrespectful, and I've noticed others have the same experiences. While I at times get frustrated about it I don't stoop to attacking people like you have chosen to do.

BTW... $260 is far more than the entire amount I've received in BD-RB donations since I first posted it back in December -- and I've put hundreds of hours into it -- so trying to guilt me about money is far from effective. It obviously isn't the driver for my efforts.

Frankly I'm not surprised the way you have been treating others lately. Making you feel guilty was not my intent at all, it was to show potential customers that although you may get treated well don't be surprised if that changes. OTOH you may make some people feel guilty for not contributing. While I was wrong to write how much I've contributed it was in the heat of the moment.

This is my last post involving BD-RB on this forum unless the tone changes. It can go one of two ways.

[jdobbs]

I told you why the files are there. It's because they save a lot of time in the case of oversizing when using CRF. Do I have to repeat it over-and-over at the expense of all the other members who are probably as tired of this discussion as I am? If that simple reason isn't enough then "dense" is an understatement. The link you reference has absolutely nothing to do with this discusssion. It was a request to remove the entire working directory automatically after encoding is completed.

You keep droning on wanting desperately to be perceived as being "right" -- it's really not very becoming.

[MikeyBK]

@turbojet...
Bro, if you aren't happy with how much JD has evolved BD-Rebuilder to this point, then just go use RipBot, and pester Atak. I truly feel that you aren't helping the progress of Bd-Rebuilder, more so hindering it with nonstop rants about why BD-REebuilder should bend over backwards so that you can get your Panasonic to work right.
As I've mentioned before, I liked some of what you input, but now it's just plain contempt... just let it go and move on... one way or another.

@JDobbs...
I know that I speak for 99% of the users of BD-Rebuilder when I say that we genuinely appreciate you and this great program. We all also basically understand that it's still in Beta, and that you, as the author, has far more knowledge to implement whatever changes you deem helpful or productive to the ongoing progress of BD-RB...
So again we all thank you for your efforts.

To get back on topic in this thread...
As I posted earlier, I had the 'Failed to retrieve audio' error for the first time, when trying to do a movie-only of Fired Up. I tried all possible settings to try and get it to work in BD-RB to no avail.
Only when I pre-processed Fired up through TSMuxer was I able to run it thru BD-RB.

This title is a multiple m2ts seamlessly branched Bluray, MPEG-4 AVC, which I appended with TSMuxer.
While running it thru TSMuxer, I get the following warnings.
I was just wondering if you had an idea as to what might have caused this??

SmartLabs tsMuxeR. Version 1.10.1(b) http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
H.264 stream does not contain fps field. Muxing fps=23.976
Decoding TRUE-HD stream (track 2): AC3 core+TRUE-HD. Peak bitrate: 4140Kbps (core 640Kbps) Sample Rate: 48KHz Channels: 6
Decoding PGS stream (track 3): Resolution: 1920:1080 Frame rate: 23.976
TRUE-HD stream (track 2): overlapped frame detected at position 00:01:03,136. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:05:55,552. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:07:35,552. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:09:08,032. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:11:25,216. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:12:09,504. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:21:03,584. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:24:40,576. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:25:48,991. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:31:47,743. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:32:39,135. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:36:48,512. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:42:38,239. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 00:49:44,032. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 01:01:11,840. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 01:05:03,552. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 01:08:07,072. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 01:22:09,119. Remove frame.
TRUE-HD stream (track 2): overlapped frame detected at position 01:22:32,640. Remove frame.
Processed 129408 video frames
Creation of Blu-ray playlist
Creation of Blu-ray stream info and seek index
Mux successful complete.
Muxing time: 11 min 1 sec

[jdobbs]

Odd indeed. Are there 19 parts to the appended input stream? I really don't have any idea... but I'm wondering if the last TRUE-HD audio frame of each stream may be extending into the first frame of the following (appended) stream -- causing the overlap.

[jdobbs]

Originally Posted by Capsbackup

That is correct. If your curious, try Terminator 3, Region A.
And from a previous post:http://forum.doom9.org/showthread.php?t=146884
Maybe rare, but it worked.

I will. Sorry for not responding to that thread -- but it became filled with rude comments and pseudo-expert opinions (not from you) so I decided to steer clear.