3D Support Discussion

[jdobbs]

Jdobbs, On mkvmerge website it list all available options I know that, in fact I think I provided that reference earlier in the thread. Please take the time to read what I wrote. The display dimensions or 3840x2160 can't be correct unless you are making pictures that double in both the horizontal and vertical directions (making it quadrascopic). So, I don't think these settings could ever have actually been used.

[HWK]

I posted in very close proximity to you post in time frame, as a result I thought maybe you were not aware of it and I just posted again.

[jdobbs]

I posted in very close proximity to you post in time frame, as a result I thought maybe you were not aware of it and I just posted again.I know you really want to correct me, apparently to prove how much smarter you are than I am. Frankly I don't care. But at least read my post before before telling me I'm wrong (again).

[HWK]

I know you really want to correct me, apparently to prove how much smarter you are than I am. Frankly I don't care. But at least read my post before before telling me I'm wrong (again).

why are you upset, when you initially posted I quickly glance at and posted a reply and after that I didn't notice you edit your post for which I am sorry if it helps you at all.

In future I am gone take extra care and not to reply so fast without reading and I am anticipating that should reduce these kind of incidents.

[jdobbs]

why are you upset, when you initially posted I quickly glance at and posted a reply and after that I didn't notice you edit your post for which I am sorry if it helps you at all.

In future I am gone take extra care and not to reply so fast without reading and I am anticipating that should reduce these kind of incidents. Even the first post before editing said the same thing: The specified picture dimensions could NOT be correct, even if the "--stereo-mode" is specified (I initially thought it was missing).

No harm, no foul. Everything is cool.

[mparade]

I know that, in fact I think I provided that reference earlier in the thread. Please take the time to read what I wrote. The display dimensions or 3840x2160 can't be correct unless you are making pictures that double in both the horizontal and vertical directions (making it quadrascopic). So, I don't think these settings could ever have actually been used.

I think the same, but this is what mkv merge read out from the file! Please give me some minute I am just reading out the dimensions from the file made by BD-RB which was just remuxed to set up the stereoscopic mode.

[jdobbs]

I think the same, but this is what mkv merge read out from the file! Please give me some minute I am just reading out the dimensions from the file made by BD-RB which was just remuxed to set up the stereoscopic mode.Here's how the reference document describes that parameter:
Matroska(tm) files contain two values that set the display properties that a player should scale the image on playback to: display
width and display height. These values can be set with this option, e.g. '1:640x480'.From that I don't see how it could ever be 3840x2160.

You mentioned that you told MKVMERGE to use 16:9, which I believe is incorrect, as the aspect ratio is actually 1:1. It's possible that it took the true Y coordinate (2160), divided it by 9 (240) and then multiplied it by 16 giving 3840. So the file itself isn't 3840x2160, it is 1920x2160, but the player thinks that's how you want it displayed. I'm surprised it actually worked in playback, since it should, by all rights, result in a display that is stretched 2x on the horizontal axis (considering the splitting of the picture into a stereoscopic presentation).

What happens if you don't enter the aspect ratio in the MKVMERGE command that creates the file? I can't really do any testing myself since I don't have that player.

[mparade]

Here's how the reference document describes that parameter:
Matroska(tm) files contain two values that set the display properties that a player should scale the image on playback to: display
width and display height. These values can be set with this option, e.g. '1:640x480'.From that I don't see how it could ever be 3840x2160.

You mentioned that you told MKVMERGE to use 16:9, which I believe is incorrect, as the aspect ratio is actually 1:1. It's possible that it took the true Y coordinate (2160), divided it by 9 (240) and then multiplied it by 16 giving 3840. So the file itself isn't 3840x2160, it is 1920x2160, but the player thinks that's how you want it displayed. I'm surprised it actually worked in playback, since it should, by all rights, result in a display that is stretched 2x on the horizontal axis (considering the splitting of the picture into a stereoscopic presentation).

What happens if you don't enter the aspect ratio in the MKVMERGE command that creates the file? I can't really do any testing myself since I don't have that player.

And here you are, this is the command of the mkv file coming directly from BD-RB:

"mkvmerge" -o "E:\\Users\\Bogárdi Mátyás\\Desktop\\JACK_THE_GIANT_SLAYER (1).mkv" "--default-track" "0:yes" "--forced-track" "0:no" "--display-dimensions" "0:1920x2160" "--language" "1:eng" "--default-track" "1:yes" "--forced-track" "1:no" "--language" "2:hun" "--default-track" "2:no" "--forced-track" "2:no" "--language" "3:eng" "--default-track" "3:no" "--forced-track" "3:no" "--language" "4:hun" "--default-track" "4:no" "--forced-track" "4:no" "-a" "1,2" "-d" "0" "-s" "3,4" "-T" "--no-global-tags" "(" "E:\\Users\\Bogárdi Mátyás\\Desktop\\JACK_THE_GIANT_SLAYER.MKV" ")" "--track-order" "0:0,0:1,0:2,0:3,0:4"

[mparade]

Here's how the reference document describes that parameter:
Matroska(tm) files contain two values that set the display properties that a player should scale the image on playback to: display
width and display height. These values can be set with this option, e.g. '1:640x480'.From that I don't see how it could ever be 3840x2160.

You mentioned that you told MKVMERGE to use 16:9, which I believe is incorrect, as the aspect ratio is actually 1:1. It's possible that it took the true Y coordinate (2160), divided it by 9 (240) and then multiplied it by 16 giving 3840. So the file itself isn't 3840x2160, it is 1920x2160, but the player thinks that's how you want it displayed. I'm surprised it actually worked in playback, since it should, by all rights, result in a display that is stretched 2x on the horizontal axis (considering the splitting of the picture into a stereoscopic presentation).

What happens if you don't enter the aspect ratio in the MKVMERGE command that creates the file? I can't really do any testing myself since I don't have that player.

And the additional set up I made afterwards (which you realized some minutes ago were totally wrong) are:

- aspect ratio was set to 16:9, I thought of 1920x1080 frame ratio in the "fast run"

- FPS was set to 24000/1001 because source framerate is23.976fps, however I think it was totally unnecessary

- and stereoscopy was set to 3 due to O/U conversion method, however I was not sure if not 2 is the correct. I checked the video in mode 3 and it was fine, I do not really know the effect of swapping the pictures between the eyes yet.

By now, you know the whole history of the finally flawlessly working material. Sometimes the users may also have some luck. :)

[jdobbs]

And the additional set up I made afterwards (which you realized some minutes ago were totally wrong) are:

- aspect ratio was set to 16:9, I thought of 1920x1080 frame ratio in the "fast run"

- FPS was set to 24000/1001 because source framerate is23.976fps, however I think it was totally unnecessary

- and stereoscopy was set to 3 due to O/U conversion method, however I was not sure if not 2 is the correct. I checked the video in mode 3 and it was fine, I do not really know the effect of swapping the pictures between the eyes yet.

By now, you know the whole history of the finally flawlessly working material. Sometimes the users may also have some luck. :)3 is correct. BD-RB makes sure the left picture is on top (by reading the flag from the BD and adjusting the AVS file). But there is a hidden option that can change that.

I'll be posting a new version (v0.45.05) in a while, try that one and see if it works without the need for any additional MKVMERGE runs.

[mparade]

Here's how the reference document describes that parameter:
Matroska(tm) files contain two values that set the display properties that a player should scale the image on playback to: display
width and display height. These values can be set with this option, e.g. '1:640x480'.From that I don't see how it could ever be 3840x2160.

You mentioned that you told MKVMERGE to use 16:9, which I believe is incorrect, as the aspect ratio is actually 1:1. It's possible that it took the true Y coordinate (2160), divided it by 9 (240) and then multiplied it by 16 giving 3840. So the file itself isn't 3840x2160, it is 1920x2160, but the player thinks that's how you want it displayed. I'm surprised it actually worked in playback, since it should, by all rights, result in a display that is stretched 2x on the horizontal axis (considering the splitting of the picture into a stereoscopic presentation).

What happens if you don't enter the aspect ratio in the MKVMERGE command that creates the file? I can't really do any testing myself since I don't have that player.

I am sure it would be working flawlessly but now I do not have unfortunately the opportunity to check. Luckily both you are and my player is much more familiar with the theme than me so please implement the option into BD-RB according to your best knowledge. Afterwards I even can test it and tell please modify because it is not working.:)

[mparade]

3 is correct. BD-RB makes sure the left picture is on top (by reading the flag from the BD and adjusting the AVS file). But there is a hidden option that can change that.

I'll be posting a new version (v0.45.05) in a while, try that one and see if it works without the need for any additional MKVMERGE runs.

Thank you for all the efforts!

[jdobbs]

Thank you for all the efforts!Let me know if it works. It currently outputs to a file with an MKV extension. Let me know if it needs to be MK3D.

[mparade]

Let me know if it works. It currently outputs to a file with an MKV extension. Let me know if it needs to be MK3D.

Unfortunately, it is not working this way at all. So, neither if the extension is set to mkv nor if it is set to mk3d.....
It is completely clear to me by now that the problem is with the resolution set in mkvmerge after the reencoding process. Only in case of setting the resolution to 1920x2160(if using O/U convesrion method in BD-RB) or to 3840x1080(if using side-by-side conversion method in BD-RB) can one get the proper result of the full resolution 1920x1080 frame to each eye. I have tested the file I got from BD-RB 1hour without any success. It handled the content as if it were a 2D 1920x1080 frame regardless of the setting in my player and Loewe Connect ID active 3D TV.

Anyway, I am really waiting for your improvement to be able to make full resolution full disc 3D backups which is BD 3D compliant. I have again sent you a support package of 40 bucks to make it faster to be available....:)

[HWK]

Jdobbs, have you came across any titles where 3D subtitle are store differently than standard method of storing them.

I know Avatar and Resident Evil: Retribution uses different method than rest of my movie collection, in terms how they store it.

If you want to read more http://forum.doom9.org/showthread.php?t=169817

[jdobbs]

Jdobbs, have you came across any titles where 3D subtitle are store differently than standard method of storing them.

I know Avatar and Resident Evil: Retribution uses different method than rest of my movie collection, in terms how they store it.

If you want to read more http://forum.doom9.org/showthread.php?t=169817I haven't looked at it closely enough. I've assumed all would be the same -- and I haven't looked at it in the standard very closely. I scanned through the link, but I think I need to read it again when I'm a little fresher (it's getting late).

[Sharc]

Jdobbs

Perhaps you have seen the discussion starting from here (http://forum.doom9.org/showpost.php?p=1658513&postcount=1674). Maybe this is of interest for your work on 3D as well.

I did some test with this plugin and FRIMEncode+tsMuxeR. It seems to be working, however it suffers from similar issues as DirectShowMVCSource.dll, i.e. occasional glitches close to the picture borders for certain problematic BD sources. It does however not depend on the "mystic folder" structure.
I don't know about the ownership of this plugin.

Here the .cmd

FRIMEncode.exe mvc -avi -sbs 2 -i MVCS.avs -viewoutput -o MVCS_Base_.avc -o MVCS_Dependent_.mvc -w 1920 -h 1080 -l 6 -cpbsize 3750 -vbr 6000 15000 -u 4 -profile high -level 4.1 -gop 24 4 0 O -PicTimingSEI off -EndOfSequence off
pause

and the MVCS.avs:

Interleaved = MVCsource("c:\...path......\in_base.264", "c:\....path ...\in_dependent.mvc",1000,2) #1000=number of Frames, 2=Stereo
Right = SelectOdd(Interleaved)
Left = SelectEven(interleaved)
return StackHorizontal(Left,Right)