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

[sheppaul]

to add the possibility to globally move all subtitles a bit more toward the spectator or behind the screen?
Yeah, there was already such a feature for normal 2d text subtitles. But, it did not work for subtitles having 3d depths. Now, it's possible.

It would be indeed a nice addition to PotPlayer if he could support the 3D depth from external or muxed OFS files. At least, it will be possible to play SBS or T&B files with SRT subtitles and the (more or less) correct depth.

That's exactly what I thought. However, there is one more thing which should be implemented before telling him about the OFS implementation. Potplayer can convert and display normal text subtitles to 3d subtitles having fixed depth but adjustable on the fly.

It works well with 3d mvc media (blu-ray iso/folder, mkv having 3d mvc streams) but re-encoded 3d videos having half resolutions do not work with a default subtitle renderer (overlay type). It should be changed to image type (mixing subtitles to video streams). It is also supported in the player but it is very inconvenient as it requires manual switching and the quality of subtitle rendering is not very good if you have large screens. I think providing the same subtitle rendering with half 3d videos should be done in advance.

Potplayer's developer said it's very complicated and he'd not like messing up the existing codes as it is actually working pretty well. So I'm stuck with the precedent feature which I think is absolutely necessary. As for OFS files, is it possible to mux it in mkv container?

[sheppaul]

Talking about subtitles, as regards pic based subtitles they are kind of too big for my use and I've always wondered if the players can reduce their size. Do you know if any players provide control over the size of the sup or idx/sub format subtitles? I haven't been able to find ... :confused:

Potplayer can do it. It's one of the features I made a feature request ago and fortunately it was implemented. It's somewhere in preferences. :p By the way, I'm not sure how it'll work for displaying 3d subtitles as my purpose for feature request was to reduce the size of 2d subtitles.

[r0lZ]

As for OFS files, is it possible to mux it in mkv container?As far as I know, no. It is certainly possible to add the 3D offsets in SEI messages within the AVC video stream (exactly like they are added to the MVC stream in a 3D BD), but that would require a specific muxer or a tool that can add the SEI messages after the original creation of the h264 or h265 stream, or to modify x264 and x265 to include the possibility to add them directly, when the video is encoded. That seems difficult. But it is already possible to include any file as attachment in the final MKV. Since an OFS file is made of approximately as many bytes as there are frames in the movie, it's a small file that can be loaded entirely in memory when the MKV is opened. But if the offset sequences are not muxed with the video stream, the difficulty will be to stay synchronized when the user seeks somewhere in the movie. The player must know the exact frame number it is playing to pick the right 3D depth, and many DirectShow codecs are not frame accurate. Also, an independent OFS file (included or not in the MKV container) is not suitable for video streaming.

Also, for movies with several different subtitle streams, it will be necessary to imagine a method to link each subtitle stream to its corresponding OFS file. It is easy to imagine a way to do it, for example with a little file describing that, or simply with the order of the subtitle streams matching the order of the OFS files, but there is currently no standard for that. I'm not sure the programmer of a specific player will accept to implement his own method, if it is not widely accepted.

So, I don't know if there are fatal difficulties in implementing the 3D offset sequences for SBS or T&B movies, but IMO it's possible, as long as they are associated with a video format and that can be decoded accurately and a good container. IMO, that should be the case of h264/h265 within a MKV container, but I'm not sure. (It is for sure not possible to do that with an AVI and old codecs like DivX. But who still uses AVI with that obsolete codec for a modern 3D movie?)

[sheppaul]

there is currently no standard for that. I'm not sure the programmer of a specific player will accept to implement his own method, if it is not widely accepted.

So, I don't know if there are fatal difficulties in implementing the 3D offset sequences for SBS or T&B movies, but IMO it's possible, as long as they are associated with a video format and that can be decoded accurately and a good container.
Yeah, you got the point. He does not really like non-standard methods. That's probably the main reason he'd not likely to support it.

[konikpolny]

Thanks sheppaul for the info about PotPlayer being able to change size of the graphic subtitles. Indeed, it can reduce picture subs and it works fine for 2D. The feature is called "Scale image caption" and can be set under the main Subtitles tab in the Preferences.

[albesp77]

dear all, i've converted 2 movie with this toos, using default parameters, one of this halfsbs movie is perfect, the other one seems to have some disturb on some scenes on background, front detail are perfect, there are some possible parameters to try to change to delete this problem ? seems like that in background i see video without using glasses, like a double image, but the front in same frame is perfect!

[r0lZ]

seems like that in background i see video without using glasses, like a double image, but the front in same frame is perfect!
I'm not sure I understand the problem.

Of course, if you watch the movie with the TV playing it in 3D but without the 3D glasses, you MUST see two slightly different images. You see the image for the left eye + the image for the right eye with your two eyes, and of course that's not how you are supposed to watch a 3D movie.

The objects that appear (with the glasses) approximately at the surface of the screen may give the impression that there is only one image, but when the distance from the screen to the background (or foreground) objects increases, the two images are more distant, and the effect of a double image becomes visible. (The effect is somewhat similar to what you can see when you are severely drunk.) It's caused by the parallax, and it's not only normal, but necessary. You can see exactly the same "double image" effect if you watch the 3D movie in a theater without the glasses.

If what you see when you use the 3D glasses is correct and appears in 3D, that means that everything is normal, and works as expected. You should NEVER watch a 3D movie without the glasses, as that doesn't make sense. (Some TVs have an option to watch the 3D movie in 2D, but in that case, they show you only a single view, and of course the "double image" effect disappears.)

[albesp77]

I'm not sure I understand the problem.

Of course, if you watch the movie with the TV playing it in 3D but without the 3D glasses, you MUST see two slightly different images. You see the image for the left eye + the image for the right eye with your two eyes, and of course that's not how you are supposed to watch a 3D movie.

The objects that appear (with the glasses) approximately at the surface of the screen may give the impression that there is only one image, but when the distance from the screen to the background (or foreground) objects increases, the two images are more distant, and the effect of a double image becomes visible. (The effect is somewhat similar to what you can see when you are severely drunk.) It's caused by the parallax, and it's not only normal, but necessary. You can see exactly the same "double image" effect if you watch the 3D movie in a theater without the glasses.

If what you see when you use the 3D glasses is correct and appears in 3D, that means that everything is normal, and works as expected. You should NEVER watch a 3D movie without the glasses, as that doesn't make sense. (Some TVs have an option to watch the 3D movie in 2D, but in that case, they show you only a single view, and of course the "double image" effect disappears.)

ok ok, i'll try to explain better my problem, i have 2 movie coded in half-sbs, i watch both movie on my tv with my glasses, one of the two movies views good, in all beautiful 3d scene, i see right the 3d depth in all scenes. Now i want to explain better the problem on other movie, i see on tv with glasses, i see the 3d depth also on this movie, but different from the another one i see on this on background like a 3d double image effect, like i see on tv without glasses, but the strange is that i see only on background this problem, the 3d depth of image is right!

[r0lZ]

i see on this on background like a 3d double image effect, like i see on tv without glasses, but the strange is that i see only on background this problem, the 3d depth of image is right!
Well, in very contrasted images (like when you see a man with black suit in a snowy landscape), the image of the left eye may be seen partially with the right eye, and vice-versa. That unpleasant effect is due to the somewhat bad quality of the 3D equipment, and can be more or less visible. It is called "ghosting". It's not really a problem of the movie, and the 3D encoding made by BD3D2MK3D is not bad. The ghosting effect is only visible because the 3D glasses are unable to filter the two views at 100%. I guess it's what you have experienced.

Of course, a bad 3D source (like most 3D BDs produced in Germany) can also be the culprit. Anyway, in both cases, the problem is also visible when you play the original 3D BD, and is not due to BD3D2MK3D.

What is the movie that causes that problem ? And can you post a SBS image extracted from that movie (preferably one where the problem is really noticeable) on an image sharing site so that I can analyse it ?

[albesp77]

Well, in very contrasted images (like when you see a man with black suits in a snowy landscape), the image of the left eye may be seen partially with the right eye, and vice-versa. That unpleasant effect is due to the somewhat bad quality of the 3D equipment, and can be more or less visible. It is called "ghosting". It's not really a problem of the movie, and the 3D encoding made by BD3D2MK3D is not bad. The ghosting effect is only visible because the 3D glasses are unable to filter the two views at 100%. I guess it's what you have experienced.

Of course, a bad 3D source (like most 3D BDs produced in Germany) can also be the culprit. Anyway, in both cases, the problem is also visible when you play the original 3D BD, and is not due to BD3D2MK3D.

What is the movie that causes that problem ?

good to know! saw 7 3d italian edition

[r0lZ]

I have not Saw 7, so I can't tell if it's a movie with highly contrasted scenes.

You have replied when I was editing my previous reply, so you have probably net seen my last request:

Can you post a SBS image extracted from that movie (preferably one where the problem is really noticeable) on an image sharing site so that I can analyse it ?

[albesp77]

I have not Saw 7, so I can't tell if it's a movie with highly contrasted scenes.

You have replied when I was editing my previous reply, so you have probably net seen my last request:

Can you post a SBS image extracted from that movie (preferably one where the problem is really noticeable) on an image sharing site so that I can analyse it ?

sure, but i really don't know how to take the right frame to analyze in scene with problem, can you help me ?

[r0lZ]

No, just select an image from a scene where the problem is really visible.

(P.S.: Please do NOT quote the entire post when you reply to the last post. It's useless and against the Doom9 rules.)

[albesp77]

ok i'll try to double check scene in those days and take the frame! thanks in advance!

[madipav]

After a convertion of a 3D movie to a 3D MKV SBS file, with BD3D2MK3D, this software don’t recognize the 3D MKV SBS file created.
It's seems there isn’t a SSIF folder or any Information inside the 3D MKV file to be reconized.

Howhever it's a 3D MKV file.

So it becomes impossible, with this software, reasize a 3D MKV file created by the software itself.

The software say's “Its seems that the file is not a MKV file created by MakeMKV or it is not in 3D format”

Please I need help how to make BD3D2MK3D recognized a 3D MKV file

https://postimg.org/image/nndv989x7/ ?

https://s17.postimg.org/5kksi0e2n/Error_reading_a_3_D_MKV_file.png

[r0lZ]

After a convertion of a 3D movie to a 3D MKV SBS file, ...
If you have already a 3D SBS file, why would you need to use BD3D2MK3D to create another 3D SBS MKV file ? That doesn't make sense.

BD3D2MK3D can convert a 3D DB or a 3D MKV with AVC + MVC video streams to 3D SBS MKV. That means that the source material (BD or MKV) must contain the two video streams. The main video stream must be encoded in AVC (aka h264) and the second video stream must be encoded in MVC, exactly like in a 3D BD. You can create a 3D MKV from a 3D BD with MakeMKV. It extracts simply the two video streams (and of course one or more audio and/or subtitle streams) from the BD and includes them in a MKV container. No streams are re-encoded during that operation, and therefore the MKV contains exactly the same video streams than the original 3D BD. That MKV can be converted to SBS, T&B or Frame Sequential by BD3D2MK3D. But if the source MKV contains only a single video stream (encoded in AVC or any other codec), BD3D2MK3D can't convert it, because it is either a monoscopic video or it is a 3D movie that has already been converted to SBS, T&B or FS format, and of course you cannot convert it a second time. (You can however re-encode it if for example you want to reduce its file size or resize the image, but you can do that with any good MVC or HEVC encoder, and it's not the job of BD3D2MK3D.)

The BD3D2MK3D dialog posted above explains how you can convert the original BD3D to the AVC+MVC MKV with MakeMKV. If you do that correctly, the MKV will be accepted by BD3D2MK3D.

[EDIT] I have modified the dialog above to remove the warnings about the old versions of MakeMKV (because the old versions cannot be used any more and I assume that the Left/Right view bug has been fixed) and I have added a short explanation about the necessity to use an AVC+MVC MKV as input, and not a 3D SBS, T&B or FS MKV.

[kevbo]

Hello...I love this program. I use it to convert my 3D Blu Rays to files that can be watched on an Android device using a 3D viewer.

As such, I'm trying to make the files small. I'm using 720p SBS, which is great. The problem is the AAC quality.

I found the option to set the AAC quality parameter. However, you use -down6. I'd rather use -downDpl (or even -downStereo), because, in this case, there will never been any need for more than two channels.

I jumped into the work directory and re-encoded the audio before calling __ENCODE_3D_LAUNCHER.cmd, but it would be nice if I could choose an option inside of BD3D2MK3D instead.

Thanks!

Kevin

[r0lZ]

That seems to be a good addition. I'll do it. It's easy. That option exists already when you use Tools -> Convert audio, but it is not available when building a project.

BTW, is it straightforward to play a SBS movie on an android phone ? Is it sufficient to use a VR adapter ? Or do you need a specific app ?

[kevbo]

Well thank you!

I actually am using an older Android device (a Nexus 5). My son likes to watch movies on it. The older 3D adapter is called "Google Cardboard" (although you can get "Cardboard" adapters that are made of plastic and padding). You do have to use a movie player app. We use AAA VR Cinema, and we've also used VR Player, both of which are available free (with ads in the UI) or you can pay for them to remove the ads.

I think that, even if you were using a newer "Daydream" 3D device, you'd have to use a movie player. Something needs to feed the movie through the VR engine and do the image separation, warping, and general UI.

Thanks again!

[r0lZ]

I did think that a Full-SBS video can be viewed with a simple carton box with 2 lenses, using a technique similar to this (http://www.vanishederas.com/ekmps/shops/vanishederas/images/zz-antique-wooden-treen-stereoscope-stereoscopic-viewer-with-large-collection-of-stereoviews-c.1900-sold-[3]-7723-p.jpg) but of course with a phone instead of the stereographic photo, and a somewhat more modern look. ;-)

Of course, a video player is necessary, but since the image is already in SBS, there should be no need for an additional 3D processing, and any good player should do the job. Right?

Anyway, I'll check AAA VR Cinema and VR Player, and perhaps I'll buy a VR adapter, if there is one compatible with my Huawei P8 2017. If that works well, I guess that the immersive effect will be much better than with a 3D TV.

Thanks for the thanks. I have already added the 5.1/stereo/ProLogic option in tab 2. I still need to do some other little tweaks, and I'll release a new version of BD3D2MK3D, probably very soon...

[kevbo]

There are actually lenses in the Google Cardboard things. I don't entirely understand why: I think they spread the image out to fill out more of your field of vision.

The video player "pre-distorts" the image. It doesn't just display the video as encoded, it splits it into two images and kind of "rounds" each one out, so it ends up in the middle of the lens on the Cardboard, which spreads it back out again.

It actually looks nice. It was more complicated than I thought it would be. :) Things "just work" though after being encoded by BD3DMK3D: the video players detect everything automatically.

Thanks!

[r0lZ]

There are actually lenses in the Google Cardboard things. I don't entirely understand why: I think they spread the image out to fill out more of your field of vision.The lenses are necessary because the screen (your phone) is very close to your eyes, and they cannot focus on the image at such a short distance without a correction.
The video player "pre-distorts" the image. It doesn't just display the video as encoded, it splits it into two images and kind of "rounds" each one out, so it ends up in the middle of the lens on the Cardboard, which spreads it back out again.
I see. But does that means that you see a relatively small image in the center of the view, like with a TV in a room? If it's the case, that reduces greatly the interest of the technique.
It actually looks nice. It was more complicated than I thought it would be. :) Things "just work" though after being encoded by BD3DMK3D: the video players detect everything automatically.
Indeed, BD3D2MK3D adds the 3D information in all possible locations (the frame-packing in the AVC stream, the stereoscopy in the MKV container, and a 3D string in the file name). A good player should therefore switch to the right 3D mode automatically.

I have had a look at the VR players on the Play Store. There is a lot of apps. Not sure what is the best. Can you conform that AAA VR Cinema and VR Player can decode the 3D videos encoded in HEVC with x265 ? IMO, to reduce the disc space without loosing much quality, it is preferable to encode with that very efficient codec than with x264, but many players are still unable to decode h265 correctly.

[r0lZ]

And here is the version that adds the possibility to convert the audio to stereo or ProLogic, to regain more disc space. It includes also the new version of SRTtoASS3D with some minor fixes).

v1.3 (November 23, 2017)
- Added the possibility to convert the audio streams to Dolby ProLogic II or to Stereo (in addition to AC3 and AAC).
- Subtitle Tools -> Convert SRT to ASS 3D (SRTtoASS3D.tcl) updated to v0.5, with some improvements and a possible bug fixed (see here (https://forum.doom9.org/showthread.php?p=1823942#post1823942))
- The warnings about Full SBS/T&B, x265, 10 or 12-bit color depth etc... are not displayed any more when the program starts.
- Changed the download link for x264 and x265 to VideoHelp.
- Updated the mkvtoolnix exes to the latest version (v18.0.0)
- Restored x265 to the latest stable version (v2.5+5)

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

[Woody3D]

BD3D2MK3D is a GUI to convert movies from 3D BDs to 3D MKV video files in Full or Half Side by Side, Top & Bottom or Frame sequential format, encoded in h264 with x264 (or in h265 with x265). Since v0.87, BD3D2MK3D can also accept lossless 3D AVC+MVC files created with MakeMKV as input.

I have written it mainly because it was difficult to do all operations necessary to do the conversion manually, and because the documentation about the method to use was poor and spread over a lot of posts in this long and technical thread: Guide to convert BD 3D to 3D Left+Right Stereoscopic and Anaglyph (http://forum.doom9.org/showthread.php?p=1663794).

My first attempt resulted in BD3D2AVS (http://forum.doom9.org/showthread.php?p=1575870#post1575870), and was based on eac3to (http://forum.doom9.org/showthread.php?t=125966), ldecod and ssifsource. Ldecod was used to decode the dependent view of the stereoscopic input streams. It works well, but it is terribly slow, and is was therefore not a good solution. Luckily, the external tools have evolved, and I wrote a second version of the GUI, called BD3D2MK3D (http://forum.doom9.org/showthread.php?p=1663794#post1663794). The original BD3D2MK3D was mainly based on ssifSource and DirectShowMVCSource, but is now also obsolete.

Starting with v0.30, BD3D2MK3D is based on new tools, much more efficient, like the tsMuxeR update for 3D blu-ray (http://forum.doom9.org/showthread.php?t=168539) and the Intel MVC decoder (https://software.intel.com/en-us/articles/intel-media-software-development-kit-intel-media-sdk) to decode the dependent view, with the help of the avisynth plugin DGMVCSource (http://forum.doom9.org/showthread.php?t=170107&highlight=DGMVCSource) by Donald Graft or FRIMSource (forum.doom9.org/showthread.php?t=169651) by videofan3d. The GUI uses also a lot of other tools. See the Help menu for a list of the most important tools.

As you can see in the original thread, the development of the method and the tools necessary to do the conversion was a collective effort. I wish to thank all contributors.

Currently, BD3D2MK3D is mature enough to have its own thread, and it's why I have created this thread. Please post all questions and bug reports related to BD3D2MK3D here, and all questions about the external tools that my GUI uses in their respective threads or in the original guide thread (http://forum.doom9.org/showthread.php?p=1663794). Thanks!

Features of BD3D2MK3D:

Convert any 3D playlist from a properly decoded blu-ray 3D to a standalone Half-side by side or Half-top & bottom (aka Over/Under) 3D MKV file.
Can also accept as input a 3D-MKV file created with MakeMKV (with the option to include the 3D MVC stream).
Can optionally convert to Full-SBS, Full-T&B or Full-Frame Sequential 3D.
Can resize the output to 720p
Can output a 3D stream compatible with 3D-Ready DLP projectors (720p Frame Sequential at 59.94fps).
Can convert the subtitle streams to 3D, using the depth stored in the original BD for each individual subtitles. (The subtitles can also be kept in 2D if you wish.)
Can hardcode (or "burn") a subtitle stream (all or forced captions only) over the video with the right depth for each individual subtitles.
The subtitles can be muxed in the original BD SUP format for an excellent quality or in VobSub (IDX/SUB) format for a better compatibility.
It is even possible, with some manual work and the help of the Tools menu of BD3D2MK3D, to use a subtitle stream coming from another source (such as a SRT downloaded from the internet or a SUP stream from the 2D BD of the same movie) and convert it to 3D with (approximately) the right depth values to mux it within the final MKV or hardcode it to the video. See the mini guide here (http://forum.doom9.org/showthread.php?p=1742601#post1742601).
Can extract the regular 5.1 DTS or AC3 cores of the DTS-HD, DTS-HD-MA, E-AC3 and TrueHD audio streams.
Can convert the audio tracks to AC3 or AAC for a better compatibility or a smaller file size.
The chapter points are automatically preserved in the final MKV file.
Can include tags about the movie (movie title, director, producer, actors, summary, comments, etc...)
Can add some seconds of black at the beginning or end of the video so that the user has some time to configure his 3D TV and to turn his active 3D glasses on before the beginning of the movie.
The encoding to h264 is made with x264 (32 or 64-bit) for an excellent image quality, and the user can select the most important encoding settings, such as the encoding mode (CQ, CRF, ABR or 2-pass), the preset, tune, profile and level. It can also specify manually additional options if he wish.
The correct 3D video mode is automatically defined in the h264 video stream (the "frame-packing"), in the header of the MKV video file (the stereoscopy mode), and optionally in the file name, so that most TVs and 3D players can switch automatically to the right 3D mode when the file is played.
The final MKV file is automatically muxed at the end of the encoding, and there is an option to shutdown the computer when everything is finished.
BD3D2MK3D has also some independent tools, notably powerful tools to convert an external subtitle stream to 3D, using the 3D depth values extracted from the original 3DBD, and optionally the subtitle positions cloned from another subtitle file.
And much more...

Download:

The latest version of BD3D2MK3D can always be downloaded here: BD3D2MK3D.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z)
The obsolete BD3D2AVS based on ldecod can still be downloaded here: BD3D2AVS.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2AVS.7z)

Please note that BD3D2AVS and BD3D2MK3D v0.23 are obsolete. They are still available if you want to try the old conversion methods, but they are no longer developed, and they do not contain all features and bug fixes of the latest BD3D2MK3D. Use them at your own risk!

Installation:

Pre-required and recommended programs:

BD3D2MK3D requires Windows Vista or greater to work properly. Windows XP is not supported (due to incompatibilities in the Intel MVC decoder).
Avisynth v2.5 (http://sourceforge.net/projects/avisynth2/) must be properly installed on your computer. (It's a complex program, but you don't need to use it directly. Just install it.)
To convert the subtitles to 3D or to IDX/SUB format, it is highly recommended to install Java (https://www.java.com/en/download/manual.jsp) (32 or 64-bit). (It is possible to use BDSup2Sub++ instead of the Java version of BDSup2Sub, but it has several important bugs and it is not developed any more. It is therefore not recommended.)
It is also recommended to install a good video player that can play BD's M2TS and MPLS files and that let you select any audio or subtitle stream. The player is used only for the preview. The free players PotPlayer (http://potplayer.daum.net/) or MPC-HC (http://mpc-hc.org/) do the job well, but there are many other good players. Just avoid the Windows Media Player, that doesn't work well at all.
Since BD3D2MK3D doesn't decrypt the commercial 3DBDs, you need a way to decrypt them. That can be a good BD decrypter (http://www.videohelp.com/software/sections/decrypters-bd-hd-dvd) that can create an ISO on hard disc, such as DVDFab HD Decrypter or Ideal Blu-Ray Copy. You can also use AnyDVD HD (https://www.redfox.bz/anydvdhd.html), that decrypts the original BD on the fly. It is also possible to decrypt only the title you want and convert it to lossless 3D-MKV with MakeMKV (http://www.makemkv.com/), preferably v1.9.11 or greater. (MakeMKV is free while in beta if you use the key provided here (http://www.makemkv.com/forum2/viewtopic.php?f=5&t=1053).)

To install BD3D2MK3D, simply extract the content of the 7Z archive to a directory of your choice. BD3D2MK3D saves its settings in its installation directory, and doesn't use the Windows registry. It is therefore highly recommended to install it in a folder where you have full access rights. Do not install it in Program Files or in Program Files (x86). (If you cannot open the 7Z archive, you need a good archiver program such as 7Zip (http://www.7-zip.org/).)
If you wish, you can create a shortcut to BD3D2MK3D.exe in your Start menu (or Start Screen under Windows 8). Or you can simply open the installation folder in Explorer, and double-click BD3D2MK3D.exe to launch the program.


I got it working again, I forgot to install support programs! :)

THANK YOU!! Love it!

[r0lZ]

Thanks, and welcome to the Doom9 forums.
But it was not necessary to quote the whole first post.

[Wildfire]

Recently installed v1.3 and today I tried encoding... but it fails, on two separate computers, right after generating the project finishes:


missing operand at _@_
in expression "round(+ _@_* 1000)"
missing operand at _@_
in expression "round(+ _@_* 1000)"
(parsing expression "round(+ * 1000)")
invoked from within
"expr round($audiodelays($audiouid) * 1000)"
(procedure "GetMKVAudioDelays" line 48)
invoked from within
"GetMKVAudioDelays $mplsfile"
(procedure "GenerateAvs" line 1346)
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)


I'm trying to encode a 3D MKV created with MakeMKV, something I've done dozens of times before without any issues.

Support tools are installed. 32- or 64-bits AVS2YUV doesn't make any difference...

Audio track is DTS by the way, which I left untouched (no conversion to AC3 or AAC).

[r0lZ]

Hum, that's strange, as I have not modified that part of the code. Perhaps it's because MakeMKV has changed. Or it's because the new version of MkvInfo doesn't return exactly the same information than previously. I will have a look...

[r0lZ]

Indeed, it's a change in MkvInfo that caused the bug. (That bug doesn't affect the creation of a project from a BD; it happens only when a project is created from an AVC+MVC MKV.) I have modified the code so that it is now able to use indifferently the new or old versions of MkvInfo, and I hope that the output of MkvInfo will not be modified again without notice !

v1.4 (November 25, 2017)
- Fix: Crash when creating a project from a MKV (due to changes in the output of MkvInfo v18.0)

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

[Wildfire]

Indeed, it's a change in MkvInfo that caused the bug. (That bug doesn't affect the creation of a project from a BD; it happens only when a project is created from an AVC+MVC MKV.) I have modified the code so that it is now able to use indifferently the new or old versions of MkvInfo, and I hope that the output of MkvInfo will not be modified again without notice !

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

Thanks! I didn't expect it to be fixed this soon :)

I'll have a look and see if it works now.

-- Edit: yup, after creating the project encoding starts as it should. Yay! :)

[frank]

Latest eac3to version is now v3.34 and supports more new formats.
v3.34
* fixed: "min/maxPlayListRuntime" worked for listing, but not processing

v3.33
* fixed a couple of HEVC bitstream bugs
* added new parameter "-minPlayListRuntime=0:15:00"
* added new parameter "-maxPlayListRuntime=4:00:00"
* added support for ".264" and ".265" file extensions

v3.32
* added support for UHD Blu-Ray playlists and clip infos
* added support for h265/HEVC bitstream parsing
* added support for m2ts h265/HEVC splitting
* added support for MKV h265/HEVC splitting
* added support for h265/HEVC framerate modifications
* added detection for Dolby Vision Enhancement Layer Maybe worth an update.

[r0lZ]

OK, I'll update it for the next release, although it is normally used only to convert audio streams well supported with v3.31.
Anyway, thanks for the info.

[kevbo]

Sorry for my delay in responding...the US Thanksgiving weekend got the best of me and I forgot.

I see. But does that means that you see a relatively small image in the center of the view, like with a TV in a room? If it's the case, that reduces greatly the interest of the technique.

No, it isn't all that small. The lenses in the headset "grow" the image. Shop around on Amazon: some of the newer headsets actually talk about having like 110-120 degree FOV.

I have had a look at the VR players on the Play Store. There is a lot of apps. Not sure what is the best. Can you conform that AAA VR Cinema and VR Player can decode the 3D videos encoded in HEVC with x265 ?

I'm pretty sure that those players just use the built-in media framework of your device to play the video, and just wrap it in 3D GPU Shaders to shape the image. As such, decoding x.265 would depend entirely on the version of Android you have, and your hardware support. I wouldn't attempt x.265 in software, and I'm using an old Nexus 5 that doesn't support it in hardware, so I've honestly not tried x.265. If you know your hardware can play an x.265 video normally, it should be OK in the 3D players.

[r0lZ]

OK, good information. Thanks again.

Have you already tested the new option to downmix the audio streams to ProLogic or stereo ? I did some tests myself, but rapidly, and only with a few short clips. In particular, I'm not sure the downmix is correctly made when the source is already in AC3 or THD.

[sjwoo]

I am getting the following error message when BD3D2MK3d v 1.1 attempts to encode a 3D video, on my laptop.

"The type of file 'MKV3D_3d.264' could not be recognized"

My desktop does not give me this error.

Does anyone here know what I need to do to eliminate this error?

Thanks
Python_61

This reply is really old, but it's because I just started using BD3D2MK3D! I got this error, too. It's because I didn't have Avisynth installed.

[r0lZ]

This reply is really old ...Yeah, but thanks for the reply. I will try to add a check to ensure that Avisynth is correctly installed when BD3D2MK3D starts.

[Wildfire]

I've been experiencing x264 encoder crashes (the basic "has stopped working" error). Switching back to the previous x264 release fixes everything. Am I the only one with this problem?

[r0lZ]

I've just launched a new encoding to verify, and it has started without problem. I will report here if it crashes before the end of the encoding.
Can you confirm that it's v0.152.2851 (Komisar build) that crashes? Do you use the 64 or 32-bit version?

[Wildfire]

I've just launched a new encoding to verify, and it has started without problem. I will report here if it crashes before the end of the encoding.
Can you confirm that it's v0.152.2851 (Komisar build) that crashes? Do you use the 64 or 32-bit version?

Yes, that version, 64-bit but I also tried 32-bit.

Currently I'm on v0.150.2833.0 and the encodes that failed with v0.152.2851 work fine with this older version.

I'll try a new encode tonight with the current version of x264 and I'll check if I can dig up any errors in the Windows log files...

[r0lZ]

No problem here with v0.152.2851 64-bit.

Are you sure that your Avisynth is correctly installed ? It is possible that x264 crashes because Avisynth sends a bad frame or issues an error not correctly handled by x264. Also, I recommend to use only the "standard" Avisynth v2.60. Other versions can have many bugs or subtle differences gthat can be incompatible with BD3D2MK3D.

Another possible cause of crash is a bad BD, possibly with a read-error, or a BD not correctly decrypted. But of course, it the encoding crashes with several BDs, you can exclude this case.

[Wildfire]

No problem here with v0.152.2851 64-bit.

Are you sure that your Avisynth is correctly installed ? It is possible that x264 crashes because Avisynth sends a bad frame or issues an error not correctly handled by x264. Also, I recommend to use only the "standard" Avisynth v2.60. Other versions can have many bugs or subtle differences gthat can be incompatible with BD3D2MK3D.

Another possible cause of crash is a bad BD, possibly with a read-error, or a BD not correctly decrypted. But of course, it the encoding crashes with several BDs, you can exclude this case.

I started having problems with a recent BD3D2MK3D update, which included the new x264. I never had problems before.

The issue also persists on my 2nd PC so that's why I thought it might be a software issue, and after replacing the x264 executable with the previous release my suspicion was confirmed.

I'm using AviSynth 2.60 as found on https://sourceforge.net/projects/avisynth2/ - the standard release, as you call it.

I use MakeMKV to create 3D MKV's which then serve as input for BD3D2MK3D. Yes, it's the latest version (1.10.8).

I'm currently trying a few new encodes. The crashes occured on several movies but I forgot which ones exactly. :P

[r0lZ]

I see. Unfortunately, there is nothing I can do, except release a new version of BD3D2MK3D with the last good x264, or wait the next x264 version and hope that it will be fixed. Anyway, the problem doesn't come from my code, as nothing has changed in the x264 command and the way it is launched.

Perhaps you could try to contact the x264 devs ? I can't do it myself, as I don't have the problem. And I will be grateful if you can check the next stable release of x264 before I release it with BD3D2MK3D.

[Wildfire]

Hmmm.... tried a new encode and while I absolutely swear I had x264 crashes before, now avs2yuv.exe crashes...

From Windows log files (in Dutch, but the relevant parts will be understandable):


Naam van toepassing met fout: avs2yuv.exe, versie: 0.0.0.0, tijdstempel: 0x4228f465
Naam van module met fout: ntdll.dll, versie: 10.0.16299.64, tijdstempel: 0xac8afc81
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0003f500
Id van proces met fout: 0x2060
Starttijd van toepassing met fout: 0x01d37006d002b8e3
Pad naar toepassing met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\avs2yuv.exe
Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: e0af5b8c-0f0a-4cad-8098-85fd22ef646b
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:



Foutbucket 1460961521198399896, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: avs2yuv.exe
P2: 0.0.0.0
P3: 4228f465
P4: ntdll.dll
P5: 10.0.16299.64
P6: ac8afc81
P7: c0000005
P8: 0003f500
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A2B.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C7F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C8A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CCA.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_avs2yuv.exe_81c98f127b2e509fff6fa7907dd996155560da26_b83b6774_2f30597b

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: e0af5b8c-0f0a-4cad-8098-85fd22ef646b
Rapportstatus: 268435456
Opgedeelde bucket: 55069c1852968d10c44660c3558b8198

[r0lZ]

OK, that seems to confirm that there is something wrong with avisynth or the original BD (or 3D MKV).

If you use the 32-bit version of x264 (not x265), avs2yuv is not necessary and therefore not used. x264 loads the avisynth script directly. It might be a good idea to test that with the same source, as we will know if avs2yuv is the culprit.

Also, you can try to use another version of avs2yuv. There are 4 versions here (http://komisar.gin.by/tools/avs2yuv/). Of course, the 64-bit version is not suitable. The version distributed with BD3D2MK3D is 0.24, but its size is 52KB. All komisar builds have a different size, so try the 3 32-bit versions.

I note also that ntdll.dll is involved in the crash. Perhaps it is the real culprit. Could it be caused by a recent M$ update ? What version of Windows do you use ?

[Wildfire]

I'm on Windows 10 Pro 64-bit, fully up-to-date (Fall Creators Update including all updates up to today).

I managed to get a x264 crash. It crashes when starting the 2nd pass... and that's with the 32-bit x264.


Naam van toepassing met fout: x264_8bit_x86.exe, versie: 0.152.2851.0, tijdstempel: 0x59581c4e
Naam van module met fout: x264_8bit_x86.exe, versie: 0.152.2851.0, tijdstempel: 0x59581c4e
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0002199e
Id van proces met fout: 0x1278
Starttijd van toepassing met fout: 0x01d37012a63aefb1
Pad naar toepassing met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\x264_8bit_x86.exe
Pad naar module met fout: C:\Program Files (x86)\BD3D2MK3D\toolset\x264_8bit_x86.exe
Rapport-id: fd94f01d-190b-4506-b020-f73162ef25f7
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:


Foutbucket 1409739612789152407, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: x264_8bit_x86.exe
P2: 0.152.2851.0
P3: 59581c4e
P4: x264_8bit_x86.exe
P5: 0.152.2851.0
P6: 59581c4e
P7: c0000005
P8: 0002199e
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8597.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A3D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A88.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_x264_8bit_x86.ex_d7f63a3eaf768c27dd490e86c91523ad361c83_7283c821_12b59025

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: fd94f01d-190b-4506-b020-f73162ef25f7
Rapportstatus: 268435456
Opgedeelde bucket: 8f75c02b66029f43539066b56e181a97


(and, as stated before, the issue also occurs on another computer, so a software issue seems most likely)

[r0lZ]

Yes, it seems that it's x264 that has a bug, but if x264 crashes sometimes then avs2yuv or even ntdll.dll, it is not easy to know where the bug really is. Is your other machine also running Windows 10 ?

Usually, I encode in CRF, but to check if I can reproduce the problem, I have just finished a 2-pass encoding of a (very small) clip, and it has not crashed. I'm still using Win7 (64-bit) because Win10 is currently still very unstable, and I hate that OS. Maybe there is something specific in Win10 that is not compatible with x264 ? But I suppose that someone else using Win10 and having experienced similar problems would have replied to this thread. It's why I persist to think that there is something wrong with your machine(s). The question is what !

Also, may I know why you encode in 2-pass ? As I've already explained several times (for example here (https://forum.doom9.org/showthread.php?p=1803343#post1803343)), it is always a bad idea to use 2-pass, unless you need to control exactly the final file size (for example to burn the final MKV on a DVD). So, if it's when starting the second pass that x264 crashes, I strongly suggest to use CRF instead. You will obtain a slightly better quality for the same file size, and no crash any more! ;-)

But of course, it will be better to know why the crash occurs...

[Wildfire]

Yes, it seems that it's x264 that has a bug, but if x264 crashes sometimes then avs2yuv or even ntdll.dll, it is not easy to know where the bug really is. Is your other machine also running Windows 10 ?

Usually, I encode in CRF, but to check if I can reproduce the problem, I have just finished a 2-pass encoding of a (very small) clip, and it has not crashed. I'm still using Win7 (64-bit) because Win10 is currently still very unstable, and I hate that OS. Maybe there is something specific in Win10 that is not compatible with x264 ? But I suppose that someone else using Win10 and having experienced similar problems would have replied to this thread. It's why I persist to think that there is something wrong with your machine(s). The question is what !

Also, may I know why you encode in 2-pass ? As I've already explained several times (for example here (https://forum.doom9.org/showthread.php?p=1803343#post1803343)), it is always a bad idea to use 2-pass, unless you need to control exactly the final file size (for example to burn the final MKV on a DVD). So, if it's when starting the second pass that x264 crashes, I strongly suggest to use CRF instead. You will obtain a slightly better quality for the same file size, and no crash any more! ;-)

But of course, it will be better to know why the crash occurs...


Windows 10 unstable? Not in my experience, in fact it's the exact opposite: it's really stable. Both my computers (yes, both Windows 10) run really smooth, I have no problems at all other than some crashes with BD3D2MK3D. And those crashes started occuring recently on both systems (before that, I already did dozens of encodes on both machines without any problem at all), although I cannot pinpoint exactly when that was...

To be sure, recently I performed several hardware tests (storage, memory, CPU) and no problems popped up. Even under extreme stress my system runs fine and no CPU overheating or anything like that.

Why 2-pass? Well, you may explain CRF into the most obscure details if you want, but I still think that 2-pass encoding at best settings just "feels" better to me. Also, I really like having a predictable file size even though the encodes go to my NAS which has ample storage space.

[r0lZ]

I have not a great experience of Win10 (although I have a partition with Win10 on the Win7 PC but I don't use it often). But I follow the RSS feed of The Windows Club (www.thewindowsclub.com), and although they are real M$ enthusiasts, almost every day they reveal a new problem with Win10. In the other hand, Win7 is old, but without the garbage of the new Windows "universal" apps, and totally stable (although they have made a questionable update recently). Anyway, on my machine, I can't reproduce the x264 problem. I must agree that that doesn't mean that it is more stable because the problem might be caused by other things (the CPU for example), but in the absence of another explanation, I must accuse the OS.

According to the x264 authors themselves, 2-pass is slightly less good because specifying a bitrate constraints the encoding between rigid walls. CRF use exactly the same encoding algorithms, but without any constraint. It is therefore free to use the most appropriate bitrate during the whole movie. 2-pass is of course much better than 1-pass ABR because the first pass is used to evaluate approximately what bitrate to use for the different parts of the movie, but it cannot predict exactly the final bitrate. Hence the slight quality difference with CRF. Unfortunately, there are many web sites that suggest to use 2-pass for the best quality, but it's because they are not well informed or their suggestions apply only to encoders without CRF (like the old encoder of DVDFab that had only 1 or 2-pass). Anyway, I just wanted to suggest to use CRF to avoid the crash during the second pass. You are of course free to use 2-pass if you want.

[viperlogic]

Getting x264 crashes on both win7 (32-bit) and win10 (64-bit) immediately when running __encode_3D.cmd. Windows pop up window of "H.264 (MPEG-4 AVC) encoder has stopped working".

Win7....
Problem signature:
Problem Event Name: BEX
Application Name: x264_8bit_x86.exe
Application Version: 0.152.2851.0
Application Timestamp: 59581c4e
Fault Module Name: FRIMSource.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 596070dd
Exception Offset: 0002ca2c
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 6153
Additional Information 1: 2d06
Additional Information 2: 2d069ee6c3d46ad12eaf589f86850707
Additional Information 3: 633c
Additional Information 4: 633c17c95b8b015860e3dddcf1a1cd9a


win10...
Log Name: Application
Source: Application Error
Date: 15/12/2017 21:17:07
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ADMINRG-T59RE8R
Description:
Faulting application name: x264_8bit_x86.exe, version: 0.152.2851.0, time stamp: 0x59581c4e
Faulting module name: FRIMSource.dll, version: 0.0.0.0, time stamp: 0x596070dd
Exception code: 0xc0000409
Fault offset: 0x0002ca1a
Faulting process id: 0xeec
Faulting application start time: 0x01d375ea0f98f4a8
Faulting application path: C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\x264_8bit_x86.exe
Faulting module path: C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\FRIMSource.dll
Report Id: 3132e220-e0a2-4fc5-9cf2-256e90da8568
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-12-15T21:17:07.601977900Z" />
<EventRecordID>1714</EventRecordID>
<Channel>Application</Channel>
<Computer>ADMINRG-T59RE8R</Computer>
<Security />
</System>
<EventData>
<Data>x264_8bit_x86.exe</Data>
<Data>0.152.2851.0</Data>
<Data>59581c4e</Data>
<Data>FRIMSource.dll</Data>
<Data>0.0.0.0</Data>
<Data>596070dd</Data>
<Data>c0000409</Data>
<Data>0002ca1a</Data>
<Data>eec</Data>
<Data>01d375ea0f98f4a8</Data>
<Data>C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\x264_8bit_x86.exe</Data>
<Data>C:\Users\johndoe\Downloads\BD3D2MK3D\BD3D2MK3D\toolset\FRIMSource.dll</Data>
<Data>3132e220-e0a2-4fc5-9cf2-256e90da8568</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

This is against the Valerian and the City of a thousand planets 1080p 3D ISO by ESiR release group

Let me know what logs are required to further troubleshoot. Thx

[r0lZ]

It seems that you are experiencing the same problem that Wildfire has reported above (https://forum.doom9.org/showthread.php?p=1826483#post1826483). Can you try another version of x264 (older here (https://download.videolan.org/x264/binaries/), or another build here (http://komisar.gin.by/) or here (http://msystem.waw.pl/x265/)) ? Unfortunately, I can't reproduce the problem so I can't check myself.

Also, I note in your two logs "Fault Module Name: FRIMSource.dll", so the problem might be caused by FRIMSource as well. So, please try to set Settings -> MVC Decoder -> Use DGMVCSource and/or set the Hardware Acceleration to Disabled.

Thanks anyway for having reported the problem, and welcome to the Doom9 forum, viperlogic !

[viperlogic]

It seems that you are experiencing the same problem that Wildfire has reported above (https://forum.doom9.org/showthread.php?p=1826483#post1826483). Can you try another version of x264 (older here (https://download.videolan.org/x264/binaries/), or another build here (http://komisar.gin.by/) or here (http://msystem.waw.pl/x265/)) ? Unfortunately, I can't reproduce the problem so I can't check myself.

Also, I note in your two logs "Fault Module Name: FRIMSource.dll", so the problem might be caused by FRIMSource as well. So, please try to set Settings -> MVC Decoder -> Use DGMVCSource and/or set the Hardware Acceleration to Disabled.

Thanks anyway for having reported the problem, and welcome to the Doom9 forum, viperlogic !

Hardware Acceleration to Disabled did the trick!

What settings should be used for no drop in quality, eg the original ISO is 44G, the intermediate .264 is 24G, mvc is 12G and audio is 1.5G resulting in a finished mkv of only 5.3G