BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Sorry, but physics denys it. HD Audio is too big to fit on a DVD-9. There would be little or no space left for the video.

Of course, since the human ear can't detect HD audio compared to DD5.1@640Kbs* it really doesn't matter anyway. JMHO.

Any custom size over 8500 would allow it -- but be careful, you still might end up with a terrible picture or "failure to fit" messages.


*According to Dolby Labs AC-3 audio is transparent (indistinguishable from source material in double-blind tests) at 640Kbs.

[laserfan]

*According to Dolby Labs AC-3 audio is transparent (indistinguishable from source material in double-blind tests) at 640Kbs.
Or if you're >60yrs old, or otherwise spent years (say, in college) using headphones and wearing-out Led Zeppelin cassette tapes, then you don't bother even w/640k as 448 is plenty good enough.

Not that I know of anyone to whom this applies of course! ;)

[omegaman7]

This is a shot from "I am number four". (They're PNG J.D.)

Jdobbs, is there a way to tweak the dark scenery? What I mean is, can it be more gentle with them? I'm still seeing significant artifacting in the darker scenes. I'm gonna burn my result and see how it looks on the plasma. The plasma has better rendering than my monitor ;) I've noticed that lots of encoders, seem to pull bitrate from the dark scenes. ConvertX is really bad. Sure would be wonderful if we could allocate more bitrate to them. I'm probably just really critical :(

Original frame #17661, no compression.
http://img202.imageshack.us/img202/4228/17661orig.th.png (http://imageshack.us/photo/my-images/202/17661orig.png/)
Slowest encode setting frame #17671(only 10 frames off, where the last encode was 29).
http://img197.imageshack.us/img197/9374/17671re.th.png (http://imageshack.us/photo/my-images/197/17671re.png/)

Ok, the video plays fine on the BD player in the living room. Though it does downscale to 720P. It's not a full HD TV :( My guess is, that TMT 3 is simply not rendering it properly. THough the original renders better.

[Sharc]

- Fixed an issue in subtitle end-times related to
previously resized (via TSMUXER) subtitles.


I just want to report back that subtitles are fine now.
I tried from a 24 fps 720p source. PAL framerate conversion to 25 fps (speedup), audio speedup without pitch shift, and subtitles speedup with correct playback times :)

[Capsbackup]

Or if you're >60yrs old, or otherwise spent years (say, in college) using headphones and wearing-out Led Zeppelin cassette tapes, then you don't bother even w/640k as 448 is plenty good enough.

Not that I know of anyone to whom this applies of course! ;)

Well if you include Jeff Beck too, I confess :o

[JJB]

Well if you include Jeff Beck too, I confess :o

Don't leave out Robin Trower or Tommy Bolin.....Then I will testify!

[steveg32]

@steveg32 and others who have reported sync issues on DVD-5/9 output.


I think I've found a connection. On my test computer I had upgraded to AVISYNTH v2.58 some time ago so I can certify it as the recommended version. When I removed it and reinstalled v2.57 (the currrent recommendation) I was able to repeat the sync issue on certain discs. When I reinstall v2.58, the problem is solved.

So, though it is still not completely clear why, it appears that the DVD-5/9 audio synchronization problem is linked to using the combination of HC Encoder and AVISYNTH 2.57.

Since I have been running v2.58 for some time now, I am confident it is safe to use and I have now updated the first link of this thread so that it now links to that version.

@steveg32

Can you please download and install this version of AVISYNTH (http://www.jdobbs.net/freeware/Avisynth_258.exe) and report if it corrects your issue?

Thanks.

@jdobbs

Will do. Mahalo jdobbs! :)

[jdobbs]

Or if you're >60yrs old, or otherwise spent years (say, in college) using headphones and wearing-out Led Zeppelin cassette tapes, then you don't bother even w/640k as 448 is plenty good enough.

Not that I know of anyone to whom this applies of course! ;) Cassettes? So you decided to go "HD audio" and give up the 8-tracks, eh? Let's add Hendrix, Jethro Tull, Deep Purple, Steppenwolf, Cream, The Byrds, CSN, Jefferson Airplane, and Creedance Clearwater Revival. We can even cover Page, Beck, and Clapton together just by saying "The Yardbirds".

"Get your motor runnin'..."

All of the above are on my iPod...

[laserfan]

*According to Dolby Labs AC-3 audio is transparent (indistinguishable from source material in double-blind tests) at 640Kbs.
BTW, am I correct in assuming that bits are applied equally to 5.1 tracks i.e. each track in this case gets 106.67Kbs? And thus my preferred (when I convert from HD audio, I use this, if the original is 640 I just leave it alone) 448 yields 75kbps?

I ask cuz in olden times when I'd rip my CDs, I did so to 160Kbps (80 per stereo track) and it sounded fine to me. I guess now that I make this comparison 448 does seem slightly weak, though I read somewhere else that 448 is as much as 9x% of the population can discern...

[Sharc]

BTW, am I correct in assuming that bits are applied equally to 5.1 tracks i.e. each track in this case gets 106.67Kbs? And thus my preferred (when I convert from HD audio, I use this, if the original is 640 I just leave it alone) 448 yields 75kbps?

I ask cuz in olden times when I'd rip my CDs, I did so to 160Kbps (80 per stereo track) and it sounded fine to me. I guess now that I make this comparison 448 does seem slightly weak, though I read somewhere else that 448 is as much as 9x% of the population can discern...
Good question. I would assume that the LFE channel with an upper cutoff of 120 Hz requires a fraction (say less than 1%) of the bitrate of any of the "regular" 5 channels. Means the LFE channel is "almost free", and we may split the 448kbps to 5 tracks rather than 6, means 448/5=90 kbps for each of the 5 "regular" channels which compares favourably with your former 80 kbps per stereo track. My speculation rather than science ...
And Dolby Digital in Cinemas is 320 kbps. So if we are aiming at Cinema experience we should be happy with even less. :devil:

And just want to add Fleetwood Mac and The Who to your list as causes for changing our ears to lowpass filters ....

[jdobbs]

BTW, am I correct in assuming that bits are applied equally to 5.1 tracks i.e. each track in this case gets 106.67Kbs? And thus my preferred (when I convert from HD audio, I use this, if the original is 640 I just leave it alone) 448 yields 75kbps?

I ask cuz in olden times when I'd rip my CDs, I did so to 160Kbps (80 per stereo track) and it sounded fine to me. I guess now that I make this comparison 448 does seem slightly weak, though I read somewhere else that 448 is as much as 9x% of the population can discern... If I remember correctly (not a sure thing) all but the LFE use equal bitrate and the LFE uses 1/3rd as much. In 448Kbs (DVD) I think that was 96Kbs per channel (80Kbs maybe?) and 32Kbs for LFE. I'd assume 640Kbs is allocated the same way.

[HWK]

Please note that the recommended version of AVISYNTH has changed. All users are advised to update to v2.5.8.0. A link to that version is included in the first post of this thread.

Jdobbs do you think changing inspect.exe would be good idea so it would say avisynth 2.5.7.0 is not recommended version.

[laserfan]

I would assume that the LFE channel with an upper cutoff of 120 Hz requires a fraction (say less than 1%) of the bitrate of any of the "regular" 5 channels. Means the LFE channel is "almost free"...
In 448Kbs (DVD) I think that was 96Kbs per channel (80Kbs maybe?) and 32Kbs for LFE.
Well 5x80=400 leaving 48kbps which is over 50% of the size of the other channels. If you believe that the table below has all the legal bitrates in it (taken from the Standards doc I have, which is almost completely indecipherable to me) this is the only way the math comes-out right. :confused:

Sorry to take this thread OT but I'm likin' 448-640kbps for 5.1 better every minute.
‘000000’ (0) 32 kbps 60 42 40
‘000001’ (0) 32 kbps 60 43 40
‘000010’ (1) 40 kbps 75 53 50
‘000011’ (1) 40 kbps 75 55 50
‘000100’ (2) 48 kbps 90 65 60
‘000101’ (2) 48 kbps 90 65 60
‘000110’ (3) 56 kbps 105 75 70
‘000111’ (3) 56 kbps 105 76 70
‘001000’ (4) 64 kbps 120 86 80
‘001001’ (4) 64 kbps 120 87 80
‘001010’ (5) 80 kbps 150 108 100
‘001011’ (5) 80 kbps 150 108 100
‘001100’ (6) 96 kbps 180 130 120
‘001101’ (6) 96 kbps 180 130 120
‘001110’ (7) 112 kbps 210 151 140
‘001111’ (7) 112 kbps 210 152 140
‘010000’ (8) 128 kbps 240 173 160
‘010001’ (8) 128 kbps 240 173 160
‘010010’ (9) 160 kbps 300 217 200
‘010011’ (9) 160 kbps 300 217 200
‘010100’ (10) 192 kbps 360 260 240
‘010101’ (10) 192 kbps 360 261 240
‘010110’ (11) 224 kbps 420 303 280
‘010111’ (11) 224 kbps 420 305 280
‘011000’ (12) 256 kbps 480 347 320
‘011001’ (12) 256 kbps 480 348 320
‘011010’ (13) 320 kbps 600 435 400
‘011011’ (13) 320 kbps 600 435 400
‘011100’ (14) 384 kbps 720 521 480
‘011101’ (14) 384 kbps 720 522 480
‘011110’ (15) 448 kbps 840 608 560
‘011111’ (15) 448 kbps 840 610 560
‘100000’ (16) 512 kbps 960 696 640
‘100001’ (16) 512 kbps 960 696 640
‘100010’ (17) 576 kbps 1080 782 720
‘100011’ (17) 576 kbps 1080 783 720
‘100100’ (18) 640 kbps 1200 870 800
‘100101’ (18) 640 kbps 1200 871 800

[jdobbs]

Jdobbs do you think changing inspect.exe would be good idea so it would say avisynth 2.5.7.0 is not recommended version. It will already say v2.5.8.0 is "Ok" -- but will also say "Ok" for v2.5.7.0. The fact is that v2.5.7.0 has been working fine for a long time... I'll probably wait a couple revisions and then start enforcing v2.5.8.0 as the only "Ok". The only issue I've found is when creating DVD output -- and that seem to be selective.

[Ch3vr0n]

It will already say v2.5.8.0 is "Ok" -- but will also say "Ok" for v2.5.7.0. The fact is that v2.5.7.0 has been working fine for a long time... I'll probably wait a couple revisions and then start enforcing v2.5.8.0 as the only "Ok". The only issue I've found is when creating DVD output -- and that seem to be selective.

You must have missed my post then. http://forum.doom9.org/showpost.php?p=1503653&postcount=12097 HP5 backup failed with 2.57 but worked with 2.58.

did get some weird behavior though. If i play the back up on my computer, both movie and extras have audio. If i play the backup on my standalone, only the movie has audio. Extra's play fine but no audio :s

[jdobbs]

You must have missed my post then. http://forum.doom9.org/showpost.php?p=1503653&postcount=12097 HP5 backup failed with 2.57 but worked with 2.58.

did get some weird behavior though. If i play the back up on my computer, both movie and extras have audio. If i play the backup on my standalone, only the movie has audio. Extra's play fine but no audio :s I read it -- but I have doubts it is definitely v2.5.7 that is the cause (without some other contributing factor), mainly because if it were that alone it would have been reported by many, many users. v2.5.7.0 has been in use with BD-RB for over two years now. I also ran Harry Potter 5 with v2.5.7.0 on my computer and had no issues

[Ch3vr0n]

well then i don't know why it failed with 2.57 but worked with 2.58. However now i have a weird audio problem on playback lo, think i'll get a batch of double layer blanks even though they're expensive. That way i'll be able to back it up without much hassle and have printable double layers for my future 3D discs :)

[steveg32]

@steveg32 and others who have reported sync issues on DVD-5/9 output.


I think I've found a connection. On my test computer I had upgraded to AVISYNTH v2.58 some time ago so I can certify it as the recommended version. When I removed it and reinstalled v2.57 (the currrent recommendation) I was able to repeat the sync issue on certain discs. When I reinstall v2.58, the problem is solved.

So, though it is still not completely clear why, it appears that the DVD-5/9 audio synchronization problem is linked to using the combination of HC Encoder and AVISYNTH 2.57.

Since I have been running v2.58 for some time now, I am confident it is safe to use and I have now updated the first link of this thread so that it now links to that version.

@steveg32

Can you please download and install this version of AVISYNTH (http://www.jdobbs.net/freeware/Avisynth_258.exe) and report if it corrects your issue?

Thanks.

@jdobbs

Big mahalos! AviSynth v2.58 fixed ALL DVD output sync issues. Also, no more oversizing too! You're amazing brah. But what I most appreciate about you is your tenacity. You never give up. True warrior spirit. Aloha, jdobbs u da man! :)

[jdobbs]

@jdobbs

Big mahalos! AviSynth v2.58 fixed ALL DVD output sync issues. Also, no more oversizing too! You're amazing brah. But what I most appreciate about you is your tenacity. You never give up. True warrior spirit. Aloha, jdobbs u da man! :) Now that you mention it -- the output from my test run was larger with v2.57 also -- mahalo back at you for the follow-up.

Go Swords.

[Jonaldinho]

I have a 1080p video and because I live in the UK it's 25fps, it's not a movie it's a video from a videographer who gave me the HD file and I would like it to be playable on a blu-ray device. I know for blu-ray compliancy at 25fps it needs to be interlaced, I typed in the hidden option DEINTERLACER_TYPE=4 for fake interlaced, it's currently encoding the 2nd pass but the LASTCMD doesn't have --fake-interlaced in the script so I was wondering will it still be fake interlaced? Do I need to enable "use DEINTERLACER on interlaced sources" for fake interlaced to work? Thanks

[jdobbs]

I have a 1080p video and because I live in the UK it's 25fps, it's not a movie it's a video from a videographer who gave me the HD file and I would like it to be playable on a blu-ray device. I know for blu-ray compliancy at 25fps it needs to be interlaced, I typed in the hidden option DEINTERLACER_TYPE=4 for fake interlaced, it's currently encoding the 2nd pass but the LASTCMD doesn't have --fake-interlaced in the script so I was wondering will it still be fake interlaced? Do I need to enable "use DEINTERLACER on interlaced sources" for fake interlaced to work? Thanks Yes, you need to enable it. The deinterlacer type only applys when "Use Deinterlacer" is selected.

[Jonaldinho]

Yes, you need to enable it. The deinterlacer type only applys when "Use Deinterlacer" is selected.

OK thanks. I enabled it to deinterlace in the setup, it's on the 2nd pass now and the LASTCMD script still doesn't have fake-interlaced in the script. Is this right?

"O:\BD Rebuilder 38.03\BD_Rebuilder\tools\x264.exe" "L:\BACK UP MEDIA\BLU-RAY\VIDEO\WORKFILES\VID_00000.AVS"
--preset slower --bluray-compat --ref 4 --b-adapt 1 --b-pyramid none --weightp 1 --qpmin=0
--bitrate 29869 --level 4.1 --qpfile "L:\BACK UP MEDIA\BLU-RAY\VIDEO\WORKFILES\VID_00000.CHP"
--sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 30000 --keyint 24 --min-keyint 1
--ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input
--stats "L:\BACK UP MEDIA\BLU-RAY\VIDEO\WORKFILES\VID_00000.AVS.264.stats"
--pass 2 --output "L:\BACK UP MEDIA\BLU-RAY\VIDEO\WORKFILES\VID_00000.AVS.264"

[jdobbs]

You're right. I just looked at the code. It isn't adding the "--fake-interlaced" because the source is 1080p. Since 1080p/25 isn't a legal BD source, BD-RB doesn't have a condition for that occurance. I'll have to add it just to cover all bases (and for 1080p/29.97 as well). Right now that command line will create output that is out-of-standard.

In the meantime, you can add this to your INI file:

TWEAK_PASS_ONE=--fake-interlaced
TWEAK_PASS_TWO=--fake-interlaced

Don't forget to remove the lines after your encode is complete, as it will affect all encodes until you do.

[Jonaldinho]

I'm glad i've raised awareness to help eliminate a problem. I've added the tweaked x264 command and it has successfully been added to the LASTCMD script. Thanks a lot.

[europeman]

Does Rebuilder support any of these similar technologies to speak up process

[jdobbs]

No. It does not use any "special features" or dependencies that requires specific hardware. I do that purposely.

[Capsbackup]

I have found a strange occurance doing a full movie backup to BD9 of the movie I AM Number Four. The deleted scenes are listed as 18:58 on the original disc. On the BD-RBV03803 backup, the same deleted scenes are listed as 30:39. :confused:
These scenes are 1080P, 23.976fps. There are numerous duplicate .m2ts files within the same playlist 00329.mpls.
Could this be the problem, that BD-RB is not making the necessary reference corrections?

[jdobbs]

I have found a strange occurance doing a full movie backup to BD9 of the movie I AM Number Four. The deleted scenes are listed as 18:58 on the original disc. On the BD-RBV03803 backup, the same deleted scenes are listed as 30:39. :confused:
These scenes are 1080P, 23.976fps. There are numerous duplicate .m2ts files within the same playlist 00329.mpls.
Could this be the problem, that BD-RB is not making the necessary reference corrections? Don't know. I'll try that one and see what happens.

Do they appear to play correctly?

[Capsbackup]

Don't know. I'll try that one and see what happens.

Do they appear to play correctly?

They play correctly until the last deleted scene, where the video freezes on the screen at the last 5 seconds or so, while the audio continues to completion.

[jdobbs]

They play correctly until the last deleted scene, where the video freezes on the screen at the last 5 seconds or so, while the audio continues to completion. Weird. If the audio is that long (full time), it makes you wonder why the original's time was shorter? The data was there, but didn't show in the original time... easter eggs, maybe?

[Capsbackup]

Weird. If the audio is that long (full time), it makes you wonder why the original's time was shorter? The data was there, but didn't show in the original time... easter eggs, maybe?

I'm pretty sure there is no easter eggs. My suspicion is this multiple, duplicate m2ts files within this playlist is the cause. I can't be certain, but this is the only thing I can see as to this backup having a different time than the original.

By the way, this was a pretty good movie too. :)

[Ch3vr0n]

Just wanted to let ya know jdobbs, i ran a couple more tests and was able to backup HP5 with avs 2.58

[jdobbs]

Just wanted to let ya know jdobbs, i ran a couple more tests and was able to backup HP5 with avs 2.58

Good to know, I sure wouldn't have thought AVISYNTH 2.57 could be the problem. But as long as its working...

Thanks.

[bassnut]

I am just ripping I Am Number Four now and will let BD Rebuilder run though there is no way I will be able to stay up for another 4 hours tonigh will let you know what happens in the early am. Anything s[eciffic you want to know or for me too look for?

[Ch3vr0n]

I think it crashed because vid_00033 and vid_00002 were generating the message "encoding secondairy ..." however when lookin on the expanded entry in the filetree, there is no secondairy video stream present nor a secondairy audio stream. Those were also the only 2 streams in the tree that were listed with ** next to the fps rate.

vid_00033 VC-1, 1080i, 29.97fps** 587.15MB
vid_00002 VC-1, 1080i, 29.97fps** 2.239,99MB

I think since there was no second stream in those stream, AVS crashed. But that only a guess for me. I'm not that experienced as you are :)

[Capsbackup]

Weird. If the audio is that long (full time), it makes you wonder why the original's time was shorter? The data was there, but didn't show in the original time... easter eggs, maybe?

To try and make better sense of what is going on for this movie, here is some additional info from the original Blu-ray:

1) 00329.mpls, 0:18:59
[514+503+502+503+505+504+505+507+506+507+509+508+509+511+510+511+512+513+512].m2ts
- Chapters, 13 chapters
- h264/AVC, 1080p24 /1.001 (16:9)
- AC3, English, stereo, 48kHz

The times listed for the original playlist 00329.mpls per BDInfo:

00514.m2ts = :33
00503.m2ts = :06
00502.m2ts = :58
00503.m2ts = 1:21
00505.m2ts = :06
00504.m2ts = 1:14
00505.m2ts = 3:06
00507.m2ts = :06
00506.m2ts = :51
00507.m2ts = :30
00509.m2ts = :06
00508.m2ts = 1:07
00509.m2ts = 1:20
00511.m2ts = :06
00510.m2ts = 1:02
00511.m2ts = 1:20
00512.m2ts = :07
00513.m2ts = :55
00512.m2ts = 3:57

The BD-RB reencoded playlist for 00329.mpls:

00514.m2ts = :33
00503.m2ts = 1:28
00502.m2ts = :58
00503.m2ts = 1:21
00505.m2ts = 3:14
00504.m2ts = 1:15
00505.m2ts = 3:06
00507.m2ts = :37
00506.m2ts = :51
00507.m2ts = :30
00509.m2ts = 1:27
00508.m2ts = 1:07
00509.m2ts = 1:20
00511.m2ts = 1:26
00510.m2ts = 1:02
00511.m2ts = 1:20
00512.m2ts = 4:04
00513.m2ts = :55
00512.m2ts = 3:57

After doing the math, reducing the times of the six duplicate files above is the difference. Now why these duplicate files and why BD-RB treats them the way it does, not matching the original is the question! :p

[thegame]

Sorry if this has been answered before but, does BD-RB work with 3D Blu-ray movies? I have decided to make the jump to 3D and have all the gear coming and was wondering this.

Thanks

[Capsbackup]

Sorry if this has been answered before but, does BD-RB work with 3D Blu-ray movies? I have decided to make the jump to 3D and have all the gear coming and was wondering this.

Thanks

No it does not. :(

[Ch3vr0n]

There currenly is only 1 way of backing up 3D blu-rays, and thats a 1:1 backup (or covert to a side-by-side portable file afaik with DVDCrap, buts thats not a real backup. Its a conversion)

[jdobbs]

Sorry if this has been answered before but, does BD-RB work with 3D Blu-ray movies? I have decided to make the jump to 3D and have all the gear coming and was wondering this.

Thanks Unfortunately the real stumbling block for 3D backups right now is a method for writing them. On a 3D disc there are blocks that are referenced by more than one file. Right now there is no popular burning software (that I know of) that would support that. Even if it did, a calling program would have to give a lot of information to the software to tell it which parts of which files are to be shared.

The only current way to get around that is to have the blocks duplicated -- which would be exceptionally inefficient.

[thegame]

Unfortunately the real stumbling block for 3D backups right now is a method for writing them. On a 3D disc there are blocks that are referenced by more than one file. Right now there is no popular burning software (that I know of) that would support that. Even if it did, a calling program would have to give a lot of information to the software to tell it which parts of which files are to be shared.

The only current way to get around that is to have the blocks duplicated -- which would be exceptionally inefficient.

Thanks, I assumed it couldn't be done, but I thought I would ask.

[bassnut]

I Am Number Four.

Extras are all encoded twiced as previously posted thopugh some do not have the directors comentary defore the clip. All play fine and I didn't have any freezes as Cap's did. Should not that this is only evident when you click on play all if you select the individual Deleted Sceen it just plays once.

[MickJT]

On a 3D disc there are blocks that are referenced by more than one file. Right now there is no popular burning software (that I know of) that would support that. Even if it did, a calling program would have to give a lot of information to the software to tell it which parts of which files are to be shared.

The only current way to get around that is to have the blocks duplicated -- which would be exceptionally inefficient.

You got me thinking. I've mentioned in another thread my opinions & theories on how it works, but I now think it's more likely the .ssif files are the real files, and the .m2ts files are the virtual files. It makes more sense if you think about how the drive & laser read the disc; It would be much more efficient and not wear out the motor as much, and also be faster, to have the .ssif as the non-virtual file.

[k-c-ksum]

this looks interesting

http://www.sisveltechnology.com/3D_tile_format.asp

720p 3D from a 1920x1080.

Your 3DTV would need to support it but it would get around the need for MVC and siff file creation. AVISYNTH could take care of the tiling :)

how much res could be created if the source material is 2:40.1 as the black space wouldnt need to be encoded? Something to look at a bit furher down the road prehaps?

[setarip_old]

@jdobbs, @thegame

For what MAY prove to be a pleasant surprise, try specifically using MakeMKV to rip "Dinosaurs Alive 3D" and then perform a FULL DISC backup with BD Rebuilder.

As opposed to using AnyDVD, which copies the .SSIF files at their full 15.2Gb combined filesizes (apparently essentially duplicates of most of the .M2TS files), it appears that MakeMKV is able to extract the pertinent data (likely primarily pointers) from the .SSIF files - and save it as a miniscule total of 56.2Kb in five "SSIF.MAP" files.

File 00008.M2TS contains the 2D full movie (8.86Gb), while file 00009.M2TS (4.67Gb) apparently contains the required additional information for 3D display. I'd speculate that 00009.M2TS likely has to remain uncompressed - and it does when using BD-RB . (I say "I'd speculate" because I do not presently have the required hardware to playback "new 3D" discs)...

Note: After compressing with BD Rebuilder, you'll have to manually copy the five tiny ".SSIF.MAP" files into the "SSIF" sub-folder.

[jdobbs]

I have found a strange occurance doing a full movie backup to BD9 of the movie I AM Number Four. The deleted scenes are listed as 18:58 on the original disc. On the BD-RBV03803 backup, the same deleted scenes are listed as 30:39. :confused:
These scenes are 1080P, 23.976fps. There are numerous duplicate .m2ts files within the same playlist 00329.mpls.
Could this be the problem, that BD-RB is not making the necessary reference corrections? I ran this one and was able to repeat it. It was caused by the fact that some CLPI/M2TS pairs were referenced more than once within the same MPLS and one of them was for partial playback. A fix I had added into v0.34.06 (to correct a TSMUXER end-time glitch and resulting "stutter") needed to be tweaked to consider the possibility of multiple-reference/partial playback.

I've fixed it for the next release.

[Capsbackup]

I ran this one and was able to repeat it. It was caused by the fact that some CLPI/M2TS pairs were referenced more than once within the same MPLS and one of them was for partial playback. A fix I had added into v0.34.06 (to correct a TSMUXER end-time glitch and resulting "stutter") needed to be tweaked to consider the possibility of multiple-reference/partial playback.

I've fixed it for the next release.

Thanks again! :) I am impressed with your continued vigilance. ;)

[Acerjen]

Jdobbs,

I have a question about DTS Express and how it differs from
AC3 Plus.

I have backed up a few movies that use AC3 Plus instead of DTS Express for the PIP track and it works fine in the final BD-25 disc. Everything is in sync. I assume this works because TSMUXER supports AC3 Plus but not DTS Express? So, I was curious what the difference is. I was also wondering if it would be possible to convert DTS Express tracks to AC3 plus and then use TSMUXER to put it back together? I was curious and thought maybe you would know the answer.

I would also like to thank you for such an awesome program and all the time you put into it. Thanks.

Later,
Acerjen

[PurpleMan]

Unfortunately the real stumbling block for 3D backups right now is a method for writing them. On a 3D disc there are blocks that are referenced by more than one file. Right now there is no popular burning software (that I know of) that would support that. Even if it did, a calling program would have to give a lot of information to the software to tell it which parts of which files are to be shared.

The only current way to get around that is to have the blocks duplicated -- which would be exceptionally inefficient.

Actually, wouldn't it be sufficient to have a program that can write such ISO files? (then use any burning software to write that ISO)

[jdobbs]

Actually, wouldn't it be sufficient to have a program that can write such ISO files? (then use any burning software to write that ISO) Yes, but typically the ISO is created by the same (or similar) program that writes it.