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

[Marty]

So the problem is not in my pc? How come the guy in the youtube video does it work?

[r0lZ]

OK, here is the fix for the bug discovered by Marty. That terrible bug was in my code, and not in BDSup2Sub.jar.

This version fixes also a couple of minor bugs, including a bug introduced in the previous version, but happening only in extremely rare circumstances. (In fact, I think there is no 3D BD with a title that can trigger that bug, unless you click on Show All 3D Playlists and you select a playlist beginning with a multi-angle MPLS, and the title has the tsMuxeR bug with the wrong angle numbers, and you convert at least a subtitle file to 3D. That should not happen often! Anyway, it's fixed now.)

I have also updated the MkvMerge binaries to the latest version.

# v0.50 (September 22, 2014)
# - Converting subtitles to 3D full-SBS or full-T&B with 3D-planes was broken. Thanks Marty!
# - Minor bug fixed: The 3D-planes were not correctly checked in MPLS files bedinning by a multi-angle video file.
# - Fix: Tools -> Find dependent view MPLS Files was broken for multi-angle playlists.
# - The errors and warnings should now appear in red in the console.
# - Updated MkvMerge and the MkvMerge GUI to the latest version (v7.2.0)

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

I am currently working to the MPLS parser, to be able to avoid tsMuxeR to analyse the content of the BD. This version is therefore probably the latest one using tsMuxeR to parse the MPLS files. I will need some time to integrate my parser in BD3D2MK3D, and I may introduce new bugs, so I hope this version is (almost) bug free.

[r0lZ]

So the problem is not in my pc? How come the guy in the youtube video does it work?
Don't worrk, the bug was in my code. I have recently modified radically the way the 3D conversion happens, because Thalyn has discovered an important bug in tsMuxeR. When I have modified the code that produces the two (left and right) XML files for the conversion to full-SBS or full-T&B, I have introduced the bug. Since personally I use only half-SBS, I have not checked that part of my code carefully enough.

I guess the guide used an earlier version, or they explain how to create half-SBS or half-T&B, and that conversion worked fine.

Please try v0.50. It should be fine, but I have tested it only roughly.

[Marty]

So it was really quick fix, now it's working without any problems, thx :)

I apologize in advance for bad English, I use google translator.

Got a question about the functionality of your program. Perhaps what I write will make sense :)

I'll give an example - I have a 3D BD Iso with English subtitles but I need to get there Czech subtitles. So through your program extracted English 3D planes and I will make him a Czech subtitles with right offset from the original English subtitles.

Is this possible? If so, it would be possible to give some guidance for beginners? The procedure I used a video from youtube (I posted above) did not work as I expected.

Thx for your work

[r0lZ]

Well, I don't know what you want to do exactly. If I have correctly understood the youtube guide, they use the conversion to 3D only to test if there are warning for undefined depth values, and they generate a 2D SUP file to incorporate it in the original BD. BD3D2MK3D is not made for that purpose, but it can help if you want to convert your 3D BD to SBS or T&B and use external subtitles, not present in the original BD.

Note that the guide has several errors. For example, it extracts the 3D-planes directly from the M2TS file. That may work, but it's very risky. The tool used to extract the 3D-planes has been designed to extract them from the MVC elementary stream, and that's much more simple. Therefore, you should demux the MVC stream first. Anyway, I repeat that creating 3D subtitles to remux them in the BD doesn't make sense.

The procedure to create a SBS or T&B MKV with additional subtitles is relatively simple. Follow the normal procedure to create the SBS movie. You should select any subtitle stream, but it will be replaced by your own subtitles later, so the selection doesn't matter much. However, for best results, I suggest to select the language that is the closest to the language of your subtitles, in the hope that the positions, widths and durations of the original subtitles will be similar to yours.

When BD3D2MK3D will have finished its work, you should convert your downloaded SRT file to a 2D SUP file. (You can do that with 3D-subtitler in 2D mode, as explained in the guide. Try to put the subtitles at approximately the same location in the screen than the original subtitles.) Then, use Tools -> Convert Subtitles to 3D (with 3D-Planes). Load your SUP file, and any valid 3D-plane, to create a 3D SUP or IDX/SUB file. Of course, you must use the same SBS or T&B mode than the mode you have used to convert the movie. (Normally, you should leave the Additional Depth to 0. I don't know why they set it to 6 in the guide.)

When you have your 3D SUP or IDX/SUB file, you should modify the _MUX_3D_OPTIONS.txt file to replace the original English subtitle with your file. That's easy. Just modify the file name, the language code and, it it's necessary, the label.

Finally, encode and mux the movie by double-clicking _Encode.cmd. Wait for a while and watch the movie to verify if the subtitles are at the correct depths.


Unfortunately, a specific 3D-plane is made for a specific subtitle stream, and if your subtitle file has different characteristics than the original SUP (such as different positions of the subtitles on screen, different widths of the strings, or, more importantly, different timings), the result might not be satisfactory. You can verify if there are many warnings in the log file (as explained in the guide), and if it's the case, try to convert your subtitles again with a different 3D-plane. Anyway, the presence of absence of warnings in the log is just an indication. You cannot be sure that the depths will be correct even when there are no warnings. The only way to do it perfectly is by trials and errors. Note also that you can manually edit the depth tags in the temp 2D XML file if you need to modify the depth of a few subtitles. (Or you can modify the depths of all subtitles at once with the Additional Depth parameter.) Anyway, when you think that your modifications should be OK, you have to convert the subtitles to 3D again. If you use another 3D-plane, use the same procedure than the first time. If you have only edited the Depth values in the XML file, you should convert the XML (and not the original SUP), and NOT specify a 3D-plane (leave that field blank). That way, the subtitles will be converted with the depths values already present in the XML file. (The Additional Depth can always be modified if you wish, and that value is never saved in the XML file, but normally it's not necessary.)

To remux the final MKV with your newly created subtitles without computing the h264 stream again, just double-click the _MUX_3D.cmd file.


Now, if you want to add your subtitles in the original BD, the procedure is totally different, and unfortunately you don't have the same possibilities. You should simply convert the SRT to 2D SUP, and remux it with an existing 3D plane. Again, it is important to select the best one, and that's not easy. If the result is not good, the only thing you can do is to try with another 3D-plane. (If I have understood the guide correctly, they use the conversion of the subtitles to 3D only to examine the number of warnings. That may be useful to help select the best 3D-plane for your subtitle stream, but remember that the absence of warnings is not a guarantee that the result will be perfect.)

Good luck!

[r0lZ]

Yet another bug fixed.


# v0.51 (September 28, 2014)
# - Bug: The AVS script was wrong in full-SBS or full-T&B and without subtitle to hardcode.


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

[CRFOnly]

Ive been a doom9 lurker for years, but I finally registered just to post here.

First of all I have to say thank you very much for coding this. Ive been looking for a reliable and powerful 3d ripper for more than a year. I didn't want to use dvdfab because I honestly think its garbage. This software is the perfect balance of power and ease-to-use.

I tried a couple encodes using my usual encoding settings for 2d encoding and i must say the result is perfect. Ive come across some problems tho, but fixed them myself. Ill post still in case someone read. I'm using Nvidia 3dVision with PowerDVD14. I found out that if i manually mux with the last mkvmerge, PowerDVD will recognize subtitles but wont make them work (even if i activate them manually). Weird thing is if I use your muxer (which is actually mkvmerge from the command line) everything works great. I dont get it but its certainly not a problem from your wonderful software.

I also found out that the 3d subtitle maker always make sup file without any problem but if i ask it to make 2d subtitles as well, it wont make them in .sup half of the time.

I'm not sure why this is happening... Im mostly using foreign subtitles and most of the time your software take the complete movie sub and extract only forced subs from it, works great in 3d but fail in 2d.

Apart from that, its perfection, Thanks again. I would like to request a feature in the software, the hability to see the source file sizes (example subtitles sizes). When i see multiple subtitles files with the same languages, im trying to pick the forced one (which is lower in size). Just saying if you cant i understand.

Thanks and keep up the good work!

[r0lZ]

Thanks for your kind words, and welcome to the Doom9 forums!
I found out that if i manually mux with the last mkvmerge, PowerDVD will recognize subtitles but wont make them work (even if i activate them manually). Weird thing is if I use your muxer (which is actually mkvmerge from the command line) everything works great.:eek: That's really strange. Especially given the fact that BD3D2MK3D includes normally the last version of mkvmerge.

Have you tried to use the same parameters than BD3D2MK3D ? You can find them in the _MUX_3D_OPTIONS.txt file. For example, BD3D2MK3D adds the global option --disable-track-statistics-tags anyway. Without that options, small stat files are muxed with all video, audio and subtitle files. Maybe these stat files confuse PowerDVD.

I also found out that the 3d subtitle maker always make sup file without any problem but if i ask it to make 2d subtitles as well, it wont make them in .sup half of the time.

I'm not sure why this is happening... Im mostly using foreign subtitles and most of the time your software take the complete movie sub and extract only forced subs from it, works great in 3d but fail in 2d.Hum, I will have a look. Personally, I use only VobSub format (for compatibility reasons) and therefore I don't verify often how the SUP files are created.

Note that when you don't explicitly ask to extract the forced subtitles only from a stream, there is no need to create a 2D SUP file. The original SUP demuxed from the BD IS the 2D SUP file. So, I assume that the bug happens only when you select a "forced captions only" stream in tab 2. Right?

I would like to request a feature in the software, the hability to see the source file sizes (example subtitles sizes). When i see multiple subtitles files with the same languages, im trying to pick the forced one (which is lower in size). Just saying if you cant i understand.
I understand, but I can't do that easily. The problem is that the stream must be demuxed to know its file size. Or, at least, the whole original M2TS file must be analysed to compute the size of their streams, and in both cases, it's a very long process.

There are several ways to examine the subtitles and decide what streams you need to keep.

You can use the preview to play the subtitle you want to examine. You need a player that displays the available subtitle streams in the same order than in the MPLS file (and therefore than in BD3D2MK3D), but it's usually the case. (You can force BD3D2MK3D to use a specific player with Settings -> Player for Preview.)

If there are several streams that can be what you want, you can also tick them all, and let BD3D2MK3D demux them. You'll see their file size and you can examine their content with BDSup2Sub. Finally, it is easy to remove the streams you don't want by editing the _MUX_3D_OPTIONS.txt file.

Final note: I like your pseudo. CRFOnly is my philosophy too! ;-)

[CRFOnly]

Yeah there is something mkvmerge put in the default command line PowerDVD doesnt like for sure. It isnt related with --disable-track-statistics-tags because ive been using this line way before i used your software. Hopefully ive done enough mkvmerge from the commandline to be able to do stuff using it.

I actually already edited _MUX_3D_OPTIONS.txt for my needs. Because honestly the default one you provide put too much useless attachments in the mkv. So i simply only keep video/audio/subs/chapters and name the tracks the way i want. Everything works great. I assume PowerDVD have the same problem with all my older muxs, but i never actually use PowerDVD except to read 3D content.

Another wierd thing PowerDVD do is not actually apply 3d on the 3d subtitles. So you see the 2 subs in the screen when the movie roll and the image is still in real 3d. Thats why im keeping 2d subs as well.

About the subtitles problems, Its happening only if the selected subtitle is the full and i tick the forced checkbox (because i want forced subs). So the software extract the subs (which is full version) then detect the forced captions and make a 3d sub out of it (which is good) but doesnt do the same to make 2d forced subs.

Thats why i wanted the ability to be able to see subtitles size, so i can select forced subs (most of the time they in a separate track for french) and then let the program do his thing without any problem. Sure thing BDINFO can detect this so its not a big deal after all.

So yeah the problem occur only if there is no separate subtitle track, sometimes it means there is just no forced sub at all. But ive seen 3 cases already that actually have many forced subs and just dont work for 2d.

About my request its not a problem if its not easy to do, i know many ways to see if the subs are forced or not already, its just many more steps to do that could be implemented :P

Keep up the good work!

[r0lZ]

I think that attaching the two (little) CMD and AVS files with the MKV is important as a documentation, because you can always verify what has been made with the original streams and how the video has been encoded. It's not essential, but sometimes useful, and that takes very little place on disc. Now, BD3D2MK3D includes also the 3D-planes (if at least a stream has been converted to 3D), because they can be useful if, later, you want to add a subtitle in another language. You can build good 3D subtitles only if you have the original 3D planes. They are zipped, and due to their nature, the ZIP file is extremely small, so again the benefit can be big for just a little disc space.

Unfortunately, most 3D players ignore the 3D subtitles. It's a pity, but afaik only BD3D2MK3D can generate them with the right depth extracted from the 3D-plane, and therefore I understand that they are not supported by many players. The 3D subtitles are useful mainly if you use a 2D player to send its output via HDMI to a 3D TV. In that case, the 3D subs are absolutely mandatory. With some luck, the player will display them without resizing or moving them, and they will be perfectly displayed in 3D. If you want to see them in perfect 3D regardless of the player you use, I recommend to hardcode them on the video.

I have already found and fixed the subtitle bug, but I still need some time to test my modifications. (I have rewritten a large part of the subtitle handling code, and I may have introduced new bugs.) Indeed, the forced subtitles were not always generated in 2D, depending of the format and other options. At least that bug is fixed, but I have still not verified if forcing the forced flag (by ticking the "forced" checkbox on a "full" stream) works as expected. I will verify that and I'll release a new version...

Sorry, I will not implement a way to display the subtitle stream sizes. It's too much work, and more importantly, that will slow down the display of the informations too much. But usually, when the forced subtitles are in their own stream, then there are several streams in the same language (French in your example). So, you can usually assume that the forced captions are in the "forced captions only" pseudo-stream when there is only a single French stream, and tick it. (Your selection will be ignored anyway if there are no forced captions in that stream.) I agree that when there are several French streams, that may be because there are different versions or a a director's comments track, but that's easy to detect using the preview. And, as you know, editing the mux options file is easy, so when you really don't know what to do, you can tick all French streams, and then remove the streams you don't need.

[frank]

BD3D2MK3D v0.51 encodes Edge of Tomorrow properly with base view = right eye.

Basicly I encode BD compliant, so I use PGS sups.
If you convert that sup subtitles to 3D via Tools you have to tick LEFT view first, otherwise the views are mismatched in the generated 3D sup (HTAB) - that's a (new?) bug.

[r0lZ]

That's not a bug. The conversion of subtitles to 3D is totally independent of the source format of the video. The fact that Edge of Tomorrow BD has the base view = right eye is therefore irrelevant. The option in the Tool must be set to Left view first, unless your SBS or T&B file has the right view first. (Normally, it is not possible to produce a 3D file with the right view first with BD3D2MK3D, because it sets always the left view first regardless of the order of the views in the original BD, but if you want to generate 3D subtitles for a SBS or T&B movie that has not been encoded by BD3D2MK3D, it may have the views inverted, and you may need to use that option.)

[frank]

Oh, I see, that option controls the output view. Many thanks. :)

[CaBleman]

'lo there,

I've been using BD3D2MK3D on a WIN 7 machine for a while and was quite happy with 0.42
I installed Avisynth 2.58 on a Windows 8.1 with all recent updates (also the .NET ones) and tried BD3D2MK3D 0.51 with different 3D BD ISOs. THe result is awlways the same.

After demuxing, all files seem to be there, in sizes which make sense.
But the encoding step would produce MKVs which have a black/blank video part in the end.

I tried a couple of things, examined the command lines, ran the commands manually - there are no specific error message, if any at all...

Non 3D chain with BluRip works fine BTW.

Any idea or guidance where to inspect further?

thx & bye,

CaBleman

[r0lZ]

Hi, welcome to the Doom9 forums.

I have never encountered that kind of problem, so I don't know how to help.

If your output movie is blank, I can only suspect something wrong with your Avisynth installation.

I suggest to install AvsPMod (http://forum.doom9.org/showthread.php?t=153248). It's an avisynth script editor. Open the _ENCODE_3D_MOVIE.avs file in AvsPMod, and click the up arrow in the bottom left corner of the main window to launch the rendering. You should see the first frame of the movie (usually black). Use the right cursor key on your keyboard to play the next frames. After some frames, you should see the video beginning to play.
In AvsPMod, you can also click the Play (right arrow) button to launch the preview of all frames, but that button doesn't work always well.
Do NOT use the seek bar or the input field to jump directly to a specific frame, as the MVC decoder doesn't support seeking, and will hang. If that happens, close AvsPMod and relaunch it.
(Note also that the script may not work in AvsPMod if you have selected the option to hardcode subtitles on the video, because AvsPMod may not find the subtitle decoder plugin. So, test without hardcoded subtitles.)
You can also test avisynth by loading the "Test_Avisynth_Installation.avs" script in the "toolset" folder of BD3D2MK3D.

If the script doesn't work, try to use the other MVC decoder. (Change it with Settings -> MVC Decoder.)

If you can see the video in AvsPMod, that means that avisynth is working correctly, and I don't understand why you obtain blank frames. Otherwise, try to re-install avisynth. (And be sure to install the 32-bit version.) You may also have to remove the additional plugins from the Avisynth plugins folder, if you have installed special plugins manually.

[r0lZ]

Oh, I see, that option controls the output view. Many thanks. :)
Yes. I have modified the title of the frame with that option from "Stereoscopy" to "Output stereoscopy format". It should be more obvious that the "left/right view first" setting is not related to the order of the views in the original BD.

[CaBleman]

Hi r0lZ,

thank for the quick reply and for the welcome!

I had tried the Avisynth re-install already, with 2.58 and 2.6 (32 bit).
I assume that Avisynth in general was working because it also belongs in the toolchain of another transcoding tool, called BluRip, which works fine on the same machine.

So I did the tests with AvsPMod you mentioned. Your test script works fine, and when I put _ENCODE_3D_MOVIE.avs of the failing project and start the rendering, all frames are black.

Is there any way I could check the demuxed video parts (the .264 and the .mvc) each by itself with another tool (like vlc, but which file ending to use?)?

And yes, I tried the other encoder option called FRIMSource - in that case I get an error message like this:
---
Encoding _ENCODE_3D_MOVIE.avs
Movie: xxx
Encoding started 20.10.2014 23:46:02,45

C:\xxx\xxx\xxx\xxx\00xxx_mpls>"D:\xxx\xxx\BD3D2MK3D\toolset\avs2yuv.exe" "_ENCODE_3D_MOVIE.avs" -frames 198357 -o - | "D:\xxx\xxx\BD3D2MK3D\toolset\x264_x64.exe" --crf 20 --preset slow --tune film --profile high --level 4.1 --keyint 96 --no-fast-pskip --b-adapt 2 --ref 4 --frame-packing 3 --qpfile chapters_3D.qpfile --output "00800_mpls.264" --frames 198357 --demuxer y4m --stdin y4m -
error: ERROR: unknown error (-1), ..\frim_decode\src\pipeline_decode.cpp (1115)

ERROR: Decoding error.

(_ENCODE_3D_MOVIE.avs, line 32)
x264 [error]: could not open input file `-'
Encoding finished 20.10.2014 23:46:02,58
---

I'm pretty clueless.
I don't have Windows Media Player installed, though (never used it in the past, so why not avoid it totally).
Are there some codecs missing perhaps? Would trying to install ffdshow make any sense?
But, for example, the "XBox video app" in Win8 plays e.g. M2TS just fine...

Thanks for listening,

CaBleman

[r0lZ]

Normally, you don't need additional codecs.

Unfortunately, the FRIM error message "unknown error" doesn't help much!

To test if the main view of the movie has been extracted normally, you can simply launch _MUX_2D.cmd. It builds a (big) 2D MKV with the h264 stream demuxed from the BD, without re-encoding. I'm pretty sure that will work fine.

Try also to untick the 64bit option in the last tab of BD3D2MK3D. That will remove avs2yuv.exe from the x264 command, and maybe that will be sufficient.

If that doesn't work, try also to copy the libmfxsw32.dll from the toolset directory to a directory in your PATH (such as C:\Windows\SYSWOW64).

I see also this: But the encoding step would produce MKVs which have a black/blank video part in the end.
What do you mean exactly with "in the end"? Do you mean that the movie itself is encoded correctly, but there is an additional black part after it? If it's the case, could it be because you have used the option "Add N seconds of black at the end of the video" in tab 4?

[CaBleman]

Thank you again r0lZ for all the hints!

First of all, with "in the end" I meant "after all, when the process is finished". Not the "add black" option...

Here are the outcomes of your suggested changes / trials:

- The 2D Mux worked fine, indeed. But this only proves that the .264 video part had been demuxed correctly, right? What about the .mvc part? How could I check this one?

- I removed the 64bit option for x264 usage; the resulting removal of avs2yuv.exe from the command line exposed another error message:
---
"x:\xxx\xxx\BD3D2MK3D\toolset\x264.exe" --crf 20 --preset slow --tune film --profile high --level 4.1 --keyint 96 --no-fast-pskip --b-adapt 2 --ref 4 --frame-packing 3 --qpfile chapters_3D.qpfile --output "xxx.264" "_ENCODE_3D_MOVIE.avs"
avs [info]: 1920x1080p 0:0 @ 24000/1001 fps (cfr)

Return on error: error code -1, pipeline_decode.cpp 799

Return on error: error code 1, sample_decode.cpp 66

x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZ
CNT BMI2
---

- Copying libmfxsw32.dll into a folder in the system path did not make a difference, unfortunately.

What now? What else could I test?

Thx & bye,

CaBleman

[r0lZ]

Yes, the 2D mux proves only that the demux of the AVC stream worked fine. But I guess that the MVC stream is fine also. I don't think that it is possible to test the MVC stream without decoding it, and it's exactly that that doesn't work.

Last suggestion: try to re-download the latest version of BD3D2MK3D. Perhaps one of your files is corrupt. But I don't think that will help.

Unfortunately, I don't know what else should be tested now. According to the two error messages, it's probably something wrong with the Intel decoder (libmfxsw32.dll), but I don't know what. I have sent two PMs to knowledgeable peoples, in the hope that they will be able to help. I hope so!

[CaBleman]

r0lZ,

I found the "culprit" causing the hiccup on my system.
At least with DGMVCSource it was the hw=0 option in the function call within the AVS script:
interleaved = DGMVCSource("xxx.track_xxx.264", "xxx.track_xxx.mvc", view = 0, frames = 198357, hw = 0)
The value 0 means "auto" and on my system it chooses hardware acceleration. So if I leave that on 0 or put it to 2, the following happens:
When the enconding starts, 3-5 seconds go by before something actually happens.
It then starts with the usual approx. 14fps and then accelerates quickly up to 90fps (wow, would be good to have for real;).
All this with the result of the black video.

It is only when I put it to 1 and enforce pure software based decoding, that the frame serving works the way it should...

You may very well be right that this is caused by the Intel 3D (decoder?) lib, since I operate a Haswell Refesh processor (Core I5 4590S), which is quite new. May be caused by other libs/components as well...

Hopefully this is a helpful clue to you or your knowledgable people; maybe "we" have to find a newer version of that lib?
If you or someone else needs any more info on my system, let me know...

Anyway, would it be asked too much to have an option (tickboxes or dropdown) in the last tab for this parameter?
Otherwise people with machines like mine have to wait for the demuxing and then amend the AVS script to run the transcoding... please think about it ;)

Thanks again for taking care and providing BD3D2MK3D!

Bye,

CaBleman

[r0lZ]

Hey, great news. Thanks for letting us know.
Sure, I'll add an option to control that flag. I have assumed that setting it to "auto" should work in all cases, but assumptions are always dangerous!

[r0lZ]

Levels and profiles changes

I have learned recently many things about the x264 encoding, and I have modified BD3D2MK3D accordingly. The x264 options are therefore much more simple than in the old versions of BD3D2MK3D. The Profile field has been removed, because usually the High profile is selected automatically (except when encoding with the ultrafast preset, where Baseline is used). If you really want to select another profile, you should type "--profile X" in the additional options field, but that should never be necessary.

Similarly, in the previous versions, it was possible to select any level, but due to the HD picture size (1080p), only levels 4.0 and up are useful. Usually, it is recommended to set the level to "do not force", so that x264 can select the level automatically, according to the preset you have selected. However, when encoding with a slow preset, you will probably end up with level 4.1 or 4.2. If that levels are too high for your target hardware, you may need to force level 4.0 or 4.1. (Personally, I recommend level 4.1, because it's the highest level compatible with most hardware players.) Note also that if you encode in Full-SBS or Full-T&B, levels 5.0 or more are mandatory. Since it doesn't make much sense to force a level higher than 5.0 (because you will mainly only limit the compatibility with more hardware players), BD3D2MK3D has implemented the levels 4.0 to 5.0 only. Again, if you want to force a level greater than 5.0, you can do it manually in the additional options field, but the casual user should never need to do that.

Note that forcing a specific level requires also to add the --vbv-bufsize and --vbv-maxrate options, to force x264 to use a buffer size and a maximum bitrate compatible with the specified level. BD3D2MK3D adds these options automatically when a level is forced, and it assumes that profile High (or baseline for the Ultrafast preset) are used. BD3D2MK3D doesn't specify them when the level is not forced. (These options, and some other options, are also used if you tick the "BD compatible" option.) So, if you want to use your own profile or specify a level with a different buffer size or bitrate, you must select "do not force", and enter the requires options manually in the additional options field.

That may seem complicated, but in fact it's much simpler than before. When you encode in Half-SBS or Half-T&B, you should select force level 4.0 or 4.1 to be sure to be compatible with most hardware players. For a slightly better compression but a less good compatibility, you should select "do not force" or level 4.2. When you encode in Full-SBS or Full-T&B, you should select level 5.0 for the best compatibility (but your file will be incompatible with most hardware players anyway), or "do not force" to let x264 decide. You cannot use level 4.*, and if a 4.* level is selected, a warning will be displayed, and you will have to fix the problem.

Note also that the level and profile settings that may have been saved with previous versions of BD3D2MK3D are lost. Don't forget to verify the new Level setting if you want to force a specific level.

Hardware acceleration of the MVC decoder

There is a big bug in the Intel MVC decoder, reported in the few posts above by CaBleman. It appears that the decoder crashes (or produces only black frames) when you have some recent models of the Intel processors, that support theoretically the hardware acceleration. It might therefore be necessary to force the decoder to turn off the hardware acceleration. For that reason, I have added the Settings -> MVC Decoder -> Hardware Acceleration menu. If previous versions of BD3D2MK3D worked fine for you, you should leave that option to its default value "Auto". If you experience crashes, you should try to set it to Disabled. (It should never be necessary to use the Enabled option.) Thanks CaBleman for the bug report, your finding and your tests!

New Tool to convert external subtitles to 3D

With Tools -> Convert Subtitles to 3D (with 3D-Plane), it is possible to convert a subtitle stream from another source to 3D and use the right depth values extracted from the 3D-plane. However, that was not always sufficient to produce the correct subtitles, because often a 3D subtitle must be placed at a precise position in the scene, where there is nothing in the foreground, so that it doesn't enter in objects or characters in the foreground of the scene. Unfortunately, usually the external subtitle file has not been designed with that locations, and the subtitle may therefore enter in objects, It's why I have added a new tool: "Clone Subtitles positions from another file". With that tool, you can use one of the subtitle file extracted from the original 3DBD as a "guide" to place the subtitles of your external stream approximately at the right positions. (It is not always possible to place correctly all subtitles of a specific stream, but the result is usually much better after having used that tool.)

So, in summary, to generate correct 3D subtitles from, say, a SRT file downloaded from the internet, you should do this:

Use BD3D2MK3D to generate a project AND tick at least one subtitle stream in tab 2 (or select a stream to hardcode in tab 4). That stream will serve as the "guide" and will be replaced with your own subtitles later.
Convert the external subtitle to IDX/SUB format. (I recommend to use SubtitleEdit (http://www.nikse.dk/SubtitleEdit/)'s Export to BDN xml/png).
Use the new "Clone Subtitles positions from another file" tool to move the subtitles of the new XML/PNG stream to their correct position extracted from the "guide" XML file that has been created automatically by BD3D2MK3D during the preparation of the project.
Use Convert Subtitles to 3D (with 3D-Plane) to convert the new XML to 3D using the 3D-plane that is associated with the "guide" stream, and output to BD SUP or VobSub format.
Edit the _MUX_2D_OPTIONS.txt file to replace the guide file with your new SUP or IDX file. (If you want to hardcode the file, you must edit _ENCODE_3D_MOVIE.avs.)


Other changes

I have also fixed the bug reported by CRFOnly, with the 2D subtitle streams not generated. I have modified a large part of my code, and I hope I haven't introduced new bugs.

There are also some other minor changes.

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


# v0.52 (October 23, 2014)
# - Modified the x264 encoding options: Profile has been removed.
# - Level is now used also to limit the bitrate peaks and the decoding buffer size and is now minimum 4.0, as it should for 1080p.
# - Added a help button next to the "Level" field to explain why it may be useful to use that option.
# - Added the Settings -> MVC Decoder -> Hardware Acceleration menu to force the decoder to use the hardware or software acceleration.
# - New Tool "Clone Subtitles positions from another file", useful to add another subtitle file to the final MKV.
# - Fix: The forced 2D subtitle SUP stream was not included in the mux. Thanks CRFOnly!
# - Minor cosmetic changes.

[frank]

After building the project BD3D2MK3D 0.52 ends with an error message:
can't read "subsfilename": no such variable
while executing
"file extension $subsfilename"
(procedure "GenerateAvs" line 1814)
invoked from within
"GenerateAvs"
invoked from within
".nbf5.gf.gen invoke "
invoked from within
".nbf5.gf.gen instate {pressed !disabled} { .nbf5.gf.gen state !pressed; .nbf5.gf.gen invoke } "
(command bound to event)

Console:
*** Saving "_ENCODE.cmd"
x264 command:
"C:\Users\Chef\BD3D2MK3D\toolset\avs2yuv.exe" ^
"_ENCODE_3D_MOVIE.avs" -frames 178660 -o - ^
| "C:\Users\Chef\BD3D2MK3D\toolset\x264_x64.exe" ^
--crf 18 --preset medium ^
--bluray-compat --profile high --level 4.1 --open-gop --keyint 24 --slices 4 ^
--colormatrix bt709 --colorprim bt709 --transfer bt709 --b-pyramid strict ^
--vbv-bufsize 30000 --vbv-maxrate 40000 --aud ^
--frame-packing 4 --qpfile chapters_3D.qpfile ^
--output "00799_mpls.264" --frames 178660 --demuxer y4m --stdin y4m -

*** Saving "tags.xml"

*** Saving "_MUX_3D.cmd"

*** Saving "_MUX_3D_OPTIONS.txt"

*** Saving "_MUX_2D.cmd" and "_MUX_2D_OPTIONS.txt"
*** can't read "subsfilename": no such variable
() 1 %

___________
frank
System: Win 7 x64

[r0lZ]

Damn! It's a stupid bug. I think it happens only when there are several subtitle streams to decode and the option to mux the 2D files is ticked in tab 2. Anyway, I have fixed the bug. Or at least I think so. I haven't enough time to test it. Please do it.
Thanks for the bug report!

# v0.53 (October 23, 2014)
# - Last minute bug fix: Problem when adding the 2D subtitle streams to the _MUX_*D_OPTIONS.txt files

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

[frank]

There were several subs, and I ticked the forced captions only option. Encoding to Half T&B, nothing with 2D.

I will test again.

[frank]

Successfully done with v0.53!! :)
:thanks:

[r0lZ]

OK, thanks for the confirmation. :-)

[Bryce2]

Hi! r0lZ
I have a query about x264 encoder options and how these are incorporated inside "BD3D2MK3D's Options & Go!" panel, and with that in mind, I would like to make a suggestion. My query is why you don't implement a option like "MeGUI - Encoder settings - Config" panel or something similar so the user could apply his own custom settings with ease and with more control on x264 options, without the necessity to wright by hand all the additional parameters someone wants to experiment with?
(Sorry for my terrible English - not my native language as you can imagine)

PS.
With encoding options like :
Mode: CRF (10)
Preset: slower
Additional options: --keyint 240 --min-keyint 24 --merange 64
my memory is up to 94%-96% in use. Any idea why this happens?
My PC:
AMD FX-8350 Vishera (8 Core - core speed 4026.3 MHz)
16GB DDR3

Thanks for the time you spend to make our life easier!

[r0lZ]

Well, I believe that my program must be accessible to everybody. I don't want to make it too difficult to understand and use. There is already a lot of options, some not obvious for a beginner. Also, x264 has excellent presets and tune options, that should be sufficient for most users. Adding all settings in a GUI is theoretically possible, but that will only be much confusing for most users. And take in mind that BD3D2MK3D sets some options automatically for you (such as --frame-packing, or the --vbv-* options if you select a specific level). It is difficult to have to disable that options in the GUI if the user selects a level, and enable them otherwise. And I don't want to encourage peoples to tick one or two options without knowing exactly what is their usage, just to check if the result will be good. Usually, that kind of experiment leads to bad images, slow encodes or bad compression. In short, I have opted for a GUI as simple as possible, but with the possibility for advanced users to specify additional options manually, if they know what they are doing.

Anyway, if you want to use the same set of options every time you use BD3D2MK3D, you can just type them once, and then use Settings -> Save Settings Now to save them permanently. (Just be sure to disable the Save Settings On Exit option, as otherwise your default options will be overwritten if you change them for a specific movie.) All options are saved, including everything that you can select via the GUI and the content of the "Additional options" field, but of course nothing directly related to the current movie, such as its title and tags. IIRC, only the global Shutdown Computer option is not saved (because it is too dangerous).

Honestly, I don't know why x264 may need almost 16GB of memory with your settings. It may be caused by the --merange parameter, but I'm not sure. I'm not at all a specialist of the x264 encoder. I can only tell you that I have only 4GB of mem, and x264 has never needed more than approximately 2GB to encode my movies (without --merange 64). You should ask your question in a forum about x264.

Don't worry for your "terrible" English. It is perfectly understandable, and anyway, English is not my native language either.

[Bryce2]

Thanks my friend for the quick reply. I perfectly understand what you mean, but I just thought that it would be easier for some of us to have more options for x264 to play with! Anyway ..thanks again for such a nice program. it makes a-lot easier to re-encode a original 3D bluray disc than before (manual way).
Can I ask for a "IMDB-id" & "TMDB-id" field and a "Genres" field in the "Title & tags" panel. I think it is important for a movie tag. (my opinion).
I have also a last question for the "Title & tags" panel. How do you put 2 different locations. I tried it for the movie "Upside Down" and it didn't work. the movie was made in Canada & France ..so I put FR, CA and it gave me an error.
PS.
Can we have a crop option in the "Options and Go" panel?
Thanks a-million!!!!!

[r0lZ]

BD3D2MK3D uses only some of the official Matroska tags (http://matroska.org/technical/specs/tagging/index.html) and, as far as I know, there is nothing to specify IMDB or TMDB IDs. You may want to use the COMMENT field to store them. There is a GENRE tag in the official Matroska list, but afaik it is used only for music (in MKA files). For the location, BD3D2MK3D uses the COMPOSITION_LOCATION official tag, and unfortunately, it is impossible to define two locations at the same time.
I can perhaps add one or two new tags, but they have to be official. Consult the list and make concrete suggestions if you wish...

For the crop, it's NO! Certainly not! Never! It is an extremely bad idea to crop a 3D movie. A 3D movie MUST be encoded with the 16:9 aspect ratio. Dot.
Most (if not all) 3D TVs require the 16:9 ar, and when the black bars have been cropped, they display the movie stretched vertically, or, in some case, they give up completely. It's already a very good reason to avoid cropping the 3D movies.

I know that some devices, and most software players can display non-16:9 3D movies correctly, but they add black borders in real time anyway, and since the black borders are very easy to encode, the gain in file size when cropping them is minimal, and negligible in regard to the numerous drawbacks. Don't forget that it's not because you watch your movies currently with a player that supports the cropped borders that you will never buy a TV or another device that requires full 16:9.

Furthermore, it is impossible to display correctly the 3D subtitles on a movie that has been cropped, because in addition to the depths of the subtitles, their exact positions on screen are very important too. Since the SubRip and BD SUP subtitle formats are made for a specific video format (in our case, 1080p full 16:9), the positions of the subtitles along the Y axis is lost if you have cropped the black borders, and the 3D effect of the subtitles is ruined. (Unfortunately, many software players reposition the subtitles in the bottom center of the screen anyway, and it's mainly because they have to adapt them to cropped movie. I hope that the authors of the 3D players will understand that it is important to display the 3D subtitles as they are, without modification. But first, we need to stop cropping our 3D movies.)

[Bryce2]

Mainly I asked if it was possible from you to add a extra field for "IMDB-id" & "Genres" in the "Title and Tags" panel taking as a paradigm the mkv tagger utility MatroskaTagger (http://forum.team-mediaportal.com/threads/mkvtagger-edit-tags-mkv-tags-incl-mp-tvseries-thetvdb-com-themoviedb-musicvideos.116870/) from Team MediaPortal (http://www.team-mediaportal.com/) as they have already added these fields in their program, thus avoiding me from using two different apps to properly (as to my opinion) tag a MKV movie file.

(Sorry for bringing you a headache with all my questions & requirements)

Maybe I ask too much or perhaps I'm wrong ..or maybe I will consult the list and make concrete suggestions in the near future...
(If you haven't kill me before I do this!!!) .Xa! Xa! Xi! Xi!
:thanks:

[Bryce2]

As for the IMDB-id & Genres tag fields, they are already implemented inside MKVTagger (MatroskaTagger) (http://forum.team-mediaportal.com/threads/mkvtagger-edit-tags-mkv-tags-incl-mp-tvseries-thetvdb-com-themoviedb-musicvideos.116870)"" from "Team MediaPortal", and that's the reason that I asked for this addition in the Title and tags panel, thus avoiding me from using 2 different tools for the same job.
(sorry for giving you a headache with so many questions and requests)

[mini-moose]

I'm doing a 3d encode for a friend with the latest version. He wanted it 2-pass for whatever reason. I've set the video bitrate to around 9k and I got the next warning:

Video bitrate is too high for h264 level 4.1. It has been forced to 56250 kbps. The final file size may be smaller than expected.


that's 6 times what I set it to initially...

I've edited the encode batch file so that's not an issue. But is it some bug or maybe I did something wrong? I didn't encounter that in previous versions.

[r0lZ]

Yes, it's something I have added to the latest version. If you force a specific level (such as 4.1 in your example), the maximum bitrate allowed for that level is now specified automatically in the command line (with the --vbv-maxrate argument). For level 4.1 (and profile high, the default), the maximum bitrate is 62500 kbps. Since the average bitrate specified by the user must be smaller than the maximum, BD3D2MK3D verifies if it is correct, and if it's not the case, it changes it to an acceptable value (90% of the maximum bitrate).

But if you have specified 9k, (I guess you mean 9000 kbps, right?) then your bitrate is largely below the limit, and BD3D2MK3D should not have displayed that warning. Obviously, there is something wrong. I will have a look. Thanks for the bug report.

[mini-moose]

Yes, it's something I have added to the latest version...
But if you have specified 9k, (I guess you mean 9000 kbps, right?) then your bitrate is largely below the limit, and BD3D2MK3D should not have displayed that warning. Obviously, there is something wrong...

Yes, 9000 kbps.
thanks.

[r0lZ]

Confirmed. There was a terrible bug in 2-pass and ABR modes. Sorry. It is fixed in v0.54. Thanks again.

# v0.54 (October 28, 2014)
# - Bug in 2-pass and ABR modes: the bitrate was forced to the maximum.
# - Minor cosmetic changes

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

[mini-moose]

Confirmed. There was a terrible bug in 2-pass and ABR modes. Sorry. It is fixed in v0.54. Thanks again.


Great. Thanks r0lZ.

[frank]

Hi r0lZ!
I welcome your opinion to the settings of BD3D2MK3D. Keep it on! Beginners forget often IT IS 3D for TV!!!

I prefer the BD compliant settings. It worked on ALL devices properly in excellent quality.
(I also hate cropping, keyint=250...) As hardware specialist I only can say: TV chipsets and acceleration are developed for standard sizes: 1080 / 720... And HDMI is based on standards.

[frank]

Currently ALL Intel SDK based MVC 3D decoders have a serious issue, they show blockiness in some movies.
(The Avengers after 12 sec, Pacific Rim...)
After a lot of tests: Here my results.
BD3D2MK3D can decode it properly using DirectShowMVCSource(), based on CoreAVC (used in Stereoscopic Player).
So DirectShowMVCSource() is NOT obsolete. We need it for that cases until Intel has corrected the bugs.
The only disadvantage: you have to mount the BD/ISO.
_______
Howto
The old BD3D2MK3D v0.23 includes a folder named \toolset\stereoplayer.exe\ with all necessary files.

1. Download BD3D2MK3D v0.23 (link on the first page of this thread) and paste the \stereoplayer.exe folder into \toolset of the current BD3D2MK3D installation.

Required content of \stereoplayer.exe\
avs2yuv.exe (copy of toolset)
x264.exe (copy of toolset)
DirectShowMVCSource.dll
CoreAVCDecoder.dll
MPEGSplitter.dll

2. Update CoreAVC DLLs
Download and install latest Stereoscopic Player and replace CoreAVCDecoder.dll and MPEGSplitter.dll in \stereoplayer.exe with the newer versions. You cannot use newer stf.dll for SBS and TAB anymore (crash). But it is not necessary with the scripts of BD3D2MK3D.

3. Start BD3D2MK3D and generate scripts and files.

4. Edit _ENCODE.cmd
set path=...\BD3D2MK3D\toolset\stereoplayer.exe;...\BD3D2MK3D\toolset;%path%
Remove the absolute path from avs2yuv.exe or x264.exe. Then the start goes from \stereoplayer.exe.

5. Edit _ENCODE_3D_MOVIE.avs

LoadPlugin("...\BD3D2MK3D0\toolset\stereoplayer.exe\DirectShowMVCSource.dll")

# Load main video without newer stf.dll otherwise CRASH!!!
# E = drive letter of BD/ISO, framecount = number of frames
# Example: Pacific Rim
left = DirectShowMVCSource("E:\BDMV\STREAM\SSIF\00098.ssif", seek=false, seekzero=true, framecount=188857, decodeleft=true)
right = DirectShowMVCSource("E:\BDMV\STREAM\SSIF\00098.ssif", seek=false, seekzero=true, framecount=188857)

# For Half SBS
StackHorizontal(HorizontalReduceBy2(left), HorizontalReduceBy2(right))

6. Mount the BD to get access to ssif
The demuxed streams .x264 and .mvc cannot be used because DirectShowMVCSource() cannot read it.

7. Start x264 encoding with _ENCODE.cmd
DirectShowMVCSource() works properly but the speed is slow - about 9-14 fps (no HW acceleration).
_______

So I ask to add again the the stereoplayer.exe folder with DirectShowMVCSource.dll. Users can download Stereoscopic Player themselves for dll updates.
On the other hand you can remove the support for FRIM, based on the same Intel DLLs. DGMVCSource() worked more stable on my systems.

r0lZ, what do you think?

[r0lZ]

I have noticed the bugs in the latest versions of the Intel DLL, and it's why I have not included that versions with BD3D2MK3D. But afaik, the libmfxsw32.dll distributed with BD3D2MK3D (libmfxsw32.dll v5.14.4.28, released april 28, 2014) works fine with all movies. At least, I have never had any problem. There is one well known exception though: Pacific Rim has one or two little glitches, I don't think it's the same bug than the one you describe.

I don't think I'll add the support for DirectShowMVCSource, because it works in a very different way than the current filters based on the Intel lib. I don't want to have to handle two very different methods in the same program. Anyway, if you really want to encode with DirectShowMVCSource, you can use the old BD3D2MK3D v0.23. And if you want to use the current BD3D2MK3D, just be sure to NOT update the intel lib with the bugged version. If, for any version, you are forced to update it, for example because it is updated automatically when you install the Intel drivers, you should switch to software mode in BD3D2MK3D. (It's why I have added the Settings -> MVC Decoder -> Hardware Acceleration option in the latest versions of BD3D2MK3D.) In SW mode, the program should use the library provided with the package, and not the one installed elsewhere with the Intel drivers.

Also, I don't want to remove the FRIMSource decoder. It is also based on the Intel lib, that's right, and therefore it has the same problems than DGMVCSource, but it is very easy to use the version you prefer. By default, it's DGMVCSource, but you can change it if you wish. (For me, supporting the two Source filters is very easy, because they work almost identically, and I have just to modify the LoadPlugin and Source commands in the AVS script.)

Of course, I may change my mind if someone can demonstrate that the current methods fail anyway, even when libmfxsw32.dll v5.14.4.28 is used.

[frank]

Maybe it's hardware dependent. I use I7 Core-i with Sandy and Ivy Bridge, no Haswell.
I have tested all updates of Intel DLLs until April 2014 - but no luck, the glitches in the movies remained there. With software decoding too. :mad:

Intel drivers of the Media SDK are not stable when transcoding to MVC 3D (FRIM). I had crashes and crashes again, often had to reboot to free memory. Then I gave up.
AFAIK professional software such as rovi TotalCode doesn't use the Media SDK and works well.

We are left with only the use of x264 -> BD3D2MK3D.
So I will test again, especially with libmfxsw32.dll v5.14.4.28.

[jdobbs]

Are you still having the same issue with software encoding and decoding? I've never had an issue with FRIM when using software for both.

[r0lZ]

I have tested all updates of Intel DLLs until April 2014 - but no luck, the glitches in the movies remained there. With software decoding too. :mad:
Can you describe the glitches you have noticed? In Pacific Rim, there are a few bad frames in the whole movie when using libmfxsw32.dll v5.14.4.28. Maybe there is a similar problem with The Avengers. I don't know, because I have not encoded that BD yet.

In the other hand, the problem I have noticed with most recent versions of libmfxsw32.dll is totally different. With many (or perhaps all) movies, the MVC stream cannot be properly decoded at all. All frames (except a few black frames at the beginning of the movie) are bad. And it's not small glitches near the borders, but the whole picture that is totally bad. I think we can live with the "Pacific Rim problem", because it occurs in very rare occasions, but of course, the new decoders cannot be used at all.

I don't have a suitable hardware, so I can't test the hardware library, but I know that recent versions have problems too. After a discussion via PM with an user, it seems that switching to software mode and using v5.14.4.28 is sufficient to solve them.

Of course, I still hope that Intel will fix the bugs rapidly...

[frank]

The pictures show the damaged location at 1:06:16 in Pacific Rim, reencoded to hTAB.
Intel software decoding (libmfxsw32.dll from BD3D2MK3D 0.54).
Hardware: Asus Notebook Intel Core I7-3517U (Ivy bridge)
OS: Windows 7 x64

http://thumbnails110.imagebam.com/36261/4216a4362609187.jpg (http://www.imagebam.com/image/4216a4362609187) Frame 95327

24 frames lost

http://thumbnails109.imagebam.com/36261/9507d3362609189.jpg (http://www.imagebam.com/image/9507d3362609189) Frame 95352
http://thumbnails109.imagebam.com/36261/a32ace362609192.jpg (http://www.imagebam.com/image/a32ace362609192) Frame 95353
...

http://thumbnails111.imagebam.com/36261/71456b362609207.jpg (http://www.imagebam.com/image/71456b362609207) Frame 95356, last damaged

The frame numbers are from reference. There are 24 lost frames (GOP) in the reencoded stream! After that point the sound is not in sync.
Sorry r0lZ, that's no glitch, that's a heavy bug in my eyes.

Very annoying is that the MVC decoder doesn't allow any seek to a location (Virtualdub) for testing. So you have to read/encode until the bad location. Very time consuming.

@jdobbs
Yes, same errors. The decoder is the culprit.
Sure, you have other hardware. I use a notebook.

[r0lZ]

I know that there is a problem with Pacific Rim, but afaik, it's the ONLY BD that BD3D2MK3D cannot decode properly. And during my tests, I have not noticed any audio sync problem, but I may be wrong. Anyway, I don't want to revert to the old method just for one BD (because that will require a big rewrite of the program, DirectShowMVCSource has also its pitfalls, it is much more difficult to maintain for me, and much slower for the peoples lucky enough to have the Intel hardware decoder).

BTW, I have just finished to encode The Avengers (with libmfxsw32.dll v5.14.4.28). I haven't had enough time and courage to watch it completely (I hate that stupid super-hero films!) but there is obviously no decoding problem around 0:00:12 or in the first half of the film. That confirms that libmfxsw32.dll v5.14.4.28 works usually well. The exception of Pacific Rim is strange, and difficult to understand, but that single exception is not sufficient to motive me to rewrite BD3D2MK3D completely. Sorry.

[mini-moose]

Maybe this was brought up before so apologies in advance...

Can the tool handle merging multi discs? For example extended versions of The Hobbit 3D are spread on 2-discs.
I'd rather have them as one long video and not two separate
vids. I assume I can append with mkvmerge but I'd rather just encode those as one if there's such a possibility.

thanks

[r0lZ]

No, sorry, BD3D2MK3D cannot do that. As you have suggested, Mkvmerge's append mode is the solution. Just be sure to use exactly the same encoding parameters when you encode the two parts.

[CaBleman]

'lo there,

I'd like to ask you, r0lZ, to add an option for how to append the file name postfix, e.g. as options "space", "underline" or "dash". People have different systems to name their files and some of the postprocessing tools / media DBs etc. do not support or stumble over spaces in file names (I know that it should not be that way). I use underline "_" in all my filenames and is it is a bit annoying that I have to rename them after the final muxing with BD3D2MK3D (sometimes I forget that, too). If I'm not mistaken, your program used an underscore before - you have probably changed it in between? It if not too much effort, please think about about reverting that or putting in an option - highly appreciated!

Another thing that I have observed is a significant black gap between the two sides for one movie (Cloudy... 2), impacting the auto-regocnition of Sony TV for 3D content. After manually setting the TV to 3D it works fine, but has anybody else encountered such a gap?

Cheers,

CaBleman