BD-3D MVC to m2ts - Missing chapters and no way to edit

[ultradj83]

Dears,
I just ripped my first BD-3D MVC to a .m2ts using tsMuxeR.

Video and audio are OK but I could't keep chapters, how to do this?

Then, I use to recode 2D blurays to save space, with Handbrake I usually do this with no appreciable quality loose on a 50" screen.
I found no tools can do this with MVC.
How can I do this with MVC?
Simply splitting the streams, recoding individually and then remuxing?


Thanks and best regards.

[sneaker]

Take a look at BD3D2MK3D. It will re-encode MVC to AVC. (no (free?) MVC encoder as good as x264) It should keep chapters if you rip the complete BluRay using e.g. AnyDVD or just the title using MakeMKV.

[ultradj83]

Very nice tool.
I'm trying it.

I'll do some tests to check what 3D format is compatible with my Samsung F6500 Smart TV.
Actually it reads, via DLNA, only one .m2ts file with MVC 3D video, but how can I check is this is Full-SBS, Full-TnB or Full-SequentialFrame?
This file has been converted by me from .mkv to .m2ts, because in .mkv the SmartTV plays it only in 2D, while simply converting to .m2ts with tsMuxeR it plays 2D and 3D.
Actually I'm converting to .mkv file a bluray .iso file with Full-SequentialFrame 3D using BD3D2MK3D, I'll check if the Smart TV can play it.

Any suggestions?

Thanks!

[ultradj83]

Failed, TV reports it doesn't support 47fps and this is why:

Video
ID                          : 1
Format                      : AVC
Format/Info                 : Advanced Video Codec
Format profile              : High@L4.2
MultiView_Count             : 2
MultiView_Layout            : Both Eyes laced in one block (left eye first)
Format settings, CABAC      : Yes
Format settings, ReFrames   : 4 frames
Codec ID                    : V_MPEG4/ISO/AVC
Duration                    : 1h 32mn
Width                       : 1 920 pixels
Height                      : 1 080 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 47.952 (48000/1001) fps
Color space                 : YUV
Chroma subsampling          : 4:2:0
Bit depth                   : 8 bits
Scan type                   : Progressive
Title                       : 3D Frame-Sequential (x264 high CRF 22 preset medium)

Why 47fps?
It should be 23.976 each eye...

I'm now trying with full T&B...

[r0lZ]

Very nice tool.

Thanks!

Why 47fps?
It should be 23.976 each eye...

Because 23.976 * 2 eyes = 47.952 fps in total. In frame sequential mode, there are two times the number of frames, and the player must play the odd frames for the left eye, and the even frames for the right eye (or the opposite). Therefore, the final frame rate is two times the usual rate. (It's not the same thing for the AVC+MVC format of the BD, where there are two independent streams, each stream at 23.976 fps.)

In half (or full) SBS or T&B, the frame rate is not modified, because the two views are combined in the same frame.

The TV must support the double frame rate to play frame sequential, or the double width or height of the frames to play the Full-SBS and Full-T&B formats.

For best compatibility, Half-SBS or Half-T&B are the best choices, and afaik all 3D TVs can play that formats.

[ultradj83]

Well this TV plays full frame 3D only from .m2ts.

I'm trying to understand:

1. If SBS, TnB or sequential (I have a 3D full movie it plays, but I found no tools to detect the kind)
2. How can I preserve chapters in the .m2ts (sounds not to be standard)
3. How can I recode it to have smaller file (for 2D I use handbrake with reference factor 22 and it's perfect on a 50" screen, for 3D I do the same with BD3D2MK3D but it creates a .mkv my TV doesn't play in full 3D)

Thanks a lot!

[r0lZ]

1. Not sure I understand your question. Normally, there are 3 ways for the player to detect the 3D format. BD3D2MK3D supports them all.
   The format is written in the header of the h264 stream. It's the --frame-packing option of x264. Many TVs recognise that format. It's the case of my Samsung.
   The 3D format is also written in the header of the container. It's the --stereoscopy argument of MkvMerge. I don't think that something similar exists for M2TS files.
   And finally, the player can use special strings in the file name to detect the 3D format. See Settings -> Output file name -> 3D format extension in BD3D2MK3D for the available options.
   
2. Unfortunately, the M2TS container does not support the chapters. If you really need them, you have to rebuild a full BD, and the chapters will be stored in the MPLS file. IMO, it's not a good solution.
   
3. You can simply untick the "mux to MKV file" in the bottom of tab 5, and BD3D2MK3D will create the h264 files, the audio streams and the 2D or 3D subtitles, and you will have to mux them manually to M2TS with tsMuxeR.

Note that it is also possible to re-encode in AVC+MVC format with FRIM, but it uses the only free MVC encoder currently available (made by Intel), and it is not very good. However, that may be a good solution for you, if your TV supports the AVC+MVC format. Have a look at the FRIM Encoder. I don't use it myself, so I cannot be sure that it's what you need, and I suggest to do a small test first.

[ultradj83]

1. Turning question: how can I read from stream or container if it's SBS, TnB or sequential?
2. You're right.
3. My TV is a Samsung F6500: the only full 3D MVC file I have was originally a .mkv and it didn't work, then I converted it to .m2ts with tsMuxeR and works (this is confirmed in the TV's specs page, MVC only with .m2ts). Also, I notice that AVC+MVC streams generated by BD3D2MK3D are smaller than original stream and that it has a reference factor field, I think it does recode and that's what I need.

As you can see I'm new to MVC.
About the codec, usually I find a AVC stream and a MVC stream: is MVC an indipendent stream or just a differential stream that contains differences by the AVC stream?
Is it also possible to have 2 full AVC stream? Does this make sense?


Thanks a lot.

[r0lZ]

how can I read from stream or container if it's SBS, TnB or sequential?

It's the player that must recognise the format, not the human beings. But if you really want to know the format, you can use MediaInfo. It displays the format of the video stream like this:

[...]
Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.1
MultiView_Count                          : 2
MultiView_Layout                         : Side by Side (left eye first)
[...]
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
[...]

Also, I notice that AVC+MVC streams generated by BD3D2MK3D are smaller than original stream and that it has a reference factor field, I think it does recode and that's what I need.

About the codec, usually I find a AVC stream and a MVC stream: is MVC an indipendent stream or just a differential stream that contains differences by the AVC stream?
Is it also possible to have 2 full AVC stream? Does this make sense?

BD3D2MK3D re-encode, that's right, but only to AVC. It doesn't do AVC+MVC. As I wrote above, only the free Intel encoder can encode to MVC, and I don't like that encoder. IMO, it is better to encode to Full-SBS or frame sequential in pure AVC with x264. The compression is equivalent, and the quality is better. Encoding to AVC+MVC makes sense only if you want to recreate a 3D BD. It's why I haven't tried to implement AVC+MVC in BD3D2MK3D.

MVC, as you suspected, is a differential stream. It is called the "dependent stream" in the BD terminology. It's why it is not easy to encode it, and there are no open source MVC encoder.

Frame-Sequential is equivalent to 2 AVC streams, but in fact, the frames are interleaved in a single video stream. I suppose that keeping two totally independent AVC streams makes sense, yes, but as far as I know, there are currently no muxers and no players supporting that format. You can mux 2 AVC video streams with MkvMerge, but they will be considered as 2 streams, not as a single 3D movie. And probably no player will be able to play it in 3D.

The 3D MVC MKV format is an exception. It has been developed by the authors of MakeMKV and is currently supported by MkvMerge and a few software players. Unfortunately for you, MakeMKV, as its name suggests, creates MKV files only, and also it's not an encoder. It extracts the original AVC and MVC files, combines them together to make a single AVC/MVC hybrid video stream that is then placed in a MKV container. IMO, it's only a good way to do a backup of a 3D BD, without quality loss, and without the useless streams and the 3D BD overhead. It's not a way to do a lighter version, and currently, you cannot use that files with hardware players.

[ultradj83]

Very interesting, thanks for all information.

Where can I find IMO? I couldn't find it googling...

About the format, my Mediainfo doesn't show the fields you highlighted, this is from the working .m2ts file:

Video #1
ID                                       : 4113 (0x1011)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Stereo High@L4.1
MultiView_Count                          : 2
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 2 frames
Codec ID                                 : 32
Duration                                 : 2 h 43 min
Bit rate mode                            : Variable
Maximum bit rate                         : 36.2 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Language                                 : English

Video #2
ID                                       : 4114 (0x1012)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.1
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 2 frames
Format settings, GOP                     : M=1, N=5
Codec ID                                 : 27
Duration                                 : 2 h 43 min
Bit rate mode                            : Variable
Maximum bit rate                         : 36.2 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Language                                 : English

What do you think?

[r0lZ]

Where can I find IMO? I couldn't find it googling...

What do you search? "IMO" means "In My Opinion". It's not a software.

What do you think?

It's normal. Your M2TS contains the two separate 3D streams (in AVC format for the main stream, and in MVC for the dependent stream). The format is therefore always 3D, like in a 3D BD. It cannot be SBS, T&B, or frame sequential (which are re-encoded formats) and it's not the MVC-MKV format created by MakeMKV (that contains only one combined AVC/MVC video stream). So, for your M2TS file, your question on how you can determine the 3D format doesn't make sense. Since there is a MVC stream, it's necessarily pure 3D. You can call it, as I does, "AVC+MVC 3D".

Note that there is another question regarding the 3D formats: the order of the views. In a 3DBD, the order of the views is stored in the MPLS file. It's usually (but not always) the "left view first". That means that the AVC stream is for the left eye, and the MVC for the right eye, and if you watch the movie in 2D, you see the view for the left eye. Approximately 5% of the commercial 3DBDs have the "right view first" order. The 3DBD player is responsible to send the pictures to the TV in the correct order, and the view order is transparent to the user... until the movie is converted to another format. Unfortunately, most of the times, hat information is lost during the conversion. BD3D2MK3D stores it in the stereoscopy field of the MKV header, and anyway, it places always the left view first, because it's the de-facto standard. But the frame-packing information within the AVC stream doesn't specify what view comes first, so when the container is not MKV, the information cannot be stored in the file itself. The only remaining option is to store it in the file name (like "3D-LR" for SBS left view first, or "3D-RL" for SBS right view first), but most players do not analyse the file name. As far as I know, all TVs assume left view first by default. When you play a movie with the views inverted, there is always an option in the player or TV to invert the order of the views at playback time. (Unfortunately, my Samsung TV takes only the frame-packing field into account, and therefore it cannot know the right view order. When it is right view first, I have to change the view order manually, and that option is deeply hidden within the Settings menu. I hate to have to do that. But since all movies that I have encoded myself with BD3D2MK3D are in the usual left view first order, I have to do it only for some rare 3D clips from Youtube.)

So, to summarize, here are the different formats available currently:

1. AVC+MVC in two streams
   It's the native 3D format used in the 3DBDs. It has two video streams. The "main view", encoded in AVC, can be played in 2D, the "dependent view", encoded in MVC, cannot be played alone.
   Containers: 3DBD or M2TS
   Not supported by BD3D2MK3D. Use FRIM to re-encode to AVC+MVC.
2. AVC/MVC in a single combined video stream
   The "main view" and "dependent view" are "combined" together by MakeMKV to create a single video stream.
   Container: Only MKV created by MakeMKV
   Not supported by BD3D2MK3D at all, but BD3D2MK3D can use that format as input, to create another (compressed) MKV.
3. Frame-sequential
   All frames for the two views are encoded in AVC and placed in a single video stream at double frame rate.
   Container: Preferably MKV, but can be placed in almost all containers, including M2TS
   Can be created by BD3D2MK3D, but most 3D TVs cannot play them. The recent Ultra-HD 3D TVs can normally play that format.
4. Full-SBS or Full-T&B
   The two views are stacked together horizontally or vertically in a single video stream
   Container: Preferably MKV, but can be placed in almost all containers, including M2TS
   Can be created by BD3D2MK3D, but most 3D TVs cannot play them. The recent Ultra-HD 3D TVs can normally play that format.
5. Half-SBS or Half-T&B
   The two views are stacked together horizontally or vertically, then resized to 1920x1080 (or smaller) and placed in a single video stream.
   They are the most common formats.
   Container: Preferably MKV, but can be placed in almost all containers, including M2TS
   Can be created by BD3D2MK3D, and (almost) all TVs can play them.

Since all formats can be "left view first" or "right view first", that give a total of 14 different possibilities theoretically available. It seems that your TV requires the first format.

[ultradj83]

Oops... sorry I read from mobile.

Following my TV specs I need to keep original AVC+MVC in the .m2ts.

Just to have a try, could you gently details all format parameters you use with your TV and how do you manage from BD to file?
I will just have a try, maybe with recent TV firmware updates it will work as on your side.

Thanks a lot.

[r0lZ]

Oh, well, it's complicated. I have written BD3D2MK3D because the manual way was too long, overcomplicated and prone to errors. Anyway, I don't convert to AVC+MVC M2TS, but to SBS MKV, and of course I use only BD3D2MK3D.

But here is the simplified procedure to create a AVC+MVC M2TS:

1. Demux the BD3D with tsMuxeR or eac3to. (Eac3to may have some problems with the subtitles.)
2. Re-encode the AVC and MVC streams with FRIM.
3. If you wish, you can also re-encode the audio with eac3to.
4. If you need so, you can create the 3D subtitles with BD3D2MK3D. (Let me know if you need that, because it's somewhat complicated.)
5. Remux with tsMuxeR.

The chapters are lost, but the rest should be OK.

[ultradj83]

Sorry maybe I've not been clear.

I want to keep the best quality so, like you suggested, I'll not use FRIM cause it returns bad quality, I just want to try to do exactly how you do for your TV.
So I think I will use BD3D to have a .mkv as you do.
Could you just tell me how you setup the frame?
Full or half? SBS or TnB or sequential?
Do you force 30/60fps?
Any other not default settings?

Thanks a lot.

[r0lZ]

Ah, OK. I convert to Half-SBS.
For the movies that have no French audio, I hardcode the French subtitles over the video (because most players and TV do not handle correctly the 3D subtitles).

The X264 parameters are: CRF 18 to 23, depending of the value of the movie, and the importance of the image quality. CRF 18 is for very detailed movies (like Sin City 2), and I keep CRF 23 for low quality movies. Normally, I use CRF 19 for animated films, and 20 or 21 for live movies.

I prefer the preset slow, because it compresses slightly better than the default (medium), but I don't use a slower preset because my TV doesn't support well the high compressions modes. Because I use the slow preset, it is necessary to "force level 4.1" (or 4.2) as otherwise the movie may be flagged as level 5.0 and my TV refuses to play it. I don't use the Tune parameter, and I encode in 8-bit colour depth (again because my TV refuses to play 10-bit). Normally, I don't need additional parameters, but sometimes I add "--threads 3" to keep one CPU thread for the other programs. That's not really necessary since the encoder runs at low priority anyway.

With that parameters, the result is very good, for a very small file size. You will certainly read on the net that CRF values greater than 17 or so produce bad quality, but it's absolutely not true. The worst thing that can happen is a banding problem (bands of discreet colours instead of smooth shades). That can be avoided only by using the greater colour depth, 10-bit, but most hardware players refuse that depth. You can slightly improve the image quality and decrease the banding problem with lower CRF values, but take in mind that lowering the CRF by 3 means that the video stream may be twice as big. So, with CRF 18, the size of the video stream is approximately 4 times greater than with CRF 23! Do not try a very low CRF, as you may run out of disc space!

Anyway, I suggest to do some tests with a small clip to select the CRF value you prefer. You may be more exigent than me if you are younger or if your screen is very big. Trust your eyes!

[ultradj83]

Dear,
about CRF I agree with you, 20 for SD and 22 for HD, I kept the same for 3D.

I understand .ssif files can contain AVC and/or MVC streams, but I need some confirmations.


As example, following Mediainfo, from a 3D bluray, this is 00000.m2ts

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                : 3 frames
Codec ID                                 : 27
Duration                                 : 1 h 32 min
Bit rate mode                            : Variable
Maximum bit rate                         : 31.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive

and this is 00000.ssif

ideo
ID                                       : 4114 (0x1012)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Stereo High@L4.1
MultiView_Count                          : 2
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 3 frames
Codec ID                                 : 32
Duration                                 : 1 h 32 min
Bit rate mode                            : Variable
Bit rate                                 : 50.2 Mb/s
Maximum bit rate                         : 22.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 1.009
Stream size                              : 32.5 GiB (96%)

then BD3D2MK3D lists

Video    :   AVC, 1080p, 23.976 fps, left-eye
Video    :   MVC, 1080p, 23.976 fps, right-eye (32, 3D-Planes)

while tsMuxeR lists

00000.m2ts     H264     Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
00000.ssif     MVC     H264/MVC Views: 2 Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976 3d-pg-plane: 32
00000.ssif     H264     Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976

I think .m2ts contains the 2D track played when when 3D is off, while .ssid contains the 3D track made by a AVC stream for the left eye and a MVC stream for the right eye computed with differences from left eye AVC.
Is this correct?


Backing to compatibility with my SmartTV, I confirm it only reads .m2ts files created from bluray with tsMuxeR: I use to keep video tracks from original .m2ts and .ssif, and doing this it plays 2D or 3D, perfectly.
I think I could cut the video track from original .m2ts to keep only the 3D track in the final .m2ts, correct?

I'd rather to use BD3D2MK3D to recode to CRF 22 but, unfortunately, there's no way to make my TV read files generated with BD3D2MK3D: if I try to play the final .mkv TV reports unsupported frame rate 47 fps (I think it fails detecting 2x23.976), and the same happens converting this .mkv to a .m2ts with tsMuxeR.

I think this is because BD3D2MK3D generates a 3D track made by 2 AVC streams and not 1 AVC and 1 MVC because, like you explained before, no free and valid MVC encoder is available, correct?


One more time really many thanks.

[ultradj83]

A little wiki from Sony: http://www.sonycreativesoftware.com/dostudio/understanding_3d_authoring_blu-ray_3d_mvc_encoding .

[r0lZ]

I understand .ssif files can contain AVC and/or MVC streams, but I need some confirmations.

I think .m2ts contains the 2D track played when when 3D is off, while .ssid contains the 3D track made by a AVC stream for the left eye and a MVC stream for the right eye computed with differences from left eye AVC.
Is this correct?

Yes. On a 3DBD, there are usually (and probably always, but I'm not sure) 4 files pertaining to the same movie (assuming that the video is not cut in several parts for multi-angle, multi-story or protection purposes):

1. The MPLS is a playlist that contains the information on how to play the video files, the description of each stream, the chapters, etc... In addition, for a 3D movie, it contains a 3D extension that references the MVC stream.
2. A M2TS file that contains only the AVC stream (with the base view) and the audio and subtitle streams. (It may contain additional PiP video and audio streams, but it's very rare.) It is strictly identical to the M2TS found on 2D BDs and is therefore compatible with the 2D BD Players. That MPLS is read when the 3D BD player shows the movie in 2D, and by old BD players (that do not take the 3D extension of the MPLS into account).
3. A M2TS file that contains only the MVC stream (with the dependent view) and sometimes the same subtitles streams than in the AVC M2TS. It doesn't contain any audio stream. Since the MVC stream is dependent of the AVC stream and anyway it has no audio, that M2TS is never directly read and cannot be read by any player. It is there only because it is needed when the BD is authored, to create the SSIF.
4. The SSIF file contains the two M2TS above, "mixed" together in a strange way. The two files are placed on the disc in such a way that the 3D player can read a part of the AVC stream, the audio and the subtitles followed directly by the corresponding part of the MVC, and then back to the AVC to continue to play the 3D movie. In fact, when the player reads the SSIF, it reads the two M2TS files (almost) simultaneously without having to seek to too different places on the disc. The SSIF is therefore not "multiplexed" like an ordinary M2TS. It is made of two M2TS files interleaved at the file system level. That strange method is necessary to maintain compatibility with the 2D players. They do not read the SSIF, but only the AVC M2TS, and skip the interleaved sectors pertaining to the MVC M2TS.

Note: To know the MVC M2TS file(s) associated with a particular 3D MPLS, select the MPLS in tab 1 and use Tools -> Dependent-view (MVC) file list.

In your examples, MediaInfo shows you the AVC M2TS as a 2D clip, because indeed that M2TS contains only the 2D part of the movie. For the M2TS, it tells you that it's a 3D movie (MultiView_Count : 2), but it shows you the info on the AVC stream only. (It's a little discrepancy. In fact, the SSIF contains also a MVC stream, not shown here.)

BD3D2MK3D shows you the 2 streams, as it should. It analyses only the MPLS, but of course, it takes the 3D extension into account, and therefore it knows that it has a MVC stream. (Note that BD3D2MK3D doesn't analyse other extensions, like PiP, and it may omit some streams not directly related to the 3D movie.)

tsMuxeR is correct: AVC for the M2TS, AVC+MVC for the SSIF. I don't know if it is able to show you the content of the MVC M2TS.

Backing to compatibility with my SmartTV, I confirm it only reads .m2ts files created from bluray with tsMuxeR: I use to keep video tracks from original .m2ts and .ssif, and doing this it plays 2D or 3D, perfectly.
I think I could cut the video track from original .m2ts to keep only the 3D track in the final .m2ts, correct?

As you should know now, there is not a single "3D track". You need the two views, either converted to side by side, top & bottom or frame sequential (in a single AVC stream) or as AVC+MVC, like in the original 3D BD.

I'd rather to use BD3D2MK3D to recode to CRF 22 but, unfortunately, there's no way to make my TV read files generated with BD3D2MK3D: if I try to play the final .mkv TV reports unsupported frame rate 47 fps (I think it fails detecting 2x23.976), and the same happens converting this .mkv to a .m2ts with tsMuxeR.

Pity. Have you tried to encode in full or half SBS or T&B ?

I think this is because BD3D2MK3D generates a 3D track made by 2 AVC streams and not 1 AVC and 1 MVC because, like you explained before, no free and valid MVC encoder is available, correct?

Indeed, BD3D2MK3D doesn't recode to AVC+MVC, and therefore you can't use it for your usage.

You should try the FRIM encoder. It uses the Intel MVC encoder, that is free. It can take the original streams and recode them to AVC+MVC. It is not as good as x264 or x265, but it may be exactly what you need, if you don't compress too much. Anyway, you have two solutions: use the original AVC+MVC files and you need much disc space, or re-encode in AVC+MVC with FRIM and you will lose some quality, but it's always the case when the video is re-encoded. You should see by yourself if the remaining quality is good enough for you.


@ultradj83: Thanks for the link. Good short explanation.

[ultradj83]

Dear,
I agree with you about files mapping, with a optical drive makes sense.

Now, simply, I'm creating a new .m2ts in tsMuxeR loading the .mpls related to the main movie .ssif file, excluding the 2D track from the related .mpls, I'm quite sure my TV will play it in 2D and in frame sequential full HD 3D when enabled.

At the same time, I'm trying to recompress to CRF 22 the AVC track in the .ssif, then I'll mux the recompressed AVC with the original MVC and Audio in a .m2ts .
This will probably lead to a corrupted 3D video but, if MVC is just an offset, why not to try?
If this will work I'll have a reduced size 3D .m2ts file with no visible quality loss (on 2D video I see no differences recoding to CRF 22 on a 50" TV).

Finally, about chapters, I'm not yet clear with tsMuxeR: opening a .mpls it loads chapters and the output is just a .m2ts so, I'm not sure it saves them in the .m2ts in some way or just discards them when output is .m2ts, very likely it discards cause a standard .m2ts needs its .mpls to store chapters.

We will see ��

[r0lZ]

You cannot re-encode the AVC and use the original MVC. Each MVC frame is very dependent of the equivalent AVC frame, including of its internal structure. The AVC frames are not just offsets. If you change the AVC stream, even slightly, the player will be unable to combine the two streams to create the dependent view, and may even crash.

And yes, M2TS cannot hold chapters, and tsMuxeR doesn't save them explicitly. It displays them as text, but it cannot store them within the M2TS file itself. You can keep track of the chapters in a chapters.ogm.txt file (like BD3D2MK3D does) or in XML format if you wish. That may be useful if someday you buy an hardware player or TV that supports AVC+MVC in a MKV container. But afaik, no player can currently read the chapters of a M2TS in an external file.