BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Thanks for the new version especially sup resize support and no .ini for easier updating.

I see that the playability issue that have been brought up by many still exist since movie only is still using --bluray if you are confused on the matter see this post (http://forum.doom9.org/showthread.php?p=1286079#post1286079) which should revert it back to how movie only was before the tsmuxer update and allow more software (hardware?) players to play both movie only and full backups.

I also found a few new bugs:
- DTS gets converted to AC3 even if its checked not to
- AC3 gets converted to AC3 even if its checked not to
- HD audio gets converted to AC3 even if its checked not to
- while its really a tsmuxer bug which they know about and are fixing, BD-RB can work around keeping resized sups most original by using: bottom-offset=0,font-border=0

Also a few requests that should be fairly simple but they affect quite a few peoples usability:
- like DVD-RB by default don't deinterlace (deinterlace as option?) and use x264.exe --tff to keep the motion smooth, retain all the video data (fielddeinterlace removes half the lines) and interlaced compresses better.
- increase max bitrate to prevent major undersize. 25 mbps with DVD has been very well tested successfully with RipBot264, BD should support 50 mbps video bitrate but maybe play it safe with 40 mbps
- use mkv as default x264 output and have 264_INTERMEDIATE ini option since 264 has issues with some software players and very well could be the reason for the Panasonic 24p issue

Any chance of any of these in a not so distant future version? I'll look at the audio retention bugs, I may have hacked something up when I added the LPCM code. You did test it with BD-25 output, right? HD isn't supposed to be retained with BD-9/5.

I'm not sure what you mean with the sups -- the ones I tested at 1280x720 look perfect.

As for the bitrate -- you're way to high. Even though the BD spec allows video bitrates up to 40Mbs (on BD media), it also has a maximum bitrate of 48Mbs for all streams combined. If you retain a couple of HD audio streams along with the video you'll bust the spec very easily. 25Mbs is plenty of bitrate for HD/AVC. As for BD-9 -- I really don't care what has been tested -- the spec doesn't allow 25Mbs, and I won't support it. I don't need any more incompatibilities floating around, the player spectrum is non-standard enough as it is.

As for using MKV instead of 264 -- there are some very severe problems imposed when I do that (if I recall correctly, multipart sources won't work anymore). It seems the only player with issues related to that is the Panasonic... which, as I've said, should be fixed by Panasonic, not BD-RB. When every other brand works correctly it make it pretty clear where the issue is.

[jdobbs]

I also found a few new bugs:
- DTS gets converted to AC3 even if its checked not to
- AC3 gets converted to AC3 even if its checked not to
- HD audio gets converted to AC3 even if its checked not toAre you sure you have your setup right? I just tried a DTS source and it worked correctly and did not convert it to AC3 when it was checked.

[Update] Same thing with AC3. It worked like it was supposed to.

[Update] Ok. I have done several of them now and they all work correctly... I have to assume you were mistaken.

[MikeyBK]

For movie only back-ups played back on PS3s, you still need to set the 'Stricter AVC-HD Compliance' in order for proper playback in PS3s....
either setting back-ups plays perfectly fine on my Sony BDP-BX1.

This is in reference to BD-RB v0.21.01

[turbojet]

I'll look at the audio retention bugs, I must have hacked something up when I added the LPCM code. You did test it with BD-25 output, right? HD isn't supposed to be retained with BD-9/5.

Yes however it could very well be the very short source I'm using to test. I'm using a 1 minute clip with DTS-HD, TrueHD, and 640 kbps AC3 and target output set to BD25. All audio gets encoded to 448 or 640 kbps depending on 'use 640 kbps for encoding AC3' which is the only audio option that has any effect in this case. I've tested it on x64 versions or win7/vista/xp. However v20.09 and 20.05 show the same behavior but I remember being able to keep DTS and AC3 without encoding. I'm thinking it might be something to do with the size of the source. Can you shine any light on this?

As for the bitrate -- you're way to high. Even though the BD spec allows video bitrates up to 40Mbs (on BD media), it also has a maximum bitrate of 48Mbs for all streams combined. If you retain a couple of HD audio streams along with the video you'll bust the spec very easily. 25Mbs is plenty of bitrate for HD/AVC. As for BD-9 -- I really don't care what has been tested -- the spec doesn't allow 25Mbs, and I won't support it. I don't need any more incompatibilities floating around, the player spectrum is non-standard enought as it is.

Oh I thought I read somewhere BD spec is 50 mbps video, 62.5 mbps combined. It's not that x264 really needs more than 25 mbps bitrate but it will prevent people from reporting major undrersize as a bug. As we already know how close BD players handle the AVCHD spec I think testing is the only real way to go as much of a hassle as it sounds.

As for using MKV instead of 264 -- there are some very severe problems imposed when I do that (if I recall correctly, multipart sources won't work anymore). It seems the only player with issues related to that is the Panasonic... which, as I've said, should be fixed by Panasonic, not BD-RB. When every other brand works correctly it make it pretty clear where the issue is.

Ya I reported that issue with mkv appending but I did the same problematic seamless branching BD and another one within the past month and it worked fine. While it's not in the changelog tsmuxer must have fixed the issue. You can also add MPC and Arcsoft TMT2/TME players to the list of players that won't play BD-RB output correctly. I think the issue goes beyond the x264 .264 output as RipBot264 uses .264 output and it works fine for all these players. But using mkv output with BD-RB fixex MPC and Arcsoft with panasonic yet TBD but I've never had an issue with Panasonic BD30 and 24p using mkv or RipBot264 output.

[bassnut]

Thanks for the update Jdobbs ........ Much aprieciated. Will give it a run tonight and see how it handles the LPCM which is what I ahve been waiting for. I can't do it today but a donation will be forth coming soon as I can get around to it these 16 hour days tend to eat up allot of my time ....... what I need is about another 6 hours added to the day to get caught up.

[jdobbs]

Yes however it could very well be the very short source I'm using to test. I'm using a 1 minute clip with DTS-HD, TrueHD, and 640 kbps AC3 and target output set to BD25. All audio gets encoded to 448 or 640 kbps depending on 'use 640 kbps for encoding AC3' which is the only audio option that has any effect in this case. I've tested it on x64 versions or win7/vista/xp. However v20.09 and 20.05 show the same behavior but I remember being able to keep DTS and AC3 without encoding. I'm thinking it might be something to do with the size of the source. Can you shine any light on this? Hmmm... I can't think of a reason why size would make it act differently. I'll create some short test clips and see what it does.

[turbojet]

Hmmm... I can't think of a reason why size would make it act differently. I'll create some short test clips and see what it does.

OK thanks. I'm running a full length movie encode right now to see if it works.

Do you still need the pictures from my previous post concerning the sups? Feel free to remove the links if you don't.

Also found a bug when extracting streams from Slumdog Millionaire region A in movie only mode keeping DTS-HD and 3 subs, stripping 3x AC3 audio
[19:00:25] - Failed to retrieve audio, aborted

It works OK with v0.20.09

[jdobbs]

OK thanks. I'm running a full length movie encode right now to see if it works.

Do you still need the pictures from my previous post concerning the sups? Feel free to remove the links if you don't.

Also found a bug when extracting streams from Slumdog Millionaire region A in movie only mode keeping DTS-HD and 3 subs, stripping 3x AC3 audio
[19:00:25] - Failed to retrieve audio, aborted

It works OK with v0.20.09 No. I see what you mean. I've changed the settings for the next release.

I have Slumdog Millionaire and have backed it up successfully in the past -- I'll do it again. The only thing I could think of is that it might be the newer TSMUXER.

How long does it take before it hits the error? It seems to be extracting the audio fine on my system.

[Furiousflea]

I'll look at the audio retention bugs, I may have hacked something up when I added the LPCM code. You did test it with BD-25 output, right? HD isn't supposed to be retained with BD-9/5.

I'm not sure what you mean with the sups -- the ones I tested at 1280x720 look perfect.

As for the bitrate -- you're way to high. Even though the BD spec allows video bitrates up to 40Mbs (on BD media), it also has a maximum bitrate of 48Mbs for all streams combined. If you retain a couple of HD audio streams along with the video you'll bust the spec very easily. 25Mbs is plenty of bitrate for HD/AVC. As for BD-9 -- I really don't care what has been tested -- the spec doesn't allow 25Mbs, and I won't support it. I don't need any more incompatibilities floating around, the player spectrum is non-standard enough as it is.

As for using MKV instead of 264 -- there are some very severe problems imposed when I do that (if I recall correctly, multipart sources won't work anymore). It seems the only player with issues related to that is the Panasonic... which, as I've said, should be fixed by Panasonic, not BD-RB. When every other brand works correctly it make it pretty clear where the issue is.

You didn't give your view on retaining the interlaced nature of the source video. :) Apparently BDRB as it is goes against the spec in that regards (29.97p video after encoding not part of standard)

[Furiousflea]

Yes. I tested it on one last night and it worked correctly.

If so....

LEGEND!!!! :)

[turbojet]

No. I see what you mean. I've changed the settings for the next release.

I have Slumdog Millionaire and have backed it up successfully in the past -- I'll do it again. The only thing I could think of is that it might be the newer TSMUXER.

OK thanks, I removed the images.

How long does it take before it hits the error? It seems to be extracting the audio fine on my system.

1% in but I've narrowed it down to a tsmuxer issue when resizing the subs. I reported the issue in the tsmuxer thread. Without resizing everything goes as normal.

Also the full movie encode finished and it kept DTS audio. However does the reencoding audio tracks message need to be in the log in this case?

- [04:04:10] Video Encode complete
- [04:04:10] Reencoding audio tracks
- [04:04:10] Multiplexing M2TS

There also seems to be a bug catching x264 status. It's reproducable by starting an x264 encode in any program. While it's running start a BD-Rebuilder encode and when it starts encoding video it will pickup the progress and speed of the first x264 process. Any chance for a fix by locking to PID or something?

[stef73]

I did not find time to test so far - but has anyone checked the 24p/BD-RB issue with Panasonic's latest 1.5 firmware (out for a week now)??

bundy as ive said before its working on my bd 35 perfectly well with 24p on ive done over 500 blurays and theyve almost all worked but i always tick the stricter avchd, im using a samsung led tv which is brand new got a ps3 60gb that played my backups since november 2007 that suddenly stopped working sp bought panasonic and samsung bdp 1500 which has up to yet played everything too

[Nkotok]

Can anybody tell me what is the benefit of not checking "Stricter AVCHD compliance"? Does it take less time if you don't check it?
I never checked it as I was told not to and as result my reencodes don't play in 24p on Panasonic. Somebody here said that he checked it and the result played fine in 24p.

So why couldn't the option be checked by default, so most people get better results and those who really don't need it, could uncheck it. Or a good explanation about the purpose of this option would be nice (in some .txt file or something).

[Bundy00]

You are talking like there is only one model of Panasonic players and only one version of FW. What 1.5. are you talking about? BD30, for example, is on 2.8 now.

Sorry! You're right. :o
I meant 1.5 for BD35 (the european version).

[Lif3styl3]

Sorry! You're right. :o
I meant 1.5 for BD35 (the european version).

i've tested the new 1.5 on my bd-55.

Git the same 24p problem.

Know i will give it a try with strict avcd enabled.

Please explain. Right now you should be able to keep DTS-HD if you are encoding to BD-25. If not, the issue is size -- if you kept HD audio on BD-9 the picture would suffer terribly.

i started reencoding of transporter 3 trying to get the hd audio.
WIll report the result tomorrow.

That's confusing as hell... since both of the software packages use TSMUXER to do the muxing... I can't imagine what setting could be changed that would cause it work.

regarding to the 24p issue on my panasonic, this meta informations are creating a working 24p bd disk through tsmuxxer,..
if u would tell me the meta file ypu are using to create an output via tsmuxxer, i will try these settings with tsmuxxer and would report my results on my bd-55

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000;00:08:03.250;00:17:15.166;00:24:33.250;00:41:44.416;00:48:54.541;01:06:40.458;01:20:40.833;01:33:51.166 --vbv-len=500
V_MS/VFW/WVC1, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts", fps=24, track=4113, mplsFile=00009
A_DTS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts", track=4352, lang=deu, mplsFile=00009
#A_DTS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts", track=4353, lang=eng, mplsFile=00009
#A_DTS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts", track=4354, lang=eng, mplsFile=00009
S_HDMV/PGS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts",bottom-offset=24,font-border=2,text-align=center,video-width=1920,video-height=1080,fps=24, track=4608, lang=deu, mplsFile=00009
#S_HDMV/PGS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts",bottom-offset=24,font-border=2,text-align=center,video-width=1920,video-height=1080,fps=24, track=4609, lang=eng, mplsFile=00009
S_HDMV/PGS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts",bottom-offset=24,font-border=2,text-align=center,video-width=1920,video-height=1080,fps=24, track=4610, lang=deu, mplsFile=00009
#S_HDMV/PGS, "C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00054.m2ts"+"C:\Users\Lifestyle\Documents\DVDFab\ISO\TRANSPORTER_3_BD\BDMV\STREAM\00000.m2ts",bottom-offset=24,font-border=2,text-align=center,video-width=1920,video-height=1080,fps=24, track=4611, lang=eng, mplsFile=00009

[GaPony]

Can anybody tell me what is the benefit of not checking "Stricter AVCHD compliance"? Does it take less time if you don't check it?
I never checked it as I was told not to and as result my reencodes don't play in 24p on Panasonic. Somebody here said that he checked it and the result played fine in 24p.

So why couldn't the option be checked by default, so most people get better results and those who really don't need it, could uncheck it. Or a good explanation about the purpose of this option would be nice (in some .txt file or something).

I ALWAYS check the block for "stricter compliance..." for my movie only copies to BD9 and they ALWAYS playback in 24p mode on my PS3, Sony 550, and Samsung BD-P2500 players. This setting has no effect on Full Movie Copies, which is fine with me, as I only put those on BD25 discs.

For movie only copies, I can see no benefit to not checking the box, but it depends on the brand/model SAP you're using. Since you're not having any success up to now, there certainly isn't any downside to at least trying a copy with that option checked (enabled).

[jdobbs]

There also seems to be a bug catching x264 status. It's reproducable by starting an x264 encode in any program. While it's running start a BD-Rebuilder encode and when it starts encoding video it will pickup the progress and speed of the first x264 process. Any chance for a fix by locking to PID or something? Really? Interesting. I'll fix it.

[jdobbs]

Can anybody tell me what is the benefit of not checking "Stricter AVCHD compliance"? Does it take less time if you don't check it?
I never checked it as I was told not to and as result my reencodes don't play in 24p on Panasonic. Somebody here said that he checked it and the result played fine in 24p.

So why couldn't the option be checked by default, so most people get better results and those who really don't need it, could uncheck it. Or a good explanation about the purpose of this option would be nice (in some .txt file or something). It's really no big deal. In earlier versions of BD-RB this would remove certain directories created by the TSMUXER --blu-ray option. Now it uses the --AVCHD option when it writes movie-only, and TSMUXER does the directory adjustment. Check it if you have a Panasonic.

[Furiousflea]

Just to confirm, LPCM audio retention seems to be working fine on 2 discs I tried (Hellboy\POTC1)

So now ALL HD Audio formats are working :)

[jdobbs]

There also seems to be a bug catching x264 status. It's reproducable by starting an x264 encode in any program. While it's running start a BD-Rebuilder encode and when it starts encoding video it will pickup the progress and speed of the first x264 process. Any chance for a fix by locking to PID or something?Ok I fixed it. I can't for the life of me remember why I didn't originally grab the window handle using the PID instead of the caption. But I'm doing it by PID now and it is working... It'll be posted in the next release.

[jdobbs]

Just to confirm, LPCM audio retention seems to be working fine on 2 discs I tried (Hellboy\POTC1)

So now ALL HD Audio formats are working :)Every now and then I do something right... ;)

[tekmobile]

Just to confirm, LPCM audio retention seems to be working fine on 2 discs I tried (Hellboy\POTC1)

So now ALL HD Audio formats are working :)

Good to know im just doing Tenacious D: The Complete Masterworks Vol2 for about the 5th titme now lol

This is the only disc I have thats giving my SONY BDP-S350 any trouble because on every encode I do it locks my player up in the exact same place mere seconds into the main feature.

Ive tried Movie Only to DVD9, Movie Only to BD25 and full disc to BD25 everyone locks up in the exact same place tried on 3 different versions of BD-RB Re Ripped the disc about 3 times using different versions of AnyDVD HD just cannot figure out whats causing it its been encoded with different versions of x264 and TsMuxer but this time im using the latest tryouts of ffdshow if this does the same I will try RipBot and see if thats the same the original plays perfect both from the disc and decrypted and burned to a BD-RE 50.

All the discs play start to finish like they should in Total Media Theatre its got me stumped and that takes some doing lol.

Ill let you all know how it turns out but I have a feeling it will be the same as all the others.

The source on this disc is only 720p but that shouldn't make a difference.

[Capsbackup]

Every now and then I do something right... ;)

Well since your on a roll, maybe you could venture in to the 1080i VC-1 problem that I and others have mentioned in this thread and it's own thread within DVD-RB. ;)
Anyway, congrats on the latest fixes and new release! I am now testing Casino Royale, NTSC, which has a LPCM audio. :thanks:

[tekmobile]

Well since your on a roll, maybe you could venture in to the 1080i VC-1 problem that I and others have mentioned in this thread and it's own thread within DVD-RB. ;)
Anyway, congrats on the latest fixes and new release! I am now testing Casino Royale, NTSC, which has a LPCM audio. :thanks:

The 1080i VC-1 problem is not really a BD-RB bug its decoder issue all that can be done for now is workarounds.

For me the best option would be to just ignore them and automaticly copy them over no matter what there size.

[jdobbs]

The 1080i VC-1 problem is not really a BD-RB bug its decoder issue all that can be done for now is workarounds.

For me the best option would be to just ignore them and automaticly copy them over no matter what there size. I can do that for BD-25 (first I have to find a way to identify them with a quick scan), but the bitrate is too high and will freeze a BD-9. But VC-1 is only an issue with mixed (hybrid) interlaced/progressive -- as I've had no problem at all with straight interlaced or progressive using WMP11 codecs. I did see that Windows 7 was having issues without the registry patches -- but I'm not even close to worrying about Windows 7 yet.

I may go back remove the defaulted deinterlacing as suggested (or add a hidden option). I need to see how it looks at playback.

[tekmobile]

I can do that for BD-25 (first I have to find a way to identify them with a quick scan), but the bitrate is too high and will freeze a BD-9. But VC-1 is only an issue with mixed (hybrid) interlaced/progressive -- as I've had no problem at all with straight interlaced or progressive using WMP11 codecs. I did see that Windows 7 was having issues without the registry patches -- but I'm not even close to worrying about Windows 7 yet.

I may go back remove the defaulted deinterlacing as suggested (or add a hidden option). I need to see how it looks at playback.

There normally pretty small files usually only used in the extras anyway so its not like it would waste much space and in my experience a full BD compressed to BD-9 looks pretty awful 99% of the time the only real exeption is animation.

Personally I would only allow Full backups to BD-25 and movie only to BD5/9/25

[Lif3styl3]

Hi Jdobbs,
as i told you i have started reenconding of transporter 3.
Again i've got only Dolby Digital.

Info;
-----------------------
[19:41:39] BD Rebuilder v0.21.01 (beta)
- Source: TRANSPORTER_3_BD
- Input BD size: 28,48 GB
- Approximate total content: [01:43:51.583]
- Target BD size: 22,46 GB
- MOVIE-ONLY mode enabled
[19:41:39] PHASE ONE, Encoding
- [19:41:39] Extracting audio/subs [VID_00054]
- [19:49:48] Reencoding: VID_00054 (1 of 2)
- [19:59:22] Extracting audio/subs [VID_00000]
- [19:59:22] Reencoding: VID_00000 (2 of 2)
[04:30:30]PHASE ONE complete
[04:30:30]PHASE TWO - Rebuild Started
- [04:30:30] Rebuilding BD file Structure
[04:47:12] - Encode and Rebuild complete
[04:47:12]JOB: TRANSPORTER_3_BD completed.

Log:
[Status]
LABEL=TRANSPORTER_3_BD
VERSION=v0.21.01 (beta)
SOURCE_SIZE=30581772288
SOURCE_VIDEO_SIZE=30581772288
TARGET_SIZE=24117248000
REDUCTION=.788615119257277
RESIZE_1080=0
AUDIO_TO_KEEP=ger;
SUBS_TO_KEEP=ger;
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=0
COMPLETED=2
REBUILD_COMPLETE=1
[00054]
AUDIO=000
PGS=1000
M2TS_TARGET=53719301
RATE=16369
NSIZE=40495104
FLINK=-1
MLINK=0
[00000]
M2TS_TARGET=24063528699
RATE=25000
AUDIO=100
NSIZE=20279654400
FLINK=0
MLINK=0

Settings:
[Options]
RESIZE=0
MODE=1
TARGET_SIZE=23000
AUDIO_TO_KEEP=ger;
SUBS_TO_KEEP=ger;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
[Paths]
SOURCE_PATH=C:\USERS\LIFESTYLE\DOCUMENTS\DVDFAB\ISO\TRANSPORTER_3_BD\
WORKING_PATH=C:\USERS\LIFESTYLE\DESKTOP\TRANSPORTER_3_BD_2\


MUXOPT --no-pcr-on-video-pid --new-audio-pes --avchd --vbr --custom-chapters=00:00:00.000;00:08:03.250;00:17:15.166;00:24:33.250;00:41:44.416;00:48:54.541;01:06:40.458;01:20:40.833;01:33:51.166 --vbv-len=500
V_MPEG4/ISO/AVC, "C:\USERS\LIFESTYLE\DESKTOP\TRANSPORTER_3_BD_2\WORKFILES\VID_00054.AVS.264"+"C:\USERS\LIFESTYLE\DESKTOP\TRANSPORTER_3_BD_2\WORKFILES\VID_00000.AVS.264", fps=24, insertSEI, contSPS
A_AC3, "C:\USERS\LIFESTYLE\DESKTOP\TRANSPORTER_3_BD_2\WORKFILES\AUD_00054_4352.AC3", lang=deu
S_HDMV/PGS, "C:\USERS\LIFESTYLE\DESKTOP\TRANSPORTER_3_BD_2\WORKFILES\00054.track_4608.SUP",fps=24,lang=deu

If you take a look at this file, the file containing the dts audio wasn't used, but it was created with a size of 3,08GB,

Here the ac3 file was used,....

That's the pic of the DTS-HD XXL selection.
http://www.lifeshammer.de/Unbenannt.jpg

[turbojet]

It's really no big deal. In earlier versions of BD-RB this would remove certain directories created by the TSMUXER --blu-ray option. Now it uses the --AVCHD option when it writes movie-only, and TSMUXER does the directory adjustment. Check it if you have a Panasonic.

Actually currently not enabling strict AVCHD still uses --bluray which only works on a handful of players when it's burned on DVD so it is quite a big deal and there's well over 100 posts in this thread concerning this issue. If it were to use --avchd it would be no difference between the two but strict AVCHD should remove some folders that aren't part of the avchd structure like it used to.

Hopefully next version will fix this issue so 95%+ people will get playable output every time from the program by default. Have you taken a look at this post (http://forum.doom9.org/showthread.php?p=1286079#post1286079) I referred to a few days ago and apply it to the next version?

Ok I fixed it. I can't for the life of me remember why I didn't originally grab the window handle using the PID instead of the caption. But I'm doing it by PID now and it is working... It'll be posted in the next release.

Thanks, just sort of an annoying cosmetic bug.

I may go back remove the defaulted deinterlacing as suggested (or add a hidden option). I need to see how it looks at playback.

Ok but just a reminder to use --tff in x264 command line or else the encode won't be nearly as efficient. Also finding out the field order might be able to be done with an avisynth function like: last.getparity() ? 1 : 0 . It accurately finds the correct field order however I have no idea how to pipe it to x264.

[drmih]

There normally pretty small files usually only used in the extras anyway so its not like it would waste much space and in my experience a full BD compressed to BD-9 looks pretty awful 99% of the time the only real exeption is animation.

Personally I would only allow Full backups to BD-25 and movie only to BD5/9/25

I haven't got a clue what settings you are using but I've now done well over a hundred full backups to bd-9 and I struggle to be able to identify them from the originals.

The last thing people want is to have restrictions placed on them and quite the opposite I would like to have no restrictions but with a warning about quality when selected. For instance I was doing the latest Wallace and Gromit movie and the original is just about 10 Gb yet there is no automatic way of keeping the audio intact and encoding to bd-9 because of a hard coded restriction.

[Capsbackup]

I have successfully backed up Casino Royale, Region A, before but without the HD audio (LPCM), but this attempt with the latest version of BD Rebuilder v0.21.01 (beta) failed. It was trying to encode a 468KB (00061.M2TS) file when it aborted. I was of the belief on BD-25 backups, 100MB or less would be skipped. Is this true? Should BD-RB try to reencode any and all files, even below 1 MB?

EDIT; I think I found out why this happened. I had inserted "MIN_M2TS_SIZE=", below options, but I removed the value/number and left it just like in the quotes. When I completely remove "MIN_M2TS_SIZE=" from below "Options", it then does not try to reencode the less than 100 MB files. So even though I did not have a value after "=", BD-RB sees it as "0MB", and trys to reencode all files. Oh well, I guess operator error on this one. :rolleyes:

Is there a way to recover this partial encode after a mistake such as this? I notice that BD-RB wants to delete the working directory if I change/remove the "MIN_M2TS_SIZE=" .

-----------------------
[17:06:41] BD Rebuilder v0.21.01 (beta)
- Source: CASINO_ROYALE
- Input BD size: 44.05 GB
- Approximate total content: [04:21:07.101]
- Target BD size: 22.46 GB
[17:06:41] PHASE ONE, Encoding
- [17:06:41] Extracting audio/subs [VID_00000]
- [17:16:24] Collecting video information [00000]
- Video: 1920x1080, 23.976fps
- Bitrate: 10,158 Kbs
- [17:16:24] Reencoding: VID_00000, Pass 1 of 2
- [18:56:36] Reencoding: VID_00000, Pass 2 of 2
- [22:42:36] Video Encode complete
- [22:42:36] Reencoding audio tracks
- [22:42:36] Multiplexing M2TS
- [22:58:16] Extracting audio/subs [VID_00001]
- [22:58:57] Collecting video information [00001]
- Video: 1920x1080, 23.976fps
- Bitrate: 8,530 Kbs
- [22:58:57] Reencoding: VID_00001, Pass 1 of 2
- [23:16:42] Reencoding: VID_00001, Pass 2 of 2
- [00:00:07] Video Encode complete
- [00:00:07] Reencoding audio tracks
- [00:00:07] Multiplexing M2TS
- [00:00:29] Extracting audio/subs [VID_00002]
- [00:01:05] Collecting video information [00002]
- Video: 1920x1080, 23.976fps
- Bitrate: 8,561 Kbs
- [00:01:05] Reencoding: VID_00002, Pass 1 of 2
- [00:17:57] Reencoding: VID_00002, Pass 2 of 2
- [00:57:03] Video Encode complete
- [00:57:03] Reencoding audio tracks
- [00:57:03] Multiplexing M2TS
- [00:57:21] Extracting audio/subs [VID_00003]
- [00:57:29] Collecting video information [00003]
- Video: 720x480, 29.970fps
- Bitrate: 2,849 Kbs
- [00:57:29] Reencoding: VID_00003, Pass 1 of 2
- [00:59:41] Reencoding: VID_00003, Pass 2 of 2
- [01:04:47] Video Encode complete
- [01:04:47] Reencoding audio tracks
- [01:04:47] Multiplexing M2TS
- [01:04:52] Extracting audio/subs [VID_00004]
- [01:05:02] Collecting video information [00004]
- Video: 720x480, 29.970fps
- Bitrate: 2,857 Kbs
- [01:05:02] Reencoding: VID_00004, Pass 1 of 2
- [01:08:01] Reencoding: VID_00004, Pass 2 of 2
- [01:14:58] Video Encode complete
- [01:14:58] Reencoding audio tracks
- [01:14:58] Multiplexing M2TS
- [01:15:04] Extracting audio/subs [VID_00005]
- [01:15:14] Collecting video information [00005]
- Video: 720x480, 29.970fps
- Bitrate: 2,842 Kbs
- [01:15:14] Reencoding: VID_00005, Pass 1 of 2
- [01:18:04] Reencoding: VID_00005, Pass 2 of 2
- [01:24:37] Video Encode complete
- [01:24:37] Reencoding audio tracks
- [01:24:37] Multiplexing M2TS
- [01:24:43] Extracting audio/subs [VID_00006]
- [01:24:45] Collecting video information [00006]
- Video: 720x480, 29.970fps
- Bitrate: 2,594 Kbs
- [01:24:45] Reencoding: VID_00006, Pass 1 of 2
- [01:25:23] Reencoding: VID_00006, Pass 2 of 2
- [01:26:33] Video Encode complete
- [01:26:33] Reencoding audio tracks
- [01:26:33] Multiplexing M2TS
- [01:26:35] Extracting audio/subs [VID_00007]
- [01:26:40] Collecting video information [00007]
- Video: 1920x1080, 23.976fps
- Bitrate: 12,207 Kbs
- [01:26:40] Reencoding: VID_00007, Pass 1 of 2
- [01:28:17] Reencoding: VID_00007, Pass 2 of 2
- [01:32:31] Video Encode complete
- [01:32:31] Reencoding audio tracks
- [01:32:31] Multiplexing M2TS
- [01:32:34] Extracting audio/subs [VID_00008]
- [01:32:38] Collecting video information [00008]
- Video: 1920x1080, 23.976fps
- Bitrate: 8,264 Kbs
- [01:32:38] Reencoding: VID_00008, Pass 1 of 2
- [01:34:16] Reencoding: VID_00008, Pass 2 of 2
- [01:37:59] Video Encode complete
- [01:37:59] Reencoding audio tracks
- [01:37:59] Multiplexing M2TS
- [01:38:02] Extracting audio/subs [VID_00009]
- [01:38:09] Collecting video information [00009]
- Video: 1920x1080, 23.976fps
- Bitrate: 14,044 Kbs
- [01:38:09] Reencoding: VID_00009, Pass 1 of 2
- [01:39:51] Reencoding: VID_00009, Pass 2 of 2
- [01:44:31] Video Encode complete
- [01:44:31] Reencoding audio tracks
- [01:44:31] Multiplexing M2TS
- [01:44:35] Extracting audio/subs [VID_00010]
- [01:44:38] Collecting video information [00010]
- Video: 1920x1080, 23.976fps
- Bitrate: 9,945 Kbs
- [01:44:38] Reencoding: VID_00010, Pass 1 of 2
- [01:45:24] Reencoding: VID_00010, Pass 2 of 2
- [01:47:09] Video Encode complete
- [01:47:09] Reencoding audio tracks
- [01:47:09] Multiplexing M2TS
- [01:47:11] Extracting audio/subs [VID_00060]
- [01:47:11] Collecting video information [00060]
- Video: 1920x1080, 23.976fps
- Bitrate: 7,372 Kbs
- [01:47:11] Reencoding: VID_00060, Pass 1 of 2
- [01:47:32] Reencoding: VID_00060, Pass 2 of 2
- [01:47:55] Video Encode complete
- [01:47:55] Reencoding audio tracks
- [01:47:55] Multiplexing M2TS
- [01:47:55] Extracting audio/subs [VID_00061]
- [01:47:55] Collecting video information [00061]
- Video: 1920x1080, 23.976fps
- Bitrate: 25,000 Kbs
- [01:47:55] Reencoding: VID_00061, Pass 1 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[01:47:56] - Failed video encode, aborted

[jdobbs]

Actually currently not enabling strict AVCHD still uses --bluray which only works on a handful of players when it's burned on DVD so it is quite a big deal and there's well over 100 posts in this thread concerning this issue. If it were to use --avchd it would be no difference between the two but strict AVCHD should remove some folders that aren't part of the avchd structure like it used to.

Hopefully next version will fix this issue so 95%+ people will get playable output every time from the program by default. Have you taken a look at this post (http://forum.doom9.org/showthread.php?p=1286079#post1286079) I referred to a few days ago and apply it to the next version?



Thanks, just sort of an annoying cosmetic bug.



Ok but just a reminder to use --tff in x264 command line or else the encode won't be nearly as efficient. Also finding out the field order might be able to be done with an avisynth function like: last.getparity() ? 1 : 0 . It accurately finds the correct field order however I have no idea how to pipe it to x264.I guess I didn't word that response correctly. I meant that --AVCHD is used if you select strict AVCHD.

--tff gives an "unknown option" error in X264. There is a --interlaced switch.

[turbojet]

I guess I didn't word that response correctly. I meant that --AVCHD is used if you select strict AVCHD.

--tff gives an "unknown option" error in X264. There is a --interlaced switch.

Oh --tff is a switch in modified with nalhrd_interlaced patch but I just encoded 3 little tff clips in crf and --tff and --interlaced produced bit identical files. I don't think I have any bff clips to test they are fairly rare, but --interlaced should be just as good as --tff / --bff and maybe even better if it auto-detects field order.

[Dark Shikari]

Oh --tff is a switch in modified with nalhrd_interlaced patch but I just encoded 3 little tff clips in crf and --tff and --interlaced produced bit identical files. I don't think I have any bff clips to test they are fairly rare, but --interlaced should be just as good as --tff / --bff and maybe even better if it auto-detects field order.It doesn't detect field order; it doesn't even write a particular field order to the bitstream.

[turbojet]

Even though x264 gave identical stats for --tff (alias to --interlaced) and --bff there is 2 bit differences in the mkv's and 100's of differences in the tsmuxer m2ts's. I can't tell a difference when viewing the m2ts's with MPC-HC and TMT3. Does anyone know if there is any signifigant difference in the 2 options in this situation?

[drmih]

I've just re-tried Godfather and Godfather 2 to bd-25 with the audio untouched and both came in oversized by about 500 Mb.

If I use a custom size am I still able to leave the audio untouched or is that hard coded for the bd-25 option only?

[tekmobile]

I've just re-tried Godfather and Godfather 2 to bd-25 with the audio untouched and both came in oversized by about 500 Mb.

If I use a custom size am I still able to leave the audio untouched or is that hard coded for the bd-25 option only?

What was the output size in bytes ?

On previous versions I have been able to keep HD audio with a custom size but there are limits if you go too low it will not keep it but I don't know what they are of if its changed.

[drmih]

What was the output size in bytes ?

On previous versions I have been able to keep HD audio with a custom size but there are limits if you go too low it will not keep it but I don't know what they are of if its changed.

23.6 Gb (25,357,897,728)

[tekmobile]

23.6 Gb (25,357,897,728)

Thats ok then

I was just wondering because ive seen many people complain about oversizing by a few hundered megs that were trying to burn to BD-RE when in fact the image was not oversize its just the BD-RE was not formatted to its full capacity (common with ImgBurn)

[Nkotok]

Thats ok then

I was just wondering because ive seen many people complain about oversizing by a few hundered megs that were trying to burn to BD-RE when in fact the image was not oversize its just the BD-RE was not formatted to its full capacity (common with ImgBurn)


No, it is BD RB that oversizes. I did Godfather movies for BD25s and they also came out oversized by about 500MB. It has nothing to do with BD-RE.

[Lif3styl3]

hi jdobbs,

by the way,...
the bd transpporter is undersized. it seems to be that bd-rb has calculated the hd audio size and pushed the dolby digital file on disc.

the difference is the audio size. Next info, i've got the dts hd audio file in my working directory, but it wasn't used,...

[drmih]

jdobbs

Given that some movies are oversized, would it be possible to remove the restrictions on Custom Size so that discs could still be done with the audio untouched?

[Capsbackup]

Casino Royale backed up perfectly to BD-25 with 1 LPCM and 1 AC3 448kbps. I Selected the standard Target Size BD-25, and the finished ISO is 22.0GB (23,627,890,688 bytes). I have not tried Custom Target Size for BD-25, nor do I feel compelled to try it when the potential oversize is not worth the questionable gain. I also believe, as jdobbs has said before, it is better to leave some room on the disc, to not burn to the outer edges where the possibility is greater for future damage.

[jdobbs]

I've just re-tried Godfather and Godfather 2 to bd-25 with the audio untouched and both came in oversized by about 500 Mb.

If I use a custom size am I still able to leave the audio untouched or is that hard coded for the bd-25 option only? Any size that is larger than a BD-9 is considered "BD-25"...

Give me some info on how oversized we're talking? I use a standard parameter to estimate how large the HD audio will be when remuxed into M2TS -- I can adjust it if I know how much it is oversizing. Even better would be a size adjustment that is specific to muxing overhead for each HD type. Then I could get very accurate. I just haven't had time to run tests. I'll see what I can do this weekend.

[jdobbs]

No, it is BD RB that oversizes. I did Godfather movies for BD25s and they also came out oversized by about 500MB. It has nothing to do with BD-RE. Oversized by your specified settings, or oversized using the standard BD-25 setting?

[Capsbackup]

@jdobbs;
I am trying to backup X-Men, Region A, to BD-25. From a previous experience with Casino Royale and BD-RB aborting when trying to reencode very small files ( less than 1MB), I was trying to avoid this from happening again. So I inserted the "MIN_M2TS_SIZE=100", and also tried "MIN_M2TS_SIZE=250", but BD-RB still shows several files less than this, one being .57MB. When viewing this file with MPC, it is just a .02 second Twentieth Century Fox advert, and should not be needed or displayed to be reencoded. And of course, it is the very last .M2TS to be reencoded, so I was hoping to avoid the ultimate and potential abort at the very end. Is this normal? Shouldn't BD-RB overlook these files when using this setting?

[jdobbs]

@jdobbs;
I am trying to backup X-Men, Region A, to BD-25. From a previous experience with Casino Royale and BD-RB aborting when trying to reencode very small files ( less than 1MB), I was trying to avoid this from happening again. So I inserted the "MIN_M2TS_SIZE=100", and also tried "MIN_M2TS_SIZE=250", but BD-RB still shows several files less than this, one being .57MB. When viewing this file with MPC, it is just a .02 second Twentieth Century Fox advert, and should not be needed or displayed to be reencoded. And of course, it is the very last .M2TS to be reencoded, so I was hoping to avoid the ultimate and potential abort at the very end. Is this normal? Shouldn't BD-RB overlook these files when using this setting?No.

If it is smaller than your setting but is still showing in the list, that means it is a part of a multipart MPLS that has at least one section meeting your criteria. If any part of an MPLS is to be reencoded, all other M2TSs in that MPLS must also be reencoded. If you don't do that you may end up with an MPLS that has one part AVC and another VC-1, or one part containing one type of audio and another that doesn't match. The result would be something unplayable because the MPLS descriptions wouldn't match at least some part of the video/audio.

I don't think I've seen any problems reencoding small video segments in a long time... can you describe the issue?

[Capsbackup]

No.

If it is smaller than your setting but is still showing in the list, that means it is a part of a multipart MPLS that has at least one section meeting your criteria. If any part of an MPLS is to be reencoded, all other M2TSs in that MPLS must also be reencoded. If you don't do that you may end up with an MPLS that has one part AVC and another VC-1, or one part containing one type of audio and another that doesn't match. The result would be something unplayable because the MPLS descriptions wouldn't match at least some part of the video/audio.

I don't think I've seen any problems reencoding small video segments in a long time... can you describe the issue?

I did not think that this .02 second advert would be part of the main .mpls, but maybe it is. The main .m2ts is one .m2ts, 00074, and is 27.7GB.
From my post above, #2981, BD-RB aborted trying to reencode a file that was 468KB in size ( Casino Royale). My attachment, waiting for approval, will show my concern for X-Men. It is running now, so I guess I will know if there is a problem in about 8 hours.

[tekmobile]

I did not think that this .02 second advert would be part of the main .mpls, but maybe it is. The main .m2ts is one .m2ts, 00074, and is 27.7GB.
From my post above, #2981, BD-RB aborted trying to reencode a file that was 468KB in size ( Casino Royale). My attachment, waiting for approval, will show my concern for X-Men. It is running now, so I guess I will know if there is a problem in about 8 hours.

It doesn't have to be the main MPLS there are 100s of them it could be included in some extras thats plays inbetween trailers for instance

Ive only ever had one instance where a m2ts wouldnt encode and that was really small but I have sucessfully done m2ts as small as 200KB in the past

[Furiousflea]

Oversized by your specified settings, or oversized using the standard BD-25 setting?

The Godfather movies do all oversize by a good 1GB roughly. Although they are the exception and certainly not the rule. Most my BD25 backups using your default conservative target pop out at 22-22.3GB

I think that's a good default the way it is. 1GB undersize is more than reasonable and takes care of the odd disc that is only a few hundred mb under the 23.3GB capacity of a BD-R.


If you could tune the target sizing more accurately then it would be a good idea to change your default target size obviously. I'm quite happy how it is though in all honesty. Not perfect but it is good enough.

[drmih]

Oversized by your specified settings, or oversized using the standard BD-25 setting?

Oversized using the standard bd-25 setting - I also had the same which is where my question came from.

The size on the hard disc was 23.6 Gb (25,357,897,728).

If by using a slightly smaller custom size I can still get untouched audio then there's no issue for me, although I suppose it could be annoying if you have a slow pc which is taken a day or so.