BD Rebuilder Beta - Bug Reports Only

[cadre]

I did the US version of that movie and it has no problems.

But I don't understand your report... you're reporting output that has audio sync issues, but your log shows an encode failure?

I'd recommend you reinstall from scratch following the directions in the first post of this thread. I'd also suggest that if you are overclocked, you lower the speed. Something is clearly wrong, and it looks like your system -- as the encode had issues during the first pass.

I think you are right. The program did encount an encode failure at the first pass, and I ignored it. I will try to install the program and rebuild it again. Thanks for you answer, jdobbs.

[Capsbackup]

Another full backup to BD9, this time Your Highness, results in DTS HD Master 5.1/48kHz/24 bit being converted to DD 2.0 640kbps. :confused:

Some additional info:
This is a multi-part .m2ts movie, with a theatrical and extended version option. Regardless of choice, the original DTS HD Master is converted to DD2.0 640kbps.

NOTE: only the last .m2ts of either version is converted properly to DD 5.1 640kbps. This is what I find with the audio AVS:

Incorrectly converted:

#Created by BD Rebuilder - v0.38.09 (beta)
LoadPlugin("C:\Users\Ed\Desktop\BD-RBV03809C\tools\nicaudio.dll")
audio=DirectShowSource("G:\YOUR_HIGHNESS BDRB\WORKFILES\AUD_50285_4352.mkv").Amplify(1.2)
ConvertAudioTo16bit(ResampleAudio(audio, 48000))

Correctly converted:

#Created by BD Rebuilder - v0.38.09 (beta)
LoadPlugin("C:\Users\Ed\Desktop\BD-RBV03809C\tools\nicaudio.dll")
audio=NicDTSSource("50306.track_4352.dts").Amplify(1.2)
ConvertAudioTo16bit(ResampleAudio(audio, 48000))

It appears when BD-RB converts the file to .mkv and trys to convert that audio file with DirectShowSource to DD 5.1 it is unsuccessful.

When BD-RB converts the audio file with NicDTSSource on the .dts file it converts properly to DD 5.1 640kbps.

[jdobbs]

While it is encoding, could you check your FFDSHOW audio decoder configuration? The "Mixer" checkbox should be unchecked. When the mixer is selected the default is for the audio to be converted to 2/0 (stereo). In BD-RB I manually turn that setting off during DirectShowSource() encoding and then reset it to its original value upon completion. The only thing I can imagine is if the setting is not "taking".

BD-RB uses this strategy on multi-part sources because NicDTSSource() isn't exact in it's timing, which can sometimes cause timing problems when attempting playback on full backups. If you look at the DD output of DTS sources when using NicDTSSource() you'll see that the audio length is very slightly different than the original. On a single-part movie it is no big deal and can be ignored, but it becomes an issue on multi-part playback (with certain players, e.g. Samsung).

[Capsbackup]

Mixer is checked right now, but I am not encoding anything at the moment.

[jdobbs]

Mixer is checked right now, but I am not encoding anything at the moment. If you uncheck it your problem will go away -- but that really only acts as a workaround and doesn't really fix the issue. BD-RB should be unchecking it temporarily during encoding.

[Capsbackup]

If you uncheck it your problem will go away -- but that really only acts as a workaround and doesn't really fix the issue. BD-RB should be unchecking it temporarily during encoding.

I have unchecked it now. I have never made any selection to that area of the ffdshow audio decoder before, so it does appear that if BD-RB is making that change as necessary, it is not reverting back to unchecked when completed.

[jdobbs]

I have unchecked it now. I have never made any selection to that area of the ffdshow audio decoder before, so it does appear that if BD-RB is making that change as necessary, it is not reverting back to unchecked when completed. Checked is the default on most installations. So it should normally be checked, but go unchecked when encoding DTS. It might be a rights issue, but it's hard to tell without actually being there to test it.

[Capsbackup]

Checked is the default on most installations. So it should normally be checked, but go unchecked when encoding DTS. It might be a rights issue, but it's hard to tell without actually being there to test it.

Since my setup is for BD-RB to do my audio conversions as necessary, I want it set to your preference. :cool: Then, if one of my test backups does this again, I can better provide you info to see if it is a bug or not.
So if it should be normally checked, I will do that.

Are you saying to us users that we need to verify the source first before making a selection to this ffdshow audio decoder mixer selection?? :confused:
Or, most likely BD-RB should be checking/unchecking if source is DTS or not!

[jdobbs]

Since my setup is for BD-RB to do my audio conversions as necessary, I want it set to your preference. :cool: Then, if one of my test backups does this again, I can better provide you info to see if it is a bug or not.
So if it should be normally checked, I will do that.

Are you saying to us users that we need to verify the source first before making a selection to this ffdshow audio decoder mixer selection?? :confused:
Or, most likely BD-RB should be checking/unchecking if source is DTS or not! It should all be automatic and the end-user shouldn't have to worry about it.

[jdobbs]

Since my setup is for BD-RB to do my audio conversions as necessary, I want it set to your preference. :cool: Then, if one of my test backups does this again, I can better provide you info to see if it is a bug or not.
So if it should be normally checked, I will do that.

Are you saying to us users that we need to verify the source first before making a selection to this ffdshow audio decoder mixer selection?? :confused:
Or, most likely BD-RB should be checking/unchecking if source is DTS or not! Is there any chance that you have another DirectShow decoder in-place that is doing the decoding (rather than FFDSHOW)? If that decoder converts to stereo it could cause the issue as well.

[jdobbs]

@Capsbackup

Just as a sanity check... does your FFDSHOW audio configuration have the DTS decoder enabled?

[Capsbackup]

Is there any chance that you have another DirectShow decoder in-place that is doing the decoding (rather than FFDSHOW)? If that decoder converts to stereo it could cause the issue as well.

None that I am aware of. I have not installed any programs on this PC for at least 6 months, except your recommended haali and ffdshow versions! :p

@Capsbackup

Just as a sanity check... does your FFDSHOW audio configuration have the DTS decoder enabled?

Yes, and is set to libavcodec.

[AGKnotUser]

Hi,

Did a Full Backup of "Paul" and the resulting BD Disc was only 13.1 GB. The size of the original was 33.4 GB. Any ideas?

[jdobbs]

None that I am aware of. I have not installed any programs on this PC for at least 6 months, except your recommended haali and ffdshow versions! :p



Yes, and is set to libavcodec. Hmmm... mine is set to libdts. Could you try and see if that makes a difference?

[jdobbs]

Hi,

Did a Full Backup of "Paul" and the resulting BD Disc was only 13.1 GB. The size of the original was 33.4 GB. Any ideas? Can't tell much without your settings or your log.

[Capsbackup]

Hmmm... mine is set to libdts. Could you try and see if that makes a difference?

I can try this, but there were many multi-m2ts movies that I have backed up to BD5/9 with previous BD-RB releases and ffdshow set as is, and I never had a DTS HD Master convert to DD 2.0. Could there have been a change to BD-RB with one of your latest updates regarding DTS decoding/encoding? My last two full backups to BD9, Limitless and now Your Highness, both multi-m2ts movies, had the audio convert to DD 640kbps/ 2.0.
I will test it tonight with libdts set and mixer selected and let you know the results.

[jdobbs]

I can try this, but there were many multi-m2ts movies that I have backed up to BD5/9 with previous BD-RB releases and ffdshow set as is, and I never had a DTS HD Master convert to DD 2.0. Could there have been a change to BD-RB with one of your latest updates regarding DTS decoding/encoding? My last two full backups to BD9, Limitless and now Your Highness, both multi-m2ts movies, had the audio convert to DD 640kbps/ 2.0.
I will test it tonight with libdts set and mixer selected and let you know the results. That would make sense. The change to DirectShowSource() was implemented in v0.38.5.

[AGKnotUser]

Can't tell much without your settings or your log.

Here's the log. Is this what you mean by settings?

- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, 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 "libavcodec": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- BD Rebuilder v0.38.0.9, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok

[jdobbs]

Here's the log. Is this what you mean by settings?

- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, 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 "libavcodec": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- BD Rebuilder v0.38.0.9, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok No. The settings would be the BDREBUILDER.INI file and the log would be BD-REBUILDER.LOG.

[AGKnotUser]

No. The settings would be the BDREBUILDER.INI file and the log would be BD-REBUILDER.LOG.

Ok, Here they are.

[jerfilm]

Here's a strange quirk. I'm trying to back up Gone With The Wind Bonus Disc. The Stream folder containing the files contains 68 files totalling 27.4 Gb. Here's the log:

07:48:04] BD Rebuilder v0.38.09 (beta)
- Source: GONE_WITH_THE_WIND_BONUS_DISC
- Input BD size: 55.16 GB
- Approximate total content: [09:25:44.043]
- Target BD size: 22.95 GB
- Windows Version: 6.0 [6002]
- Auto Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
- Target too small. Encode stopped.

And I get the error message "Target size too small to continue"

As you can see, for some reason it seems to think there are 55 Gb - double - in the input file. This problem occurred with vs 38.09.

????? Jerry Rutledge
jerfilm@aol.com

[Capsbackup]

Hmmm... mine is set to libdts. Could you try and see if that makes a difference?

Tried this but same results. :(

That would make sense. The change to DirectShowSource() was implemented in v0.38.5.

This looks more likely, perhaps you could investigate. :p

[jdobbs]

Tried this but same results. :(



This looks more likely, perhaps you could investigate. :p The problem is that it is working perfectly on my system... so I need to know what is different in your case. The only other option is to use NicDTSSources() all the time -- and that causes issues on Samsung players.

[Capsbackup]

The problem is that it is working perfectly on my system... so I need to know what is different in your case. The only other option is to use NicDTSSources() all the time -- and that causes issues on Samsung players.

Well since I don't own a Samsung player, I don't have these issues. :confused: Is there a way for me to use/set BD-RB to use NicDTSSources()?
And since this change that took place with BD-RB, regardless of playback device, I now am unable to do multi-m2ts full movie backups and get properly reencoded DTS HD Master to DD 5.1. :(
Since it does not happen to you, and I know I have not added or changed anything to my system, and it does not appear anyone else is reporting this same problem, I will have to just accept my dilemma. :devil:

[jdobbs]

Well since I don't own a Samsung player, I don't have these issues. :confused: Is there a way for me to use/set BD-RB to use NicDTSSources()?
And since this change that took place with BD-RB, regardless of playback device, I now am unable to do multi-m2ts full movie backups and get properly reencoded DTS HD Master to DD 5.1. :(
Since it does not happen to you, and I know I have not added or changed anything to my system, and it does not appear anyone else is reporting this same problem, I will have to just accept my dilemma. :devil:

Just uncheck the mixer and it should work ok.

I don't want to "accept it" -- I want to fix it. If it happens to you it will likely happen to others -- even if they don't report it. I think I'll go back through the versions of NicAudio.dll and see if this happens on all of them.

[[SLiM]D12]

Trying to do a backup of "Bridesmaids" and i'm getting a Audio/PGS sizing issue error that pops up and my resulting encode is oversized. Any idea how to fix?

thx

[Ch3vr0n]

well for starters you could post the actual entire bd-rb logfile from the encoding with the failure & inspect at the bottom. Without it jdobbs probably will have no idea what you're talking about. He needs the error code

[jdobbs]

Well since I don't own a Samsung player, I don't have these issues. :confused: Is there a way for me to use/set BD-RB to use NicDTSSources()?
And since this change that took place with BD-RB, regardless of playback device, I now am unable to do multi-m2ts full movie backups and get properly reencoded DTS HD Master to DD 5.1. :(
Since it does not happen to you, and I know I have not added or changed anything to my system, and it does not appear anyone else is reporting this same problem, I will have to just accept my dilemma. :devil: Hmm... I was going through the code and remembered that "yes", I did add a switch to disable this. Just add the following line to your INI file:

AUDIO_DIRECTSHOW=0

[laserfan]

Can't tell much without your settings or your log.
Seems like there's a rash of these lately, or maybe I'm just getting cranky! :p

I notice there's nothing in Post#1 (that I can find anyway) about how to post a bug report here.

[[SLiM]D12]

well for starters you could post the actual entire bd-rb logfile from the encoding with the failure & inspect at the bottom. Without it jdobbs probably will have no idea what you're talking about. He needs the error code

It's all good. Reducing the number of audio streams has resolved the issue.

[jdobbs]

D12;1525568']It's all good. Reducing the number of audio streams has resolved the issue. Sometimes when you keep HD audio (especially with numerous streams) you'll find that the audio alone is larger than the output target, making it impossible to fit it.

Since HD audio is essentially just a gimmick with no real benefit (proven by double-blind tests) -- I always suggest you reencode to Dolby Digital or just keep the core (uncheck "Keep HD audio"). That way you don't sacrifice video quality for non-existent audio improvements.

Just my humble opinion.

[[SLiM]D12]

Thx jdobbs, I and i'm sure many others value your true opinion.

[Capsbackup]

Hmm... I was going through the code and remembered that "yes", I did add a switch to disable this. Just add the following line to your INI file:

AUDIO_DIRECTSHOW=0

OK thanks. I will give that a try. :D
So I should leave Mixer checked and just use the switch in BD-RB?

[jdobbs]

OK thanks. I will give that a try. :D
So I should leave Mixer checked and just use the switch in BD-RB? If you use that switch it won't make a difference whether "Mixer" it is checked or not. NicDTSSource() doesn't use DirectShow/FFDSHOW.

[Ch3vr0n]

Just had this weird error. Any idea's?

-----------------------
[17:38:45] BD Rebuilder v0.38.09 (beta)
- Source: THE_PUNISHER
- Input BD size: 40,54 GB
- Approximate total content: [03:35:05.224]
- Target BD size: 22,95 GB
- Windows Version: 6.0 [6002]
- Auto Quality: Good (Very Fast), ABR
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[17:38:45] PHASE ONE, Encoding
- [17:38:45] Extracting A/V streams [VID_00260]
- [17:38:48] Reencoding: VID_00260 (1 of 12)
- [17:38:48] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 1.440 frames
- Bitrate: 8.242 Kbs
- [17:38:48] Reencoding: VID_00260, Pass 1 of 1
- [17:39:05] Video Encode complete
- [17:39:05] Reencoding audio tracks (if req'd)
- [17:39:05] Multiplexing M2TS
- [17:39:07] Extracting A/V streams [VID_00262]
- [17:49:19] Reencoding: VID_00262 (2 of 12)
- [17:49:19] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 177.673 frames
- Bitrate: 16.323 Kbs
- [17:49:19] Reencoding: VID_00262, Pass 1 of 1
- [19:38:09] Video Encode complete
- [19:38:09] Reencoding audio tracks (if req'd)
- [19:38:09] Multiplexing M2TS
- [19:49:39] Extracting A/V streams [VID_00263]
- [19:49:39] Reencoding: VID_00263 (3 of 12)
- [19:49:39] Collecting video information
- [19:49:39] Keeping original video (no reencode)
- [19:49:39] Reencoding audio tracks (if req'd)
- [19:49:39] Multiplexing M2TS
- [19:49:40] Extracting A/V streams [VID_00264]
- [19:49:40] DoEncoding() 00006 1607
[20:18:49] - Failed to complete.

If i try to resume the message changes to

- [20:18:54] DoEncoding() 00006 1509

[Rich86]

Sometimes when you keep HD audio (especially with numerous streams) you'll find that the audio alone is larger than the output target, making it impossible to fit it.

Since HD audio is essentially just a gimmick with no real benefit (proven by double-blind tests) -- I always suggest you reencode to Dolby Digital or just keep the core (uncheck "Keep HD audio"). That way you don't sacrifice video quality for non-existent audio improvements.

Just my humble opinion.

I agree that lossless audio codecs are not as dramatic an improvement over quality compressed audio as some folks like to suggest. However, if you have & use high quality home theater audio equipment (decoding, amplification & speakers), I find there IS an improvement in the audio. I always retain the lossless audio track if making a backup on BD, and am perfectly willing to stick to "movie only" mode to limit video quality degradation as much as possible.

[jdobbs]

I agree that lossless audio codecs are not as dramatic an improvement over quality compressed audio as some folks like to suggest. However, if you have & use high quality home theater audio equipment (decoding, amplification & speakers), I find there IS an improvement in the audio. I always retain the lossless audio track if making a backup on BD, and am perfectly willing to stick to "movie only" mode to limit video quality degradation as much as possible. If you think there is a difference and you want to keep HD audio, then more power to you.

But...

In all the double-blind tests in which people who think they can hear a difference are asked to identify the HD source compared to a compressed source, they all fail. The only requirement is that the compressed audio mean certain minmal criteria (in DD it is 640Kbs for a 5.1 source). I believe in science and engineering, and not black magic -- and in the scientific world the results of these tests would be considered a slam dunk.

[omegaman7]

Thank you for posting that JD. I'm gonna strongly consider at the very least compressing the HD audio now. Provided I don't lose channels, I believe I can be happy ;)

[Ch3vr0n]

Any idea on My issue JD? Currently running a different encode but it's about to finish. I'd love to be able to finish that other one

[jdobbs]

Thank you for posting that JD. I'm gonna strongly consider at the very least compressing the HD audio now. Provided I don't lose channels, I believe I can be happy ;) That's a good point. Non-HD audio typically is limited to 5.1 channels.

[jdobbs]

Any idea on My issue JD? Currently running a different encode but it's about to finish. I'd love to be able to finish that other one Not really. I know that 00006 is an overflow error (usually attempting to put a value that is too large into a variable). But I really can't see how I can get it at those points (1607 and 1509).

[Ch3vr0n]

I'll run the job again. See if it was a 1 time fluke. Disc in Question has EAN number 8 712609 665710. If the ISO fails again i'll then try an encode straight from the disc. I'll let you know

[Ch3vr0n]

JD: Good news. A full restart of the job did the trick. Looks like it was a 1 time fluke and BDRB didnt detect the IVTC on the first run probably. The first time after the extended mpeg2 scan it attempted to encode directly. The 2nd time it detected IVTC See the logfile below. VID_00264 was the problematic one

-----------------------

[00:04:03] BD Rebuilder v0.38.09 (beta)
- Source: THE_PUNISHER
- Input BD size: 40,67 GB
- Approximate total content: [03:35:05.224]
- Target BD size: 22,95 GB
- Windows Version: 6.0 [6002]
- Auto Quality: Good (Very Fast), ABR
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[00:04:04] PHASE ONE, Encoding
- [00:04:04] Extracting A/V streams [VID_00262]
- [00:18:24] Reencoding: VID_00262 (2 of 12)
- [00:18:24] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 177.673 frames
- Bitrate: 16.203 Kbs
- [00:18:24] Reencoding: VID_00262, Pass 1 of 1
- [02:28:37] Video Encode complete
- [02:28:38] Reencoding audio tracks (if req'd)
- [02:28:39] Multiplexing M2TS
- [02:41:20] Extracting A/V streams [VID_00263]
- [02:41:27] Reencoding: VID_00263 (3 of 12)
- [02:41:27] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 3.336 frames
- Bitrate: 9.322 Kbs
- [02:41:27] Reencoding: VID_00263, Pass 1 of 1
- [02:42:36] Video Encode complete
- [02:42:36] Reencoding audio tracks (if req'd)
- [02:42:36] Multiplexing M2TS
- [02:42:42] Extracting A/V streams [VID_00264]
- [02:42:59] Reencoding: VID_00264 (4 of 12)
- [02:42:59] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 8.030 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 4.846 Kbs
- [02:42:59] Reencoding: VID_00264, Pass 1 of 1
- [02:43:47] Video Encode complete
- [02:43:47] Reencoding audio tracks (if req'd)
- [02:43:47] Multiplexing M2TS
- [02:43:57] Extracting A/V streams [VID_00283]
- [02:44:08] Reencoding: VID_00283 (5 of 12)
- [02:44:08] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 2.369 frames
- Bitrate: 9.229 Kbs
- [02:44:08] Reencoding: VID_00283, Pass 1 of 1
- [02:45:38] Video Encode complete
- [02:45:38] Reencoding audio tracks (if req'd)
- [02:45:38] Multiplexing M2TS
- [02:45:46] Extracting A/V streams [VID_00284]
- [02:45:54] Reencoding: VID_00284 (6 of 12)
- [02:45:54] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 2.544 frames
- Bitrate: 9.322 Kbs
- [02:45:54] Reencoding: VID_00284, Pass 1 of 1
- [02:47:00] Video Encode complete
- [02:47:00] Reencoding audio tracks (if req'd)
- [02:47:00] Multiplexing M2TS
- [02:47:03] Extracting A/V streams [VID_00285]
- [02:47:07] Reencoding: VID_00285 (7 of 12)
- [02:47:07] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 1.632 frames
- Bitrate: 9.241 Kbs
- [02:47:07] Reencoding: VID_00285, Pass 1 of 1
- [02:47:52] Video Encode complete
- [02:47:52] Reencoding audio tracks (if req'd)
- [02:47:52] Multiplexing M2TS
- [02:47:54] Extracting A/V streams [VID_00286]
- [02:49:10] Reencoding: VID_00286 (8 of 12)
- [02:49:10] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 53.935 frames
- Bitrate: 4.848 Kbs
- [02:49:10] Reencoding: VID_00286, Pass 1 of 1
- [02:53:34] Video Encode complete
- [02:53:34] Reencoding audio tracks (if req'd)
- [02:53:34] Multiplexing M2TS
- [02:53:54] Extracting A/V streams [VID_00287]
- [02:54:13] Reencoding: VID_00287 (9 of 12)
- [02:54:13] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 11.470 frames
- Bitrate: 4.850 Kbs
- [02:54:13] Reencoding: VID_00287, Pass 1 of 1
- [02:55:03] Video Encode complete
- [02:55:03] Reencoding audio tracks (if req'd)
- [02:55:03] Multiplexing M2TS
- [02:55:07] Extracting A/V streams [VID_00288]
- [02:57:40] Reencoding: VID_00288 (10 of 12)
- [02:57:40] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 49.915 frames
- Bitrate: 4.848 Kbs
- [02:57:40] Reencoding: VID_00288, Pass 1 of 1
- [03:01:56] Video Encode complete
- [03:01:57] Reencoding audio tracks (if req'd)
- [03:01:57] Multiplexing M2TS
- [03:02:14] Extracting A/V streams [VID_00289]
- [03:02:22] Reencoding: VID_00289 (11 of 12)
- [03:02:22] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 4.580 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 4.763 Kbs
- [03:02:22] Reencoding: VID_00289, Pass 1 of 1
- [03:02:48] Video Encode complete
- [03:02:48] Reencoding audio tracks (if req'd)
- [03:02:48] Multiplexing M2TS
- [03:02:51] Extracting A/V streams [VID_00293]
- [03:03:01] Reencoding: VID_00293 (12 of 12)
- [03:03:01] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29,970fps, 6.140 frames
- Bitrate: 4.844 Kbs
- [03:03:01] Reencoding: VID_00293, Pass 1 of 1
- [03:03:29] Video Encode complete
- [03:03:29] Reencoding audio tracks (if req'd)
- [03:03:29] Multiplexing M2TS
[03:03:32]PHASE ONE complete
[03:03:32]PHASE TWO - Rebuild Started
- [03:03:32] Rebuilding BD file Structure
[03:03:46] - Encode and Rebuild complete
[03:03:46] BURNING BD structure to disc
- ImgBurn completed successfully
- THE_PUNISHER folder removed.
- WORKFILES folder removed.
[03:17:18]JOB: THE_PUNISHER finished.


I did notice something on the final burn. The original had the PS3 folder "PS3_UPDATE", "PS3_VPRM" and the file "PS3_DISC.SFB" on it. Although the PS3 FOLDERS were correctly excluded from the burn, the file "PS3_DISC.FSB" WAS present on the burnt disc. Perhaps a small error in the code. That being said, the file is only 2kb in size so i doubt it has a big impact :p

[jdobbs]

Interesting -- good analysis, thanks for all the detail. Hmm... it makes sense that the error is in the MPEG-2 scan -- that would match the description you gave of where it happens. I should have caught that. The questions are: why does it act differently on different runs? and which variable is overflowing?

[Ch3vr0n]

VID_00289 also has IVTC so i "crossed my fingers" that it wouldnt jam on that one, went through the extended scan and encoding without a hitch. Anyway that would be your department to figure out what is happening, why & where. All i can say is that the rebuild worked & disc has been tested and worked like it should. Perhaps another look at the folder exclusion is needed too as the FSB file was included on the burn. Anyway, any progress on that idea of mine we pmed about a while back? Hope you've also made progress on the DTS-E front, cause i've got a dozen discs now that make use of it that i wanna back up :)

[setarip_old]

Hope you've also made progress on the DTS-E front, cause i've got a dozen discs now that make use of it that i wanna back up +1, if "DTS-E" is the same as DTS Express (Especially all of that World War II additional detail)...

[Rich86]

If you think there is a difference and you want to keep HD audio, then more power to you.

But...

In all the double-blind tests in which people who think they can hear a difference are asked to identify the HD source compared to a compressed source, they all fail. The only requirement is that the compressed audio mean certain minmal criteria (in DD it is 640Kbs for a 5.1 source). I believe in science and engineering, and not black magic -- and in the scientific world the results of these tests would be considered a slam dunk.

I also believe in factual assessments and try to avoid being suckered in by hype. With a modern home theater system, it is pretty easy to switch between and compare lossless audio vs. the compressed core and I feel confident I heard a slight improvement in detail with lossless audio when I experimented. However, I certainly did not attempt to set up and run a double blind test, so there is surely a possibility of kidding myself somewhat.

I'd be interested in seeing these professionally conducted and verified double blind tests that prove there is no difference between lossless audio & compressed audio on a high quality audio reproduction system. Are there some links available for us to read and learn? Thanks.

[jdobbs]

Interestingly most of the tests that I've seen reported were actually conducted by the same people who are "selling" you HD audio. There are lots of sources, but with a quick Google, here's a quote from the DTS Wiki:In the consumer (home theater) market, AC-3 and DTS are close in terms of audio performance. When the DTS audio track is encoded at its highest legal bitrate (1509.75 kbit/s), technical experts rank DTS as perceptually transparent for most audio program material (i.e., indistinguishable to the uncoded source in a double blind test). Dolby claims its competing AC-3 codec achieves similar transparency at its highest coded bitrate (640 kbit/s).

[AGKnotUser]

I went back and looked at the oversize problem I am having with "Disney's A Christmas Carol" and have new information:

The original disc is 33.7 GB. I used Clown_BD BD Copier to get the size down to 27.17 GB. Converted it to an ISO with ImgBurm, then ran BD-Rebuilder to fit it on a 25 GB disc. This is where I ran into the size problem.

An excerpt from the log shows what I think is the root of the problem:

[23:03:18] Extracting A/V streams [VID_00000]
- [23:19:35] Reencoding: VID_00000 (1 of 70)
- [23:19:35] Reencoding secondary video [TRK_02]
- [23:32:05] Collecting video information
- [23:32:05] Keeping original video (no reencode) <--------- Here's the problem
- [23:32:05] Reencoding audio tracks (if req'd)
- [23:32:05] Multiplexing M2TS

When I look at the 00000.m2ts file the size is: 24.2 GB (26,051,844,096 bytes) all by itself, not including the other 69 VIDs.

Attached you will find the INI and LOG files.

[jdobbs]

I went back and looked at the oversize problem I am having with "Disney's A Christmas Carol" and have new information:

The original disc is 33.7 GB. I used Clown_BD BD Copier to get the size down to 27.17 GB. Converted it to an ISO with ImgBurm, then ran BD-Rebuilder to fit it on a 25 GB disc. This is where I ran into the size problem.

An excerpt from the log shows what I think is the root of the problem:

[23:03:18] Extracting A/V streams [VID_00000]
- [23:19:35] Reencoding: VID_00000 (1 of 70)
- [23:19:35] Reencoding secondary video [TRK_02]
- [23:32:05] Collecting video information
- [23:32:05] Keeping original video (no reencode) <--------- Here's the problem
- [23:32:05] Reencoding audio tracks (if req'd)
- [23:32:05] Multiplexing M2TS

When I look at the 00000.m2ts file the size is: 24.2 GB (26,051,844,096 bytes) all by itself, not including the other 69 VIDs.

Attached you will find the INI and LOG files. I'm sorry, but as I've said many, many times -- I don't respoind to trouble reports on sources that have been preprocessed. There error historically almost always is a result of from the preprocessing.

Run BD-RB against the original -- and if you have an issue I will look at it.