BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Have tried several times to re-encode Independence Day (Region A) "movie only" with no luck.

Steup is:

[Status]
LABEL=ID4_US_V2
VERSION=v0.29.03 (beta)
SOURCE_SIZE=37979387904
SOURCE_VIDEO_SIZE=37979387904
TARGET_SIZE=25165824000
REDUCTION=.662617945913487
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=3
COMPLETED=1
[00001]
AUDIO=10000
PGS=1000001
M2TS_TARGET=25165803644
RATE=20000
NSIZE=22487697408
FLINK=0
MLINK=0
[00002]
M2TS_TARGET=20356


The rebuilder log is:
-----------------------
[12:27:21] BD Rebuilder v0.29.03 (beta)
- Source: ID4_US_V2
- Input BD size: 35.37 GB
- Approximate total content: [02:24:48.680]
- Target BD size: 23.44 GB
- MOVIE-ONLY mode enabled
[12:27:21] PHASE ONE, Encoding
- [12:27:21] Extracting A/V streams [VID_00001]
- [12:51:47] Reencoding: VID_00001 (1 of 2)
- [12:51:47] Collecting video information
- Video: 1920x1080, 23.976fps, 208,296 frames
- Bitrate: 20,000 Kbs
- [12:51:47] Reencoding: VID_00001, Pass 1 of 2
- [12:51:48] Reencoding: VID_00001, Pass 2 of 2
- [14:36:47] Video Encode complete
- [14:36:47] Reencoding audio tracks (if req'd)
- [14:43:41] Multiplexing M2TS
- [14:58:13] Extracting A/V streams [VID_00002]
- [14:58:14] Reencoding: VID_00002 (2 of 2)
- [14:58:14] Collecting video information
- Video: 1920x1080, 23.976fps, 24 frames
- [14:58:14] Reencoding: VID_00002, Pass 1 of 1
- [14:58:16] Video Encode complete
- [14:58:16] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00002.meta
- Can't open file: F:\ID4\WORKFILES\VID_00002.AVS.264
[14:58:16] - Failed to build structure, aborted


However, I can do the full disc with no problem.

Rebuilder log is:
-----------------------
[15:57:57] BD Rebuilder v0.29.03 (beta)
- Source: ID4_US_V2
- Input BD size: 40.54 GB
- Approximate total content: [02:46:56.756]
- Target BD size: 23.44 GB
[15:57:59] PHASE ONE, Encoding
- [15:57:59] Extracting A/V streams [VID_00017]
- [15:57:59] Reencoding: VID_00017 (1 of 14)
- [15:58:02] Extracting A/V streams [VID_00002]
- [15:58:02] Reencoding: VID_00002 (2 of 14)
- [15:58:04] Extracting A/V streams [VID_00013]
- [15:58:15] Reencoding: VID_00013 (3 of 14)
- [15:58:59] Extracting A/V streams [VID_00016]
- [15:59:17] Reencoding: VID_00016 (4 of 14)
- [16:00:23] Extracting A/V streams [VID_00006]
- [16:00:28] Reencoding: VID_00006 (5 of 14)
- [16:01:19] Extracting A/V streams [VID_00011]
- [16:01:26] Reencoding: VID_00011 (6 of 14)
- [16:03:07] Extracting A/V streams [VID_00007]
- [16:03:24] Reencoding: VID_00007 (7 of 14)
- [16:04:36] Extracting A/V streams [VID_00010]
- [16:04:58] Reencoding: VID_00010 (8 of 14)
- [16:06:47] Extracting A/V streams [VID_00015]
- [16:07:18] Reencoding: VID_00015 (9 of 14)
- [16:09:28] Extracting A/V streams [VID_00014]
- [16:10:10] Reencoding: VID_00014 (10 of 14)
- [16:12:02] Extracting A/V streams [VID_00008]
- [16:12:12] Reencoding: VID_00008 (11 of 14)
- [16:14:11] Extracting A/V streams [VID_00012]
- [16:14:37] Reencoding: VID_00012 (12 of 14)
- [16:16:42] Extracting A/V streams [VID_00009]
- [16:17:13] Reencoding: VID_00009 (13 of 14)
- [16:19:20] Extracting A/V streams [VID_00001]
- [16:34:12] Reencoding: VID_00001 (14 of 14)
[18:36:20]PHASE ONE complete
[18:36:20]PHASE TWO - Rebuild Started
- [18:36:20] Rebuilding BD file Structure
[18:36:48] - Encode and Rebuild complete
- WORKFILES folder removed.
[18:36:50]JOB: ID4_US_V2 finished.Thanks for the helpful report. Found it and fixed it.

[setarip_old]

@jdobbs"--avchd" is used for all movie-only encodes.1) What is the earliest version of BD-RB to incorporate this as a default setting?

2) Does/Can this affect the "HDDVD_Compliant" setting in any way?

[skylab1]

@skylab1

Hi!

What version of "AnyDVDHD" did you use?

I ask because according to postings at the SlySoft forum, a proper rip requires the use of v.6.5.8.1 beta...


That may have explained the problem, I upgraded to the latest version after I already did the rip. AnyDVD HD did ask me to download an update before the rip so I though that would have been enough.

I try rip it again with the latest version see if the same problem occur.

Thanks for the tip.

[samtroy]

"--avchd" is used for all movie-only encodes. Strict compliance removes certain directories. If you want it to use "--blu-ray" add "FORCE_BLURAY=1" to your INI file. Warning: The blu-ray format will NOT work on some standalone players.

The MKV_INTERMEDIATE=0 really shouldn't make any difference -- but it has been reported to work better with certain systems.

Ok I see, thanks.

Well, my BD-Player (LG BD390) supports 'real' blu-ray BD9s without a problem. Would there be *any* disadvantage for me if I continue to use "--avchd"? Or is it better to use FORCE_BLURAY=1 in my case? Some disc navigation advantages maybe?

And would you please be so kind and share your thoughts on that "double AC3" problem I'm having again:

http://forum.doom9.org/showthread.php?p=1327346#post1327346

It's driving me nuts.. ;)

Thanks alot for your time. :thanks:

[jdobbs]

@jdobbs1) What is the earliest version of BD-RB to incorporate this as a default setting?

2) Does/Can this affect the "HDDVD_Compliant" setting in any way?

1. v0.22.01 (May, 2009, it's in the change log)
2. No. AVCHD is the output file format and isn't related at all to what HDDVD_Compliant does.

[jdobbs]

Ok I see, thanks.

Well, my BD-Player (LG BD390) supports 'real' blu-ray BD9s without a problem. Would there be *any* disadvantage for me if I continue to use "--avchd"? Or is it better to use FORCE_BLURAY=1 in my case? Some disc navigation advantages maybe?

And would you please be so kind and share your thoughts on that "double AC3" problem I'm having again:

http://forum.doom9.org/showthread.php?p=1327346#post1327346

It's driving me nuts.. ;)

Thanks alot for your time. :thanks:In most cases it is better to leave it at the default. If you set FORCE_BLURAY you may be creating a disc that isn't compatible with future players, etc. Give it another year and players are going to be under $100 -- and you'll start seeing multiple players in a single home (like DVD). You don't want to lock yourself into a single player brand/type.

There are no advantages I can think of for changing it... I just put the option in to maintain backward compatibility and "just in case".

I've gone through the code over-and-over and I can't see any way that an AC3 would be generated unless it is chosen to do so. As for the two instances of each -- that's perfectly normal. If you have selected to reencode AC3 you will have the original (demuxed) and the reencode (@ either 640Kbs or 448Kbs). The reason that is done (e.g. from 640Kbs to 640Kbs) is so other adjustments can be made (filtering, normalization, etc.) in future versions. Today the only adjustment is "AUDIO_AMPLIFY=" which can increase reencoded volume levels.

I've added an entry to the log that shows the audio settings at the start of the backup. That way, when I get a report of this type I can see absolutely what the settings are. Right now, until I can find a way it could happen, I have to assume the settings weren't what was thought at the time the job was started. Sometimes (especially in batch mode) the settings used for encoding aren't the ones you have in your INI file. They are what was there at the time the job was added to the queue.

[jdobbs]

I've updated the first post of this thread with a link to a new version of BD-RB (v0.29.05). Changes for this version are:- Corrected an issue in which, while the new audio
delay routine in v0.29.04 was finding the delays
correctly, they weren't being properly applied at
remux. It should work correctly now.
- Corrected an error in BATCH mode that could result
in "RebuildFiles() 00075 2202" when output folder
already exists.
- Corrected an error in which small files that are a
part of a multi-part movie-only encode could cause
a "Can't open file: ...\VID_XXX.AVS.264"
- Added code to adjust initial value when using CRF
while resizing to 720p. Should reduce prediction
passes.
- Fixed an error in which sometimes (when PiP exists)
the selection of 720p resizing was not following
through in the encode.
- Made changes to ensure that all 720p encodes held to
BD specs -- especially when converting 29.97 or 25fps
sources (requires framerate doubling).
- Added "AssumeFPS()" to the AVS file when appropriate
to make frame timing more exact.
- Corrected an error in which resizing would not occur
when destination space would not require encoding.
- Added a new setting to the SETUP dialog that will
convert standard definition (SD) sources (480/576)
to 720p. This mode is useful for SAPs that always
output in wide screen mode giving a "stretched"
appearance to SD sources. It may also improve
picture quality on some sources.
- Added "--qpmin=0" to all command lines. This should
reduce the likelihood of undersizing on high bitrate
encodes.
- Updated X264.EXE in zip distribution package to the
latest (r1159) version.
- Other minor corrections and cosmetic fixes.

[chudm]

redoing for the 3rd time braveheart, last night had the same problem with this:

Corrected an error in BATCH mode that could result
in "RebuildFiles() 00075 2202" when output folder
already exists.

will let you know if it works! thx again jdobbs!

[samtroy]

I've gone through the code over-and-over and I can't see any way that an AC3 would be generated unless it is chosen to do so. As for the two instances of each -- that's perfectly normal. If you have selected to reencode AC3 you will have the original (demuxed) and the reencode (@ either 640Kbs or 448Kbs). The reason that is done (e.g. from 640Kbs to 640Kbs) is so other adjustments can be made (filtering, normalization, etc.) in future versions. Today the only adjustment is "AUDIO_AMPLIFY=" which can increase reencoded volume levels.

OK, just to be clear: Even if I choose NOT to reencode AC3 tracks, BD Rebuilder will process the demuxed original AC3 tracks anyway to "amplify" the sound by using nicaudio.dll?

Isn't this bad because reencoding the AC3 tracks will degrade the audio quality? Or is this "amplifying" done without really reencoding the audiodata?

Can this be turned off by any chance? I'm sure some users would like to leave the AC3 tracks completely untouched..

[jdobbs]

OK, just to be clear: Even if I choose NOT to reencode AC3 tracks, BD Rebuilder will process the demuxed original AC3 tracks anyway to "amplify" the sound by using nicaudio.dll?

Isn't this bad because reencoding the AC3 tracks will degrade the audio quality? Or is this "amplifying" done without really reencoding the audiodata?

Can this be turned off by any chance? I'm sure some users would like to leave the AC3 tracks completely untouched..It will reencode by default. You can decide not to reencode by choosing to keep the original AC3. You do that by selecting "Do not reencode AC3" in the SETUP dialog.

Be careful, though, because deciding to keep anything other than standard AC3 at 640Kbs or below -- you are violating the AVCHD specification for movie-only reencodes.

In most cases the reencode is not distinguishable from the original.

[samtroy]

It will reencode by default. You can decide not to reencode by choosing to keep the original AC3. You do that by selecting "Do not reencode AC3" in the SETUP dialog.

Be careful, though, because deciding to keep anything other than standard AC3 at 640Kbs or below -- you are violating the AVCHD specification for movie-only reencodes.

In most cases the reencode is not distinguishable from the original.

Thanks for your answer but I think we have some kind of misunderstandig here:

I *always* select not to reencode the AC3 track because I want to keep the original, untouched 640kbs AC3 tracks (when available).

But BD Rebuilder *always* does process the demuxed AC3 files anyway. They are written again to the workfolder with nicaudio.dlls amplify-settings applied. Which means they are now modified and not untouched anymore. Those new, modified AC3 files are also used at the end for the final muxing. Even if I have chosen not to re-encode AC3 tracks. I have checked with different movies.

My question was if this (automatic) AC3 amplifying step can be turned off, maybe by some ini-setting? Or some clarification on how this amplifying is done by nicaudio.dll: By completely re-encoding or only by modifying some volume values in the AC3 file and keeping the core audiodata untouched?

[samtroy]

Strange VC-1 encoding errors

I've noticed that with VC-1 sources there are strange picture distortions in certain scenes. The effect appears only in *very grainy scenes* (like the whole movie "300" is shot). The picture then has some kind of pulsating horizontal distortions. As soon as these grainy scenes are over the problem is completely gone.

This problem is absolutely *not* there with AVC/H.264 movies! I've already tried different VC-1 de-coders: ffdshow's internal one and WMP9. But both show the same problem :mad:. So it's apparently not a decoding issue..

I suspect it has something to do with x264's encoding. As if x264 has problems to properly encode VC-1 movies with very grainy scenes in it. Maybe it doesn't distribute the bitrate correctly.. ??

Could BD Rebuilder's encoding settings for x264 have something to do with it? Or has anyone had similar problems like this with VC-1 movies?

Latest BDR version, Win7 (also tried Vista), movie-only, BD9, no resizing, 2-pass high quality. Like I said, H.264 sources are perfectly OK.

Thanks for any help!

[jdobbs]

Strange VC-1 encoding errors

I've noticed that with VC-1 sources there are strange picture distortions in certain scenes. The effect appears only in *very grainy scenes* (like the whole movie "300" is shot). The picture then has some kind of pulsating horizontal distortions. As soon as these grainy scenes are over the problem is completely gone.

This problem is absolutely *not* there with AVC/H.264 movies! I've already tried different VC-1 de-coders: ffdshow's internal one and WMP9. But both show the same problem :mad:. So it's apparently not a decoding issue..

I suspect it has something to do with x264's encoding. As if x264 has problems to properly encode VC-1 movies with very grainy scenes in it. Maybe it doesn't distribute the bitrate correctly.. ??

Could BD Rebuilder's encoding settings for x264 have something to do with it? Or has anyone had similar problems like this with VC-1 movies?

Latest BDR version, Win7 (also tried Vista), movie-only, BD9, no resizing, 2-pass high quality. Like I said, H.264 sources are perfectly OK.

Thanks for any help!Not likely -- X264 doesn't know or care about the source of the frames, they are delivered by AVISYNTH as decoded frames. Have you looked at the source by playing back through the AVS files. My guess would be that the error is there before the encode.

But BD Rebuilder *always* does process the demuxed AC3 files anyway. They are written again to the workfolder with nicaudio.dlls amplify-settings applied. Are you using BATCH mode? I have done many, many encodes keeping the original -- and it never reencodes for me. It just remuxes with that AVC encode. Give me an example source upon which it happens and the contents of the INI file and I'll do the same encode on mine. If it happens I'll fix it -- but it hasn't happened yet.

[samtroy]

Are you using BATCH mode? I have done many, many encodes keeping the original -- and it never reencodes for me. It just remuxes with that AVC encode. Give me an example source upon which it happens and the contents of the INI file and I'll do the same encode on mine. If it happens I'll fix it -- but it hasn't happened yet.

I'm not saying it re-ENCODES, it just re-WRITES it and does something to it, maybe reencoding, maybe not. No, no batch mode. Also always deleted all relevant ini-files or log data produced by BDR to have a "clean start" ("do not reencode AC3" is checked of course).

I'm sending you the latest log/ini-files and more detailed info via private message.

[Furiousflea]

I'm not saying it re-ENCODES, it just re-WRITES it and does something to it, maybe reencoding, maybe not. No, no batch mode. Also always deleted all relevant ini-files or log data produced by BDR to have a "clean start" ("do not reencode AC3" is checked of course).

I'm sending you the latest log/ini-files and more detailed info via private message.

It would have to re-encode it. If you modify a compressed audio stream in any way it will be re-encoded. Much like if you alter a jpeg image and save it as a jpeg again.

I think you might be forgetting that BDRB ALWAYS encodes AC3 audio no matter what - it doesn't mean that you will be using that recoded stream when muxing though.

For proof load the m2ts in eac3to and check if "dialogue normalization" is present. If it is, that means it hasn't been touched since BDRB strips it when it re-encodes.

[Capsbackup]

I can also confirm on a movie only backup to BD5 that BD-RB does not reencode the AC3 and does remux this original demuxed AC3 back into the new reencoded .m2ts.
I have only one AC3 file in my WORKFILES folder.
For proof load the m2ts in eac3to and check if "dialogue normalization" is present. If it is, that means it hasn't been touched since BDRB strips it when it re-encodes.
Log after running eac3to does say:
M2TS, 1 video track, 1 audio track, 1 subtitle track, 2:23:46, 24p /1.001
1: h264/AVC 1080p24 /1.001 (16:9)
2: AC3, English 5.1 channels, 640kbps, 48khz, dialnorm: -27dB
3:Subtitle (PGS), English

[jdobbs]

I can also confirm on a movie only backup to BD5 that BD-RB does not reencode the AC3 and does remux this original demuxed AC3 back into the new reencoded .m2ts.
I have only one AC3 file in my WORKFILES folder.

Log after running eac3to does say:
M2TS, 1 video track, 1 audio track, 1 subtitle track, 2:23:46, 24p /1.001
1: h264/AVC 1080p24 /1.001 (16:9)
2: AC3, English 5.1 channels, 640kbps, 48khz, dialnorm: -27dB
3:Subtitle (PGS), English Same thing I'm seeing. I just did another disc with an AC3 source with this latest release to be sure. It certainly looks to be working correctly to me.
I think you might be forgetting that BDRB ALWAYS encodes AC3 audio no matter what - it doesn't mean that you will be using that recoded stream when muxing though.It used to do that -- but now it just skips over the encode step when the original audio is being kept.

[samtroy]

Thanks for the input. This is driving me crazy. I think I'm going to reinstall my OS (Win7 32bit) first.. and then check again.. :cool:

[GaPony]

Maybe you should step back to XP or Vista until jdobbs has a chance to ensure compatibility with Windows 7, once its officially released.

[jdobbs]

Thanks for the input. This is driving me crazy. I think I'm going to reinstall my OS (Win7 32bit) first.. and then check again.. :cool: I can't for the life of me figure why it would act differently on Win7. The entire decision is based on the setting in the INI.

In the version I posted yesterday I added an entry in the log that shows the settings at the time the encode is started. If you run into it with that one please post the log so I can tell whether the setting is being read properly from the INI.

Where did you install BD Rebuilder (the path)? I worry that Win7 may have some of the quirks that were there with Vista when it was first released -- and when the INI is being read, it is from a virtual location rather than the true one. If you installed in the "Program Files" directory that may be the case.

[Brian5970]

1st post on the BD-Rebuilder, but I've been doing "movie only" most of the time. Works great, and the improvements are great! Right on Jdobbs! I find I do need to activate the "stricter AVC" option for the discs to play on my samsung player.

In regard to Windows 7 - I'm running 64 bit ultimate and just re-installed the avi-synth and matroska. VERY important to have the vc-1 turned off on ffdshow! It does work good with that WMV11. The boys at Microsoft have come up with a pretty nifty codec for HD playback on the media player here - uses almost no CPU to run a movie in HD. I was impressed. It also appears that win7 does have the same vista-like hang-up with the program being installed on the same drive as the os.

Hope this helped...

[samtroy]

@jdobbs

Before I run some more tests, could you be so kind and tell me what this file from the workfolder is for:

AUD_00000_4352.AVS

#Created by BD Rebuilder - v0.29.05 (beta)
LoadPlugin("D:\BD Rebuilder\tools\nicaudio.dll")
audio=NicAC3Source("00000.track_4352.ac3").Amplify(1.2)
audio = (AudioChannels(audio) > 6) ? GetChannel(audio,1,2,3,4,5,6) : audio
audio

What's exactly happening there?

[jdobbs]

@jdobbs

Before I run some more tests, could you be so kind and tell me what this file from the workfolder is for:

AUD_00000_4352.AVS

#Created by BD Rebuilder - v0.29.05 (beta)
LoadPlugin("D:\BD Rebuilder\tools\nicaudio.dll")
audio=NicAC3Source("00000.track_4352.ac3").Amplify(1.2)
audio = (AudioChannels(audio) > 6) ? GetChannel(audio,1,2,3,4,5,6) : audio
audio

What's exactly happening there? That file is the AVISYNTH script that is used when/if audio reencoding is done. It is always created for any audio stream that has been selected, even if the audio isn't being reencoded. The number (4352) is the Packet Identifier (PID) for that specific audio stream (within the original M2TS file). The "00000" indicates which M2TS contains that stream ("00000.M2TS).

You can open it with Media Player Classic or Microsoft Media Player and it will convert the AC3 to PCM and play it back. When reencoding, this script feeds that audio as PCM to the AC3 encoder.

[samtroy]

OK, thanks. That's what I was thinking.

Funny thing is that I demuxed the AC3 audio from BD Rebuilder's BD9 output and compared it with the freshly demuxed AC3 track from the original movie. Result: They were NOT identical (I used AC3Tool). The BDR AC3 had a different dialog level (-31db compared to -27db on the original) and the Mixlevel info was missing completely. So it has been re-encoded using that Avisynth script! Although the AC3 re-encode setting in BDR was turned off (I checked 100 times)!

But I'm doing new tests with a different movie on a freshly installed OS as we speak..

[drjake]

I tried to do a BD25 Movie Only back up of Coraline (VC-1) and failed. I have successfully done other movie only backups, but with this one the Disc immediately stops after the player or Windvd reads it. I burned the disc with Imgburn. If I play the mts file with media player it works fine. However, if I try to play the disc, my BD35 and Windvd correctly identify the disc as Blu-Ray but it gets no further than that. On Windvd, once it reads the disc, the player says "Stop" and it won't go any further. The BD35 just gets no further than identifying the disc as a BD. Any thoughts as to what is going on?

[nurbs]

The BDR AC3 had a different dialog level (-31db compared to -27db on the original) and the Mixlevel info was missing completely.
Different dialog normalization doesn't mean it was reencoded. It's just a tag that can be changed. Most software changes it to -31db (= no normalization) by default for various reasons I don't want to list now (look in the audio subforum if you are interested). The same may be true for the mixlevel, but I'm not sure about that.

[samtroy]

Different dialog normalization doesn't mean it was reencoded. It's just a tag that can be changed. Most software changes it to -31db (= no normalization) by default for various reasons I don't want to list now (look in the audio subforum if you are interested). The same may be true for the mixlevel, but I'm not sure about that.

Of course you are right. But it proves that the used AC3 for the final muxing was not the original, untouched one (like it should have been). And just like jdobbs explained, the AviSynth file in question feeds the AC3 as PCM to the AC3 encoder (even with an amplify command added!). Very suspicious indeed ;)..

But like I said, maybe its an problem on my end. I'm doing some tests right now..

[TRONDROM]

Need help. I just want to make sure that I'm using the correct BD-RB Setup settings for a BD-25 encode. I've done about 15 so far and ten of them have come out fine, but five will not load or play in my Sony BDP-S300. I looked at the BD-Rebuilder notes and I get this error GUI issue, no hWnd returned. I will tell you that since I've updated to the newest version I've haven't had any problem, but just want to make sure that the bottom settings I'm using are the best settings for making a BD-25 full disc copy with DTS audio and one subtitle stream only.

Here are the settings I'm using.

Do not convert DTS to AC3 is checked.
Do not reencode AC3 is checked
Keep HD Audio for BD25 output is checked
Target size is BD-25 is checked

Configuration/INI Settings
[Options]
RESIZE=0
MODE=0
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450
PROCESS_SECONDARY=0
VERBOSE_STATUS=1
SD_CONVERT=0

Is there anything wrong with these settings? I just want DTS English and English subtitles only, want all extras of the Bluray but AC3 sound is fine for the extras.

Just don't understand why some come out okay and others don't.

Also I use AnyDVD HD to remove Region Codes and remove any protection.

[DK]

I find I do need to activate the "stricter AVC" option for the discs to play on my samsung player.


Samsung player dont like AUXDATA folder; strict avchd is a wise move for BD5/9 and depending on the model stay away from booktyping to -rom.

[samtroy]

@jdobbs

OK, I've managed to reproduce the AC3 reencoding error:

First I did an BD5 backup of the movie with only *one* AC3 and subtitle track (eng), AC3 re-encode OFF, movie-only, no batch.

Everything was OK, no re-encoded/new AC3 track in the workfolder. The original AC3 track was used for the final muxing. No problems at all!

But...

Then I did the same movie again but now I changed the following things:

- not one but *two* AC3 and subtitle tracks (eng+ger)
- not BD5 but BD9
- I set MKV_INTERMEDIATE=0

All other settings stayed exactly the same!

And now BD Rebuilder DID re-encode the AC3 tracks although AC3 re-encoding was turned OFF in the settings! I ended up with *four* AC3 files in the workfolder, not two. I even made a screenshot of the processing which I attached for proof!

So there must be a bug somewhere which leads to the unwanted re-encoding of the AC3 tracks. Somewhere in the audio selection maybe, when *more than one* AC3/sub track is selected?

I hope you can trace it down.. :thanks:

[turbojet]

There's been reports of the samsung auxdata issue fixed in the july batch of firmwares for all but the BD-P1000. Are you guys using July or newer firmwares?

Also seems BD-Px600 series play mkv/mp4 with a firmware update.


Thanks jdobbs for the assumefps, now eac3to doesn't throw errors and panasonic/samsung 24p may just work now. It should be safe to remove --fps from the x264 command if you want, it has no effect either way.

Also I see that 20000 is max bitrate for BD25 is that right?
If so it takes over 2.5 hours of video\audio to fill a BD25 which could be the cause of the undersizing reports.

[Capsbackup]

@jdobbs;
I am trying to do a full movie backup to BD-25, and test the new option to convert SD to HD (720p). When I select this box and select save changes, the box does not stay checked/selected.

EDIT:
The INI does seem to get the call though, SD_CONVERT=1.
If I close BD-RB, then reopen, box is not checked, but INI still says SD_CONVERT=1.
If I open BD-RB, select the box, then deselect the box, click save changes, then the INI says SD_CONVERT=0.
So appears to be working in the INI just not the GUI. :(

[Sn8kbordin]

@skylab1

Hi!

What version of "AnyDVDHD" did you use?

I ask because according to postings at the SlySoft forum, a proper rip requires the use of v.6.5.8.1 beta...

The current one is version 6.5.8.2, 2009-09-10.
Is this one good?

[setarip_old]

@Sn8kbordin

Hi!The current one is version 6.5.8.2, 2009-09-10. Is this one good?Logically, yes - unless a new bug was introduced with the new beta.

The only way to be sure is to try it ;>}

[jc243]

Great Work.

I have a project with multiple audio, and only select those who wanted to randomly deleting some, on the top menu does not work when I select that I want or to select another of the erased this works.

Example

Select French and Spanish is heard and if I select Spanish it does not sound.

Is possible add a blank audio on delete track?

[jdobbs]

Need help. I just want to make sure that I'm using the correct BD-RB Setup settings for a BD-25 encode. I've done about 15 so far and ten of them have come out fine, but five will not load or play in my Sony BDP-S300. I looked at the BD-Rebuilder notes and I get this error GUI issue, no hWnd returned. I will tell you that since I've updated to the newest version I've haven't had any problem, but just want to make sure that the bottom settings I'm using are the best settings for making a BD-25 full disc copy with DTS audio and one subtitle stream only.

Here are the settings I'm using.

Do not convert DTS to AC3 is checked.
Do not reencode AC3 is checked
Keep HD Audio for BD25 output is checked
Target size is BD-25 is checked

Configuration/INI Settings
[Options]
RESIZE=0
MODE=0
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450
PROCESS_SECONDARY=0
VERBOSE_STATUS=1
SD_CONVERT=0

Is there anything wrong with these settings? I just want DTS English and English subtitles only, want all extras of the Bluray but AC3 sound is fine for the extras.

Just don't understand why some come out okay and others don't.

Also I use AnyDVD HD to remove Region Codes and remove any protection. I would get rid of the "SUBS_TO_KEEP=eng;" and "SUBTITLE_TRACK_LIMIT=1". Sometimes the PGS's are used for other functions. In most cases it's best (especailly in BD-25) to keep all subtitles.

[jdobbs]

There's been reports of the samsung auxdata issue fixed in the july batch of firmwares for all but the BD-P1000. Are you guys using July or newer firmwares?

Also seems BD-Px600 series play mkv/mp4 with a firmware update.


Thanks jdobbs for the assumefps, now eac3to doesn't throw errors and panasonic/samsung 24p may just work now. It should be safe to remove --fps from the x264 command if you want, it has no effect either way.

Also I see that 20000 is max bitrate for BD25 is that right?
If so it takes over 2.5 hours of video\audio to fill a BD25 which could be the cause of the undersizing reports.The maximum average bitrate for BD25 should be set to 35000 with a the maximum peak bitrate is 40000. But I'll make sure I haven't screwed it up. I changed it once (in several places) to 20000/25000 to accommodate moving to level 4.0 before the new "--slices" option was added to X264 -- it's possible I may have missed changing it back somewhere. I'll take a look at it.

[Edit] Yep. The maximum was set to 20000. Actually I think I did that a long time ago... I'll change it for the next release, but I'll have to figure out a good tradeoff. I was being cautious because the maximum combined bitrate for all streams (primary, secondary, audio and PGS) has to stay under 48000 Kbs. With a 5.1 LPCM audio up around 6MBs for a track and a secondary video track at 8Mbs it can gets a little risky at 35000/40000.

[jdobbs]

@jdobbs;
I am trying to do a full movie backup to BD-25, and test the new option to convert SD to HD (720p). When I select this box and select save changes, the box does not stay checked/selected.

EDIT:
The INI does seem to get the call though, SD_CONVERT=1.
If I close BD-RB, then reopen, box is not checked, but INI still says SD_CONVERT=1.
If I open BD-RB, select the box, then deselect the box, click save changes, then the INI says SD_CONVERT=0.
So appears to be working in the INI just not the GUI. :( There's probably a syntax error in the line where it is read in SETUP. I'll look at it.

[jefrey]

I have a strange playback issue with le dobermann bluray. i have to skip the playback several times (intro, and other titles.)..until Title 3 starts to play, and that is the movie itself.
and the second issue is, thats extremly undersized:( 16gb @20000kbs max bitrate.
:confused:

[drjake]

I tried again with Coraline forcing a reencode to see if it had something to do with the VC-1. It still will not play in any standalone nor in Windvd. As soon as you press play it immediately stops and shows "Stop" on the screen. This is the only BD that has not worked for me. Here are my log file and ini files:

-----------------------
[10:53:51] BD Rebuilder v0.29.04 (beta)
- Source: CORALINE
- Input BD size: 19.28 GB
- Approximate total content: [01:40:36.238]
- Target BD size: 22.46 GB
- MOVIE-ONLY mode enabled
[10:53:51] PHASE ONE, Encoding
- [10:53:51] Extracting A/V streams [VID_00010]
- [11:28:56] Reencoding: VID_00010 (1 of 1)
[11:37:46]PHASE ONE complete
[11:37:46]PHASE TWO - Rebuild Started
- [11:37:46] Rebuilding BD file Structure
[11:58:21] - Encode and Rebuild complete
- WORKFILES folder removed.
[11:58:21]JOB: CORALINE finished.


[Options]
RESIZE=0
MODE=1
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
FORCE_ENCODE=1
[Paths]
SOURCE_PATH=C:\CORALINE\CORALINE\
WORKING_PATH=C:\TEMP\

Anybody have any ideas what is going on here.

I tried to do a BD25 Movie Only back up of Coraline (VC-1) and failed. I have successfully done other movie only backups, but with this one the Disc immediately stops after the player or Windvd reads it. I burned the disc with Imgburn. If I play the mts file with media player it works fine. However, if I try to play the disc, my BD35 and Windvd correctly identify the disc as Blu-Ray but it gets no further than that. On Windvd, once it reads the disc, the player says "Stop" and it won't go any further. The BD35 just gets no further than identifying the disc as a BD. Any thoughts as to what is going on?

[jdobbs]

I have a strange playback issue with le dobermann bluray. i have to skip the playback several times (intro, and other titles.)..until Title 3 starts to play, and that is the movie itself.
and the second issue is, thats extremly undersized:( 16gb @20000kbs max bitrate.
:confused: See the post a few back.

If it is as 20000Kbs -- any additional bitrate would almost assuredly be wasted anyway. The quality is important, not the size -- and the two don't always correlate. A good test would be to look in the stats files -- and I think you'll find QP values in the "under 16" range. That is an indicator of a virtually perfect backup.

I'm not aiming at you personally, but I have serious issues with reports that are looking at output size or say "it didn't fill the disc!"... in most cases it is meaningless. I'll be happy to add a zero filled file to the output to make it 24GB -- as in most cases that will do about the same to improve the quality as adding bitrate above 20000 Kbs.

[Capsbackup]

Just finished testing a full movie backup to BD-25 of The Shining with BD-RBV02905, with the option to convert SD to HD (720p), burned to BD-RE for playback on my BX-1.
I have to say that the quality of the 480i extras upconverted to 720p are absolutely perfect compared to the original disc. I was skeptical that upconverting could improve the original, and probably has not, but there is definately no loss from the original and visually it is equivalent! For a pretty old movie, I am impressed.
Another great option jdobbs, and your program has developed quite nicely. A big :thanks:

[TRONDROM]

I would get rid of the "SUBS_TO_KEEP=eng;" and "SUBTITLE_TRACK_LIMIT=1". Sometimes the PGS's are used for other functions. In most cases it's best (especailly in BD-25) to keep all subtitles.

All right, will do J....thanks for your help and your amazing program....:smile:

[setarip_old]

@jdobbs

Hi!

It appears that the newer methodology for creating HDDVD-compliant files ("HDDVD_COMPLIANT=1" in .INI) produces less compliant (Read as, "no longer works completely when used with "multiAVCHD") files than did the earlier concept of directly adding to the .INI two "custom" lines plus, if I remember correctly, a specific line for "ENCODE_QUALITY=" (was it "6"?) and, possibly, "FORCE_ENCODE=1".

I confirmed that "multiAVCHD" is not the cause of this, by using an earlier version of BD-RB that utilized the "custom" lines, etc. to compress the same BluRay to "movie-only" again - and "multiAVCHD" properly and successfully processed and converted it to HDDVD (Burned DVD5 plays perfectly on my Toshiba HDDVD standalone).

I also tried replacing "HDDVD_COMPLIANT=1" with the "custom" lines, etc. with both v.29.04 nd v.29.05. Both efforts resulted in the same previously described failure.

Your thoughts please?

[Sharc]

@jdobbs
v0.29.05. Movie Gladiator. Resize to 720p. Full backup.
Main feature is split into many .m2ts. Some of these are still not resized to 720p but stick to the original 1080p.
In one case, instead of starting a crf prediction the log just indicates "Reencoding: ....Pass 1 of 1". In the second case the crf prediction runs normally but the encode remains at 1080.
Any thoughts?

[jdobbs]

@jdobbs

Hi!

It appears that the newer methodology for creating HDDVD-compliant files ("HDDVD_COMPLIANT=1" in .INI) produces less compliant (Read as, "no longer works completely when used with "multiAVCHD") files than did the earlier concept of directly adding to the .INI two "custom" lines plus, if I remember correctly, a specific line for "ENCODE_QUALITY=" (was it "6"?) and, possibly, "FORCE_ENCODE=1".

I confirmed that "multiAVCHD" is not the cause of this, by using an earlier version of BD-RB that utilized the "custom" lines, etc. to compress the same BluRay to "movie-only" again - and "multiAVCHD" properly and successfully processed and converted it to HDDVD (Burned DVD5 plays perfectly on my Toshiba HDDVD standalone).

I also tried replacing "HDDVD_COMPLIANT=1" with the "custom" lines, etc. with both v.29.04 nd v.29.05. Both efforts resulted in the same previously described failure.

Your thoughts please? Nothing has changed at all except the adding of "--slices 4" to all command lines. Could that be it?

Other than that, it uses the settings I was asked to use... you'll have to ask someone else what is correct -- as I don't have HD-DVD. It's a standard that is as dead as a doornail. If you can tell me what you want the settings to be I can set them. That's about the extent of my involvement (and as far as I plan to ever get involved).

By the way, the custom feature hasn't changed either.

[jdobbs]

@jdobbs
v0.29.05. Movie Gladiator. Resize to 720p. Full backup.
Main feature is split into many .m2ts. Some of these are still not resized to 720p but stick to the original 1080p.
In one case, instead of starting a crf prediction the log just indicates "Reencoding: ....Pass 1 of 1". In the second case the crf prediction runs normally but the encode remains at 1080.
Any thoughts? The "1 of 1" is normal. Extremely small segments can sometimes fail if you try to do two passes so it does a standard setting CRF pass.

I'll take a look at the 1080p thing...

[Sharc]

The "1 of 1" is normal. Extremely small segments can sometimes fail if you try to do two passes... I'll take a look at the 1080p thing...
Sorry, I forgot to mention that I went for One-Pass (crf) Encoding.
The segment was not even really small: 202 MB in the original / reencoded to 63 MB. So it has been reencoded, but not resized to 720p.

[DK]

There's been reports of the samsung auxdata issue fixed in the july batch of firmwares for all but the BD-P1000. Are you guys using July or newer firmwares?

Also seems BD-Px600 series play mkv/mp4 with a firmware update.


I'm using latest 2.02 FW for EU on my 1600.
Havent tested "Auxdata" present (if that's what you were driving at?) but -ROM booktyped media still does NOT work here.

And yes, MKV plays fine, i havent tested MP4 before because i only knew about MKV support along with YouTube and NTFS for external drives, which i really appreciate.

[jefrey]

Yes the size at that bitratevalue doesnt matter, i was just surprised about the size ;)