# BD3D2MK3D: Convert 3D BDs or MKV to 3D SBS, TAB or FS MKV - Support thread

Thread
1. Originally Posted by r0lZ
BD3D2MK3D v1.32 released

v1.32 (February 27, 2023)
- Fix: Wrong filenames when a multi-angle/multi-story MPLS is made of only 2 parts (for example Blade Runner 2049 French version)
- Added the menu Help -> MkvToolnix for Windows 7 to download easily a MkvToolnix version compatible with Windows 7 (Thanks Ennio!)
- Added a link to the mini-guide on how to convert an external SRT or SUB to 3D in the Subtitle Tools menu.
- Added a link to the Bernard's Wiki page about BD3D2MK3D in the Help menu. (Thanks Bernard!)

r0lZ, after putting proper win7 mkv.exe tools in the tools folder, there's still the popup with the win10 warning. It's of course no trouble to ignore, but maybe a popup is possible that will only alert when win7 tools aren't there or updates are available?
2. Originally Posted by kiwwx
Why is the processing on the gpu less good? I would like to speed up the process. I have rtx40-series. The gpu's starting from 3000 series have powerful encoders/dencoders.
The authors of x264 and x265 do not want to add GPU support, because the quality is less good. I don't know exactly why, but I trust them. It's related to the parallel nature of the GPU processing. Anyway, there is no way to enable GPU encoding with these encoders.

However, if you really want to use a GPU powered encoder, you can use any command line encoder. You must install it and know how to use it. In BD3D2MK3D, select Settings -> AVC/HEVC Encoder -> Use your own custom command for encoding. The content of the last tab will change, and you will have to type the command you wish to use. For example, here is a command that use nvEnc with CUDA. I use it sometimes to do quick tests, but I am usually somewhat disappointed by the quality and the (relatively) slow speed.

"path\\to\\nvencc64.exe" ^\n --codec avc --cqp 26 --profile high --level 4.1 --preset quality --sar ${sar} ^\n --colorprim bt709 --colorrange limited --chapter chapters_3D_delay.ogm.txt --key-on-chapter ^\n --input "__ENCODE_3D_MOVIE.avs" --output "video3D_nvenc.avc" Note that you can use variables (such as the${sar} in the command above) so that your command will be automatically adapted to other conditions (such as HSBS vs FSBS). Note also the required double \\ in the paths.

Also, when your custom command works as expected, don't forget to use Settings -> Save Tabs Settings Now to force BD3D2MK3D to remember your custom command for the next time.
3. Originally Posted by Ennio
r0lZ, after putting proper win7 mkv.exe tools in the tools folder, there's still the popup with the win10 warning. It's of course no trouble to ignore, but maybe a popup is possible that will only alert when win7 tools aren't there or updates are available?
I have tried to do exactly that, but unfortunately, the special Win7 builds of mkvtoolnix have exactly the same version string than the official, Win10+ release. So, I have no way to know what version is installed. Hence the warning.
4. Originally Posted by jonesy16
I'm hoping someone can help me because I must be doing something wrong. I'm trying to use MakeMKV 1.15.3 and BD3D2MK3D 1.2 to rip some of my 3D blu-rays for playback on an Oculus Rift 2. The problem that I'm running into is that the left and right images are not being reassembled by the player correctly, which I suspect is something in the tags and not so much in the actual video files themselves. I'm using defaults everywhere for half (and tried full) side-by-side. The opening Paramount logo, for example, has the Paramount mountain dead center. However, what I see is the left half of the image touching the right edge of the screen and the right half of the image touching the left edge of the screen so instead of () I see )(, if that makes sense. 2D playback looks fine, opening the file in VLC appears to show the right and left halves at the same time and they look fine as well, so I just don't understand why the 3D player is struggling with it (I've tried two different players, BigscreenVR and GizmoVR. I downloaded a sample SBS file online and that had no problems. Ideas?
Having this same issue.

The same files that fail in BigScreen video player also fail on my brothers projector.

However other files I have that I didn't make work fine in BigScreen and on his projector.

ALL files work fine on my Plasma TV.

So there must be some strange difference with the files made using BD3D2MKV3D that is tripping up the projector and the VR player. (even tho they work fine elsewhere)

I can't find the difference, but I'm a noob at this stuff.
5. IMO, the only settings that can explain that kind of problem are the two aspect-ratios.

The first AR setting is the picture AR, srored in the header of the MKV container. You can easily change it after having encoded the movie: just edit the __MUX_3D_OPTIONS.json file, and change the AR value in the file following "--aspect-ratio", or just delete the "--aspect-ratio" and the following lines to let the player decide. Then, launch __MUX_3D.cmd to remux the MKV with the new settings. Honestly, I don't think that this AR value can be the culprit, but who knows ?

The second AR setting is the SAR, encoded in the video stream itself. You can also change it without having to restart the whole project. Edit or remove the --sar 1:1 argument in __ENCODE_3D.cmd. Unfortunately, you will have to restart the encoding with __ENCODE_3D_LAUNCHER.cmd. Again, I'm not sure that changing that setting may solve the problem, but try anyway.

Normally, the two settings are correct for HSBS, HTAB and Frame Sequential, but for Full-SBS or Full-TAB, it seems that some TV or hardware players require different values. It's why you can change them with Settings -> Full-SBS/T&B Aspect Ratio menu. But that will be taken into account by BD3D2MK3D only for a Full-* encoding.

I suggest to encode a small clip to try different values. And please, if it appears that a precise setting works as expected, let me know. I will modify the program to add the required option. I am also interested in a short 3D clip that works well with your hardware. Perhaps I will be able to locate the difference ? (You can send me an email. The address is near the end of the PgcEdit home page. Link in my signature.)

I suggest also to contact the developers or the forum of your hardware. IMO (perhaps with the exception of Full-SBS/T&B) BD3D2MK3D uses the correct AR settings, and is probably not responsible of the problem, but again, who knows ?

[EDIT] Another thing. Can you tell me if your hardware requires to be manually informed of the correct 3D format (for example HSBS or FSBS) ? If it's the case, the two settings that encode the format into the final MKV file can perhaps also be problematic.
6. Originally Posted by r0lZ
IMO, the only settings that can explain that kind of problem are the two aspect-ratios.

The first AR setting is the picture AR, srored in the header of the MKV container. You can easily change it after having encoded the movie: just edit the __MUX_3D_OPTIONS.json file, and change the AR value in the file following "--aspect-ratio", or just delete the "--aspect-ratio" and the following lines to let the player decide. Then, launch __MUX_3D.cmd to remux the MKV with the new settings. Honestly, I don't think that this AR value can be the culprit, but who knows ?

The second AR setting is the SAR, encoded in the video stream itself. You can also change it without having to restart the whole project. Edit or remove the --sar 1:1 argument in __ENCODE_3D.cmd. Unfortunately, you will have to restart the encoding with __ENCODE_3D_LAUNCHER.cmd. Again, I'm not sure that changing that setting may solve the problem, but try anyway.

Normally, the two settings are correct for HSBS, HTAB and Frame Sequential, but for Full-SBS or Full-TAB, it seems that some TV or hardware players require different values. It's why you can change them with Settings -> Full-SBS/T&B Aspect Ratio menu. But that will be taken into account by BD3D2MK3D only for a Full-* encoding.

I suggest to encode a small clip to try different values. And please, if it appears that a precise setting works as expected, let me know. I will modify the program to add the required option. I am also interested in a short 3D clip that works well with your hardware. Perhaps I will be able to locate the difference ? (You can send me an email. The address is near the end of the PgcEdit home page. Link in my signature.)

I suggest also to contact the developers or the forum of your hardware. IMO (perhaps with the exception of Full-SBS/T&B) BD3D2MK3D uses the correct AR settings, and is probably not responsible of the problem, but again, who knows ?

[EDIT] Another thing. Can you tell me if your hardware requires to be manually informed of the correct 3D format (for example HSBS or FSBS) ? If it's the case, the two settings that encode the format into the final MKV file can perhaps also be problematic.
Thanks for the quick suggestions.

I def should've made a small test file sooner, now I can rapid prototype in seconds instead of nearly an hour waiting on a full movie. lol

Working with Edge of Tomorrow ISO, used makemkv, then used mkvtoolnix to cut out a 30 second clip for testing.

Defaults (HSBS) I have the issue.....tried your suggestions and removed the aspect ratio info from both files (vs changing as not sure what to change to) and remuxed it and same issue. No change. Both files look the same in VLC and both play as 2D in bigscreen. The projector is my brothers who lives nearly 1 hour away so can't easily test on that. However because they fail similarly if I can get it working in bigscreen, safe to assume it will work on his projector which is my primary goal.

Bigscreen will auto play in SBS when I load up a working file, however I am able to manually cycle through its other options and none of them work on the failing files. Working files auto work every time.

I have gone ahead and sent you an email with a link to various files.

Looking forward to your findings!
7. Thanks. I have received your email and I am downloading your samples. Will let you know my findings (if any!)
8. For any onlookers with the same issue, this worked!

Remove from __MUX_3D_OPTIONS.json: (doing this allows the file to play straight into SBS mode, otherwise you likely need to tell your player to change manually....this is not a necessary step, just a quality of life step)

"--stereo-mode",
"0:1",

Remove from __ENCODE_3D.CMD: (doing this makes it play as a 3D file in BigScreen, rather than showing as 2D even though it's an SBS file, this is necessary)

--frame-packing 3

Then run __ENCODE_3D_LAUNCHER.cmd to create the final output.

Thanks again r0lZ, would love to see this as the default of the app, but understand if that can't be done if it would break it for most everyone else...for me, seems to work everywhere much better without it.
9. Thanks for the confirmation. I will add one (or two) additional option(s) in the Settings menu to remove them, although it's certainly the programmers of the faulty hardware players who should fix the bug. The modification in BD3D2MK3D will only be a workaround for the peoples impacted by the problem.

[EDIT] Note that the --frame-packing tag was required to allow Youtube to display the 3D content correctly. An additional evidence that that tag MUST be correctly recognised and used. Shame on the hardware players that do not support it !
10. So the fix above is how to rip correctly if you have the issue.

However, if you already ripped wrong and want to fix, without starting from scratch, a very fast fix is below.....credit to r0lZ and his efforts, along with videofan3d:

Grab the BDTools files linked in the thread here:

https://forum.doom9.org/showthread.php?t=174563

Then use these commands (mkvtoolnix is the other program needed)

mkvextract tracks "C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename.mkv" "0:C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename.264"
h264Modify.exe C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename.264 -frame_packing DELETE C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename-fixed.264
mkvmerge -o "C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename-fixed.mkv" --stereo-mode 0:1 "C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename-fixed.264" --no-video "C:\1\mkvtoolnix-64-bit-71.1.0\mkvtoolnix\filename.mkv"
11. That's correct, but note that the --stereo-mode 0:1 is for Side-by-Side (left view first). If your movie has been encoded in Top and Bottom, you should use 0:3.

BD3D2MK3D places always the left frame on the left side or on top, but if your movie has been encoded with another tool, you must select the right value below:
1 side_by_side_left_first
2 top_bottom_right_first
3 top_bottom_left_first
10 anaglyph_cyan_red
11 side_by_side_right_first
12 anaglyph_green_magenta

The other stereo-modes are less common.

Statistics