BD3D2MK3D v1.17: Convert 3D BDs or MKV to 3D SBS, T&B or Frame-sequential MKV

[sneaker_ger]

CRF is usually recommended. The lower the CRF value the better the quality and the bigger the file. But at some point there are diminishing returns. The file could become even bigger than the original BluRay! Most people on here seem to use a value between 16 and 20.

[r0lZ]

Yep. I use CRF 18 for the movies where the video quality is very important (like Sin City 2), and CRF 22 when I just want to keep a movie but I want the smallest file size. The default, CRF 23, gives already very good results.

Note also that the CRF mode gives very different file sizes for movies of the same length. For example, CRF 20 may produce a very small file of only 2 or 3 GB if the movie is very easy to compress, like a CGI (Pixar) movie. In the other hand, an old movie with much noise may require 10 GB for the same movie duration. It's absolutely normal, and it's one of the major advantages of the CRF mode over 1 and 2-pass. The quality is maintained in all cases, regardless of the difficulty to compress the movie. (It's different if you use 1 or 2-pass encoding, where the bitrate is specified. And anyway, 2-pass gives always a slightly lower quality than CRF for the same file size.)

The CRF value is not all. You can compress even better without quality loss if you select a slower preset. I use normally the slow or slower preset, to keep a very good quality with a small file size.

And don't forget that in the original BD, two full-size video streams are encoded. In Half-SBS or Half-T&B, the resolution is divided by 2 and therefore the resulting movie requires much less disc space anyway.

Finally, don't be scared by the final size. It may appear too small, but x264 is an excellent encoder, and IMO, the large bitrates used for the commercial BDs are mainly to impress the consumer, and justify the high price for a double-layer BD 50. IMO, it's usually not necessary. Trust your eyes, and watch the small movies encoded with a relatively high CRF without prejudice. I bet that you will not see the difference with the original BD.

[Triple-M]

Thanks both of you.

I finished my first File and compared it with the original BD. In my opinion the 3D-Effect of the new encoded MKV-File ist much better as directly from the BD! This is great!

Is there an option in the Settings or so that my TV recognized automatically the 3D-Signal and switch on 3D-Mode? My MediaPlayer is AppleTV 4....

[thahandy]

[...]
I don't understand why it does that. Does it make sense to store the AC3+ stream without its core? AFAIK, the "+" extension cannot be decoded without the core. Correct?

Is it a known bug of MakeMKV ? If it's the case, should BD3D2MK3D prohibit to use the AC3+ streams from a 3D-MKV container created by MakeMKV ? Or should we report that bug to the MakeMKV staff ?

Thanks in advance if someone can help me understand that mess!
Seems its MakeMKV.

Dolby Digital Plus Problem (http://www.makemkv.com/forum2/viewtopic.php?f=8&t=9182)

Dazkine Wed Jun 24, 2015 7:38 am

yeah but also PowerDVD doesnt like what MakeMKV is producing...

Dolby Digital Plus on Bluray contains a Dolby Digital 5.1 Stream + 4ch encoded in Dolby Digital Plus.

A non DD+ capable device uses the Dolby Digital Stream
A DD+ capable device uses the Dolby Digital 5.1 Stream, but replaces the 2 rear channels with the four channels encoded in Dolby Digital Plus. That makes a 7.1 Signal (3.1 from the DD Stream, and 4.0 from the DD+ Stream)

Dolby Digital+ can also exist alone (Television, Streaming, HD-DVD), but on Bluray its like I said.

I guess MakeMKV is just producing 2 independent Audiostreams, but that doesnt work for Blurays. The Bluray Player always needs the DD Signal + the DD+ "extension".

So it's a mix of 2 audiocodecs.

It more like DTS-HD cause there the HD extension also needs the "core"

When you play back the original disc PowerDVD is reporting "Dolby Digital Plus 7.1"

[r0lZ]

Is there an option in the Settings or so that my TV recognized automatically the 3D-Signal and switch on 3D-Mode? My MediaPlayer is AppleTV 4....
There are 3 things that a player can use to switch to the right 3D-mode automatically: the stereoscopy mode in the MKV header, the frame-packing in the video stream, and an extension in the file name. BD3D2MK3D sets the stereoscopy and the frame-packing automatically. Most hardware players recognise the frame-packing. If it's not sufficient, maybe you have to select one of the two 3D extension in the file name. See Settings -> Output File Name -> 3D Format Extension. You may also try to use the .mk3d file extension instead of .mkv.

If nothing works, consult the Apple TV manual, and if there is a special file extension not already implemented in BD3D2MK3D, I'll add it. Otherwise, ask Apple to do a better job! ;)

[r0lZ]

Seems its MakeMKV.
Yep. It's also what I've noticed. Pity. And thanks for the info.

[Triple-M]

Support your Tool DTS 7.1 or Dolby Atmos? I have a BD with DTS 7.1 and the File at the End has only DTS 5.1.

[tebasuna51]

Yes.

In tab '2: Select Streams' uncheck 'Use the 5.1 core of DTS-HD...'

[Triple-M]

Ok, thanks. I didn't unchecked it because the note "highly recommended".

[r0lZ]

As promised, it is now possible to convert any audio stream to AAC.

I have also verified the conversion when using a 3D-MKV file created by MakeMKV as input, and unfortunately I have had to prohibit to use the E-AC3/DD+ streams with 4 channels only. They are bad conversion by MakeMKV, totally unusable. Luckily, the E-AC3 format is rarely used on the commercial BDs, but if you have a movie with DD+ streams, you will have to select the AC3 core in the MakeMKV GUI. When that huge bug will be fixed in MakeMKV, BD3D2MK3D should accept the E-AC3 tracks (with 7.1 channels) without problem.

Please note that when using a 3D MKV as input, it is not possible to convert or extract the core of the TrueHD audio tracks, because the THD stream is stored "alone", without a 5.1 pseudo-core in the MKV. (It's a Matroska requirement.) Therefore, there is nothing to extract. It is not possible either to convert the THD track to AC3, simply because it doesn't make much sense to convert the THD track when the AC3 track is available without conversion in the original BD. If you want to keep the AC3 track, you have to select it in the MakeMKV GUI. (Of course, you can also convert the THD track manually with the Tool menu or with eac3to, but that's another story.)

There are also two important bugs fixed in the tool to convert a SRT subtitle file to ASS 3D.

v0.88 (April 16, 2016)
- When the option to convert the audio streams to AAC is selected in tab 2, all audio tracks are now converted, instead of only the DTS and LPCM tracks.
- The extension .dtshdma for the demuxed DTS-HD-MA tracks was wrong. It is now .dtsma as it should for eac3to.
- The option to keep only the core of HD audio tracks in tab 2 is now removed when a 3D-MKV created by MakeMKV is the source.
- It is not possible any more to use the bad and useless E-AC3 (DD+) audio tracks created by MakeMKV (with only 4 channels)
- The labels of the DTS-HD/MA audio tracks in the final MKV show now the number of channels for the HD and the core (like 7.1/5.1)
- The labels of the audio tracks converted to AAC show now also the Quality value that has been used to do the conversion.
- Small cosmetic changes.
- Bug fix in Convert SRT to ASS 3D: The first subtitle was sometimes missing when the input file is encoded in UTF-8/16.
- Bug fix in Convert SRT to ASS 3D: The 2-lines subtitles were not properly converted as one long line with \N.
- Bug fix: Some tools crached when trying to open a file or folder if no BD or MKV was loaded first.
- Updated x264 to the latest version (0.148.2692)

Download: BD3D2MK3D.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z)

[Triple-M]

There's an Update of makeMKV, now the View (left eye or right eye) is stored in the MKV made by makeMKV. 3D-Planes i haven't tested yet.

[r0lZ]

OK, thanks.

If the view order is correctly stored in the "stereoscopy" field of the MKV header, BD3D2MK3D should recognise it already. That means that the correct view should be selected automatically in the first tab, and the red warning should not be visible any more.

Similarly, the 3D-planes assignments should be automatic if they have been implemented with "3d-plane" tags (as suggested by tebasuna51), but that needs to be confirmed because they may have defined another tag or used a totally different method. I will have a look this evening...

[Triple-M]

The correct view ist selected automatically, i have tested it today.

[r0lZ]

Perfect! :)

[r0lZ]

I confirm that the stereoscopy is correctly saved in the MKV header and the 3D-Plane number in the "3d-plane" tag of the subtitle stream. Therefore, MakeMKV v1.9.10 generates now 3D-MVC MKV files with the full information necessary to convert them to SBS or T&B with BD3D2MK3D. Good point.

I confirm also that BD3D2MK3D recognises that information correctly. You can use BD3D2MK3D v0.88 without problem with the MKV files created by MakeMKV v1.9.10 or greater.

However, the terrible EAC3/DD+ bug is still not fixed. Therefore, you still need to include the 5.1 core of the EAC3 tracks in MakeMKV if you want to include it in the final MKV, and it is totally impossible to use the full EAC3 track. Pity. I hope that that bug will be fixed soon.

Of course, if you open a 3D-MVC MKV file created with MakeMKV v1.9.9 or any previous version, the information will still be missing, and you will have to enter it manually. For that reason, it will always be possible to modify the views order and the 3D-Plane numbers in the BD3D2MK3D GUI. But you should do it only if you see the red warnings.

[tebasuna51]

I confirm that the stereoscopy is correctly saved in the MKV header...
Bug detected by nevcairiel :
http://www.makemkv.com/forum2/viewtopic.php?f=10&t=13892#p49039

I don't have rigth eye BD's to test.

[frank]

There are 2 types of DD+ or eac3.
The old eac3 version used on HD-DVD has no core!
DD+ was mandatory on HD-DVD. Such audio streams have to be completely re-encoded, they are not backward compatible.
Probably the software is a bit outdated, because BD mostly use DTS.

With eac3to I never could demux a core from eac3 (to ac3). But I could create a multichannel wav for reencoding to ac3.
You can't see from what source (HD-DVD, BD) the mkv comes. (OK, there are no 3D movies on HD-DVD...)
DD+ from BD or TV is backward compatible. If you have an AV receiver with HDMI 1.3 or later, you’ve already got support for DD+.
Hope you have the right test stream.

[r0lZ]

@tebasuna51
Damn! I haven't verified with a right-view in AVC movie. And if it's really a MakeMKV bug, it's even worse than the previous situation, because the user will think that the correct views order is selected, and end up with the views inverted! I hope they will fix that bug immediately! I can't implement a workaround in BD3D2MK3D, because I have no way to know what version of MakeMKV has been used to create the 3D MKV.

@frank
BD3D2MK3D doesn't use eac3to to demux the audio streams. It uses tsMuxeR. (Except for the TrueHD tracks in a MKV container, that tsMuxeR cannot demux.)

The bug is in MakeMKV. It can successfully extract the 5.1 core of the DD+ tracks from the BD 3D. But you can also tick if you wish the DD+ track itself, to include it in the MKV. And the problem is here. The DD+ track (on BD) consists of the 5.1 core and an extension with 4 channels. MakeMKV extracts the extension only and create a bad 4-channels tracks that is not EAC3 nor AC3. The main channels are missing! It's just unusable and it is not recognised by eac3to, MediaInfo and all players I have. Only tsMuxeR seems to recognise it, and luckily shows that it has 4 channels. It can also demux it, but again, that track is useless. That means that, as long as that bug is present in MakeMKV, you have to tick the 5.1 core of the EAC3 tracks, and untick the "EAC3" track in the MakeMKV GUI. (If you don't untick it, BD3D2MK3D will detect that it has only 4 channels and refuse to process it.) It's a problem only for peoples who want to keep the best audio quality and use MakeMKV to decrypt the BD.

I agree that BD mostly use DTS for high quality audio. TrueHD is also very frequent. Luckily, EAC3 tracks are relatively rare, but they exist. A good example is the French track on Brave (Pixar).

[thahandy]

@tebasuna51
[...]
I have no way to know what version of MakeMKV has been used to create the 3D MKV.
[...]



mkvinfo Sample_t00.mkv -G |Find "Writing application"

| + Writing application: MakeMKV v1.9.10 win(x64-release)

is one way to get it ;)

[r0lZ]

Thanks for the tip!

[r0lZ]

It's not an important release, but you should download it if you use MakeMKV to decrypt your 3DBDs. I've just implemented a test of the version of MakeMKV that has been used to create the input MVC MKV, and if it's v1.9.10 (the current version), BD3D2MK3D does not trust the views order in the MKV header, due to the MakeMKV bug. I suppose that the next version will have the correct stereoscopy value.

BTW, I have also noticed that MakeMKV doesn't set the Forced MKV flag on the "forced only" subtitle streams. It's a pity, as it's very easy to do. But it's not really serious, because the user can set the flag manually in the GUI or MakeMKV or BD3D2MK3D. Anyway, I have reported the bug on the MakeMKV forum.


v0.89 (April 23, 2016)
- BD3D2MK3D does not trust any more the views order written by MakeMKV v1.9.10 due to its bug.
- Modified some dialogs to explain that MakeMKV v1.9.11 should be OK.

Download: BD3D2MK3D.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z)

[tebasuna51]

Thanks r0lZ!

[Triple-M]

Is there a difference (in the Video Quality perhaps) if i play the MVC-MKV directly with an right Player or the MKV after i converted it with your Tool? Is the Video Quality both the Same?

[sneaker_ger]

Technically, every lossy encoding loses information (read: quality). If the bitrate is high enough a human won't be able to tell the difference, though. We call that "transparent". So the MVC should in theory be better but it might not make any difference in practice if you use sufficient bitrate (i.e. sufficiently low --crf or sufficiently high --bitrate).

P.S.: While it is possible to employ lossless encoding (in x264 using --qp 0) the resulting file would be much larger than the original BluRay.

[Triple-M]

Ok thanks. And with the right Player i can switch between 2D and 3D in die MVC-MKV without a second Version of this File only for 2D without MVC, right?

[r0lZ]

Sneaker_ger is right. But you should also take into account that the resolution of the image is divided by 2 in one direction if you encode in Half-SBS or Half-T&B. Therefore, in addition to the re-encoding, there is also a quality loss in resolution. (To avoid that problem, you can encode in Full-SBS, Full-T&B or Frame Sequential format, but that formats are not supported by the majority of the hardware players.)

Most players do not recognise at all that a MVC-MKV contains a 3D movie. They play only the AVC stream, in 2D, and ignore completely the MVC stream. As fas as I know, only Stereoscopic Player is currently able to play the MVC-MKV in 3D. I don't know if it can play it in 2D, but you can use another player anyway. In the other hand, almost all software or hardware 3D players can play the Half-SBS or Half-T&B formats generated by BD3D2MK3D in 3D. It's why I wrote it. Most players or 3D-TVs have an option to display the 3D movie in 2D, except some software 3D players. And, of course, you cannot use a 2D-only player to play a 3D movie generated by BD3D2MK3D in 2D, because it will show you the two views at the same time.

So: Use the MVC-MKV generated by MakeMKV if quality matters much, if you have plenty of disc space, and if you are happy with Stereoscopic Player to watch your movies in 3D. You can watch them in 2D easily, without quality loss.
Use Half-SBS or Half-T&B created by BD3D2MK3D if you want a format recognised by all 3D players or if disc space matters. It may be more difficult to watch the movie in 2D on a PC, but it's possible with the right software.

[sneaker_ger]

As fas as I know, only Stereoscopic Player is currently able to play the MVC-MKV in 3D.
And LAV + madVR.

[Nico8583]

Does anyone know if there is a way to combine AVC and MVC like MakeMKV ? CombineMVC is too old now and compatibility is not so good..

[r0lZ]

I don't think there is a direct way, but you can create a BD-3D ISO with tsMuxeR, mount it and then create the AVC+MVC MKV with MakeMKV.

[Nico8583]

Yes but I would like to skip some steps :)
I would like to try to make MKV AVC+MVC and it seems the only way to do that is to combine AVC+MVC into a single H264 elementary stream... Also I would like to try dual stream (1 full stream for left eye and 1 for right eye) but I don't know if it's possible, even if some camcorders support that.

[r0lZ]

Yes but I would like to skip some steps :)
I don't think it's possible currently. :(

I would like to try to make MKV AVC+MVC and it seems the only way to do that is to combine AVC+MVC into a single H264 elementary stream...
Well, it's what MakeMKV tries to promote. But IMO, adding the AVC and MVC streams as two different elementary streams in a MKV container is probably a better option, much easier to implement. However, currently, it's not possible. The MKV standard does not accept the MVC stream. It's probably why MakeMKV has developed its combined format, recognised by MkvMerge as a single 2D AVC stream (but unfortunately also by almost all players).

Anyway, since the combined AVC+MVC stream is only supported by stereoscopic player so far (or by complex combinations of filters), I think that all that techniques are very limited, and will probably be usable only with some very rare software players at best. I don't think they are really interesting, except perhaps for backup purposes.

Also I would like to try dual stream (1 full stream for left eye and 1 for right eye) but I don't know if it's possible, even if some camcorders support that.
You can add two AVC streams in a MKV without problem, but that would require to re-encode at least the MVC stream. And indeed, I don't think it is possible to play that dual-AVC MKVs in 3D with any player so far.

Currently, the only widely supported 3D formats in full resolution are Full-SBS, Full-T&B and Frame Alternate. They require to re-encode the video, but at least, you can play them almost everywhere (if your hardware supports the required level). It's why BD3D2MK3D can produce them. I don't think it is a good idea to try other formats requiring to re-encode the video. The quality is not better, and the compatibility is and will probably always be terrible.

[Sharc]

As far as I understand the Blu-ray standard accepts both the the ssif structure (base AVC and dependent MVC in 2 separate .m2ts files) and the interleaved format (base AVC and dependent MVC in the same .m2ts file combined/interleaved). This means that any player which claims to be Blu-ray compliant must accept both formats.
(MKV is a different story however as you mention).

[Nico8583]

Mastroska supports TrackOperation to combine AVC and MVC track : https://www.matroska.org/technical/specs/notes.html#TrackOperation
But I don't know how to use it. I think it's used by MakeMKV in order to create MK3D but perhaps I'm wrong.

[Sharc]

I see, thanks. Obviously mkvmerge does not yet support the muxing of base (AVC) and dependent (MVC) streams. The matroska page also says:
The 3D support is still in infancy and may evolve to support more features.
So we need to be a bit patient, I think .....

Edit:
You could use DGMVCCombine.exe to create a single interleaved (frame alternate) stream of an AVC and dependent MVC source, then mux to mkv with mkvmerge with the stereoscopic flag set accordingly. It plays 3D in bino player, but not in stereoscopic player ...... :(

[Nico8583]

Thank you for DGMVCCombine.exe, I will look at it.
You can play MKV from MakeMKV in Stereoscopic Player ? If yes, MakeMKV may use this function from Matroska so it is functional

[Nico8583]

I've tried many files and only Half-SBS / Half-TB are well supported by my TV and my RPi. AVC/MVC combined in a M2TS is supported by my TV without problem.
3D from MakeMKV files are not supported by my TV and my RPi, the movie is displayed only in 2D. Same issue for DGMVCCombine into MKV container...

[Sharc]

^^^
That's pretty much how it is. As soon we move outside of released industry standards things may or may not work.

[sambal]

It's very good possible this question has been asked before, but I don't feel like reading 50 pages right now:D

Many 3D-movies don't have any 3D-plane, so the subtitles are 'flat'. In those cases I give them a fixed depth of 8. Of course I only find out about not having any planes after ripping de BD, so I have to create those 3D-subtitles afterwards. Unfortunately all versions after 0.71 lack the option to convert subtitles to a fixed depth, so I must use that older version.
Is there a particular reason for not supporting this option anymore?

[r0lZ]

You can convert the subtitles to 3D with a fixed depth with the current version. Just leave the 3D-Plane field empty, and fill your desired depth (8 in your case) in the "Additional depth" field. You'll get a warning about the flat subtitles. Just accept it.

(You can also leave the 3D-Plane field blank to use the depth tags already present in the input XML, if the XML has already been created with BD3D2MK3D and a 3D-Plane. That allows you to manually edit some depth values if you wish. Note that the Additional depth is never stored in the XML. It is taken into account only when the conversion occurs.)

I have removed the old "fixed depth" conversion because it used obsolete tools, and since it is possible to do the same thing with the new conversion function, it was useless. Its only advantage was the possibility to process several subtitle files in batch. But is it really necessary?

[EDIT] I have slightly modified the labels and help dialogs of the subtitle conversion tool to make it more obvious that the tool can be used without 3D-Plane to convert subtitles to fixed depth 3D.

[sambal]

That's good to hear, I didn't know that! I'll give it a try next time I encounter such a movie.
Thank you for the quick reply, it is much appreciated.:thanks:

[sneaker_ger]

Mastroska supports TrackOperation to combine AVC and MVC track : https://www.matroska.org/technical/specs/notes.html#TrackOperation
But I don't know how to use it. I think it's used by MakeMKV in order to create MK3D but perhaps I'm wrong.
I don't think MakeMKV uses Matroska TrackOperation. And I don't think it is even intended for that. TrackOperation is for tracks that are independently decodable which isn't the case for MVC views.
Notice how mkvmerge handles audio: DTS-HD MA is muxed as a single track because it is made of extensions building on a core. Like MVC view relying on a base view.

[Nico8583]

I've looked at MakeMKV source code and if I'm right it uses KaxVideoStereoMode to mux stream. KaxVideoStereoMode is a part of libmatroska and again if I'm right it's based on TrackOperation. This is why it was my conclusion about MakeMKV but perhaps I'm wrong, I don't know this specification :)

[Sharc]

You can play MKV from MakeMKV in Stereoscopic Player ? If yes, MakeMKV may use this function from Matroska so it is functional
Yes, mkv from MakeMKV play correctly in 3D with Stereoscopic Player.

I could also re-encode 3D sources into new 3D using x264 with --frame-packing 5 (1-pass crf), and muxing the encoded .264 with tsMuxer or mkvmerge. 3D playback however works only with Bino, in my case. Stereoscopic Player swapped the views regularly about every half second . :confused:
(I tested video only, without audio or subs).

[Sxc]

I had been using 0.85 and just updated to 0.89, I just noticed (I'm using x265) that on the y4m [info] line it says

1920x2160 fps 24000/1001 i420p8 sar 1:1

when in my old version it has sar 2:1 - will this matter, my previous files which I play on my LG 4K were stretched across the full width and then I used the 3D button to set it to top and bottom and it looks perfect.

Also, I have been replacing the x265_x64 executable with one that has 10 bit support, which gives a better output (reducing banding significantly), maybe you could either bundle a exe with 8/10/12 bit support and make it selectable in h265 options?

[r0lZ]

Welcome to the Doom9 forums, Sxc!
I had been using 0.85 and just updated to 0.89, I just noticed (I'm using x265) that on the y4m [info] line it says

1920x2160 fps 24000/1001 i420p8 sar 1:1

when in my old version it has sar 2:1 - will this matter, my previous files which I play on my LG 4K were stretched across the full width and then I used the 3D button to set it to top and bottom and it looks perfect.
The SAR has been changed in v0.86. It is now 1:1 for all frame packing modes (Full and Half SBS and T&B). It seems that it's the best SAR to use with the vast majority of players. It's the conclusion of a long discussion and many tests (starting with this post (http://forum.doom9.org/showthread.php?p=1758904#post1758904)).

Do you have a problem with the new setting? AFAIK, as soon as you switch to 3D mode (or the TV switches automatically to 3D mode), the SAR should be ignored and the aspect ratio should be correct. At least, it's what happens with my Samsung TV.

If your TV does not display the movie correctly, try to change Settings -> Full-SBS/T&B aspect ratio. And if that doesn't work, you can edit the __ENCODE_3D.cmd script and change the --sar option manually.
Also, I have been replacing the x265_x64 executable with one that has 10 bit support, which gives a better output (reducing banding significantly), maybe you could either bundle a exe with 8/10/12 bit support and make it selectable in h265 options?
I will consider that suggestion. But take in mind that the 10 or 12 color bit modes are not compatible with many hardware players and/or graphic cards. But I agree that reducing the banding artefacts is a good thing if it works for you. Banding remains certainly the most noticeable problem of the videos encoded in h264 or h265.

[Airmiles]

r0lZ,

Haven't been in here for a while now, so hi again to everybody.

Just a brief question: will the demise of slysoft have any impact on your app? I mean, support for new BR-discs will now obviously stop (there goes my life long subscription :angry:). Wouldn't it be helpful to add support for MKVs that contain the MVC track?

Just a question inspired by concern for future use of this fantastic app of yours.

[r0lZ]

Well, afaik, AnyDVD HD is not dead. It should be continued by RedFox (https://www.redfox.bz/). (See this (https://www.redfox.bz/about.html).) Anyway, there are other ways to remove the protection from the original BD. You can now open MVC-MKV files created with MakeMKV (currently with some limitations, but the next version of MakeMKV should be better). And there are other BD decrypters around.

The philosophy of BD3D2MK3D is to re-encode the two views as SBS, T&B or Frame-Sequential. I don't think that adding the re-encoding in AVC+MVC is a job for BD3D2MK3D. And MakeMKV does already lossless AVC+MVC MKVs with the original BD files (without re-encoding). Doing the same thing with BD3D2MK3D will be more time consuming, because MkvMerge cannot accept MVC tracks. I will have to combine the MVC with the AVC track first, and that takes a long time and much disc space. However, I have considered to implement lossless remux of AVC+MVC to M2TS. tsMuxeR can mux the AVC and MVC tracks separately to M2TS. There are some limitations (no chapters and no metadata for example), but it's not fundamental. I'm still not sure I'll implement that, because I don't think that many peoples are interested in simply remuxing the original streams to create a huge M2TS file. Also, you can already do it with the tsMuxeR GUI. But I may do it when I'll have some free time, simply because it's easy. All I have to do is generate a cmd file and a meta file for tsMuxeR.

Anyway, BD3D2MK3D will never implement the decrypting operation itself, so merging the AVC+MVC tracks to MKV or M2TS will never be a solution to replace AnyDVD HD.

[Sxc]

Welcome to the Doom9 forums, Sxc!

The SAR has been changed in v0.86. It is now 1:1 for all frame packing modes (Full and Half SBS and T&B). It seems that it's the best SAR to use with the vast majority of players. It's the conclusion of a long discussion and many tests (starting with this post (http://forum.doom9.org/showthread.php?p=1758904#post1758904)).

Do you have a problem with the new setting? AFAIK, as soon as you switch to 3D mode (or the TV switches automatically to 3D mode), the SAR should be ignored and the aspect ratio should be correct. At least, it's what happens with my Samsung TV.

If your TV does not display the movie correctly, try to change Settings -> Full-SBS/T&B aspect ratio. And if that doesn't work, you can edit the __ENCODE_3D.cmd script and change the --sar option manually.

I will consider that suggestion. But take in mind that the 10 or 12 color bit modes are not compatible with many hardware players and/or graphic cards. But I agree that reducing the banding artefacts is a good thing if it works for you. Banding remains certainly the most noticeable problem of the videos encoded in h264 or h265.

Thanks for the reply - given the settings I use (CRF20, veryslow, main10) I didn't want to wait for a movie complete to find there was an issue, when my current encodes finish I will do a 3D trailer and see how that plays back, I'm only concerned about playback on my LG 4K OLED via Xplay (plex client). If it works fine I'll leave it at 1:1 too.

[r0lZ]

It should play fine. AFAIK, the SAR is almost always ignored for half SBS or T&B 3D, and when it is not ignored, 1:1 is correct 90% of the times.

[r0lZ]

Also, I have been replacing the x265_x64 executable with one that has 10 bit support, which gives a better output (reducing banding significantly), maybe you could either bundle a exe with 8/10/12 bit support and make it selectable in h265 options?
I will consider that suggestion. But take in mind that the 10 or 12 color bit modes are not compatible with many hardware players and/or graphic cards. But I agree that reducing the banding artefacts is a good thing if it works for you. Banding remains certainly the most noticeable problem of the videos encoded in h264 or h265.
Well, I've read some doc on 10bit color depth support and the BD standard and compatibility with avisynth (including this doc (http://avisynth.nl/index.php/High_bit-depth_Support_with_Avisynth)), and I'm not sure it is a good idea to implement it. AFAIK, currently, avisynth is still limited to 8-bit (although some filters may use more bits internally), and I wonder if encoding in 10-bit is really interesting if avisynth returns a 8-bit video anyway.

Perhaps it is possible to use various alternative filters within avisynth to output 10 or 12-bit, but honestly, I don't know how, I'm not sure they will be compatible with the filters BD3D2MK3D requires, and again, given the fact that the input BD is encoded in 8-bit (TV range), I don't think that the gain will be major. Note also that most monitors and TVs are 8-bit only, and therefore you can only expect a more or less well dithered 8bit color depth in final, even if the whole processing and encoding processes are made correctly in 10 or 12-bits.

So, unless somebody can explain what I'll have to do to effectively support 10 or 12-bit color depth during the whole process and can show me clearly that there is a big advantage, I will not do it. Sorry.

Anyway, if you really want to encode in 10 or 12-bit, you can replace the x264/x265 exe with the 10/12-bit version, as you know. You can even create several small cmd files to restore the 8-bit version or overwrite it with another version, and call the right batch when necessary, before launching the encoding.