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

[ecou2508]

There is a warning in the log, i 've possibly selected the wrong pls on the 4 pls... probably the one in 2D :-)

i retry with another one....and keep posting ;-)
Eddy

[ecou2508]

redone the job but with mpls 335 and get these errors in BD3D log:

Streams demuxed by tsMuxeR:
00335.track_4353.ac3 784627200 bytes
00335.track_4612.sup 19398935 bytes
Error: Can't rename "00360+___+00354.track_4113.264" to "00335.track_4113.264": error renaming "00360+___+00354.track_4113.264": no such file or directory
Error: Can't rename "00360+___+00354.track_4114.mvc" to "00335.track_4114.mvc": error renaming "00360+___+00354.track_4114.mvc": no such file or directory

[ecou2508]

i just renamed these 2 files manually and restart encoding (__ENCODE_3D_LAUNCHER.cmd): ok, encoding is now running.

Job finished: Final mkv seems ok, have to test it when back to home (no 3D monitor here..)

[ecou2508]

Hi r0,
i just launched the same job again on another PC: same error and that same Bluray... Tried with another Bluray 3D : No problem !

Looks like this problem is specific to this Bluray...

[ecou2508]

Here are the details from the log of the error on that other PC:
Error: Can't rename "00362+___+00354.track_4113.264" to "00334.track_4113.264": error renaming "00362+___+00354.track_4113.264": no such file or directory
Error: Can't rename "00362+___+00354.track_4114.mvc" to "00334.track_4114.mvc": error renaming "00362+___+00354.track_4114.mvc": no such file or directory

And in attachement, the 2 files related to the problem

[r0lZ]

Yes, I have just seen the error messages. The problem is related to the filenames tsMuxeR uses for the demuxed streams when they are made of many M2TS. Previously, it tried to save files with filenames containing all numbers of the M2TS files, and that failed when there were too many M2TS, because the filename was too long for Windows. I have reported that bug, and the naming scheme has been changed. At that time, I have modified the code of BD3D2MK3D to use the new filenames (the ones shown in the error messages), and that worked well. But obviously, the naming scheme of tsMuxeR has changed again, and BD3D2MK3D is now unable to find the demuxed files. I will have to fix that problem, but I will need a BD with a MPLS made of enough M2TS files to cause the problem. I will try to find one in my collection, but that can take some time...

In the meantime, can you post here the names of the 264 and MVC files as they were in the project folder (before your manual rename) ?

[ecou2508]

Oops, attachement with capture jpg is pending.. :-(
before i manually renamed them:
00362+00354.track_4113.264
00362+00354.track_4114.mvc

and related error messages:
Error: Can't rename "00362+___+00354.track_4113.264" to "00334.track_4113.264": error renaming "00362+___+00354.track_4113.264": no such file or directory
Error: Can't rename "00362+___+00354.track_4114.mvc" to "00334.track_4114.mvc": error renaming "00362+___+00354.track_4114.mvc": no such file or directory

[ecou2508]

In the first post i made, there is jpeg with all the files in the dir before i tried renaming them manually. (the 360 that should be rename 335) starting the job with 335 mpls

With the playlist 334 (my last attempt on another PC), 362 should be renamed to 334

[r0lZ]

OK. I still need another info. What is the list of SSIF (M2TS) parts in the MPLS you have processed ? You can easily copy it with the menu "Tools -> Dependent-view (MVC) file list". When the dialog is shown (and active), just press Control-C to copy its content and post it here.

[r0lZ]

The bug with the filenames happens only when the converted M2TS contains exactly two parts (two M2TS per eye-view), because the filename generated by tsMuxeR is not what it is when there is only one part, or when there are more than 2 parts. The bug is fixed in this version.

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!)

Download it here: BD3D2MK3D.7z

[r0lZ]

In this version, a new Tool has been added, to help the users of the hardware players that do not support correctly one of the 3D format "tags" (the MKV stereoscopy mode and/or the AVC frame-packing), as well as Settings options to not create that tags when a new project is created.

The new Tools -> Modify 3D Format Tags in MKV or AVC can be used to easily either delete, modify or create one or both tags from a 3D MKV or from an AVC (h264) elementary stream. Note that all 3D stereoscopy modes can be defined, including the modes not supported by BD3D2MK3D. That means that the tool can be used to modify a 3D movie downloaded from the internet, or created with another program.

The two options to not include the 3D tags during the creation of a project with BD3D2MK3D are in Settings -> Hardware Players Compatibility Options.

Thanks to Archon for having submitted this problem (at VideoHelp here) and for his help in finding the culprit. Note that the real culprit is not BD3D2MK3D, but the BigScreen software, unfortunately used by several hardware players, projectors or VR headsets. The new features of BD3D2MK3D are therefore only workarounds for badly written software. If you have such a player, please contact the developers. The 3D tags should normally be present in all good 3D movies !

Note also that I have used the word "Tag" to refer to the two 3D methods to define the correct 3D format, but it's just a shortcut. The 3D stereo-mode in the header of the video track of a 3D MKV should be called "Stereoscopy Video Property", and the AVC frame-packing tag is in fact a series of "SEI messages" inside the video stream itself.

v1.33 (April 6, 2023)
- Added Options -> Hardware Players Compatibility Options as a workaround for serious bugs of some hardware players (notably those based on the Bigscreen software). Thanks Archon!
- Added Tools -> Modify 3D format tags in MKV or AVC to fix the frame-packing and stereo-mode information in any MKV file with an AVC video stream.
- Added Videofan3D's h254Modify.exe in the toolset folder (required for Tools -> Modify 3D format tags in MKV or AVC) as well as sfk.exe.
- Added Help -> Check for Update to easily download the new BD3D2MK3D version (if any). Requires Windows 10 or greater.
- Modified the dead CinDe download link in Help -> Cinavia Detection -> Download CinDe (free) and updated the How to Detect Cinavia? message.
- Updated x264 to the latest version (v0.164.3106)
- Updated x265 to the latest version (v3.5+96)
- Updated mkvtoolnix to the latest version (v75.0.0 'Goliath')

Download the latest version: BD3D2MK3D.7z

[thxoptimizer]

Hi,

It has been a long time since I did my last conversion from Blu-Ray 3D.

I have just generated a mkv but with a lot of questions :
1) why the default value is the checkbox "Half" checked by default for side-by-side, I suppose the best is to preserve quality if we can
2) "3-Select stream" tab, I have chosen my subtitles (despite the long explanation not sure to fully understand but anyway...) ==> in "5-Options and Go" tab if we choose "Hardcode subtitles..." it means that subtitles will be always displayed and nothing to select in the player, right?
3) X264 and all the configuration... I have no idea what to choose to have the best quality supported by my Meta Quest 3 headset.

Note : 2 attempts

• Default values (Half, X264 to CRF/23) ==> 3,4Go
• Full side-by-side + X264 to CRF/17 ==> 15 Go (I can't see any difference in quality in Meta Quest 3)

Thank you.

[r0lZ]

1) When it's possible, I have adopted the "official" settings by default. Since only Half-SBS and Half-TAB are described officially in the 3D specs, and SBS is much more often used than TAB, it was logical to set Half-SBS as the default.
Furthermore, Half-SBS is fully supported by all 3D devices, such as the 3D TVs. It's not at all the case of Full-SBS (hence the warning).
And finally, the 3D subtitles are not possible for Full-SBS/TAB (except by hardcoding them).

2) Yes, it's correct. And hardcoding a stream is the only way to have the subtitles displayed in 3D,with the correct depth, if you select any Full-* picture format.
Another advantage is that all players will display the subtitles correctly, since they are part of the video. With the 3D subtitle streams and Half-SBS, many players are unable to display them correctly, because they resize or move them elsewhere, or because they cannot display them over the video before splitting the two views.
So, if it's not a problem for you to have the subtitles constantly displayed, I suggest to chose that solution. (In that case, you don't have to select the subtitle stream in tab 2.)

3) In your note, you have yourself replied to the question. CRF 23 is the default, carefully selected by the authors of x264 because it offers a good quality and an excellent compression. Of course, you can lower it more or less to obtain a better quality, but as you wrote, most of the times, the difference is not really visible. Some peoples are obsessed by the file size and think that a small file size is synonym of bad quality. It's mainly wrong. Just do some tests with a small clip, and adopt the settings offering a good balance between quality and size.
Personally, I use often CRF 20 or 21, preset slow.

[TDS]

Just a quick question about MVC 3D's.

How to keep that, and not converting to other types.

[kempodragon]

Regarding full SBS vs. half SBS, I have the Quest 1 and have always used full SBS for my 3D videos. The Quest is essentially a video version of the old Viewmaster. I use the Skybox app to play them with no problems. The only thing I wish that Skybox could do is play sequential 3D so I could compare SBS vs sequential.

[thxoptimizer]

Thanks r0lZ for you answers.

Originally Posted by kempodragon

Regarding full SBS vs. half SBS, I have the Quest 1 and have always used full SBS for my 3D videos. The only thing I wish that Skybox could do is play sequential 3D so I could compare SBS vs sequential.

I moved from Quest1 to Quest3 and from my experience, even with this gap of quality of the screen I couldn't see any difference from default settings (half SBS) to better settings (like full SBS).

PS : I think headsets like Quest doesn't have to play sequential 3D like old 3D Tvs with active glasses (1 time for left eye / one time for right eye) because or 2 eyes could receive a different image at the same time in these headsets

[r0lZ]

Originally Posted by TDS

Just a quick question about MVC 3D's.

How to keep that, and not converting to other types.

MakeMkv does it. But be warned: only a couple of players can play the AVC+MVC MKV in 3D. Almost all players ignore the MVC stream and play only the AVC in 2D. And, of course, the file size will not be reduced.

If you want a better compatibility, a backup of the original BD3D might be a good solution.

[r0lZ]

Originally Posted by thxoptimizer

PS : I think headsets like Quest doesn't have to play sequential 3D like old 3D Tvs with active glasses (1 time for left eye / one time for right eye) because or 2 eyes could receive a different image at the same time in these headsets

Correct.
What's more, I think that FS gives poorer quality than FSBS for the same size, because the encoder isn't designed to calculate motion vectors taking only every other frame into account. The fact that large parts of the image are moving between each frame, even when there is no camera movment, must therefore greatly complicate the encoding, and make it less efficient. This problem does not exist with FSBS.

[thxoptimizer]

Originally Posted by r0lZ

Correct.
What's more, I think that FS gives poorer quality than FSBS for the same size, because the encoder isn't designed to calculate motion vectors taking only every other frame into account. The fact that large parts of the image are moving between each frame, even when there is no camera movment, must therefore greatly complicate the encoding, and make it less efficient. This problem does not exist with FSBS.

Interesting! During all these years you have learned deep about all these settings and now I see that default values have been carefully chosen ;-)
We have a lot of options everywhere not always easy to understand but the most important is that if we don't have any reason to modify something, there isn't anything to modify!

[thxoptimizer]

https://ibb.co/VxFD0fZ


We cannot rip easily from commercial Blu-Ray we bought...

Does it mean that if I have AnyDVD, BD3D2MK3D will work directly from the disk?
But it's not free...

It seems there is a solution with VLC to rip ISO but even after adding keydb.cfg and libaacs.dll I can read the disc but not extract ISO (and if I could, note sure it would remove any protection).

Last option MakeMKV : I tried to extract everything before undestanding that I can't do anything with that (only Blu-Ray or mkv for BD3D2MK3D).
Trying to generate this MKV from MakeMkv (but I don't understand why I would need BD3D2MK3D after)...