BD Rebuilder Beta - Bug Reports Only

[lauguru]

install windows 8 x64 last night, and the truth, bd-rebuilder that works great, no errors

[setarip_old]

Originally Posted by setarip_old
@jdobbs

It looks like BD-RB is now capable of just about anything under the sun.

Therefore I'll ask, is there anything new regarding the long running DTS Express situation?

Originally Posted by jdobbs
No. I looked at everything I can imagine related to it -- and I've not been able to find anything wrong with the output. I've given up.

Sorry to hear that.

I guess those of us facing this problem will just have to determine which Blu-ray releases are worth copying with 50GB media...

[jdobbs]

Originally Posted by setarip_old

Sorry to hear that.

I guess those of us facing this problem will just have to determine which Blu-ray releases are worth copying with 50GB media...

Of course there is also the option of having more than one person looking at the problem and helping determine its cause. I'm sure there is someone out there who has enough background to help find what is the cause of the issue...

I don't think it's too much to ask for improving software that is essentially free to anyone who can download it.

[setarip_old]

Of course there is also the option of having more than one person looking at the problem and helping determine its cause. I'm sure there is someone out there who has enough background to help find what is the cause of the issue...

I don't think it's too much to ask for improving software that is essentially free to anyone who can download it.

I wish I was that person. Unfortunately, I don't have the requisite skills.

On the other hand, I share your belief that there's "somebody out there" who DOES have sufficient background to accomplish this. In reading through the posts to this thread, it seems obvious (to me, at least) that several of the posters here would be able to accomplish this.

So I'll get on bended knee and outright beg of the community:


Hopefully, if only as a "thank you" for your massive ongoing effort regarding this, the finest program of its type (free or for pay) , they'll step forward and volunteer to actively research the DTS Express anomaly and resolve the issue.

You certainly deserve any and all possible assistance ;>}

All qualified posters to this and creators and posters to other related sub-forums here (e.g. the "GUI" sub-forums), please come forward to help "jdobbs" and, therefore help ourselves and, at the same time, help the community!

[Guest]

Originally Posted by setarip_old

Hopefully, if only as a "thank you" for your massive ongoing effort regarding this, the finest program of its type (free or for pay) , they'll step forward and volunteer to actively research the DTS Express anomaly and resolve the issue.

You certainly deserve any and all possible assistance.

OK then, how about giving us a description of the said anomaly and how to reproduce it with a minimum of fuss? A link to existing descriptions would be acceptable.

[Ch3vr0n]

@neuron2: that's exactly the problem, there are no fixed steps that guarantee you are able to reproduce the problem. It is just for some reason that certain players don't accept the dts-e stream remuxed by bdrb while others like my Panasonic dmp-bd85 do accept it and play it perfectly with insync audio and video. Jdobbs has been over everything multiple times with a finetoothed comb no doubt and can't fine anything that could cause that behavior. Some accept it, some others don't. Why they don't, well that's the 1million dollar question and solution to be found.

Verstuurd van mijn HTC Sensation XE with Beats Audio Z715e met Tapatalk

[jdobbs]

Here's a summary of the issue.

1. Some discs have secondary audio that use DTS Express. Unfortunately when trying to back them up, there also isn't a way to demux them and remux them (TSMUXER doesn't support DTS Express). So for a long time there was no support for that audio codec and it was left out of backups.

2. So I decided I'd try extracting and reintegrating it myself. I just pulled the associated packets (headers and all) from the source M2TS stream, and after TSMUXER completed it's muxing, I updated the timing information of the extracted packet stream and reintegrated (merged) it into the TSMUXER created M2TS and CLPI. I also updated all the PMT and PAT entries, etc. in the M2TS.

3. That seemed to work fine. The audio is recognized correctly by packages like BDEdit, etc. and most players (like Samsung and others) recognized the audio and played it back fine. Others, however (like Sony), while indicating they recognized the existence of the audio, don't seem to be able to play it back. It's as if the stream doesn't exist.

I have no idea what is wrong with the stream. I'm confident something is wrong with the way it is either integrated into the stream or in the updated CLPI entry -- but I just can't seem to find it. I'll admit that I'm a little out of my normal swimlane when it comes to multiplexing M2TS files (I've always depended on TSMUXER for that)... but I looked through the associated Blu-ray and M2TS specs and nothing stands out as an obvious flaw.

It's gotten to the point where I've looked at it so much that I don't think I'd see it now even if it was obvious.

[setarip_old]

@neuron2

Hi!

In addition to the information in jdobbs' post #16030, I'd just note that, from my experience the DTSExpress audio is almost always used on commercial discs in conjunction with "PIP" (Picture In Picture) - and after you use BD-RB to convert/compress such a disc (with no errors reported/indicated), on playback you'll SEE the "PIP" but hear silence.

The most frequently noted culprit standalone player is the SONY BDP S360.

I believe you'll find "Band of Brothers" to be an example that will produce the anomalous result we're discussing...

I'd like to personally thank you for your interest ;>}

[abbadon]

^^ If it helps, I used to have that problem on "The Pacific" until I changed my LG BD630 from "Primary Pass-Thru" to "DTS Re-encode" . Now it's fine. DTS-Express with BDRB and the hidden option

[alfalaval]

hello, you can add the ability to set two separate folders, one for work and one final, just as it was with dvdrebuilder?
I would be very grateful, thank you very much

[Ch3vr0n]

That has been asked by quite alot of users already, I'm one of them. I wish it was implemented too but no such luck yet.

Verstuurd van mijn HTC Sensation XE with Beats Audio Z715e met Tapatalk

[abbadon]

Originally Posted by Ch3vr0n

That has been asked by quite alot of users already, I'm one of them. I wish it was implemented too but no such luck yet.

When I asked jdobbs said with the way he programmed bdrb there was no speed improventment, and had tested as such. Though it can be a bit annoying for those with OCD or "secretarial" preference

[Ch3vr0n]

Perhaps not if u use only 1 drive but in my case i use 3-5 drives. All 1 or 2 TB. If there was an extra output folder possible i'd have the SOURCE on 1 drive, the workfiles on a 2nd, and the final output on a 3rd drive. That way not 1 drive has to do more than 1 thing at the same time. Any drive at any given time will either be READING from the source, RECODING the workfiles or WRITING the final output. How ever small the speed increase will be, i'll take it. That and it would also be a huge timesaver file moving wise. I'd no longer have to move my ISO's to a certain drive after BDRB finished creating it (currently in the workfiles on the 2nd drive). It would instantly be created on the Drive & folder i want the final output to be at.

[jdobbs]

It won't make a difference and I've explained why about 30 times... but I'll add an alternate output folder as a hidden option -- just so I don't have to hear about it anymore. I'd appreciate it if people post there speed increases so I can say "I told you so".

The only real advantage would be if you are running batch jobs and space on the working drive is getting low.

[Ch3vr0n]

<3, i'll do a couple speed tests if ya want, but for me as said it's mainly for file storage purposes. They'd be right on the drive & folder where i want them to be, and i wouldn't have to go arround moving them anymore the Temp folder (bdrb working folder) is currently approx 400GB here while my "iso storage" drive is a different one with over 1TB free and the working drive barely 1-200GB (& rapidly decreasing)

[AmigaFuture]

I get your perception for the data... I agree that it may not make a difference with an alternate output directory. I'm willing to test it. If it does show to be helpful, though, I won't gloat. I'm not into that..just like pride...no need for it. So, let's have some fun. It also depends on the speeds of HDDs.

[alfalaval]

the possibility of having a temporary folder and a folder ending is not to have an increase in speed of the process but to share folders on two different drives and not on the same disk, and thus have less risk of destroying the huge amount of work!

[Crocluvr92]

I know I have everything installed correctly but my encoding keeps crashing! Heres my log:

[10/31/12] BD Rebuilder v0.42.03 (beta)
[09:26:17] Source: VOLUME_ID
- Input BD size: 25.50 GB
- Approximate total content: [03:26:52.308]
- Target BD size: 23.30 GB
- Windows Version: 6.1 [7601]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:26:18] PHASE ONE, Encoding
- [09:26:18] Processing: VID_00003 (1 of 9)
- [09:26:18] Extracting A/V streams [VID_00003]
- [09:42:54] Reencoding video [VID_00003]
- [09:42:54] Reencoding secondary video [TRK_02]
- Encode failed. Aborting.
- BD-Rebuilder v0.42.03 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[09:43:04] - Failed video encode, aborted

Any suggestions?

[colinhunt]

This is not a bug report, quite the opposite in fact. Praise is surely allowed, right?

I'm loving some of the recent new features, Import especially. I'm in the habit of encoding most interesting extras into MKV and doing a movie-only backup of the main feature. Previously I was out of luck if the extra feature did not have a playlist of its own - but now I can use the Import feature! No more messing about with MeGUI, for example. Lovely.

Earlier today Import saved my bacon another way. I had done a Full Backup of a title with lots of extras but the output was 100MB too large. That was solely my fault because I'm always aiming to use the entire BD25 by setting a Custom output size (24400 works pretty well with DGD). Now, instead of re-encoding the entire title I used Import to re-encode a single (original) m2ts and setting the Custom output size so that the resulting m2ts was 100MB smaller than the previously encoded one. I used Alternate Movie-Only Output but set it to "Output BD or AVCHD Compliant Structure" so the result was like a very small BD. After that it was simply a question of renaming the file from 00000.m2ts to 00006.m2ts and copying it over the other, 100MB larger 00006.m2ts. Worked like a charm!

[colinhunt]

That wasn't a bug report, but this is. And it's the weirdest thing. I'm trying to do a movie-only backup of a French title which consists of:

* VID_00001 MPEG-4 (AVC), 1080p, 24fps, 61.58MB
* VID_00000 MPEG-4 (AVC), 1080p, 24fps, 26584.42MB
- Audio 1 DTS-HD XLL, Multi-Ch, French
- Audio 2 DTS-HD XLL, Multi-Ch, English
- Audio 3 DTS-HD XLL, Stereo, French

I disabled both French tracks. BD-RB re-encodes VID_00001 but calculates VID_00000 fits without re-encoding. As PHASE TWO Rebuild starts, this happens:

- [16:40:18] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Can't open file: U:\BDRB\WORKFILES\00001.track_4113.264
[16:40:21] - Failed to REBUILD

Here's the content of MUX_MOVIE_ONLY.meta:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000;00:05:55.916;00:13:24.166;00:20:59.000;00:29:11.500;00:35:52.375;00:44:52.541;00:49:30.083;00:56:28.750;01:01:14.041;01:07:30.291;01:17:24.458;01:49:05.125 --vbv-len=500
V_MPEG4/ISO/AVC, "U:\BDRB\WORKFILES\00001.track_4113.264"+"U:\BDRB\WORKFILES\00000.track_4113.264", fps=24, track=1, insertSEI, contSPS
A_DTS, "U:\BDRB\WORKFILES\00001.track_4353.DTS", timeshift=14125ms, lang=eng

The reason rebuild fails is simple: there is no "00001.track_4113.264" in the WORKFILES directory.

The directory does have "00000.track_4113.264" (19.7GB) and "00001.track_4353.dts" (1.54GB), but "00001.track_4113.264" is missing. VID_00001 is re-encoded without problems, as the log shows:

[16:19:51] PHASE ONE, Encoding
- [16:19:51] Processing: VID_00001 (1 of 2)
- [16:19:51] Extracting A/V streams [VID_00001]
- [16:29:36] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 339 frames
- Bitrate: 28*708 Kbs
- [16:29:36] Reencoding: VID_00001, Pass 1 of 2
- [16:29:48] Reencoding: VID_00001, Pass 2 of 2
- [16:30:11] Video Encode complete

Update: I guess I found the culprit. Even though it's encoding VID_00001, BD-RB names the output file "00000.track_4113.264". And when the next file, VID_00000, is being processed, that too is named "00000.track_4113.264", thus deleting the earlier file.