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

[r0lZ]

I can't see the image (not yet approved), but the error message in the log is easy to interpret: bad ISO. When there are different numbers of frames in the two video streams, that indicates usually that there are errors in the streams. Furthermore, if tsMuxeR demuxes only 6445 and 6447 frames, that means that the streams are seriously damaged. Sorry, but BD3D requires a good BD3D image as input. Re-rip the BD.

[igvk]

Ok, but when I press "Preview M2TS", it shows only "00001.m2ts", which exactly corresponds to the part that is demuxed.
And this ISO can be played fully in PowerDVD.

[r0lZ]

OK, I see the image now. I note that the title bar shows the full path to a folder (F:\Video\Movies\BluRay\Avatar...), indicating probably that you have not used a mounted ISO. When the disc image has been mounted, BD3D2MK3D should show something like this in the title bar: "Z:\ - 00800.mpls" (without the quotes).

Apparently, you are running Windows 8. Under Win8, you can mount the disc image (the ISO file) without an external program. It is normally sufficient to double-click it. Try it. That should work.

Of course, if you have ripped the files directly from the BD, you will have to start over, and rip the BD to an ISO instead of as files in a directory. Then mount the ISO. Or you can also process the original BD through AnyDVD HD directly with BD3D2MK3D.

It is ALWAYS a very bad idea to copy the files of a 3DBD (or of its ISO) directly to hard disc. The SSIF files have a complex structure that is totally destroyed when the files are extracted from the BD. Also, you end up with all 3D video files twice: once in the form of the SSIF file, and once as M2TS file, and therefore your copy consumes about two times the disc space of the ISO. The fact that you can play the M2TS files independently but not rip the SSIF files (referenced by the MPLS) is an evidence that something is broken. Delete the files you have copied to disc, and try again with the mounted ISO.

[igvk]

Ok, my fault - I was not using ISO image, but files copies.
I am working with mounted ISO now, it looks correct.
Thanks!

[frank]

TATAAAA!!!
BD3D2MK3D v0.61 passed the Pacific Rim Test on new 5. generation Intel CPU I7-5500U (Broadwell) without errors!
New dgMVCdecode.dll and FRIMsource.dll worked fine in HW- and SW-mode. Thanks!

Edit: Latest Intel graphics drivers (2015) are required.

[r0lZ]

Thanks for the (noisy!) confirmation. :-)

[|1313|]

Will you add x265 later on or?

[r0lZ]

I don't know. I suppose that that will be useful one day, but currently, h265 is too young and not really supported by most hardware players. Also, I have never used it, and I don't know if it will be easy to add it in BD3D2MK3D.

[|1313|]

Okey! Thanx for the answer.

[frank]

Intel has actually updated the drivers for 2nd gen cpu, Sandy Bridge in February!
Now BD3D2MK3D workes properly on Dell XPS (Intel 7, 2nd gen, igfx3000, Sandy Bridge). No more glitches with hardware or software decoding.

[r0lZ]

OK, good news! Please keep us informed if you notice a new update of the Intel drivers for one of your machines. Thanks!

[frank]

Using our reference: Avatar.
There are 85 forced subpictures (german). The time stamps are ok but the depth values go out of sync.
The video has 23.976 fps.
Look at forced sup 57, 1:36:07 "Vater!" and the following "Mutter!": depth=10
That is too little, goes into the persons.
The old v0.56 calculates depth=40 and 28. Comparing with PowerDVD this is right.

So I can't trust BD3D2MK3D v0.61 and had to recalculate the 3D sup with v0.56 Tools. (same .3dp file, plane 02)
______
frank

[r0lZ]

There is something I don't understand! There is no change in the handling of the subtitle timings or in the way the 3D-planes are used between v0.56 and v0.61!

Or, there is only one change in v0.57: I have added the patch for the "correct frame rate" in the XML file. But since then, I have discovered that that patch causes other problems, and therefore I have removed it in v0.59. That cannot be the reason.

Anyway, I will try to compare the code of the two versions to find a culprit, but I don't think there is something really different.

[frank]

In the xml of v0.56 are really 24 fps time stamps but FrameRate="23.976".
In the xml of v0.61 are really 23.976 fps time stamps but FrameRate="25".

AFAIK you have to handle the .3dp with 24 fps.

[r0lZ]

Originally Posted by frank

In the xml of v0.56 are really 24 fps time stamps but FrameRate="23.976".
In the xml of v0.61 are really 23.976 fps time stamps but FrameRate="25".

The FrameRate value in the XML is not used the normal way bt BDSup2Sub. It must be 25, even if it's not at all the frame rate of the movie. It's why I have restored that value in v0.59.
The frame rate written in the XML is ignored by BD3D2MK3D, and should not influence the conversion to 3D.
The fact that the frame rate has changed in the time codes is very strange. Currently, BD3D2MK3D does not force any frame rate, and the conversion should not modify the timings of the original SUP. But I may be wrong. It is very difficult to understand how BDSup2Sub works!

Originally Posted by frank

AFAIK you have to handle the .3dp with 24 fps.

But IIRC it's what I do. Anyway I will verify that tomorrow. In v0.57. I have introduced so many changes that I may have modified something inadvertently.

[frank]

I know the wrong fps param of xml.
Look at help from BDSup2Sub 5.1.2: https://github.com/mjuhasz/BDSup2Sub/wiki
Supported formats.
The culprit is the Sony BDN XML format that only knows integer fps.
Mjuhasz wrote:

Note: although the BDN XML looks pretty straight forward and clean, the timing information in this format is a little weird for unknown reasons. Indeed the timings are always based on an integer frame rate.

The parameter --convert-fps 24p,24p is set in v0.56 and 24p symbol means 23.976 fps. The BDN xml is always converted to real 24 fps! (x 1.001)
In v0.61 is no parameter --convert-fps and BDSup2Sub thinks it is 25 fps standard. So the time stamps are untouched 23.976 fps.
Using this with .3dp results in asynchronous depth values.

[r0lZ]

Indeed, I have removed the --convert-fps argument. And, similarly, I have removed the --fps-source 24p argument when BDSup2Sub++ is used instead of the Java version (because the ++ version doesn't have the --convert-fps option). I can restore them, but if I have removed them, that was probably because they created problems. I don't remember the exact reason, but I think it's because that doesn't work well when the user specifies a frame rate in the GUI of the Convert Subtitle to 3D tool. I have to verify that too...

BTW, maybe the culprit is Sony, but in the XML, there is a frame rate AND a dropframe field. If you specify 24fps and Dropframe true, the real frame rate is indeed 23.976. No need for floating point numbers. But BDSup2Sub stores always 25 fps and dropframe false, even when the original subtitles come from a 3DBD at 23.976 fps, and if you "fix" this by forcing the right frame rate and dropframe field, you can't get your subs in sync anymore! Furthermore, having to specify --convert-fps 24p,24p (that should not convert anything) is extremely bizarre. I persist to think that the handling of the frame rate by BDSup2Sub is not correct, or at least totally counter-intuitive.

I'll do some tests with the restored --convert-fps and --fps-source options, and if that works correctly, I'll release a new version. Anyway, I will have to find a solution! Thanks for the bug report.

[|1313|]

I got anoother question is it possible to to 2d to 3d conversions? DVDFab sucks arse i think sorry for the language. And if my favourite app dont do it does anyone else know of a tool that does it? (NOT DVDFAB)

[r0lZ]

Aaah! Vade retro Satanas! ;-)

No, BD3D2MK3D doesn't do conversions. IMO, all Windows programs that are supposed to convert 2D to 3D are bad. If you have a good 3D TV like my Samsung, you don't need to convert the 2D movies to 3D. Just use the real-time conversion of the TV. Although not perfect, it is certainly much better than any conversion by a Windows program. Anyway, don't expect miracles. No automatic 3D conversion can be really satisfactory. Professional conversions are better, but they require a huge manual work, and they are very expansive.

If you want to convert anyway, the Laewo Blu-ray to MKV Converter might be better than DVDFab, but I'm not sure. I have never tried it. There are certainly other alternatives, but I don't know them.


@everybody: Please be patient if you post here or wait for an update. I have had a virus and I had to re-install Windows. My programming environment is damaged, and I need to restore a lot of things. I may be absent for some days...

[|1313|]

Thanx i just asked cause i heard that i could use Avisynth. Are you finnish? And also I wanted a free software i aint gonna pay todo crappy conversions :P