Backup full Blu-Ray Disc to a 25GB, possible??? [Archive]

kaid

13th October 2008, 11:44

Hi Guys,

I'm trying to backup a Blu-Ray Disc which is 27GB to a 25GB recordable.

I realise I'm out by 2GB, is there any way to compress a Full Blu-Ray Disc down a few GB to allow it to be copied.

I'm wanting to keep the Menus in-tact and will be happy to rip out some bits and pieces here and there.

Basically I'm looking for something like DVD2one for Blu-Ray, anything I can use?

Cheers.

I doubt there's anything like that yet, but once BD and especially BD-backupping becomes more mainstream, there undoubtedly will be! ;-)
Which will finally answer my question if lower-bitrate-transcoding like with DVD and MPEG2 is actually possible with H.264...

Right now as I see it your best option is manually. If you only want to remove something, identifying the respective .m2ts stream and merely deleting it should do the job already (i've done so with Tsmuxer-made AVCHDs, and they work fine!), just make sure to keep the respective .clpi and .mpls files!
If you want to re-compress something it's way more tricky, you need to rip it out, put it through x264 to re-encode with a lower bitrate (make sure to keep it BD-standard compatible, no cropping, Level 4.1 max, not too many reference frames etc! If you need BD-compatible x264 args just ask!), re-mux a BD-structure with tsmuxer and then integrate the .m2ts, and .clpi, I'm not sure about the .mpls, because in there in the information on play-order of the clip, and I dunno if TsMuxer's matches your BD... Checking both .mpls (original .m2ts and TSmuxer-made) in a binary editor to compare if they're roughly similar should give you an idea if you should replace it (=quite different) or not (=rather similar). E.g. if the original .mpls references many .m2ts files and the tsmuxer one only one, it will most likely NOT work (or atleast not work properly!) if you keep the original one!
I still don't quite know what data really *can* be in the .clpi and .mpls files, I only worked with the rather simple TsMuxer made ones, so they could e.g. do some far out advanced menu stuff on original BDs that also ends up in there, which will most probably result in the BD fucking up if you replace it with a TsMuxer made one. "Fucking up" completely or just when you run that track? I don't know, since haven't had the chance to trial-and-error with original BDs yet! ;-)

Now, please don't hang me if BD has some more coherency-checks than AVCHD in place, cause AVCHD is all I ever burned myself, and you end up with a $8 coaster! ;-) All I can say is that I did simply delete .m2ts files and the AVCHD (which was btw burned in a Bluray Filestructure with long filenames!) worked fine on my PS3...