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

[kevbo]

I have version 1.19. Upon startup, it can't detect Java and throws a warning/error message.

I have Java 1.8 and 11 installed. However, I don't use the Oracle JDK, I use AdoptOpenJDK, due to Oracle's new licensing restrictions.

If I bring up a command prompt and type "java", I get Java (so java.exe is in the path). I also have a JAVA_HOME environment variable set.

I'm wondering how the program actually tries to find Java. I can think of two things that have gone wrong. One, the java that comes up is Java 11. Maybe you only want 8? Or two, you're looking for something specifically Oracle that I don't have, because I have a different Java package.

Adding: AdoptOpenJDK can do 4 things when installing. It can add Java to the system PATH, it can associate itself with .jar files, it can set JAVA_HOME, and it can set values in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft

Each of these 4 things is optional in the installer, but I have all 4 things enabled here. AdoptOpenJDK doesn't install in the Oracle location in Program Files: if you are specifically looking for Java there, it isn't there. But there are 4 other things that can looked for to try to find Java (well, at least 3, not sure the .jar association is all that helpful). At the very least, I'd think that looking for java.exe in the path and/or looking for JAVA_HOME should work. Or maybe allow the location of the JRE to be a configured option?

There are quite a few packagings of Java these days, and the new Oracle licensing makes that particular one quite sub-optimal. (I say knowing full well that Java's usage on the desktop is really minimal these days anyways.)

I'd like to help figure this out: I develop with Java so I'm familiar with how it installs/integrates.

Thanks,

Kevin

[r0lZ]

Thanks foir your detailed description of the problem. I don't know AdoptOpenJDK, but I will try it and investigate the problem. Can you confirm that it is fully compatible with the programs developed for the Oracle version ? Also, I suppose that the version most users have currently is OpenJDK 11 HotSpot. Correct ?

The way BD3D2MK3D detects java is somewhat complex, because Oracke has a strange installation method. Therefore, BD3D2MK3D uses several different methods, one after each other :

1. First, it tries to use the java path stored in the BD3D2MK3D configuration file. It's only when the path has changed due to a new installation that the whole procedure is started over.
2. It tries to execute the command "where java" in the command prompt. That command is supposed to return the path of java.exe if it is in the PATH environment variable and afaik it has always worked (except of course if java.exe is not in the %PATH%).
3. Then, it builds its own list of directories where the programs are usually installed. It uses the environment variables ProgramFiles and ProgramFiles(x86) (if they exist) to discover the paths of those folders. It appends "Java" to those directories, and then it checks in all sub-directories if java.exe exists. Therefore, it should be able to discover for example "C:\Program Files (x86)\Java\jre1.8.0_271\bin\java.exe".
4. Finally, it gives up and tries to use just "java.exe", without path.
5. The final test, always executed, consists in trying to execute the command "path/to/java.exe -version". In the output of that command, it searches for "java version", and assumes that the version is just after that words, on the same line.
6. If the version string has not been found and is therefore empty, it issues the warning telling that java is not properly installed. However, it returns the path anyway.

I guess that it's the last step that doesn't work, as "where java" should work, even if java is not installed in the usual Program Files directory.

Note that the function that checks for java can return the path or the version string. Normally, BD3D2MK3D doesn't check the version, as it assumes that any version should be OK. It uses the version string only to display it when the menu Help -> Java Version is called, as well as in the log when the Java version of BDSup2Sub is executed, for example to convert the subtitles to 3D.

I will try to locate the problem. In the meantime, try to edit the file BD3D2MK3D.cfg. Locate the line beginning with set ::config(javapath), and insert the path to your version of java.exe. The directory separator character must be linux-like (/), or two backslashes (\\), and the whole string must be enclosed between accolades, like this:

set ::config(javapath)         {C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath\\java.exe}

Please let me know if that trick works. Unfortunately, it may trigger an error when the version is printed, but I'm not sure.

Anyway, that bug will be fixed in the next version. Thanks again for your report.

[r0lZ]

OK, the fix I just did seems to work. Indeed, the problem was related to the string with the version. For the Oracle Java, the line begins with "java version" and for AdoptOpenJDK, it begins with "openjdk version". I have modified the code to check only if the word " version " is present, and now, the Oracle and OpenJDK releases are correctly recognised and accepted.

I have also modified the error message and the link to download Java to direct the user to the AdoptOpenJDK site rather than to Oracle.

Originally Posted by kevbo

There are quite a few packagings of Java these days

Can you tell me if some of them are well established, and where to find them ? I will try them also, to verify if all good avatars of Java are compatible and accepted by BD3D2MK3D.

Thanks in advance.

[kevbo]

Great that you were able to fix it by looking at the string! I hadn't thought of that.

OpenJDK releases should all be compatible. They're all built from the same source code (even Oracle's these days, although apparently Oracle changes some strings). Oracle's releases aren't supported for long, and have really strange licensing terms that are so silly that I've honestly not bothered figuring them out. I just get the JDK from somewhere else.

I know of a few of them:

• AdoptOpenJDK https://adoptopenjdk.net/
• Amazon Coretto https://aws.amazon.com/corretto/
• Azul Zulu https://www.azul.com/downloads/zulu-...it&package=jdk

There are a few more on the Wikipedia page: https://en.wikipedia.org/wiki/OpenJDK#OpenJDK_builds

[r0lZ]

OK, thanks. Not sure I will check all variants, especially if I can be almost sure that the word "version" is present in the output of the java -version command. Also, I think I will change the code again to replace the version string with "undefined", or something like that, when it cannot be found, so that a release that doesn't follow the standard will be accepted anyway (at the risk of the user).
I will probably release a new version of BD3D2MK3D soon...

[kevbo]

Cool. I suspect "openjdk version" is going to be pretty standard on all of the rebuild projects.

Just for kicks, I checked on Linux, which uses a JDK build by Red Hat. It says "openjdk version".

Thanks again for being so responsive!

Kevin

[r0lZ]

BD3D2MK3D v1.20 is available. It fixes a few bugs, supports now most (all?) releases of java, and has been compiled with the latest freeWrap version (so its look may have slightly changed).

But most importantly, the version of tsMuxeR distributed with BD3D2MK3D has changed. It is now a relatively old build of the new open source version, with several important bugs fixed, but also some important changes in the meta file format. For that reason, BD3D2MK3D is not compatible any more with the old (closed source) versions of tsMuxeR. You may try to update tsMuxeR to the latest beta of the open source version, but do it at your own risk, as it is still heavily modified, and you may encounter incompatibilities or new bugs. The version distributed with BD3D2MK3D, although a nightly release, is recommended, as it has been successfully tested by me and several beta testers.

Also important, if you use the Custom Encoder command line instead of the built-in x264 or x265 encoders : the syntax has slightly changed, especially for the paths of the exe to call. So, after having installed this version, please try a custom encoding of a small clip to verify that your custom command works fine. Sorry for the inconvenience.

Note: Avisynth+ v3.5.1 has been released and it works perfectly with BD3D2MK3D: https://github.com/AviSynth/AviSynth...ses/tag/v3.5.1 (You may need to install the vcredist variant if vcredist is not yet installed.)

v1.20 (November 3, 2020)
- Compiled and wrapped with freewrap 6.73, using Tcl/Tk 8.6.10.
- Adapted to the new Open Source version of tsMuxeR. Most (all?) demux bugs have been fixed, and it is no longer necessary to demux the angles with many M2TS with eac3to.
- IMPORTANT: The syntax of the custom command has slightly changed. Now, the backslach character \ in Windows paths MUST be typed twice, to avoid escaping problems.
- Workaround for a BDSup2Sub++ bug when loading some full-width subtitles: the X position is -2147483648 instead of 0!
- Fix: Java was not detected correctly when the installed version was not Oracle Java. It is now possible and recommended to install the open source AdoptOpenJDK instead of Oracle Java.
- Fix: Preview and Do It! buttons were disabled when the BD shows no 3D-playlist after opening it, but some playlists become available when the "Show all 3D playlists" is selected.
- Tools -> TsMuxer GUI opens now automatically the currently selected MPLS (if any)
- In case of error when checking if Avisynth+ is properly installed, the error message suggests now to install the version with the vcredist package.
- Removed the Power Plans stuff when BD3D2MK3D doesn't run under Windows (so that it doesn't crash under Linux with Wine)
- Removed Tab 3 -> Web -> Search TCM for Title, because the TCM site is now unusable
- Updated the FrimSource MVC decoder to the latest version (v1.31)
- Updated x264 to the latest version (v0.161.3027)
- Updated x265 to the latest version (v3.5+26)
- Updated the MkvToolnix tools to the latest version (v51.0.0 'I Wish')

Download BD3D2MK3D or visit its home page.
Have fun !

[r0lZ]

BD3D2MK3D v1.21 has been released. It fixes a single bug in a tool that has no impact on the conversion of a movie to 3D. It affects only some power users.

v1.21 (December 5, 2020)
- Fix: Clone Subtitles Positions did not clone the Y position if the X position was not changed. (Thx Ennio!)

Download : BD3D2MK3D.7z

[r0lZ]

BD3D2MK3D v1.22 is available.

It adds a new option available when you encode in Half-Top/Bottom to use the even and odd lines of the source material instead of merging them with a resize. If you have a LG passive 3D TV that can display the full 1080p resolution, you will benefit from this option, as there is no need to resize the image, and all details are retained. But please note that it is suitable only if your TV has the correct polarity: the even lines must correspond to the left eye and the odd lines to the right eye. In all other polarity configuration (such as "checkered") or if you have an active TV, this option is not recommended. (Thanks to Muf for suggesting this option.)

v1.22 (January 2, 2021)
- Added an option to use the even/odd lines for the left and right views to encode in Half-T&B mode for a LG 3DTV, while retaining the full 1080p resolution. (Thx Muf!)
- Updated x265 to the latest version (v3.4+35)

Download: BD3D2MK3D.7z

[TVI]

Hello. I wonder if somebody could help me with a problem please?

I’m doing everything I normally do but when I launch the encoder it starts without saying ‘press a key’, encodes in an hour (normally takes 4-5hrs) and isn’t saving to my MKV folder (small black screen stays on screen).

Help! Thanks.

[TVI]

...here is the error I’m getting.

Thanks!

[r0lZ]

It seems that the Intel Media library is the culprit. If you have an Intel CPU, try to update the Intel drivers.
If that doesn't work, use the software MVC decoder: Settings -> MVC Decoder -> Hardware Acceleration -> Disabled.
Good luck !

[videoh]

Wouldn't be the first time Intel breaks backward compatibility. That's why DGDecIM met its demise.

[TVI]

Originally Posted by r0lZ

It seems that the Intel Media library is the culprit. If you have an Intel CPU, try to update the Intel drivers.
If that doesn't work, use the software MVC decoder: Settings -> MVC Decoder -> Hardware Acceleration -> Disabled.
Good luck !

Hi,

I disabled the Hardware Acceleration as you suggested and it worked.

Thank you for your help which is much appreciated!

[sfatula]

I've seen messages saying this should run under wine. I get through the demux portion, and, when it runs the 3d launcher and is in encode_3d.cmd, instead of a window where it shows progress of encoding, it shows, well, garbage. Anyone here have any tips for running under wine to clear that part up? It's helpful to see remaining runtime like it does under Windows. If it's even working. See image

EDIT; I did find that if I remove the ^ in the __ENCODE_3D.cmd file, that' the garbage goes away and it seems to run. Was true on ubuntu standard apt package, and, WINHEHQ-DEVEL also. 32 or 64 bit.

[r0lZ]

Originally Posted by sfatula

EDIT; I did find that if I remove the ^ in the __ENCODE_3D.cmd file, that' the garbage goes away and it seems to run.

Thanks for the information. The ^ at the very end of a line under the Windows command prompt is the line continuation character. Theoretically, if you remove it and you don't replace it with a Linux equivalent, the encoding command will be considered as several different commands, and produce as many errors. I guess that you have concatenated the lines together, to form a single long command. Correct ?

If it's the only thing to change to use BD3D2MK3D under Linux with Wine, I may add an option in the Settings menu to be compatible with Wine. However, it seems that it's a Wine bug, that should be fixed, as this breaks the compatibility with some Windows batch files. Perhaps you should report it to the Wine authors...