BD Rebuilder Beta - Bug Reports Only

[jdobbs]

@jdobbs

Sorry for the late reply I have not been on the forum since yesterday morning.
I have checked my side and it would seem that there has been a slight mistake when I converted using Anydvd hd I converted Rip dvd to harddisk instead of Rip to image. I'm wandering if somehow this has caused the discrepancy with my file format.

I would also like to say sorry for your time taken to find this out and for any inconvenience to yourself as I understand that your time is very valuable to you and you resolve numerous problems/issues for people every day. As a result of your financial costs I have made a donation of $80 via your Paypal Transaction ID:9BU13049NV1728529. This should cover the cost of the 4 disc box set and the same again towards your ongoing costs.

Please accept my sincere apologies and gratitude for your time taken and efforts to accommodate me. This was my first attempt at using the software for 3D ReEncode, And it is a learning curve all be it one which seems could have been avoided.

I will double check and check again before making any further posts in the future.

Kind Regards

ScotlandmanYour donation is very much appreciated.

As for the ripping process, I pretty much always rip to hard drive -- I just have AnyDVD running and use Explorer to copy the BDMV and CERTIFICATE folders to a location on my HDD. I'm not sure what could account for the differences between your attempt to encode and mine. But I suspect there may have been some confusion involved between the 2D and the 3D discs of the four disc set.

[jdobbs]

Just a heads-up to everyone. If you have any bug reports that need to be cleaned up in the short term, please post them in the next few days. I plan to post one more BD Rebuilder release toward the end of next week, and then I will be unavailable for a few weeks.

[scotlandman]

Your donation is very much appreciated.

As for the ripping process, I pretty much always rip to hard drive -- I just have AnyDVD running and use Explorer to copy the BDMV and CERTIFICATE folders to a location on my HDD. I'm not sure what could account for the differences between your attempt to encode and mine. But I suspect there may have been some confusion involved between the 2D and the 3D discs of the four disc set.

Hi jdobbs

Thank you very much for your kind words and your understanding.

I think you are correct and I have made the rookie error with the discs so very sorry and very embarrassing on my part.

I very much look forward to your next release and I will continue to make contributions when I can to support your hard work for which we are all very grateful.

Kind Regards

Scotlandman

[jdobbs]

I've recently turned on the option to use internal LAVF for frame serving. I've encountered an issue with resizing to 1440 which is not present using DirectShow.
When I choose to resize to 1440x1080 both (LAVF and Directshow) generate an output with 1440x1080. If LAVF is used the display aspect ratio seems to be wrong at 4:3 - the generated disc doesn't use the full screen for playback and the picture is clearly squeezed horizontally. Mediainfo shows a "Display Aspect Ratio" of 4:3 on the resulting m2ts. Encoding the same source with DirectShow used for Frameserving produces an output that correctly display as 16:9 during playback - Mediainfo shows a "Display Aspect Ratio" of 16:9. The result is independent of specific discs and can also be reproduced with small Full-HD-Imports for Quick Testing.

Both generate the same AVS script:


The encoding command line is different (taken from LASTCMD.txt):
LAVF

Directshow


Settings usedCan you give me some more information on the source. What size is it? I'm looking at the command lines, and other than the resizing being internal and LAVF being used they are the same. I'd be interested to see if the sar=1:1 in the resize statement is correct.

It appears that the source is flagged as 4:3 in the source, since both encoding lines has that command line option set. Also, can you tell me more about how you imported the source. I also need to make sure that the error isn't in the import. 4:3 aspect shouldn't be legal on any source other than 720x480/576, and in that case it should be put into a 4:3 box (with borders) on a 1440x1080 encode.

[mparade]

Just a heads-up to everyone. If you have any bug reports that need to be cleaned up in the short term, please post them in the next few days. I plan to post one more BD Rebuilder release toward the end of next week, and then I will be unavailable for a few weeks.

101$ is already on the way so that you can afford some of your time-robbering "wild goose chase" 3D projects in the future..;)

[krassle]

Yes it will break things. There are several other new enhancements (such as DTS-Express support) that BD-RB uses now (beyond the 3D enhancements). Unfortunately your problem is with multiAVCHD's lack of support -- not BD-RB.

I can think of no reason why you couldn't use v1.10.6 with multiAVCHD while keeping the new one (v2.6.12) for BD-RB. BD-RB uses the one in its TOOLS folder by default.

Hi jdobbs,

I failed to state my main reason for being "not quite happy" with the new version of tsMuxeR. It isn't incompatibility with multiAVCHD, as its doing a remux with its own version (v1.10.6) anyway and goes on without any problem. Here is my explanation:

My simple MOVIE-ONLY backups for AVCHD are kept in ISO form or burned to BD-5/9. From there, I want to be able to [1] quickly mount/burn the image for playing with any software/hardware blu-ray player; [2] remux with just a single cmd directly from the M2TS stream file to Matroska using mkvmerge.
[1] is perfectly functioning with the new version of tsMuxeR, but [2] isn't. The resulting MKV file is played fine, but seeking through it is not possible! Tried all versions of MKVToolNix from 6.1.0 to 6.9.1. No change. So, there must be something tsMuxeR(v2.6.12) removes or adds from/to the stream, that leads to the seeking failure. Muxing with the old version(using same MUX_MOVIE_ONLY.meta from WORKFILES DIR without --label & --start-time) and then converting to MKV works just as expected.

So, this is why I have to remux after every finished job, simply to ensure muxed MKV is working as well.
I think MKVMERGE is not to blame here and BD-RB definitely not, but the new tsMuxeR. I did over 300 BD to AVCHD backups so far, and every single one extracted from m2ts and converted to mkv plays also nicely.
What might be the fault here? Me, or just my limited understanding of the matter maybe...

I'm sorry, I did not make myself clear from the beginning.

Thank you very much for the help.

Gesendet von meinem Nexus 7 mit Tapatalk

[jdobbs]

101$ is already on the way so that you can afford some of your time-robbering "wild goose chase" 3D projects in the future..;)Wow. It is very much appreciated. You are a gentleman and a scholar -- and have given much more than your fair share over time.

Thanks.

[AmigaFuture]

"Live Free Or Die Hard", since you asked about bugs, the only one I've encountered in a while is M2TS(?) not keeping it's "Bookmarks" or "Chapters"?? I don't get well enough of the details for how those function. So, after using Movie & Menus...the "don't advance" isn't retained. Or whatever is used to allow a Standalone player to interact with it. Could you look into that?

When processing with Full Backup the files aren't "processed" with BD-RB other than copying/moving to the Output BD structure, but some of the unwanted items aren't showing to be blanked. I've used MIN_M2TS_SIZE, but still cannot get them to show...to check if BD-RB would do the same thing as Movie & Menus does.

Thanks.

[Lathe]

Hello!

I processed one movie using BDRB to MKV (alternate output) and it came out just fine. Wanting to experiment a little bit, I tried dropping in one line of Avisynth coding (LimitedSharpen) With the exact same input files, settings, and output choice; absolutely no difference, but, this time trying to run it, I now got the 2 warnings concerning AnyDVD settings which are incompatible (you know the 2: 'Remove annoying adverts' & 'Remove short titles') which I previously used when using AnyDVD. BUT... the first encode, which worked perfectly, was with the EXACT same source and with all the exact same settings, but everything was fine and I did not get any warnings and it did not fail.

Now, I will make sure not to use these AnyDVD settings in the future. But, out of curiosity about how BDRB works, with all other things being exactly equal, would just dropping in one line of Avisynth code prompt a failure and specifically those 2 AnyDVD incompatibility warnings when BDRB ran the encode just fine before with the exact same source file?

Thank you for the clarification!

[jdobbs]

Hello!

I processed one movie using BDRB to MKV (alternate output) and it came out just fine. Wanting to experiment a little bit, I tried dropping in one line of Avisynth coding (LimitedSharpen) With the exact same input files, settings, and output choice; absolutely no difference, but, this time trying to run it, I now got the 2 warnings concerning AnyDVD settings which are incompatible (you know the 2: 'Remove annoying adverts' & 'Remove short titles') which I previously used when using AnyDVD. BUT... the first encode, which worked perfectly, was with the EXACT same source and with all the exact same settings, but everything was fine and I did not get any warnings and it did not fail.

Now, I will make sure not to use these AnyDVD settings in the future. But, out of curiosity about how BDRB works, with all other things being exactly equal, would just dropping in one line of Avisynth code prompt a failure and specifically those 2 AnyDVD incompatibility warnings when BDRB ran the encode just fine before with the exact same source file?

Thank you for the clarification!If you've added an AVISYNTH filter then it isn't "the exact same source file". The filter assuredly caused an error. You have to be extremely careful with filters, as they require an good understanding of AVISYNTH, the filter, and how they interact.

The BD-RB checks that report incorrect AnyDVD settings only happen when you get an error (because that's the only time you need to see them). So when it is trying to give you possible reasons for the error -- it let's you know that a possible cause might be the AnyDVD settings. It doesn't imply they absolutely are the cause. In your case the usage of the filter (usually syntax) was the issue.

[Starfiresg1]

Can you give me some more information on the source. What size is it? I'm looking at the command lines, and other than the resizing being internal and LAVF being used they are the same. I'd be interested to see if the sar=1:1 in the resize statement is correct.

It appears that the source is flagged as 4:3 in the source, since both encoding lines has that command line option set. Also, can you tell me more about how you imported the source. I also need to make sure that the error isn't in the import. 4:3 aspect shouldn't be legal on any source other than 720x480/576, and in that case it should be put into a 4:3 box (with borders) on a 1440x1080 encode.

I noticed it first with a standard Blu-Ray-Disc doing a movie-only-encode to BD-5. Since the movie was close to 2 hours I choose to downsize to 1440x1080, which I don't do normally. Since the result puzzled me I tried to find the source by using the import function on a small M2TS with 1920x1080 resolution to avoid having to encode full discs while changing encoding settings.

I just started another job on "Filfth" (Region B) using the same settings (LAVF and resize to 1440x1080) and will report the outcome.

This is the media info on the M2TS in the import structure
General
ID : 1 (0x1)
Complete name : K:\BR-TEMP\IMPORTS\00110\BDMV\STREAM\00000.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 535 MiB
Duration : 3mn 52s
Overall bit rate mode : Variable
Overall bit rate : 19.3 Mbps
Maximum Overall bit rate : 35.5 Mbps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : 27
Duration : 3mn 52s
Bit rate mode : Variable
Bit rate : 18.2 Mbps
Maximum bit rate : 32.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.366
Stream size : 504 MiB (94%)
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS
Format/Info : Digital Theater Systems
Mode : 16
Format settings, Endianness : Big
Codec ID : 130
Duration : 3mn 52s
Bit rate mode : Constant
Bit rate : 318 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.80 MiB (2%)

Text
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 3mn 49s
Delay relative to video : 958ms

[jdobbs]

I noticed it first with a standard Blu-Ray-Disc doing a movie-only-encode to BD-5. Since the movie was close to 2 hours I choose to downsize to 1440x1080, which I don't do normally. Since the result puzzled me I tried to find the source by using the import function on a small M2TS with 1920x1080 resolution to avoid having to encode full discs while changing encoding settings.

I just started another job on "Filfth" (Region B) using the same settings (LAVF and resize to 1440x1080) and will report the outcome.

This is the media info on the M2TS in the import structure
General
ID : 1 (0x1)
Complete name : K:\BR-TEMP\IMPORTS\00110\BDMV\STREAM\00000.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 535 MiB
Duration : 3mn 52s
Overall bit rate mode : Variable
Overall bit rate : 19.3 Mbps
Maximum Overall bit rate : 35.5 Mbps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : 27
Duration : 3mn 52s
Bit rate mode : Variable
Bit rate : 18.2 Mbps
Maximum bit rate : 32.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.366
Stream size : 504 MiB (94%)
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS
Format/Info : Digital Theater Systems
Mode : 16
Format settings, Endianness : Big
Codec ID : 130
Duration : 3mn 52s
Bit rate mode : Constant
Bit rate : 318 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.80 MiB (2%)

Text
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 3mn 49s
Delay relative to video : 958ms
Actually I may have misinterpreted what I saw. Since 1440x1080 has to be displayed at 16:9 -- that would mean (if I'm thinking correctly) it has a display aspect ration of 4:3 ((4/3) * 1440 = 1920).

[jdobbs]

I noticed it first with a standard Blu-Ray-Disc doing a movie-only-encode to BD-5. Since the movie was close to 2 hours I choose to downsize to 1440x1080, which I don't do normally. Since the result puzzled me I tried to find the source by using the import function on a small M2TS with 1920x1080 resolution to avoid having to encode full discs while changing encoding settings.

I just started another job on "Filfth" (Region B) using the same settings (LAVF and resize to 1440x1080) and will report the outcome.

This is the media info on the M2TS in the import structure
Actually I may have misinterpreted what I saw in the command lines. Since 1440x1080 has to be displayed at 16:9 -- that would mean (if I'm thinking correctly) it has a display aspect ratio of 4:3 ((4/3) * 1440 = 1920).

Let me know how this one turns out.

[Edit] I'm able to repeat the issue -- and I'm scratching my head as to why it happens. I'll let you know what I find.

[Lathe]

If you've added an AVISYNTH filter then it isn't "the exact same source file". The filter assuredly caused an error. You have to be extremely careful with filters, as they require an good understanding of AVISYNTH, the filter, and how they interact.

The BD-RB checks that report incorrect AnyDVD settings only happen when you get an error (because that's the only time you need to see them). So when it is trying to give you possible reasons for the error -- it let's you know that a possible cause might be the AnyDVD settings. It doesn't imply they absolutely are the cause. In your case the usage of the filter (usually syntax) was the issue.

Ah, I see; thank you very much Mr. Dobbs! Actually, I am brand new to using Avisynth script, so.... :)

Cheers!

[Lathe]

Actually I may have misinterpreted what I saw in the command lines. Since 1440x1080 has to be displayed at 16:9 -- that would mean (if I'm thinking correctly) it has a display aspect ratio of 4:3 ((4/3) * 1440 = 1920).

Let me know how this one turns out.

I don't know if this is relevant, but perhaps does the square pixel/rectangular pixel thing enter into this...? I remember recently asking about the 'forced' 16x9 display of the supposedly 4x3 1440x1080 format, and I THINK I was told that the pixels in that case are rectangular instead of square.

[jdobbs]

I don't know if this is relevant, but perhaps does the square pixel/rectangular pixel thing enter into this...? I remember recently asking about the 'forced' 16x9 display of the supposedly 4x3 1440x1080 format, and I THINK I was told that the pixels in that case are rectangular instead of square.Yes they are. They are 4:3 pixels... so a 1440x1080 picture would be displayed as 16:9. 1440x1080 is only legal in BD as a 16:9 display.

I know it's confusing... but 4 divided by 3 is 1.3333. So if a 1440 width is multiplied by 1.3333 you end up with 1920x1080 (which is a 16:9 display at 1:1 aspect ratio).

[Lathe]

Yes they are. They are 4:3 pixels... so a 1440x1080 picture would be displayed as 16:9. 1440x1080 is only legal in BD as a 16:9 display.

I know it's confusing... but 4 divided by 3 is 1.3333. So if a 1440 width is multiplied by 1.3333 you end up with 1920x1080 (which is a 16:9 display at 1:1 aspect ratio).

Excellent, thanks!

[Starfiresg1]

Actually I may have misinterpreted what I saw in the command lines. Since 1440x1080 has to be displayed at 16:9 -- that would mean (if I'm thinking correctly) it has a display aspect ratio of 4:3 ((4/3) * 1440 = 1920).

Let me know how this one turns out.


The job finished and is displayed with 4:3 ratio during playback.

Media info of the resulting m2ts
General
Complete name : K:\BR-TEMP\DRECKSAU\BDMV\PLAYLIST\00000.mpls
Format : Blu-ray Playlist
File size : 790 Bytes
Duration : 1h 37mn
Overall bit rate mode : Variable
Overall bit rate : 1 bps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Codec ID : 27
Duration : 2h 37mn
Bit rate mode : Variable
Bit rate : 2 408 Kbps
Maximum bit rate : 15.0 Mbps
Width : 1 440 pixels
Height : 1 080 pixels
Display aspect ratio : 4:3
Frame rate : 24.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.065
Stream size : 2.66 GiB (62%)
format_identifier : HDMV
Source : 00000.m2ts

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Codec ID : 129
Duration : 2h 37mn
Bit rate mode : Constant
Bit rate : 640 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 723 MiB (17%)
Language : German
bsid : 8
dialnorm : -31
dialnorm/String : -31 dB
acmod : 7
lfeon : 1
dialnorm_Average : -31
dialnorm_Average/String : -31 dB
dialnorm_Minimum : -31
dialnorm_Minimum/String : -31 dB
dialnorm_Maximum : -31
dialnorm_Maximum/String : -31 dB
dialnorm_Count : 30
format_identifier : AC-3
Source : 00000.m2ts

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Codec ID : 129
Duration : 2h 37mn
Bit rate mode : Constant
Bit rate : 640 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 723 MiB (17%)
Language : English
bsid : 8
dialnorm : -31
dialnorm/String : -31 dB
acmod : 7
lfeon : 1
dialnorm_Average : -31
dialnorm_Average/String : -31 dB
dialnorm_Minimum : -31
dialnorm_Minimum/String : -31 dB
dialnorm_Maximum : -31
dialnorm_Maximum/String : -31 dB
dialnorm_Count : 30
format_identifier : AC-3
Source : 00000.m2ts

Text
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 2h 37mn
Delay relative to video : 1s 0ms
Language : German
Source : 00000.m2ts

Menu
00:00:00.000 : Chapter 1
00:11:25.666 : Chapter 2
00:19:34.541 : Chapter 3
00:26:24.833 : Chapter 4
00:36:23.166 : Chapter 5
00:42:44.916 : Chapter 6
00:50:24.291 : Chapter 7
00:59:13.666 : Chapter 8
01:07:08.125 : Chapter 9
01:14:44.000 : Chapter 10
01:23:40.207 : Chapter 11
01:32:28.125 : Chapter 12
01:37:57.250 : Chapter 13



Edit: I just saw that you were able to reproduce the issue

Edit2:
Since the width is changed from 1920 to 1440 should the sar maybe change from 1:1 (1920x1080) : (1920x1080) to (1920x1080) : (1440x1080), which would meen 2073600:1555200 or 4:3 ? (If the formula for cropped encodes applies here, e.g. encode to 720p after removing the horizontal black bars)

[gonwk]

Hi jdobbs,

I just decided to give BD Rebuilder (BD-RBV04706.zip) a try, but as usual I run any software that I get thru VirusTotal ... and VT tagged your latest version with 3 TROJANS

https://www.virustotal.com/en/file/21267f671731ebcc4ba6eee03a3aeda827d017976112b2d35a996948ea855a45/analysis/

But since I totally TRUST doom9 and the team here, I am totally baffled.

So, what is the Story ... are these False Positive?

Thanks,

G! :)

[omegaman7]

Hi jdobbs,

I just decided to give BD Rebuilder (BD-RBV04706.zip) a try, but as usual I run any software that I get thru VirusTotal ... and VT tagged your latest version with 3 TROJANS

https://www.virustotal.com/en/file/21267f671731ebcc4ba6eee03a3aeda827d017976112b2d35a996948ea855a45/analysis/

But since I totally TRUST doom9 and the team here, I am totally baffled.

So, what is the Story ... are these False Positive?

Thanks,

G! :)
Most certainly a false positive. I seriously doubt that your download is being intercepted.
Anyhow, malwarebytes does not detect anything. And I trust Malwarebytes.

[jdobbs]

Hi jdobbs,

I just decided to give BD Rebuilder (BD-RBV04706.zip) a try, but as usual I run any software that I get thru VirusTotal ... and VT tagged your latest version with 3 TROJANS

https://www.virustotal.com/en/file/21267f671731ebcc4ba6eee03a3aeda827d017976112b2d35a996948ea855a45/analysis/

But since I totally TRUST doom9 and the team here, I am totally baffled.

So, what is the Story ... are these False Positive?

Thanks,

G! :)If you downloaded from Doom9 or from my site you are getting a false positive. Dump your virus software and replace it with one that works.

As always... I'm not positive which is worse, viruses or anti-virus software. They both prevent your computer from working they way it should. I keep mine disabled most of the time. Not only are they always interfering with other software -- they also slow your system down to a crawl. :mad:

[gonwk]

If you downloaded from Doom9 or from my site you are getting a false positive. Dump your virus software and replace it with one that works.

As always... I'm not positive which is worse, viruses or anti-virus software. They both prevent your computer from working they way it should. I keep mine disabled most of the time. Not only are they always interfering with other software -- they also slow your system down to a crawl. :mad:

Hi jdobbs,

Thanks for taking the time to respond. Feel much better, I will make sure I get it from Doom9.

G! :thanks:

[italianodemivida]

When I perform the compression to full 3D BD25, the image is excellent but I don't get the subtitles in 3D, why?

[HWK]

When I perform the compression to full 3D BD25, the image is excellent but I don't get the subtitles in 3D, why?

This is known problem and limitation. BD-Rebuilder rely on external program to build disc back. As a result program which it relies on can't work with 3D subtitle.

Jdobbs, try to get working but no go in this case.

[Lathe]

Mr. Dobbs,

I recently used BDRB to import 3 Blu-ray folders and create one playable disc, which worked perfectly fine. But, for some odd reason, in playing back the resulting disc, only one of the 3 movies allowed me to use chapter stops; the other 2 would not. Is there anything that BDRB would do while importing that would somehow remove the chapter functionality, or do you think that that would more likely have been caused by TSMuxer which I used to create the Blu-ray folders before importing? This was really odd, because in using TSMuxer hundreds of times, this was the very first time ever that I had seen ANY Blu-ray created that would not allow chapter stops on playback.

Thank you JDobbs!

[Guest]

@Lathe

This appears to be a crosspost of an issue you raised in another thread.

http://forum.doom9.org/showthread.php?t=170644

Therefore, I ask you again:

What is your source file please? An original bluray disk? Why do you need TSMuxer?

Note that crossposts can incur strikes. I recommend that you carefully read and follow our forum rules.

[jdobbs]

Mr. Dobbs,

I recently used BDRB to import 3 Blu-ray folders and create one playable disc, which worked perfectly fine. But, for some odd reason, in playing back the resulting disc, only one of the 3 movies allowed me to use chapter stops; the other 2 would not. Is there anything that BDRB would do while importing that would somehow remove the chapter functionality, or do you think that that would more likely have been caused by TSMuxer which I used to create the Blu-ray folders before importing? This was really odd, because in using TSMuxer hundreds of times, this was the very first time ever that I had seen ANY Blu-ray created that would not allow chapter stops on playback.

Thank you JDobbs!I'm sorry, but please review the thread and the criteria for bug reporting. I don't accept bug reports on preprocessed sources. Experience has proven that almost ALL reports using preprocessed sources were shown to have issues before being presented to BD-RB for backup.

[Lathe]

I'm sorry, but please review the thread and the criteria for bug reporting. I don't accept bug reports on preprocessed sources. Experience has proven that almost ALL reports using preprocessed sources were shown to have issues before being presented to BD-RB for backup.

Sure thing; my apologies. I will be more careful in the future.

Thanks!

[Pod7381]

I have been using BD-Rebuilder to make backups of my Blu-ray collection for years so I am not a complete novice. Having said that, trying to backup a 3D movie has become way to complicated for my feeble brain. Do I need to modify the ini file when using the latest build or do the automatic settings work "as is"? What are the correct settings anyway? I have tried to configure the settings but it takes 15 hrs. to complete a trial run. That's too long to find out the encode has failed in some way. (so I just abort each attempt).
I have an old i7 processor. Can I enable Quick Sync and how exactly do I do that?
I am not lazy. I have read hundreds of posts, but I cannot figure out what the current "working" configuration is.
If someone could just post step by step instructions on how to back up 3D movies for dummies like me, I would be truly grateful and I bet alot of other people would be grateful as well.
Before ending this quick rant I would like acknowledge the great work that JDobbs has done over the years to develop this software. I am not complaining, I appreciate having this software....just a little frustrated right now that I can't figure this out on my own.

[jdobbs]

I have been using BD-Rebuilder to make backups of my Blu-ray collection for years so I am not a complete novice. Having said that, trying to backup a 3D movie has become way to complicated for my feeble brain. Do I need to modify the ini file when using the latest build or do the automatic settings work "as is"? What are the correct settings anyway? I have tried to configure the settings but it takes 15 hrs. to complete a trial run. That's too long to find out the encode has failed in some way. (so I just abort each attempt).
I have an old i7 processor. Can I enable Quick Sync and how exactly do I do that?
I am not lazy. I have read hundreds of posts, but I cannot figure out what the current "working" configuration is.
If someone could just post step by step instructions on how to back up 3D movies for dummies like me, I would be truly grateful and I bet alot of other people would be grateful as well.
Before ending this quick rant I would like acknowledge the great work that JDobbs has done over the years to develop this software. I am not complaining, I appreciate having this software....just a little frustrated right now that I can't figure this out on my own.You really don't have to do anything special. Use the same settings you always use, and BD-RB handles it fine. It recognizes a 3D source automatically and does what needs to be done without intervention. The only time you have to worry about the INI with 3D is if you want to make a 2D backup from a 3D disc.

But... it does take quite a bit longer since you can't use X264 for the encoding. You are also encoding twice as many frames (left and right views).

If you have an older processor it is unlikely you have quick-sync.

[HWK]

You really don't have to do anything special. Use the same settings you always use, and BD-RB handles it fine. It recognizes a 3D source automatically and does what needs to be done without intervention. The only time you have to worry about the INI with 3D is if you want to make a 2D backup from a 3D disc.

But... it does take quite a bit longer since you can't use X264 for the encoding. You are also encoding twice as many frames (left and right views).

If you have an older processor it is unlikely you have quick-sync.

Jdobbs, I would also add require minimum of windows 7 for 3D to work.

[jdobbs]

Jdobbs, I would also add require minimum of windows 7 for 3D to work.Good point.

[Chuckwagon]

Hello all. I hate to ask again, but I was wondering if anyone else was having problems importing mkv files and re-encoding them to 720p BD5s. I don't believe that it is my system, but it would be nice to know for sure that I'm not crazier than previously thought. Thanks!

As an aside, is there any way to make an older version of BD Rebuilder work again once you get the expired notice from said version?

I didn't see that there had been a resolution to this problem, and I think I've run into the same issue.

I have only recently started playing with the import feature, so I'm not sure I really know what I'm doing. But, as a test, a tried to import an MKV file that is 1912x1072, using BDRB version 47.06. The resulting output is just a gray screen. Further digging led me to look at the pseudo BD created during the process, prior to backup and re-encode. Looking at the stream created from the MKV, for some reason, it is converted to 720x480. It plays fine, it's just small. Then when the re-encode takes place, BDRB thinks it's 1280x720. I believe this is where the fail occurs and the result is the gray screen.

Since tsmuxer was mentioned earlier, I back-revved it to a different version I had on my system from Aug of last year. (1.10.6) Using that version, the pseudo BD has a stream from the MKV that is now 1912x1072. It also plays fine, and is now the same size as the original.

Wondering if it had something to do with the slightly off resolution of the input file, I have tried with several different MKV files, of varying resolutions, and it always makes them 720x480. However, when I used a MKV file create by BDRB from a blu-ray source, that is exactly 1920x1080, the intermediate step creating the pseudo BD works fine, and I get a stream that is 1920x1080. I then tried a video shot with my DSLR, which is 1920x1080, and it works fine also in spite of being an odd .mts file, and the BD created from it also plays fine, no grey screen.

So it would seem there is some oddity with the 2.6.12 version of tsmuxer included with the 47.06 build. It seems to resize the video, if it isn't 1920x1080, while creating the pseudo BD structure. And that resize seems to cause the re-encode to fail with a gray screen.

I don't have any 1280x720 sized MKVs readily available to test if they import ok, or any slightly off sized ones in the same 720 range. So I can't say if that has an issue or not.

:)

[Guest]

@Chuckwagon

Where do you get these MKV files? And did you not see jdobb's statement:

"I'm sorry, but please review the thread and the criteria for bug reporting. I don't accept bug reports on preprocessed sources. Experience has proven that almost ALL reports using preprocessed sources were shown to have issues before being presented to BD-RB for backup."

[krassle]

I didn't see that there had been a resolution to this problem, and I think I've run into the same issue.

I have only recently started playing with the import feature, so I'm not sure I really know what I'm doing. But, as a test, a tried to import an MKV file that is 1912x1072, using BDRB version 47.06. The resulting output is just a gray screen. Further digging led me to look at the pseudo BD created during the process, prior to backup and re-encode. Looking at the stream created from the MKV, for some reason, it is converted to 720x480. It plays fine, it's just small. Then when the re-encode takes place, BDRB thinks it's 1280x720. I believe this is where the fail occurs and the result is the gray screen.

Since tsmuxer was mentioned earlier, I back-revved it to a different version I had on my system from Aug of last year. (1.10.6) Using that version, the pseudo BD has a stream from the MKV that is now 1912x1072. It also plays fine, and is now the same size as the original.
...
So it would seem there is some oddity with the 2.6.12 version of tsmuxer included with the 47.06 build. It seems to resize the video, if it isn't 1920x1080, while creating the pseudo BD structure. And that resize seems to cause the re-encode to fail with a gray screen.

I don't have any 1280x720 sized MKVs readily available to test if they import ok, or any slightly off sized ones in the same 720 range. So I can't say if that has an issue or not.

:)

I also have one issue with latest tsMuxeR (though not same) and after reverting back to v1.10.6 it disappears.
It seems either tsmuxer or MKVToolNix(or both) cut/add something from/to the elementary stream, so that after making a MKV out of AVCHD muxed m2ts source, there is seeking problem in software players(mpc-hc).
So I'm staying with old version for now, until I figure the cause.

Also MediaInfo does not show 'Writing library' & 'Encoding settings' entries in Video section anymore... Someone know why this is? (I liked being able to see x264 version & settings)


Gesendet von meinem Nexus 7 mit Tapatalk

[jdobbs]

I didn't see that there had been a resolution to this problem, and I think I've run into the same issue.

I have only recently started playing with the import feature, so I'm not sure I really know what I'm doing. But, as a test, a tried to import an MKV file that is 1912x1072, using BDRB version 47.06. The resulting output is just a gray screen. Further digging led me to look at the pseudo BD created during the process, prior to backup and re-encode. Looking at the stream created from the MKV, for some reason, it is converted to 720x480. It plays fine, it's just small. Then when the re-encode takes place, BDRB thinks it's 1280x720. I believe this is where the fail occurs and the result is the gray screen.

Since tsmuxer was mentioned earlier, I back-revved it to a different version I had on my system from Aug of last year. (1.10.6) Using that version, the pseudo BD has a stream from the MKV that is now 1912x1072. It also plays fine, and is now the same size as the original.

Wondering if it had something to do with the slightly off resolution of the input file, I have tried with several different MKV files, of varying resolutions, and it always makes them 720x480. However, when I used a MKV file create by BDRB from a blu-ray source, that is exactly 1920x1080, the intermediate step creating the pseudo BD works fine, and I get a stream that is 1920x1080. I then tried a video shot with my DSLR, which is 1920x1080, and it works fine also in spite of being an odd .mts file, and the BD created from it also plays fine, no grey screen.

So it would seem there is some oddity with the 2.6.12 version of tsmuxer included with the 47.06 build. It seems to resize the video, if it isn't 1920x1080, while creating the pseudo BD structure. And that resize seems to cause the re-encode to fail with a gray screen.

I don't have any 1280x720 sized MKVs readily available to test if they import ok, or any slightly off sized ones in the same 720 range. So I can't say if that has an issue or not.

:)No resolution because as best as I can tell there is no problem. I've tested it to death -- and it works every time for me.

But... why on earth would anyone create a source that is 1912x1072? That's just silly. I could understand 1920x1072 (to remove an upper/lower border). I could understand 1912x1080 (to remove a left/right border)... but when would you ever need to create something that is that far from any kind of standard?

[Edit]
I just looked at the code, and it will add borders to the top/bottom and left/right to make the source 1920x1080. I see no possible way that it will be resized to 720x480/576 unless you have checked an alternate output of that size (told it to do so).

[Chuckwagon]

No resolution because as best as I can tell there is no problem. I've tested it to death -- and it works every time for me.

But... why on earth would anyone create a source that is 1912x1072? That's just silly. I could understand 1920x1072 (to remove an upper/lower border). I could understand 1912x1080 (to remove a left/right border)... but when would you ever need to create something that is that far from any kind of standard?

[Edit]
I just looked at the code, and it will add borders to the top/bottom and left/right to make the source 1920x1080. I see no possible way that it will be resized to 720x480/576 unless you have checked an alternate output of that size (told it to do so).

Heh, I also can't figure why anyone would make such an odd sized resolution. I also encountered files that were even stranger, like 8 hundred something by 960. No telling what folks will try I guess. I doubt this is a code issue on your end, since I'd expect if it were a BDRB issue switching tmuxer wouldn't help. I just thought that since I hadn't seen any resolution I'd play around and see if I could figure out what was causing it.

All of my MKVs are created by BDRB, and I haven't had a problem with them. But since I was just playing around with this, and I thought resolution might have an impact, I grabbed a bunch of MKVs off the net, and ended up with several different resolutions. I'd bet anyone running into this issue has odd sized files, for whatever reason. When the files are "normal" resolutions there doesn't seem to be any trouble.

The 2.6.12 version of tsmuxer seems to dislike the odd sized files, but the older tsmuxer doesn't. Why I couldn't say. I didn't think you did any resizing until the final re-encode. I assumed tmuxer would just grab the video as is and put it into the pseudo BD structure without making adjustments, and any resizing would be done as part of the re-encode. But that isn't how it's working with the 2.6.12 version. The process goes far too fast for it to be encoding the files, so is there some way for tsmuxer to just alter the res? Is tsmuxer supposed to resize when extracting to the pseudo structure, or is that an unexpected behavior?

In any case, there's an easy work around. The older version of tsmuxer did complete an import of 7 of these 1912x1072 resolution MKVs, each around 2GB, and BDRB created an ISO with them and they all play nicely. So, if someone hits this, they can use the older tsmuxer to get around it. Though I have also encountered files that encode the video fine, but pork the audio. So clearly it's best to use well conforming sources in the first place. :) But folks don't often do what's best. So, for future reference, next time someone has a gray screen issue, maybe it's from this.

Cheers,
:)

[jdobbs]

Heh, I also can't figure why anyone would make such an odd sized resolution. I also encountered files that were even stranger, like 8 hundred something by 960. No telling what folks will try I guess. I doubt this is a code issue on your end, since I'd expect if it were a BDRB issue switching tmuxer wouldn't help. I just thought that since I hadn't seen any resolution I'd play around and see if I could figure out what was causing it.

All of my MKVs are created by BDRB, and I haven't had a problem with them. But since I was just playing around with this, and I thought resolution might have an impact, I grabbed a bunch of MKVs off the net, and ended up with several different resolutions. I'd bet anyone running into this issue has odd sized files, for whatever reason. When the files are "normal" resolutions there doesn't seem to be any trouble.

The 2.6.12 version of tsmuxer seems to dislike the odd sized files, but the older tsmuxer doesn't. Why I couldn't say. I didn't think you did any resizing until the final re-encode. I assumed tmuxer would just grab the video as is and put it into the pseudo BD structure without making adjustments, and any resizing would be done as part of the re-encode. But that isn't how it's working with the 2.6.12 version. The process goes far too fast for it to be encoding the files, so is there some way for tsmuxer to just alter the res? Is tsmuxer supposed to resize when extracting to the pseudo structure, or is that an unexpected behavior?

In any case, there's an easy work around. The older version of tsmuxer did complete an import of 7 of these 1912x1072 resolution MKVs, each around 2GB, and BDRB created an ISO with them and they all play nicely. So, if someone hits this, they can use the older tsmuxer to get around it. Though I have also encountered files that encode the video fine, but pork the audio. So clearly it's best to use well conforming sources in the first place. :) But folks don't often do what's best. So, for future reference, next time someone has a gray screen issue, maybe it's from this.

Cheers,
:)You are correct. BD-RB doesn't resize until reencoding. The parameters to be used are stored in the PSEUDO folder and in the PSEUDO.INF file.

[jdobbs]

Heh, I also can't figure why anyone would make such an odd sized resolution. I also encountered files that were even stranger, like 8 hundred something by 960. No telling what folks will try I guess. I doubt this is a code issue on your end, since I'd expect if it were a BDRB issue switching tmuxer wouldn't help. I just thought that since I hadn't seen any resolution I'd play around and see if I could figure out what was causing it.

All of my MKVs are created by BDRB, and I haven't had a problem with them. But since I was just playing around with this, and I thought resolution might have an impact, I grabbed a bunch of MKVs off the net, and ended up with several different resolutions. I'd bet anyone running into this issue has odd sized files, for whatever reason. When the files are "normal" resolutions there doesn't seem to be any trouble.

The 2.6.12 version of tsmuxer seems to dislike the odd sized files, but the older tsmuxer doesn't. Why I couldn't say. I didn't think you did any resizing until the final re-encode. I assumed tmuxer would just grab the video as is and put it into the pseudo BD structure without making adjustments, and any resizing would be done as part of the re-encode. But that isn't how it's working with the 2.6.12 version. The process goes far too fast for it to be encoding the files, so is there some way for tsmuxer to just alter the res? Is tsmuxer supposed to resize when extracting to the pseudo structure, or is that an unexpected behavior?

In any case, there's an easy work around. The older version of tsmuxer did complete an import of 7 of these 1912x1072 resolution MKVs, each around 2GB, and BDRB created an ISO with them and they all play nicely. So, if someone hits this, they can use the older tsmuxer to get around it. Though I have also encountered files that encode the video fine, but pork the audio. So clearly it's best to use well conforming sources in the first place. :) But folks don't often do what's best. So, for future reference, next time someone has a gray screen issue, maybe it's from this.

Cheers,
:)You are correct. BD-RB doesn't resize until reencoding. The parameters to be used are stored in the PSEUDO folder and in the PSEUDO.INF file. This also applies to any audio manipulation (e.g. if the source is 44.1Khz).

It would make sense that TSMUXER might have issues importing odd resolutions. It has to determine how to set the parameters in the MPLS and CLPI files (and they are limited to legal BD resolutions). I'm guessing these files are just to weird for it.

[Guest]

I grabbed a bunch of MKVs off the net You can't discuss that stuff here, per rule 6. If you do it again you'll get a strike.

[Chuckwagon]

@Chuckwagon

Where do you get these MKV files? And did you not see jdobb's statement:

"I'm sorry, but please review the thread and the criteria for bug reporting. I don't accept bug reports on preprocessed sources. Experience has proven that almost ALL reports using preprocessed sources were shown to have issues before being presented to BD-RB for backup."

There are many video files, all of legal content, floating about on the web. Finding samples with which to work is easy.

And as for "preprocessed" sources, this is a discussion of the import feature, which accepts MKV files, so it sort of has to include preprocessed sources in this case, since you can't get an MKV without processing a source to make it. ;) And I wasn't reporting a bug, just trying to find more details about an issue some one else reported, in an effort to clarify the issue.

I grabbed a bunch of MKVs off the net
You can't discuss that stuff here, per rule 6. If you do it again you'll get a strike.

No such discussion was taking place nor intended.

:)

[Guest]

You cannot discuss downloaded material unless you specifically show for each instance that it is in the public domain. Strikes will follow if you do not abide by this. Is it clear? If not, please follow up in PM to me and not in this thread. Thank you.

[Diego]

Hi everyone, my name's Diego. I have used bdrebuilder many times, but with the last upgrade, I have some problems....
I have two pc, with Windows 7.
In the first pc, when I try to convert a bluray 50 to 25 gb, after a few minutes the pc shutdow. This appen with a movie of 2002, Rookie from Disney.

In the second pc, when I try to do the same ( rebuild from 50 to 25 ) all goes ok, but at the end, the size is 14 gb, and the movie freeze after 20 minutes.

I've ripped with anydvdhd, and burnt on 50 gb it works...

Any ideas?

Thanks.

P.S. the log show no error ... :(

[jdobbs]

Go to the first page of this thread and install exactly as outlined with exactly the links provided. If you follow that sequence BD-RB will work every time.

[RobertM]

Hi Diego,

First, do what JD suggested above. But keep in mind that it could still be a bad rip. BD players are designed to throw out data errors and keep going. BD-Rebuilder is not. A bad rip can sneak through, without causing an error message during ripping, and then cause unpredictable results later on. So if re-loading the helper apps doesn't solve the problem, then try cleaning the disc and ripping again.

I've ripped with anydvdhd, and burnt on 50 gb it works...

[gonca]

In the first pc, when I try to convert a bluray 50 to 25 gb, after a few minutes the pc shutdow.

Maybe time to clean the dust bunnies. Tis the season for overheating.

[Diego]

Thanks to everyone,I'have reinstalled all, as the first page and the file readme. said, but still the problem remains.
I've made a try with another disk, machete kills.
Made new rip. The original copy burnt on br rewritable works ( it is about 27 gb ) but, the resize made to fit it in br 25, is 17 gb, and the movie freeze in the first 20 minutes....

Here the process :
LABEL=MACHETE_KILLS_BD
VERSION=v0.47.06 (beta)
SOURCE_SIZE=28830789738
SOURCE_VIDEO_SIZE=28796123136
TARGET_SIZE=24641536000
REDUCTION=.8545202172454
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;ita;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=7
REBUILD_COMPLETE=1
[00004]
AUDIO=11
PGS=10
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=19590818113
RATE=22009
SPLITS=1
NSTART=27000000
NEND=318352934
NSIZE=13953964032
FLINK=0
MLINK=0
[00005]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=591473901
RATE=18179
SPLITS=1
NSTART=27000000
NEND=37713202
NSIZE=576651264
FLINK=0
MLINK=0
[00006]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=587714778
RATE=18172
SPLITS=1
NSTART=27000000
NEND=37645635
NSIZE=580958208
FLINK=0
MLINK=0
[00007]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=291746820
RATE=18562
SPLITS=1
NSTART=27000000
NEND=32178298
NSIZE=288024576
FLINK=0
MLINK=0
[00008]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=324339889
RATE=18487
SPLITS=1
NSTART=27000000
NEND=32777021
NSIZE=330252288
FLINK=0
MLINK=0
[00009]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=237764549
RATE=18770
SPLITS=1
NSTART=27000000
NEND=31172293
NSIZE=233533440
FLINK=0
MLINK=0
[00010]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2983011348
RATE=17912
SPLITS=1
NSTART=27000000
NEND=81872317
NSIZE=2456303616
FLINK=0
MLINK=0

the target was 24 gb , but at end process it is 17.... :confused:

[Ch3vr0n]

The original copy burnt on br rewritable works

If it's burnt to a bd-re then it's not an original, that being said if that one works, then why don't you simply use IMGBurn to burn the disc again. Do a straight copy

[worknstiff]

@ Diego; RE: I've made a try with another disk, machete kills.

You are not showing your BD Rebuilder log and did you run the inspect to see if everything is installed correctly. Plus you don't say what player you're using to play back the final rebuilt BD. It seems like maybe it has something to do with cinavia since this is an infected disk and it's also stopping at 20 min. Just sayin', maybe it's a player problem if you are using a up to date software player or a BD player that's mfg. after Feb 2012.

[kabster]

possible Bug 101!!

have made an bd50 → bd25 from the movie AvP Extended edition and during playback the movie freezes at every chapter for an few secs and continue's with playback on stand alone player !!
tested in software player (TMT 6) the image freezes and stay's frozen !!

This is happening with the Extended selection .., when selecting Theatral (original) everything play's fine both on stand alone and software player !!

Have tried an Movie only backup, and it seems to play fine BUT!!

The movie only wos the original (cutted) version and not the extedended version !!

Thats another thing i like to know, how to choose the extended version when doing an "movie only" backup !!


Original Rip seems unaffected and play fine !!

BD-rebuilder 0.47.6
Every utility up to date (check)

regards,