Removing 3D SSIF Folder from Bluray

[KeVe1983]

Hey,

i have some 2D/3D Blurays.
The Blurays containing the main movie in 2D and also in 3D.

I want to remove the 3D movie parts.
So i have to delete the SSIF Folder in the STRAM Folder.

But after that the Bluray did not play, or did not play correctly.

Can some1 help?
What i have to do?
Or is is not possible?

Which apps did i need?

I just want to save some space on my HDD, also i want to convert the BD50 to BD25 without the 3D Feature.

[MickJT]

Have you tried movie only? The java code on the disc would look for various 3D indicators. As far as i'm aware, and I could be very wrong, the .mpls playlists do not reference the SSIF files.

If you wipe the SSIF folder and try a movie only encode, that may work.

Otherwise, I do know of another way to do a movie only encode.

[jdobbs]

BD-RB ingores the SSIF folder. Movie-only would be the only thing that would have a chance of working.

[HWK]

BD-RB ingores the SSIF folder. Movie-only would be the only thing that would have a chance of working.

I don't think movie-only would work. Since ffdshow doesn't decode mvc encoded file.

[k-c-ksum]

I don't think movie-only would work. Since ffdshow doesn't decode mvc encoded file.

the left eye stream is avc encoded so is compatible for a movie only backup

[MickJT]

That is correct. From my observations, without the SSIF folder, you simply have a 2D Blu-Ray structure but the Java code on the disc would still check for 3D. Thus a movie only encode should work fine. As said above, from what i've seen, the playlists do not reference SSIF files. It's up to the player to see them.

My opinions are based on me looking at my Tron Legacy disc.

The .ssif files are virtual files interleaving the left eye AVC .m2ts and a right-eye MVC encoded data. The left-eye information in the virtual .ssif points to the same data (actual physical location) in the .m2ts.

For a disc only containing the 3D movie at the maximum bitrate, if the MVC data for the right eye was a 50% overhead, you'd have a 33GB .m2ts and 17GB MVC data in the .ssif interleaved with the data in the m2ts making it look like the disc has 83GB of data on it.

In order to re-author a 3D Blu-Ray disc, and assuming you have an MVC encoder and can create an .ssif yourself, you could reduce the bitrate heavily or you'd need specialised burning software designed specifically for burning 3D Blu-Rays.

Though this post is veering off the original topic of discussion, it should help you understand what BD-RB can and can not do, and why.

(For purposes of this post, 1GB = 1 billion bytes)

Edit: Read http://forum.doom9.org/showthread.php?p=1504970#post1504970 | It's probably more likely that the .m2ts files are the virtual files.

[setarip_old]

It's probably more likely that the .m2ts files are the virtual files. To be more accurate, it seems that the SECONDARY .M2TS files (about half the size of the primary REAL .M2TS files) apparently contain the required additional information for 3D display.

I say this because, if you load a PRIMARY M2TS file into tsMuxeR, it will, as usual, show you video and audio stream information. However, if you load a SECONDARY M2TS file into tsMuxeR, you'll see a message stating, "Some tracks not recognized..." and it will only show the M2TS file in the upper window and nothing in the lower window.

BTW - In order to create a trouble free "movie only" version, create a folder named anything you want to name it, load the PRIMARY M2TS file into tsMuxeR, set as "Blu-ray" (at the bottom) and save to the folder you created.

Then use BD-RB to select as "Movie Only"...

BTW2 - Good guy "Mike Chen", author of MakeMKV, offers the following information/insight:
Many file systems, including UDF, support a notion of hard-linking - the same area on the disc may be referenced by multiple files. On a blu-ray disc the 3D title is presented by following files:

CLPI and M2TS for a "primary" clip that only has a 2D picture and all audio/subs. This file is played by a regular player.

CLPI and M2TS for a "secondary" clip that only has a 3D MVC extension data.

On the disc these two files are physically interleaved - a few kilobytes of first, few kilobytes of second, few kilobytes of first and so on. The physical (interleaved) area where these files are stored is referenced by 3 files - first M2TS, second M2TS and the whole area again as SSIF file.

[MickJT]

Ahh when I typed that I was thinking the MVC data was in the .ssif and there was no secondary .m2ts files. I do remember seeing them before but had forgotten. So the .ssif is interleaving the two .m2ts's together.

It'd be interesting to know how this is burnt to disc. You don't want the drive to be backtracking and wearing out the motor.

I still think it makes more sense that the .ssif is the regular file and the primary and secondary .m2ts files are virtual files.

Also this makes my calculations above incorrect. Your 50 gig (both primary and secondary) of data will look like 100 gig (when including ssif) instead of one primary 33 gig m2ts and secondary+primary in the ssif for 83gig as said earlier.

[KarstenS]

3D BDs are not that magic.

Look at the analysis of OpenSeason 3D done by ClownBD:

http://forum.doom9.org/attachment.php?attachmentid=12308&stc=1&d=1307905162

So its as I already said earlier: The complete stuff is stored in the ssif file. The m2ts file ist that one with hard links as this is optional (2D backward compatibility is an optinal feature and no must have). If it would be different, continous reading during 3D playback would not be possible.

As ClownBD is a remux tool and i can select the video stream, left and rigth eye video stream must be discrete and not things like extention data for right eye.

[jdobbs]

Ahh when I typed that I was thinking the MVC data was in the .ssif and there was no secondary .m2ts files. I do remember seeing them before but had forgotten. So the .ssif is interleaving the two .m2ts's together.

It'd be interesting to know how this is burnt to disc. You don't want the drive to be backtracking and wearing out the motor.

I still think it makes more sense that the .ssif is the regular file and the primary and secondary .m2ts files are virtual files.

Also this makes my calculations above incorrect. You're 50 gig (both primary and secondary) of data will look like 100 gig (when including ssif) instead of one primary 37 gig m2ts and secondary+primary in the ssif for 83gig as said earlier. The spec says they will be interleaved.

[LowDead]

Reading this thread it seem I was rather lucky ^^

I did the new disney movie tangled eu release. Removed the SSIF folder. Run it through multiAVCHD to remove warnings and other junk. Got ALOT of warnings.. Run it through BD-RB.. success.. have tried on both software players and standalones..