Guide to convert BD 3D to 3D Left+Right Stereoscopic and Anaglyph

[Wolfy59]

Ready for detect AVC/MVC or MVC/AVC order.

Small Tools => First view of SSIF.rar (http://ul.to/b3reswxz)

Works Now with Drag & Drop "xxxxx.mpls" directly to "First view of SSIF.exe" and show Message Box!!!

http://i41.tinypic.com/2wqqqgk.png
http://i44.tinypic.com/21ki9dx.png

A problem, let me know ;)

Work like a charm too :-)

[ludeboy12]

Hey guys hoping someone could help me out. I've had no problems using BD3D2MK3D until today. Pretty sure I haven't changed anything here but I'm getting an error now all of sudden when trying to encode.

An ideas as to how to fix this??

[Thalyn]

Looks like it extracted with the wrong extension: "264" instead of "h264". Not sure how exactly to fix that in the automated process but you should be able to go in and manually change the extension so you can merge the files together on your own.

[Cedvano]

@frencher : Did you ever try to convert your trailer (MVC) in M2TS by tsMuxeR?
When I try to read this in TMT6 it does not work.

I'm looking for a way to introduce MVC in a 3D Blu-ray.

[r0lZ]

The .264 extension and mkvmerge are not the problem. The problem is certainly due to multiple SSIF files in the MPLS. Unfortunately, currently, there is no real solution, except doing the job partially manually.

You should try to use MVCCombine (from the Tools menu of the BD3D2MK3D GUI) to combine the content of the MPLS file. Save the combined file in the project folder. Then, edit the AVS script to replace the original method with the MVCCombine method. (The lines of code to use are already in the script. You should uncomment them and edit the file name of the combined file, and delete or comment out all lines above that part.) That should work.

BTW, the "unknown file type" error message from mkvmerge is not relevant. It fails with that message when x264 cannot render the file, and the h264 file is empty or not standard compliant. And x264 fails because the AVS script fails. And the script fails because the method used to decode the MVC stream (either ssifsource2 or DirectShowMVCSource) has failed too. And currently, they fail usually only when there are too many parts in the SSIF file of the original blu-ray.

Note also that the new ssifsource3 method (supposed to fix that multi-MPLS problem) is not yet implemented in BD3D2MK3D, because ssifsource3 has too many problems with lost or additional frames, causing left/right sync problems. I'll implement that method when it will be safer. Currently, only the MVCCombine method works well, but it is too long and difficult to implement in the current version of BD3D2MK3D, and I prefer to wait for a quicker and easier method. Sorry.

[frencher]

@frencher : Did you ever try to convert your trailer (MVC) in M2TS by tsMuxeR?
When I try to read this in TMT6 it does not work.

I'm looking for a way to introduce MVC in a 3D Blu-ray.

mts = m2ts (from tsMuxer)

I doubt that it works, it will go through an authoring program and paying :confused:

[Cedvano]

mts = m2ts (from tsMuxer)

I doubt that it works, it will go through an authoring program and paying :confused:

Ok, thanks, I work actually to make a program for that.

[Nico8583]

I have a problem with MVCCombine or TsMuxer.
I have demux 3D movie with eac3to. I've found that Right is base view so from eac3to, left becomes right and right becomes left.
So I launch MVCCombine -l (right.h264) -r (left.h264) -o CombinedMVC.h264
I remux CombinedMVC.h264 to M2TS with TsMuxer and I try to play with AVS scripts and DirectShowMVCSource but it doesn't work :(

Edit : If I use MVCCombine -l (left.h264) -r (right.h264) -o CombinedMVC.h264 all seems to be OK, so with MVCCombine -l must be AVC and -r must be MVC ?

http://img809.imageshack.us/img809/8049/3ohb.jpg

[r0lZ]

with MVCCombine -l must be AVC and -r must be MVC ?Yes.
It's when you encode to SBS or T&B that the order of the views matters.

[Nico8583]

Yes.
It's when you encode to SBS or T&B that the order of the views matters.
Okkkk thanks :)
I believe it was also for MVCCombine left/right informations.
So :
- eac3to (left is allways AVC) -> MVCCombine (left is allways AVC) -> Encoding left or right (depending 0x38 value)
- eac3to (right is allways MVC) -> MVCCombine (right is allways MVC) -> Encoding left or right (depending 0x38 value)
It's allright ?
Thanks !

[r0lZ]

Yes, that looks correct.

In fact, eac3to ignores the MVC_Base_view_R_flag, and therefore its left/right information is not relevant. We need to examine the MVC_Base_view_R_flag to know how the streams are assigned.

For MVCCombine, it doesn't make sense to distinguish the left and right channels. It is made to combine an AVC and a MVC stream, in that order, together. (IMO, the -l and -r arguments are misleading. They should be -avc and -mvc.)

So, in your chain of operations, you should verify what stream contains the left stream by analysing the MVC_Base_view_R_flag, but you need that information only when you encode the video, to SBS, T&B or to AVC/MVC again. In all cases, the usual encoding is left channel first.

[Nico8583]

Thanks for this complete response ;)

[HWK]

I recently start using this program and I noticed when you extract base view only using ssifsource.dll it is set to decode mvc view and if you extract dependent view it is also set to decode mvc view. My understanding is it should decode avc view for base view.

Version of program 0.19

[r0lZ]

Right. Bug fixed. Thanks for the report.

[HWK]

Right. Bug fixed. Thanks for the report.

No problem, glad I could help.

On a side note do you think auto crop black border would be good idea.

[r0lZ]

No, for two reasons.

First, BD3D2MK3D has no way to analyse the video stream. It is a simple GUI, that doesn't process the video itself. It uses only external viewers to preview the video, and avisynth to process it. Adding a way to load and analyse the video in the GUI just to determine how it must be cropped is not really easy.

Secondly, I hate the cropped 3D videos, because most TVs require a real 16:9 aspect ratio to display the movie correctly in 3D. Cropped movies appear stretched vertically, and it's terrible! On a PC with a software player (and maybe on some rare TVs), there is no problem, but since the black borders are easily compressed, leaving them doesn't consume much disc space, and ensure a much better hardware compatibility. IMO, they should never be cropped.

[HWK]

No, for two reasons.

First, BD3D2MK3D has no way to analyse the video stream. It is a simple GUI, that doesn't process the video itself. It uses only external viewers to preview the video, and avisynth to process it. Adding a way to load and analyse the video in the GUI just to determine how it must be cropped is not really easy.

Hmm, In case if you ever decide to add it, I want to add that autocrop.dll plugin work very well with avisynth and know where to crop and where not to crop. I tried with 5 movies so far and it worked each time. Jdobbs also use it in his program as well.

Secondly, I hate the cropped 3D videos, because most TVs require a real 16:9 aspect ratio to display the movie correctly in 3D. Cropped movies appear stretched vertically, and it's terrible! On a PC with a software player (and maybe on some rare TVs), there is no problem, but since the black borders are easily compressed, leaving them doesn't consume much disc space, and ensure a much better hardware compatibility. IMO, they should never be cropped.

I use spline64resize (1920, 1080) to overcome the issue. However every one will choose what works for them. I thought I share what I knew about plugin and how it works with program.

[r0lZ]

Hum, adding an automatic crop in the avs script is of course possible, but that cause other problems. I will have to know exactly what has been cropped to figure out the aspect ratio to pass to x264 and MkvMerge, for example. And I guess that hard-coding subtitles on the video will not work any more, since currently it assumes the full 16:9 resolution.
Also, note that converting to top/bottom will have to be done in several avisynth commands, as it is not possible to crop the black borders of the already stacked video stream. I will have to separate it in two views, crop them, and re-compose them.
Anyway, I don't want to encourage people to crop their 3D videos, for the second reason explained above. You will certainly regret to have cropped your movies when you will have to play them on a Samsung or LG TV. Of course, you can modify the avs script yourself before encoding it if you wish.

[HWK]

Thank you, r0lz for your point of of view. Since I don't make side by side or over-under and use x264. I can probably get away with this and crop video.

On a side note I also appreciate you effort to make program available to public, any everyone else who works behind the scenes.

[r0lZ]

Thanks! :-)

[Thalyn]

Anyway, I don't want to encourage people to crop their 3D videos, for the second reason explained above. You will certainly regret to have cropped your movies when you will have to play them on a Samsung or LG TV.

An observation on this part: it's not universal, even across the same brand. When viewed as an MP4 or MKV from a USB drive my younger brother's LG screen, for example, gives unwatchable playback from cropped OU3D material, but my elder brother's LG screen (which is one of their "smart" ones) works perfectly. The main difference is that the TV which doesn't work also doesn't detect it as 3D source material, so requires the use of the "3D Mode" facilities - facilities which assume the introduced letterboxing is part of the output you want, offsetting the left eye down too far and the right eye up too far.

If you use SBS instead of OU, cropping the letterboxing has no negative effect either way.

I still crop mine as OU, though. Partly because I'm still watching via a PC, but mostly because my intent is for display independence - having to use a zoom feature if I should ever get a 22:9 screen would be annoying, just like 4:3 with letterboxing is already.

[r0lZ]

I have a Samsung, and I don't know exactly how the LGs react. But on my Samsung, the movie is resized to occupy the full screen anyway as soon as the 3D mode is enabled, regardless of the input source. Of course, if you use an external player that can add the black borders in SBS mode and send a fully compliant 16:9 frame to the TV, there is no problem. I don't think my Lacie Lacinema HD can do that (with SBS movies only since it doesn't handle the 3D mode), but I'm not sure. Anyway, I hate to use an external player in 3D mode, as the on-screen display of the player is unreadable on the TV.

Note also that if one day you buy a 22:9 TV, it will certainly have some kind of autocrop option, or a button to manually hide the black borders. I can't imagine a 22:9 TV forcing you to watch a Cinemascope movie in 16:9, surrounded by horizontal and vertical black borders simply because the original movie comes from a DVD or BD in 16:9 format!

Anyway, you are free to crop the 3D movies if you wish. I just think that it's not a good idea, and since it is somewhat complex to implement the autocrop option in BD3D2MK3D, I will not do it.

[Rany]

MVC Player Free v0.0.2.3 You can export to avi with mpls?
mvc to avi does not work with mpls for multiple SSIF

[frencher]

MVC Player Free v0.0.2.3 You can export to avi with mpls?
mvc to avi does not work with mpls for multiple SSIF

In a future release it will be possible :rolleyes:

[Rany]

In a future release it will be possible :rolleyes:


thanks for answering :goodpost:

[mini-moose]

Hi

I haven't been toying with the app in a while and thought I'd have a look at the recent developments.

I have a few questions, sorry if those were already discussed in length before, I just don't have time to read back everything.

1) I'm happy to see there is now a 3d vobsubs option, is the default depth usually works ? or it needs experimenting with every movie?

2) I see "additional options" for x264 settings launches with --keyint 96. Is there a reason for that ?

3) Is there a merge solution for 3d movies split into 2 discs (Titanic for example), or those would need to be encoded in 2 mkvs?

4) would it be possible to add crop & resize generating options?
I know it can mess up Aspect Ratios on some hardware players and that it doesn't save a whole lot of space, but would still be nice to have it as an option. r0lZ instructed me at the time how do add it manually but it was a bit challenging for me to figure out on my own.

5) Is there a way to re-generate the encode cmd/avs without going through the demux/subs process again?

6) On 2-pass option (if anyone would ever wanna use that), I noticed an .264 files gets created on first pass. This seems somewhat unneeded, unless some might wants to preview the video before starting 2nd pass. But it's a raw stream anyway, so it would need to be remuxed for that.


thanks!

[r0lZ]

1) I'm happy to see there is now a 3d vobsubs option, is the default depth usually works ? or it needs experimenting with every movie?Unfortunately, the depth depends of the movie. I have selected the default value after several tries with different movies, because it works relatively fine with all of them, but it may be completely wrong with other movies. Currently, there is no way to verify if a value works well with a certain movie without encoding it. (Hint: you can encode only the beginning of the movie with the --frames additional x264 argument, and use the ultrafast preset. It's often sufficient to verify if the depth value is suitable.)

2) I see "additional options" for x264 settings launches with --keyint 96. Is there a reason for that ?I have noticed that many players have trouble with the seek operations when the default keyint value is used. 96 is a good compromise between compression and seek efficiency. That setting is not mandatory and can be removed if you wish, but IMO it is better to keep it.

BTW, the last versions also forces a keyframe at each chapter point. That should facilitate the jump from chapter to chapter greatly. (This feature is automatic and doesn't depend of the --keyint arg.)

3) Is there a merge solution for 3d movies split into 2 discs (Titanic for example), or those would need to be encoded in 2 mkvs?Not in 3DBD2MK3D. You have to create the 2 MKVs. But you can merge them together easily later with MkvMerge GUI. (Install mkvtoolnix (http://www.bunkus.org/videotools/mkvtoolnix/) if you don't have it already.)

4) would it be possible to add crop & resize generating options?
I know it can mess up Aspect Ratios on some hardware players and that it doesn't save a whole lot of space, but would still be nice to have it as an option. r0lZ instructed me at the time how do add it manually but it was a bit challenging for me to figure out on my own.No, for the reasons I have already explained several times, I will not add that possibilities. It is already possible to resize to 720p, and IMO it's sufficient to reduce the disc size without losing the video quality and the compatibility with hardware TVs.

5) Is there a way to re-generate the encode cmd/avs without going through the demux/subs process again?Currently, no. It's something I should add. However, if you want to change some rendering settings only, you can edit the _ENCODE batch file yourself, and relaunch it. It's easy. Modifying the AVS script is also possible, although that requires some knowledge.

6) On 2-pass option (if anyone would ever wanna use that), I noticed an .264 files gets created on first pass. This seems somewhat unneeded, unless some might wants to preview the video before starting 2nd pass. But it's a raw stream anyway, so it would need to be remuxed for that.Correct, it's totally useless, and it was not created with the previous versions. But I have been forced to leave it, as otherwise x264 crashes always. It seems that it needs to write the video stream, for any reason. I have not verified if a newer version has fixed that problem. If it appears that it works fine, I may revert to the old behaviour.

Can you test x264?

[mini-moose]

r0lZ, thanks for taking the time to answer my questions.

(Hint: you can encode only the beginning of the movie with the --frames additional x264 argument, and use the ultrafast preset. It's often sufficient to verify if the depth value is suitable.)
That would require muxing the clip with subs at least and to mkv/mp4. Not a big deal really. Since using vobsubs doesn't harcode the subs, one can also redo the subs and remux the video again by pretty much running the same mux cmd with new vobsubs. The only difficulty with that maybe is you need to repeat the preparation stage to redo the subs. I don't know how to create the 3d subs process myself, I was surprised it's possible cause I don't remember bdsup2sub++ thread mentioning 3d support yet.

I have noticed that many players have trouble with the seek operations when the default keyint value is used. 96 is a good compromise.

thanks for explaining.

You have to create the 2 MKVs. But you can merge them together easily later with MkvMerge GUI.
Yeah, I suppose append option on mkvtoolnix should work fine for that.

No, for the reasons I have already explained everal times, I will not add that possibilities.
ok

Currently, no. It's something I should add. However, if you want to change some rendering settings only, you can edit the _ENCODE batch file yourself
It's not too hard changing the encode parms manually. If you don't like something and want to change it, chances are you already know what you're doing. If you jump between encode methods (crf to 2-pass to abr etc), it might be easier for some to let the program generate it, also redoing the vobsubs from already demuxed sups as I mentioned before.


But I have been forced to leave it, as otherwise x264 crashes always.
Can you test x264?

I'm happy to try recent versions. Does the first pass crash right away when output is set to NUL? or it can happen at a certain later stage?

[mini-moose]

Can you test x264?

I did 7% of first pass with r2345 (komisar clean build and videolan) and with provided 2273 using --output "NUL" "_ENCODE_3D_MOVIE.avs"
I'm not experiencing crashes with any of them. Unless the crash comes at a random later stage.

I'm not sure I understand the "move cinemascopic image up in 16:9 frame" function - can you explain it if it's not too much effort ?

On a different note, I'm happy to see the encode process is a lot faster than it used to be when I tried it last. Unless my memory fails me :)

[r0lZ]

That would require muxing the clip with subs at least and to mkv/mp4. Not a big deal really. Since using vobsubs doesn't harcode the subs, one can also redo the subs and remux the video again by pretty much running the same mux cmd with new vobsubs. The only difficulty with that maybe is you need to repeat the preparation stage to redo the subs. I don't know how to create the 3d subs process myself, I was surprised it's possible cause I don't remember bdsup2sub++ thread mentioning 3d support yet.
There is an option in the Tools menu to convert the 2D subs file (that should be present in the project dir) to 3D. You can simply overwrite the original 3D file if you wish, and restart the mux.

If you want to convert the 3D subs from CLI, have a look at the BD3D2MK3D log to see what command is used.

Yeah, I suppose append option on mkvtoolnix should work fine for that.Exactly.

It's not too hard changing the encode parms manually. If you don't like something and want to change it, chances are you already know what you're doing. If you jump between encode methods (crf to 2-pass to abr etc), it might be easier for some to let the program generate it, ...Right, but for me, it's a big work. The problem is that the user may have changed options that requires to demux again, or to convert the subs to 3D again, and therefore, re-creating the AVS script and/or batch files is not always sufficient. Also, BD3D2MK3D requires to analyse the output of some tools to create the script and the mux options file. If it skips the demux part, that info will be missing. Not sure I can find a solution. Will try, but I promise nothing.

I'm happy to try recent versions. Does the first pass crash right away when output is set to NUL? or it can happen at a certain later stage?
Honestly, I don't remember. Perhaps it was only when the first pass was finishing. You should try with a short clip.

[r0lZ]

I did 7% of first pass with r2345 (komisar clean build and videolan) and with provided 2273 using --output "NUL" "_ENCODE_3D_MOVIE.avs"
I'm not experiencing crashes with any of them. Unless the crash comes at a random later stage.
As I wrote above, I don't remember, but it is probable that the crash happens only at the end of pass 1.

I'm not sure I understand the "move cinemascopic image up in 16:9 frame" function - can you explain it if it's not too much effort ?
One of the big problems with the 3D subs is the risk that they will be placed "inside" the objects that are popping out of the screen. That give a very unpleasant effect, and renders the subtitle difficult to read. In the other hand, if you select a 3D depth too high, you have to focus your eyes alternatively on the subs and on the image all the time, and it's also unpleasant. Movies shot in Cinemascope have horizontal black borders. My idea is that it is usually less unpleasant to have the subtitles in the bottom black border instead of over the real image, because there is no risk of collision, even with a low subtitle depth value. The subs may appear below some objects, but never inside them. The move Cinemascope image up in 16:9 frame option allows you to enlarge the bottom black border (and shrink the top one accordingly) to make more room for the subtitles, and ensure that they will never be outside the border.

On a different note, I'm happy to see the encode process is a lot faster than it used to be when I tried it last. Unless my memory fails me :)May be caused by other settings, or the selection of another MVC decoder. The encode process itselfs depends only of the parameters passed to x264. The MVC decoding is still somewhat experimental, and its speed may vary from version to version.

[mini-moose]

As I wrote above, I don't remember, but it is probable that the crash happens only at the end of pass 1.


I added trim(10000,15000) to the avs.

r2345 seems to complete first pass and starts 2nd. r2273 that comes with the package, takes a long time to start and spits thousands of such lines:

ssifSource2: End of graph. Frame # 10216 duplicate added (debug: g03108868 m03108700 s03108868)
[3.2%] 160/5073 frames, 2.27 fps, 8821.51 kb/s, eta 0:36:07
ssifSource2: End of graph. Frame # 10228 duplicate added (debug: g03108868 m03108700 s03108868)

but then I ran it again and it didn't seem to have issues starting or finishing....

[r0lZ]

The "duplicate added" messages stinks!
BTW, are you encoding with the 64-bit option enabled? Maybe that has also some importance.

[mini-moose]

BTW, are you encoding with the 64-bit option enabled? Maybe that has also some importance.

I used x86


May be caused by other settings, or the selection of another MVC decoder. The encode process itselfs depends only of the parameters passed to x264. The MVC decoding is still somewhat experimental, and its speed may vary from version to version.

I think the last version I used was ssif1 with bd3d 0.12. I see it's now ssifSource2 and there's a coreavcdecoder.dl there too. Wasn't there some issue with coreavc? When I looked at recent post earlier, I saw you posted a screenshot with odd glitches.

[Sharc]

....I have noticed that many players have trouble with the seek operations when the default keyint value is used. 96 is a good compromise between compression and seek efficiency. That setting is not mandatory and can be removed if you wish, but IMO it is better to keep it.
....

Sidenote: if you want strict blu-ray compatibility the GOPs should be no longer than 1 second, means it is good practice to stick to --keyint 24. I don't however now how picky players are ....

[Nico8583]

I have a little question : on Windows 7, is it necessary to install FFDShow to work with DirectShowMVCSource and AviSynth or is it a "stand-alone" decoder ?

[frencher]

MVC Player Free v0.0.2.3 You can export to avi with mpls?
mvc to avi does not work with mpls for multiple SSIF

"MVC Player Free v0.0.2.4" In my signature... :rolleyes:

Extract and run directly MVC Player Free.exe or play associated file with MVC Player Free.exe
# Added : Now can export to .mkv .264 .mp4 .avi .flv
# Experimental : GoPro ProTune Mode => Levels(16, 1, 235, 0, 255, coring=FALSE).Tweak(sat=0.90).Sharpen(0.75).Blur(0.33)
# Update : x264 core:133 r2334 a3ac64b
# Minor Fix : MVC Player Free Demuxer v0.0.0.7 (beta) Fix some forgotten extensions...
# Some fixes
http://i46.tinypic.com/2d2nf6.png

[frencher]

I have a little question : on Windows 7, is it necessary to install FFDShow to work with DirectShowMVCSource and AviSynth or is it a "stand-alone" decoder ?

FFDShow and Avisynth is necessary for "MVC Player Free" (http://forum.doom9.org/showthread.php?p=1602605#post1602605)

[Nico8583]

Hi,
I have a problem when I try to extract video streams from "MONSTERS INC 3D" with eac3to.
I have this message one time for each video stream : [v02] The video bitstream framerate field doesn't seem to match the timestamps. <WARNING>
And several warnings like that : [v02] Video has a gap of 14 frames at playtime 0:00:00. <WARNING>
On playlist info, it is indicated "48p /1.001" but streams are 24p/1001.
I have also tried with the new TsMuxer and no problems.
Anyone can help me ?
Thanks !

[tebasuna51]

@Nico8583
Double post is not allowed in this forum: http://forum.doom9.org/showthread.php?p=1643173#post1643173

If tsMuxeR work without problems, what help need you?

[Nico8583]

Sorry !
Because I have made a GUI for eac3to and I would like to use only one soft (and I like to know why it doesn't work)

[pyk123]

Hi
first understand me plz for my bad english

thx for made BD3D2MK3D
and i am using it very usefully


when i encoding i always use this option
"MONOSCOPIC_M = 2 # Monoscopic 2D: Dependent view only"

and i make Left mkv file with non encoded h264 source file from original bluray title (just do muxing in case of left source)

and i see it with "stereoscopic player" method of

open left and right file style

but i have this problem

some movie does not match sync left and right file

some times left file is more faster than right file

or some times left file played more fastly

why this things happen?

[r0lZ]

Hum, I don't know. Can you open the 2 files in a good player, or in MKVInfo, and see if they have exactly the same frame rate and the same number of frames?

Also, try to remux the two files with MkvMerge GUI, and force the frame rate to 24000/1001. Does it fix the problem?

If you cannot fix the problem with the remux, can you confirm that the MPLS is made of several SSIF files? If it's the case, that can mean that the sync is correct, but one of the two files has missing or additional frames at the joint between the different parts.

[Thalyn]

Hi,
I have a problem when I try to extract video streams from "MONSTERS INC 3D" with eac3to.
I have this message one time for each video stream : [v02] The video bitstream framerate field doesn't seem to match the timestamps. <WARNING>
And several warnings like that : [v02] Video has a gap of 14 frames at playtime 0:00:00. <WARNING>
On playlist info, it is indicated "48p /1.001" but streams are 24p/1001.
I have also tried with the new TsMuxer and no problems.
Anyone can help me ?
Thanks !
I remember having the same problem with this movie, and I managed to get it working, but I don't remember exactly what my solution to it was.

I know it was before MKV support was added to (or at least verified for) SSIFSource, so I know I didn't use MakeMKV to get around it. I also know I tinkered a lot with combining both the SSIF and M2TS files within the AVISynth script I was using, but I don't remember that being successful.

What's standing out in my memory is manually joining all the parts in an EAC3To command line to extract the H.264 parts - but I had to extract the M2TS files themselves, not the SSIF files (there's about 16 parts for each view - use MakeMKV to identify them if you can't read the playlist files like me). Afterwards MVCCombine was used to merge them together, muxed with TSMuxer and finally using SSIFSource to actually work with it.

It's probably easier to just extract it using MakeMKV first, though, and odds are it'll work fine.

[Nico8583]

Thanks for your response.
So for you the solution was to extract xxxxx.m2ts+yyyyy.m2ts+zzzzz.m2ts.... instead of xxxxx.mpls ? I've to try that and I'll try to extract them with MakeMKV also.
Thanks !

[jj666]

Making some testing here with the same BD above (Monsters INC).

Is anyone aware of a way to extract the individual streams from a MAKEMKV created 3D MKV file? Neither MKVEXTRACT or EAC3TO recognise both streams in the end MKV.

Cheers,

-jj-

[Nico8583]

I have made a new test.
I have extracted h264 streams from playlist and I got several warnings about gap etc..
I have extracted h264 from joining all parts for left, no error, for right, no error.
I have made a MD5 checksum for the 4 streams : left are identical, right are identical...

[jj666]

Interesting... I will re-rip the disk and see what happens (I was working from a .ISO remux I made with DVDFab).

Would you mind posting the EAC3TO command line you used?

Cheers,

-jj-

[Nico8583]

Interesting... I will re-rip the disk and see what happens (I was working from a .ISO remux I made with DVDFab).

Would you mind posting the EAC3TO command line you used?

Cheers,

-jj-
With the playlist : eac3to E:\BDMV\PLAYLIST\00802.MPLS 2:Left.h264 3:Right.h264
With multiple files : eac3to E:\BDMV\STREAM\00800.M2TS+E:\BDMV\STREAM\00910.M2TS+E:\.... 2:Left.h264 and same line with right files (I have found all files with MakeMKV)

Edit : More details

With the playlist :
eac3to v3.27
command line: eac3to E:\ 1) 2:H:\BD\PLLeft.h264 3:H:\BD\PLRight.h264
------------------------------------------------------------------------------
M2TS, 2 video tracks, 6 audio tracks, 4 subtitle tracks, 1:32:38, 48p /1.001
1: Chapters, 32 chapters
2: h264/AVC (left eye), 1080p24 /1.001 (16:9)
3: h264/AVC (right eye), 1080p24 /1.001 (16:9)
4: TrueHD/AC3, English, 7.1 channels, 48kHz
(embedded: AC3 EX, 5.1 channels, 640kbps, 48kHz)
5: AC3 Surround, English, 2.0 channels, 320kbps, 48kHz
6: AC3 Surround, English, 2.0 channels, 320kbps, 48kHz
7: AC3 EX, Dutch, 5.1 channels, 640kbps, 48kHz
8: AC3 EX, French, 5.1 channels, 640kbps, 48kHz
9: AC3 EX, Dutch, 5.1 channels, 640kbps, 48kHz
10: Subtitle (PGS), English
11: Subtitle (PGS), English
12: Subtitle (PGS), French
13: Subtitle (PGS), Dutch
[v02] The video bitstream framerate field doesn't seem to match the timestamps. <WARNING>
[v03] The video bitstream framerate field doesn't seem to match the timestamps. <WARNING>
[v03] Extracting video track number 3...
[v02] Extracting video track number 2...
[v03] Creating file "H:\BD\PLRight.h264"...
[v02] Creating file "H:\BD\PLLeft.h264"...
[v02] Video has a gap of 14 frames at playtime 0:00:00. <WARNING>
...
[v02] Video has a gap of 15 frames at playtime 0:46:17. <WARNING>
[v03] Video has a gap of 14 frames at playtime 0:00:00. <WARNING>
...
[v03] Video has a gap of 15 frames at playtime 0:46:17. <WARNING>
Video track 2 contains 133278 frames.
Video track 3 contains 133278 frames.
eac3to processing took 30 minutes, 33 seconds.
Done.

With multiple files :
eac3to v3.27
command line: eac3to E:\BDMV\STREAM\00800.M2TS+E:\BDMV\STREAM\00910.M2TS+E:\BDMV\STREAM\00880.M2TS+E:\BDMV\STREAM\00912.M2TS+E:\BDMV\STREAM\00882.M2TS+E:\BDMV\STREAM\00914.M2TS+E:\BDMV\STREAM\00884.M2TS+E:\BDMV\STREAM\00916.M2TS+E:\BDMV\STREAM\00886.M2TS+E:\BDMV\STREAM\00918.M2TS+E:\BDMV\STREAM\00888.M2TS+E:\BDMV\STREAM\00920.M2TS+E:\BDMV\STREAM\00890.M2TS+E:\BDMV\STREAM\00922.M2TS+E:\BDMV\STREAM\00892.M2TS+E:\BDMV\STREAM\00908.M2TS+E:\BDMV\STREAM\00524.M2TS+E:\BDMV\STREAM\01020.M2TS 2:D:\BD\NewLeft.h264
------------------------------------------------------------------------------
M2TS, 1 video track, 6 audio tracks, 4 subtitle tracks, 1:32:38, 43.485p
1: Chapters, 32 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: TrueHD/AC3, English, 7.1 channels, 48kHz
(embedded: AC3 EX, 5.1 channels, 640kbps, 48kHz)
4: AC3 Surround, English, 2.0 channels, 320kbps, 48kHz
5: AC3 Surround, English, 2.0 channels, 320kbps, 48kHz
6: AC3 EX, Dutch, 5.1 channels, 640kbps, 48kHz
7: AC3 EX, French, 5.1 channels, 640kbps, 48kHz
8: AC3 EX, Dutch, 5.1 channels, 640kbps, 48kHz
9: Subtitle (PGS), English
10: Subtitle (PGS), English
11: Subtitle (PGS), French
12: Subtitle (PGS), Dutch
[v02] Extracting video track number 2...
[v02] Creating file "D:\BD\NewLeft.h264"...
Video track 2 contains 133278 frames.
eac3to processing took 10 minutes, 32 seconds.
Done.

eac3to v3.27
command line: eac3to E:\BDMV\STREAM\00893.M2TS+E:\BDMV\STREAM\00911.M2TS+E:\BDMV\STREAM\00895.M2TS+E:\BDMV\STREAM\00913.M2TS+E:\BDMV\STREAM\00897.M2TS+E:\BDMV\STREAM\00915.M2TS+E:\BDMV\STREAM\00899.M2TS+E:\BDMV\STREAM\00917.M2TS+E:\BDMV\STREAM\00901.M2TS+E:\BDMV\STREAM\00919.M2TS+E:\BDMV\STREAM\00903.M2TS+E:\BDMV\STREAM\00921.M2TS+E:\BDMV\STREAM\00905.M2TS+E:\BDMV\STREAM\00923.M2TS+E:\BDMV\STREAM\00907.M2TS+E:\BDMV\STREAM\00909.M2TS+E:\BDMV\STREAM\00936.M2TS+E:\BDMV\STREAM\01021.M2TS 1:D:\BD\NewRight.h264
------------------------------------------------------------------------------
M2TS, 1 video track, 1:32:38, 33.492p
1: h264/AVC (right eye), 1080p24 /1.001 (16:9)
[v01] Extracting video track number 1...
[v01] Creating file "D:\BD\NewRight.h264"...
Video track 1 contains 133278 frames.
eac3to processing took 6 minutes, 8 seconds.
Done.

[jj666]

Thanks a lot!

I re-ripped the disk with AnyDVD, and extracted again with EAC3TO (with the playlist - so still a lot of spam). However, this time the frame numbers were identical, and I was able to remux using Scenarist fine.

Cheers,

-jj-