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

r0lZ

28th September 2019, 11:09

Damn ! Of course. It's due to the bug I have reported previously. When BD3D2MK3D checks your versions of AviSynth, it doesn't understand correctly that no 64-bit version is installed. Although it "thinks" that you have an unsupported 64-bit version installed, it tries to use it anyway, and it loads the 64-bit plugins. Therefore, I was wrong when I wrote that the bug should have no impact on the creation of the project.

I will release a new version as soon as possible...

Thanks for pointing this out, tebasuna51 !

r0lZ

29th September 2019, 09:25

• First of all sorry, the orginal error I got is:
(...)
avs [error]: failed to load avisynth
x264 [error]: could not open input file `__ENCODE_3D_MOVIE.avs'

Yes, sorry for that. As explained above, the problem is that BD3D2MK3D thinks that you have a 64-bit version of AviSynth installed on your computer (although it doesn't recognise AviSynth+ 64-bit). Therefore, it generates the AVS script fo 64-bit, and that produces the error you got.

I will immediately release a new version without that bug. In the meantime, if you want to encode your project without regenerating it with the new version, you can install AviSynth+ 64-bit (and optionally also 32-bit). Then, relaunch __ENVODE_3D_LAUNCHER.cmd, and everything should work fine.

Thanks anyway for the bug report. You have found an important bug !

r0lZ

29th September 2019, 09:29

And here is the fix.

v1.14 (September 29, 2019)
- Fixed the bug introduced in v1.12: The AVS script was generated for AviSynth 64-bit when no 64-bit version of AviSynth was installed.

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

bottom

29th September 2019, 11:40

Thank you for the Quick-Fix!!!

... and it was mainly my fault for posting the wrong error message:
Avisynth was found, but couldn't be started / loaded correctly.

Thus I sent you all in the wrong direction ... sorry, again!

marsdust

5th October 2019, 21:12

With AviSynth+ installed can't seem to encode with x265 with v1.14. Selecting from menu still shows x264 options in the GUI? The generated job is x264 regardless also.

r0lZ

5th October 2019, 23:50

Damn ! You're right ! I'll fix that tomorrow...

r0lZ

6th October 2019, 07:32

OK, here is the fix. As always, that was a stupid bug ! Thanks for pointing it out, marsdust, and welcome to the Doom9 forums.

v1.15 (October 6, 2019)
- Important bug introduced in v1.12 fixed: The option of the Settings -> AVC/HEVC Encoder to encode in HEVC with x265 did not change the encoder.
- Renamed the __CUSTOM_* files generated when the user has defined a custom encoding command to _CUSTOM_* (with only a single leading "_") so that they appear in the directory after the regular files to encode with x264 or x265.

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

marsdust

6th October 2019, 13:16

frank

6th October 2019, 15:30

r0lZ

7th October 2019, 08:54

That's fantastic. Just tested encoding x265 with Full SBS and working wonderfully. Though had to change the display width manually to 1920x1080 in MakeMKVToolNix but might be my TV not liking 3840x1080. Thanks again!
Thanks for your enthusiasm !

You can change the aspect ratio to "16:9 for both" in Settings -> Full-SBS/T&B aspect ratio", so you don't have to modify manually the display width (another way to specify the AR). Some TVs (for example LG) require that value.

r0lZ

7th October 2019, 09:04

And where you look your encodes? On PC only?
3D stereo is not certified for HEVC / x265.
Is there any TV or beamer that can show 3D SBS/TAB encoded in HEVC?

I only know Google Cardboard V2 apps use HEVC or V8 webm.
I think you are partially right. It is true that a 3D movie is supposed to be encoded in AVC (as well as with other constraints like the 16:9 aspect ratio). Also, x265 has no --frame-packing argument, and that means that many TVs will not recognize automatically the 3D format of the movie, and you will have to use the 3D button of your remote when the playback starts. But I think that most UHD TVs support HEVC, for 2D and therefore also for 3D. I don't think they want to prohibit playing a 3D HEVC movie just because it's not the standard.

Of course, for a better compatibility and for the ease of use, x264 is the preferred encoder, and it is and will stay the default in BD3D2MK3D.

Anyway, your remark is interesting. Someone can confirm if his TV supports 3D HEVC, or not ?

marsdust

7th October 2019, 20:03

I'm backing up my 3D collection to NAS and save time in the long run not getting out my chair and flipping discs. Many are straight backups via MakeMKV and thus can use Framepacking (preferred) but take up a lot of space.

So just re-encode some of the titles that would not play that much to reduce space, get good compression results with x265 (tolerate 12fps encode times). So since already breaking a spec may as well go full SBS and take advantage of the efficiency of the encoder at 3840x1080 as not constrained by the shiny disc spec.

Plasma TV detects the 3D signal fine and so does the DLP Projector. So although the Framepacked version is better (40GB) on the projector (100ft) the 8GB Full SBS is 95% there. And 3D films are generally clean anyway. Half SBS is not as good on the Projector but appreciate smaller screens would not matter so much and x264 would be fine.

Using a Vero 4K+ (testing the Framepacked beta) and also a $25 x96 mini plays them fine also (the encodes, as x96 does not do Framepacked).

konikpolny

15th October 2019, 22:20

staina

16th October 2019, 08:55

With the help of tsMuxer I'm yourself created ISO files with main 3D movie and selected audio and subtitles streams and now I'm found out with the help of BD3D2MK3D that the some that's how created files have assigned other 3D-plane than original 3D Bluray.

I can apply these created ISO files in tsMuxer and set for subtitles streams correct 3D-plane and recreate new ISO files and or I have to for creation apply original 3D Bluray?

For example:

Original Bluray in BD3D2MK3D

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream JPN - 3D-Planes 6
3. subtitle stream TUR - 3D-Planes 2
4. subtitle stream RUS - 3D-Planes 3
5. subtitle stream POL - 3D-Planes 4

Original Bluray in tsMuxer

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream JPN - 3D-Planes 2
3. subtitle stream TUR - 3D-Planes 3
4. subtitle stream RUS - 3D-Planes 4
5. subtitle stream POL - 3D-Planes 5

Remux select subtitle stream 1,3,5

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream TUR - 3D-Planes 3
3. subtitle stream POL - 3D-Planes 5

Correct remux select subtitle stream 1,3,5

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream TUR - 3D-Planes 2
3. subtitle stream POL - 3D-Planes 4

Thank for answer Staina

r0lZ

16th October 2019, 09:58

Hi r0lZ,
why does BD3D2MK3D create a project with 2 different files eg.
00098.track_4608.Eng.2D.sup and
00098.track_4608.Eng.sup
for the same 2D subtitles? I always thought they are identical but I noticed their filesize is different.
The 2D stream must be converted to XML/PNG by BDSub2Sub before the conversion to 3D. Unfortunately, sometimes, BDSup2Sub creates bad PNG frames for some subtitles. (They are either completely transparent, or their size is 0x0 !). But I have noticed that converting the original subtitle stream from BD SUP to BD SUP has the effect of solving that issue. Therefore, to convert the stream to 3D, BD3D2MK3D begins by a (theoretically unnecessary) conversion to 2D and create the stream with the .2D.sup extension.

Also, sometimes a single subtitle is split in several identical parts in the original stream, and so close together that they appear as a single subtitle to the spectator (known as "multiple ODS"). BDSup2Sub has an option to concatenate these double subtitles together, to form a single subtitle. Therefore, unnecessary subtitles are removed during that first conversion to 2D.

For that reason, previously BD3D2MK3D muxed the converted stream in the final MKV, as it was theoretically free of unnecessary double subtitles and invisible black images. But I have noticed later that sometimes, BDSup2Sub misses some subtitles, and therefore the converted stream can be somewhat incomplete. Therefore, now, BD3D2MK3D muxes the original 2D stream (without the .2D extension) in the MKV, and uses the converted 2D stream for the conversion to 3D only.

It is also correct that the filesize changes when the stream is converted, even if you don't change the format. Of course, it's normal if BDSup2Sub has concatenated some double subtitles, but it seems that there is another bug here, as if you convert again the .2D.sub stream to SUB, you will notice again a filesize change. I'm not sure why, and it it's important, but now, I think that the less you convert is the better. Unfortunately, it is necessary to convert several times the original stream to convert it to 3D.

r0lZ

16th October 2019, 10:18

I can apply these created ISO files in tsMuxer and set for subtitles streams correct 3D-plane and recreate new ISO files and or I have to for creation apply original 3D Bluray?
I'm not sure I understand what you mean, and that question is related to tsMuxer and only indirectly to BD3D2MK3D, so IMO you should have posted your question in the tsMuxer forum. But here is my answer anyway.

I'm sure that you can use BD3D2MK3D to know the exact assignment of the 3D-streams, and I'm also sure that they are often wrong in tsMuxer. I don't know if using the correct assignments from BD3D2MK3D to remux the streams with tsMuxer is sufficient to solve the tsMuxer bug. I hope so, but I use tsMuxer only to demux things, and therefore I don't know its bug when it muxes.

Therefore, I suggest to do a test yourself. Remux a 3D BD that has the wrong 3D-Planes assignments in tsMuxer, but use the correct values from BD3D2MK3D. Then, use tsMuxer and BD3D2MK3D to compare the 3D-Planes list of the newly remuxed BD, and it they are again different, you will know that tsMuxer has the same bug when it muxes.

In that case, you may have to use its (bad) 3D-Planes assignments, and with some luck, the final remuxed BD will be correct. Honestly, I'm not sure, but I think that it may again store the 3D-Plane numbers in the MPLS without paying attention to the order of the streams, and if it does that, the demux bug will be undone by the remux bug ! Of course, if that works, you will have to remux the same number of subtitle streams, in the same order than in the original BD, and with the same 3D-Plane numbers.

konikpolny

16th October 2019, 21:31

... Therefore, now, BD3D2MK3D muxes the original 2D stream (without the .2D extension) in the MKV, and uses the converted 2D stream for the conversion to 3D only.

OK, thanks r0lZ,
so I understand that it's the regular, not the 2D one, is best for OCR conversion to text.

r0lZ

16th October 2019, 23:07

so I understand that it's the regular, not the 2D one, is best for OCR conversion to text.
If you don't care about double subtitles, probably yes.

staina

17th October 2019, 10:21

I'm not sure I understand what you mean, and that question is related to tsMuxer and only indirectly to BD3D2MK3D, so IMO you should have posted your question in the tsMuxer forum. But here is my answer anyway.

I'm sure that you can use BD3D2MK3D to know the exact assignment of the 3D-streams, and I'm also sure that they are often wrong in tsMuxer. I don't know if using the correct assignments from BD3D2MK3D to remux the streams with tsMuxer is sufficient to solve the tsMuxer bug. I hope so, but I use tsMuxer only to demux things, and therefore I don't know its bug when it muxes.

Therefore, I suggest to do a test yourself. Remux a 3D BD that has the wrong 3D-Planes assignments in tsMuxer, but use the correct values from BD3D2MK3D. Then, use tsMuxer and BD3D2MK3D to compare the 3D-Planes list of the newly remuxed BD, and it they are again different, you will know that tsMuxer has the same bug when it muxes.

In that case, you may have to use its (bad) 3D-Planes assignments, and with some luck, the final remuxed BD will be correct. Honestly, I'm not sure, but I think that it may again store the 3D-Plane numbers in the MPLS without paying attention to the order of the streams, and if it does that, the demux bug will be undone by the remux bug ! Of course, if that works, you will have to remux the same number of subtitle streams, in the same order than in the original BD, and with the same 3D-Plane numbers.

Change 3D-plane in tsMuxer does work, Shall I tested.

What I don't know is that a if can use already remuxovaný ISO file with main function in that is only several subtitles streams and me here change 3D-plane to to those that this remux does not contain, but in original him contained. Or I have to always use original Bluray, because after remux with at 3D-plane, that is not used clear all data e.g . about depth display subtitles.

Where there are saved data to single 3D-plane? Is that a video stream, CLPI file or MPLS file.

r0lZ

18th October 2019, 10:19

Where there are saved data to single 3D-plane? Is that a video stream, CLPI file or MPLS file.
Again, it is difficult to understand your English. If I understand correctly, you want to know where are the original 3D-Planes.

The 3D-Planes (officially called Offset Sequences, or OFS) are in the MVC video stream (the "dependent stream" specific to the 3D movies). You can extract the OFS files from the MVC stream with, for example, MVCPlanes2OFS.exe, included with BD3D2MK3D, but as far as I know, there is currently no way to attach new 3D-Planes to the MVC stream, or to edit them easily.

If you remux the video without re-encoding it (for example to simply add a new audio or subtitle stream), the 3D-Planes are preserved, and if their numbers are assigned correctly to the right subtitle streams (in the MPLS) by the remuxer, then everything should be fine. But if you re-encode the video, the 3D-Planes are lost. That means that the reencoded 3D-BD25 usually found on the internet have lost the depth of their subtitles.

r0lZ

21st October 2019, 11:59

Someone has noticed that BD3D2MK3D is unable to start when AVSVersion**.exe crashes due to a bad installation of Avisynth. I have added some safeguards to avoid this problem. Now, if AVSVersion crashes, BD3D2MK3D assumes that the 32 or 64 bit version of Avisynth that has caused the crash is not installed, and issues an error message, but it should now be able to start. (Difficult to check, as my Avisynths are properly installed.)

There is also a new tool to modify the Y positions of all subtitles of a stream, useful when you import an external stream to align it with the original subtitles and minimize the risk of subtitles entering in foreground objects. It can also be used if you want to move a subtitle stream without 3D depth in the horizontal black bar of a movie shot in cinemascope.

v1.16 (October 21, 2019)
- Workaround for a crash of AVSVersion**.exe when Avisynth is not properly installed that prevented BD3D2MK3D to start.
- Added Subtitle Tools -> Move XML/PNG Subtitles Vertically, to allow you to easily move your subtitles in the black bar of a Cinemascope movie or align them with another subtitle stream.

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

Groucho2004

21st October 2019, 12:17

Someone has noticed that BD3D2MK3D is unable to start when AVSVersion**.exe crashes due to a bad installation of Avisynth.Define "crashes". Is there any error message?

TVI

22nd October 2019, 08:37

r0lZ

22nd October 2019, 11:05

Define "crashes". Is there any error message?
No, not directly. BD3D2MK3D prints this in its log:
32 Bit: Avisynth 2.5.8.5 child killed: unknown signal.

Since the error message begins with "32 Bit: Avisynth" and this happens before BD3D2MK3D has had a chance to open its main window, I'm sure it's when BD3D2MK3D verifies if at least one version of Avisynth is installed with AVSVersion.

The new version catches now the call to AVSVersion, and when it crashes, it issues a warning telling that Avisynth is not properly installed, then it continues normally.

The original error has been reported here (https://forum.videohelp.com/threads/394592-BD3D2MK3D-v1-15?highlight=BD3D2MK3D), but without much information.

r0lZ

22nd October 2019, 11:33

Hello,

I wonder if somebody could assist me with a problem.

I am trying to convert a 3D Blu Ray using BD3D2MK3D (The Adventures of Tin Tin). The MKV file plays fine without any issues but when I convert it to SBS using BD3D2MK3D the video/audio is slightly out of synch. I've converted quite a few 3D blu rays and this is the first time I've ever had this problem.

Any help would be most appreciated!

Thanks.
Hum, strange. I have converted Tintin without problem, and I have never seen a report for this kind of problem, for any movie.

Have you used the option "Add X seconds of black at the beginning of the video" in the last tab ? Personally, I use it almost always without problem, but if you did it, you may have to retry without that option.

Also, can you verify if there is a delay in the original MKV (as produced by MakeMKV) with MediaInfo ? Usually, I don't use MakeMKV to convert my movies, and it is possible that a delay in the original MKV is not correctly taken into account by BD3D2MK3D. (I will try here anyway.)

If your stream has a delay, or if you can figure out the duration of the offset yourself, you can fix it manually by editing the __MUX_3D_OPTIONS.json file. In the Audio stream(s) section, change the line just after the --sync line with 0:500, where the number in red is the offset to apply, in milliseconds. (Positive numbers mean move the audio later.) Then, launch __MUX_3D.cmd to remux the file (without re-encoding of course).

Sorry, I can't help much more.

TVI

22nd October 2019, 12:36

Hum, strange. I have converted Tintin without problem, and I have never seen a report for this kind of problem, for any movie.

Have you used the option "Add X seconds of black at the beginning of the video" in the last tab ? Personally, I use it almost always without problem, but if you did it, you may have to retry without that option.

Also, can you verify if there is a delay in the original MKV (as produced by MakeMKV) with MediaInfo ? Usually, I don't use MakeMKV to convert my movies, and it is possible that a delay in the original MKV is not correctly taken into account by BD3D2MK3D. (I will try here anyway.)

If your stream has a delay, or if you can figure out the duration of the offset yourself, you can fix it manually by editing the __MUX_3D_OPTIONS.json file. In the Audio stream(s) section, change the line just after the --sync line with 0:500, where the number in red is the offset to apply, in milliseconds. (Positive numbers mean move the audio later.) Then, launch __MUX_3D.cmd to remux the file (without re-encoding of course).

Sorry, I can't help much more.

Fantastic, thanks r0lZ.

I'll have a tinker and let you know how I get on.

r0lZ

22nd October 2019, 15:20

Fantastic, thanks r0lZ.

I'll have a tinker and let you know how I get on.
Just verified, and indeed, there is something that doesn't work well when the audio delays are retrieved from a MKV file. It's due to slight changes in the output of MkvInfo. I have already fixed the bug, and the next version should work as intended, but I need some time to fix another bug.

Anyway, there is something strange. Normally, there is no audio delay in an original BD, or it is very short (5ms or so, not enough to be noticeable). So, I still wonder why you have that problem. Can you confirm that there is an audio delay with MediaInfo ? If it detects one, then that will confirm that the culprit is the bug I have just fixed.

tebasuna51

22nd October 2019, 22:52

No, not directly. BD3D2MK3D prints this in its log:
32 Bit: Avisynth 2.5.8.5 child killed: unknown signal.
Avisynth 2.5.8.5 is a old but valid version.
There are a problem with AVSVersion32.exe?
For me work fine:

AVSVersion32
32 Bit: Avisynth 2.5.8.5

There are a new Avs+ version (https://forum.doom9.org/showthread.php?p=1888102#post1888102), with:
AVSVersion32
32 Bit: AviSynth+ 3.4 (r2923, 3.4, i386) (3.4.0.0)
AVSVersion64
64 Bit: AviSynth+ 3.4 (r2923, 3.4, x86_64) (3.4.0.0)

r0lZ

22nd October 2019, 23:21

Avisynth 2.5.8.5 is a old but valid version.
There are a problem with AVSVersion32.exe?

I don't think it's a problem with Avisynth 2.4.8.5, but I suspect that it is not installed correctly. Not sure why, but anyway, AVSVersion crashes, and prevents BD3D2MK3D to start, or even display an error message. As I wrote above, I have modified the code so that that will not happen any more, but when AVSVersion crashes, BD23D2MK3D will assume that the 32 or 64 bit version is not installed, and issue an error message.

I think it is better to re-install Avisynth, and it's probably the perfect occasion to switch to Avisynth+. Basically, it's what the next version of BD3D2MK3D will suggest. I will release it tomorrow...

r0lZ

23rd October 2019, 08:59

Minor update, with mainly the update of the x265 and mkvtoolnix exes, and the fix for the audio delays when opening a MKV file made with MakeMKV with audio delays (rare).

v1.17 (October 23, 2019)
- Fixed the bug of the audio delays not taken into account when using a MKV file make with MkvMerge as input.
- Added some definitions specific to UHD BD so that the option to show the 2D content the BD works with an UHD BD.
- Updated x265 to the latest stable version (v3.2+5)
- Updated Mkvtoolnix to the latest version (v38.0.0 'The Silent Type')

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

TVI

23rd October 2019, 21:03

Minor update, with mainly the update of the x265 and mkvtoolnix exes, and the fix for the audio delays when opening a MKV file made with MakeMKV with audio delays (rare).

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

Thanks r0lz I'll have another go at converting Tin Tin with this update.

So you know, Mediainfo did confirm a 1s 1ms "delay relative to video" on the MakeMKV file.

r0lZ

24th October 2019, 08:00

So you know, Mediainfo did confirm a 1s 1ms "delay relative to video" on the MakeMKV file.
OK, that confirms my impression. I'm sure the fix will solve that problem.

staina

24th October 2019, 09:19

Again, it is difficult to understand your English. If I understand correctly, you want to know where are the original 3D-Planes.

The 3D-Planes (officially called Offset Sequences, or OFS) are in the MVC video stream (the "dependent stream" specific to the 3D movies). You can extract the OFS files from the MVC stream with, for example, MVCPlanes2OFS.exe, included with BD3D2MK3D, but as far as I know, there is currently no way to attach new 3D-Planes to the MVC stream, or to edit them easily.

If you remux the video without re-encoding it (for example to simply add a new audio or subtitle stream), the 3D-Planes are preserved, and if their numbers are assigned correctly to the right subtitle streams (in the MPLS) by the remuxer, then everything should be fine. But if you re-encode the video, the 3D-Planes are lost. That means that the reencoded 3D-BD25 usually found on the internet have lost the depth of their subtitles.

English is not OKs sorry.

If then is do nothing but remux (no encode) so 3D - plane stay keep all and you unused for subtitles streams in MVC stream. If isn't executed reencode video streams (H.264 and MVC) are all 3D - plane from original 3D Bluray anytime usable.

Thank you Staina

r0lZ

25th October 2019, 09:52

Sorry. I can't understand. I can only repeat:

The 3D-planes are in the MVC stream. If you remux the video, all of them are preserved. If you re-encode the video, they are lost. A 3D-Plane doesn't need to be used by a subtitle stream to exist in the MVC stream (but of course, it's usually the case in original BDs). Several different subtitle streams can use the same 3D-Plane (although it's not frequent in commercial 3DBDs). So, if you remove some subtitle streams, their 3D-Streams will probably be unused, but they are still present in the original MVC video stream. And if you want to mux a new subtitle stream with the original video, you can use any existing 3D-plane, even if it is also used by another subtitle stream.

For an external subtitle stream, I suggest to use the 3D-Plane that is defined originally for the language that is the most similar to the language of your additional stream (with the size of the subtitles in the two streams as similar as possible) to minimize the risk of collisions with the foreground objects.

tarrega

29th October 2019, 19:24

Hey Everyone,
when I execute BD3D2MK3D.exe on my Windows 10 Home PC the Console opens with the message:

Error sourcing /Tcl/work/BD3D2MK3D/src/BD3D2MK3D.tcl: C:\WINDOWS
The system cannot find the path specified.
() 1 %

I used BD3d2MK3D successfully last year, back then a GUI started where I could load a mkv file.
I do not understand this error message. A google search for that
file name (BD3D2MK3D.tcl) gives 0 results. I also don't find that file on my system.

I assume it has something to do with Avisynth but I don't know that program.

I have the latest Version 1.17.
I have Avisynth+ v2772 (64bit) installed.
I have Avisynth 2.58 installed.

Any help would be very much appreciated.

r0lZ

30th October 2019, 11:38

Welcome to the Doom9 forums, tarrega

The error you have is very strange. It seems that it is caused by a missing file, probably located in the Windows directory. Where is Windows located in your system ? Usually, it's in C:\windows, and BD3D2MK3D uses the environment variable %WINDIR% to discover it. Maybe there is something wrong here.

Please open a command prompt window and type this:
echo "%WINDIR%"
On most systems, it replies this:
"C:\Windows"
Let me know what it has replied for you.

Also, the only thing that BD3D2MK3D searches now in the Windows directory is if .NET v4 or greater is installed (as it's necessary to hardcode the subtitles on the video). So, please open this directory in the File Explorer:
C:\Windows\Microsoft.NET\Framework\
And let me know if there is at least one folder beginning with "v4." And if it's not the case, please install Microsoft .NET V4 (https://dotnet.microsoft.com/download/dotnet-framework) (currently, v4.8 is the latest version).

Also, in the big white window where the error message is shown, after the prompt () 1 %, type this:
IsNetV4Installed
Normally, you should see "true" if .NET v4 is already installed, or "false" otherwise. But if that command produces the error message you have noticed, that will confirm my suspicion that it's the .NET checking function that is the culprit, and I should be able to fix the bug.

Also, be sure to use the latest version of BD3D2MK3D (v1.17). I have recently fixed another bug that can also explain the problem.

tarrega

30th October 2019, 15:20

Hi r0lZ,
thanks for the reply.
1.) echo "%WINDIR%" returns "C:\Windows"
2.) In "C:\Windows\Microsoft.NET\Framework" there is a folder "v4.0.30319"
3.) IsNetV4Installed: Error sourcing /Tcl/work/BD3D2MK3D/src/BD3D2MK3D.tcl: C:\WINDOWS
The system cannot find the path specified.
() 1 % IsNetV4Installed
C:\WINDOWS
The system cannot find the path specified.
(BD3D2MK3D) 2 %
4.) I used version 1.17

So it is the .NET checking function?

r0lZ

31st October 2019, 10:42

So it is the .NET checking function?
It seems yes, but I don't understand why. I have exactly the same configuration, and the function works correctly here. I supposed that the function crashes on you due to some differences with the "normal" windows installation, but it's not the case, and I'm puzzled.

Anyway, I will try to modify it, and I'll contact you by PM to give you a beta to test. Perhaps I will not be able to discover that .NET v4 is indeed installed, but at least the program should start. In the worst case, BD3D2MK3D will not let you hardcode the subtitles on the video (option in last tab). Do you need it ?

Please be patient. I have a RV right now, but I'll do the fix as soon as possible...

tarrega

31st October 2019, 15:12

Anyway, I will try to modify it, and I'll contact you by PM to give you a beta to test. Perhaps I will not be able to discover that .NET v4 is indeed installed, but at least the program should start. In the worst case, BD3D2MK3D will not let you hardcode the subtitles on the video (option in last tab). Do you need it ?

Please be patient. I have a RV right now, but I'll do the fix as soon as possible...

No I don't need it. Thank you for your work I'll be patient :).

mi3gai4rui4

3rd November 2019, 20:49

Just getting back to trying to get a 1920x2160 interleaved video.

tebasuna51's suggestion:

Maybe:

left = SelectEven(interleaved).AssumeFieldBased()
right = SelectOdd(interleaved).AssumeFieldBased()

# Build combined Row-interlaced image
Interleave(left, right).Weave()

It did produce a 1920x2160 video with the correct aspect ratio.
MPC-HC + madVR seem to play it back correctly, but the left and right eyes seem to swap back and forth rapidly (not sure if every frame). If I pause at different arbitrary points, sometimes left eye is on top, sometimes right eye.

Any ideas as to how to fix that?

Thanks in advance :-)

thxoptimizer

6th November 2019, 11:41

Hi,

In the last version, I don't see any BD3D2MK3D.cfg file ==> "BD3D2MK3D/BD3D2MK3D.cfg": no such file or directory

Thanks

von Suppé

6th November 2019, 12:15

Hi r0lZ,

For the sake of your tool, I don't know if tsMuxer can have certain issues with demuxing BD iso's. I never encountered them, for 3D BD anyways.

This (de)muxer tool is rather dated, and you know filler56789 is busy with it in his tsMuxer Open Source thread.

Don't know if you were already aware of it, but as for purely demuxing, maybe a thought to look into this thread?: https://forum.doom9.org/showthread.php?t=177053

r0lZ

7th November 2019, 00:09

In the last version, I don't see any BD3D2MK3D.cfg file ==> "BD3D2MK3D/BD3D2MK3D.cfg": no such file or directory
Well, I have just tested without the cfg file, and the program works perfectly. The cfg file is created when BD3D2MK3D is used for the first time, and doesn't issue an error message if the file doesn't exist. It has never been released with the program itself.

Have you installed BD3D2MK3D in a directory where you have full write access ? The CFG file is normally written in the installation directory. When exactly do you see the error message ?

thxoptimizer

7th November 2019, 07:44

https://nsa40.casimages.com/img/2019/11/07/19110707462094060.jpg

r0lZ

7th November 2019, 11:09

OK, I think I know why it fails. It's probably due to the accented character in the path ("vidéos"). I have already encountered a similar problem. Try to move the entire BD3D2MK3D folder elsewhere, or rename vidéos to videos, and I guess that everything will be fine.
In the meantime, I'll do some tests to see if I can fix that annoyance here...

[EDIT] I did the test here with exactly the same installation folder as you, and I have no problem. It's not the accented character that causes the problem. I'm puzzled.

Try to download again the program, and re-install it. Perhaps in another folder anyway. Who knows ?