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

[Privateer5000]

Thanks for the fast fix. Now it works like it should. Thank you very much

[rod93]

hi
i try to encode a bd3d in frame sequential but when i want to see it on 3d projector with powerdvd 15, the film isn't in 3d why?

(i was thinking fs was in 2040*1080 but the output file is in 1080p why?)

thank you to save me

[r0lZ]

Welcome to the Doom9 forums, rod93.

First, if you use BD3D2MK3D, please use the BD3D2MK3D official thread. This one is obsolete and dead since July 2014.

Frame sequential 3D is just like a normal video, without changes in resolution, but there are two times the number of frames (so 47.952 fps instead of 32.976). Therefore, the 1080p resolution is absolutely normal.

FS is usually not well supported by most players. I suggest to try to use Half-SBS or Half-T&B first. If that works, try Full-SBS or Full-T&B. That should work on PC with a good player (but most relatively old hardware players will probably refuse to play the full resolution.) Also, be sure to use the last version of BD3D2MK3D.

[EDIT] The previous post, by rod93, has been posted in the old "Guide to convert BD 3D to 3D Left+Right Stereoscopic and Anaglyph", and moved here by tebasuna51 after a few replies. Hence my request in the beginning of this post.

[rod93]

Ok so full t&b mâke à 3840*2160 mkv ?

Envoyé de mon 6039Y en utilisant Tapatalk

[rod93]

Powerdvd dont support fs ?

Envoyé de mon 6039Y en utilisant Tapatalk

[r0lZ]

Originally Posted by rod93

Ok so full t&b mâke à 3840*2160 mkv ?

No. 1920 x 2193. In Full-SBS, the two full size 1080p images are stacked vertically: 1920 x (1080*2) = 1920 x 2193. In full-SBS, it's the opposite: 3840 x 1080.

Originally Posted by rod93

Powerdvd dont support fs ?

I don't know. I don't use PowerDVD. But anyway, your projector must support the resolution or frame rate.

Also, have you tried to change the PowerDVD 3D-mode setting manually? Many players do not automatically switch to the right 3D-mode, because they ignore the stereoscopy and frame-packing info stored in the MKV. When it's the case, you have to go to the 3D settings menu of the player, and select yourself the right SBS, T&B or FS mode.

[youli]

Hello, r0lZ. Hello, everyone.
I made the first HEVC 10-bit full over-under BD-Rip for test of my new UHD TV LG 55UF85.
It looks great!

Really, x265 default settings trying to convert noise pixels to flat areas for bitrate reduction - it looks like artefacts. After tests for preserving high-frequency detail by x265 encoder, and also saving of the native noise during the compression I added few command line options (bold):
--me umh --subme 7 --aq-mode 3 --aq-strength 0.7 --no-sao --no-deblock --rd 3 --psy-rd 0.8 --b-adapt 1 --ctu 64 --rc-lookahead 24 --bframes 4 --merange 25 --ipratio 1.1 --pbratio 1.0 --qcomp 0.8 --rdoq-level 1 --psy-rdoq 0.7

Media info:
wpp / ctu=64 / min-cu-size=16 / max-tu-size=32 / tu-intra-depth=1 / tu-inter-depth=1 / me=2 / subme=7 / merange=25 / no-rect / no-amp / max-merge=2 / temporal-mvp / early-skip / recursion-skip / rdpenalty=0 / no-tskip / no-tskip-fast / strong-intra-smoothing / no-lossless / no-cu-lossless / no-constrained-intra / fast-intra / open-gop / no-temporal-layers / interlace=0 / keyint=250 / min-keyint=23 / scenecut=0 / rc-lookahead=24 / lookahead-slices=8 / bframes=4 / bframe-bias=0 / b-adapt=1 / ref=1 / limit-refs=0 / no-limit-modes / no-weightp / no-weightb / aq-mode=3 / qg-size=32 / aq-strength=0.70 / cbqpoffs=0 / crqpoffs=0 / rd=3 / psy-rd=0.80 / rdoq-level=1 / psy-rdoq=0.70 / no-rd-refine / no-signhide / no-deblock / no-sao / no-sao-non-deblock / b-pyramid / cutree / no-intra-refresh / rc=crf / crf=23.0 / qcomp=0.80 / qpmin=0 / qpmax=51 / qpstep=4 / ipratio=1.10 / pbratio=1.00



x265 [info]: frame I: 669, Avg QP:20.95 kb/s: 23348.66
x265 [info]: frame P: 98386, Avg QP:22.91 kb/s: 11636.39
x265 [info]: frame B: 66156, Avg QP:24.43 kb/s: 3368.81
x265 [info]: consecutive B-frames: 36.1% 61.9% 1.4% 0.5% 0.2%

encoded 165211 frames in 37868.77s (4.36 fps), 8373.20 kb/s, Avg QP:23.51

r0lZ, thanks again for your program!

[r0lZ]

Thanks for the info, and for the thanks, youli !

[rod93]

Thank you i will test in fp
Its working on t&b in full HD res


Envoyé de mon 6039Y en utilisant Tapatalk

[rod93]

ok it's working very well with t&b in x264

i trying in x265 can you help me to configure it for that profil for have quality with a reasonable size?

[tebasuna51]

Originally Posted by rod93

i trying in x265 can you help me to configure it for that profil for have quality with a reasonable size?

The quality/size is controlled by the crf parameter. There are other parameters than can be changed, can improve some movie sources but not for all sources.

The x265 encoder is still under development and, by the moment, is better let default parameters and use only the CRF, to control the quality/size, and PRESET (..., Medium, Slow, ...) to control the encoding time.

BTW you can read this post.

[r0lZ]

Well, I don't encode in x265 myself, because my TV doesn't understand that format yet. I have simply encoded the default settings in BD3D2MK3D. (For example, the default CRF value is 28 instead of 23 for x264.) Many peoples consider the default CRF values too high, and they prefer to encode with a lower CRF, between 17 and 20 for x264. Personally, I use often the CRF 20, but with a slower preset (slow or slower instead of medium, again for x264), but take in mind that x265 is by nature much slower than x264, and selecting a slow preset can result in extremely long encoding times.

Personally, I don't like to change individual settings precisely, because usually that give worse results than a good preset, that has been fine-tuned by specialists to give excellent results. But again, some peoples want to try different settings, perhaps (and IMO too often) because they have read somewhere on the net that incredible compression with low quality loss can be archived with specific settings. It's usually not true, and often, that settings were conceived when there was no "Preset" setting in x264. It was therefore necessary to give all settings explicitly anyway. But now, things are much more simple, and I see no good reason to overwrite the selected preset with specific settings. If you are not happy with an encoding, try to lower the CRF or use another preset first, and specify manually additional settings only if you know what you are doing.

Also, don't forget that x265 is still under constant development, and it may have some bugs or weakness that will be fixed over time. Therefore, it might be difficult to say today what are the best parameters for that encoder. And, of course, there is no "best" method. The quality of the encoding depends greatly of the source video, and even with the same source, some peoples may prefer an encoding that others don't like. So, there is no precise answer to your question.

Here in the BD3D2MKL3D thread, youli has posted recently a message explaining that he is not happy with the x265 default settings, and he suggests to add manually a lot of additional settings. Maybe he is right. You can try his settings if you wish. But don't ask me if that will certainly give better results than the default parameters. Honestly, I don't know.

You may also use the SSIM or PSNR tunes to have a relatively precise and objective measure of the quality of the encodings. You should encode the same short clip several times with different settings, and compare the final SSIM or PSNR values to determine the "best" method. However, remember that it's not because one settings gives excellent results with your test clip that it's the best setting for any video source. See the articles on Wikipedia for more info (SSIM, PSNR).

[EDIT] tebasuna51 has posted his reply when I was writing mine. And he has explained essentially the same thing than me.

@tebasuna51: Perhaps you can move these new posts in the BD3D2MK3D thread?

[tebasuna51]

Originally Posted by r0lZ

@tebasuna51: Perhaps you can move these new posts in the BD3D2MK3D thread?

Done.

[youli]

Originally Posted by rod93

ok it's working very well with t&b in x264

i trying in x265 can you help me to configure it for that profil for have quality with a reasonable size?

For example:

--crf 23 --preset ultrafast --me umh --subme 7 --aq-mode 3 --aq-strength 0.7 --no-sao --no-deblock --rd 3 --psy-rd 0.9 --b-adapt 1 --ctu 64 --rc-lookahead 24 --bframes 4 --merange 25 --ipratio 1.2 --pbratio 1.1 --qcomp 0.8 --rdoq-level 1 --psy-rdoq 1.5 --sar 2:1

P.S.
1. It will no fast, just settings based on ultrafast preset only!
2. You can get the file size between 5 - 20GB, it depends of movie. For example, with one sound stream R.I.P.D. - 5,12 GB or Ant-man - 17,2 GB.
3. Option "--sar 2:1" for LG TV.

[youli]

Originally Posted by r0lZ

You may also use the SSIM or PSNR tunes to have a relatively precise and objective measure of the quality of the encodings. You should encode the same short clip several times with different settings, and compare the final SSIM or PSNR values to determine the "best" method...

Yes, you are right. But...

If the "psy" and "aq" optimizations are enabled, then they will reduce the level of SSIM, and also misrepresent the level of PSNR. Rather, these values will be assessed incorrectly.
I mean this options : "--rd, --psy-rd, --rdoq-level, --psy-rdoq" and "--aq-mode, aq-strength".

Correct results of PSNR and SSIM can only be obtained if psycho-visual optimizations and adaptive quantization are disabled.

Of course I assessed structure similarity during the tests. If crf = 23, the SSIM Mean about 98.9%.

For x264 "Avg QP" for B frames recommended less than 23.
It can be assumed, that for x265 "Avg QP" for B frames recommended less than 28.

x265 [info]: frame I: 560, Avg QP:20.08 kb/s: 29462.21
x265 [info]: frame P: 81439, Avg QP:23.06 kb/s: 10158.44
x265 [info]: frame B: 55969, Avg QP:25.15 kb/s: 2148.81

So above, I have a slight excess of the bitrate at --crf 23.

[r0lZ]

Afaik, when you specify the SSIM or PSNR options, the incompatible optimisations are automatically disabled. Of course, if you specify them manually (via the Additional Options field of BD3D2MK3D), they will conflict, and I don't know exactly what will happen, but I suppose you're right and the values will be assessed incorrectly.

[youli]

I made a lot of rips. In my experience, in most cases the average QP for B frames is one of the main indicators of quality.

At crf mode for x264 default value 23 minus 5 = 18 - very good quality (average QP for B will less then 23).
So at crf mode for x265 default value 28 minus 5 = 23 (average QP for B will less then 28).
It is just analogy
Of course the options - me, subme, merange, rc-lookahead, qcomp... are very important too.

[tebasuna51]

All opinions about x265 encoder (HEVC) configuration are welcome, but there are a specific thread High Efficiency Video Coding (HEVC) when you can read about that with experienced users.

Further discussion about that is a little off topic here. Even when r0lZ (and myself) don't use x265 to encode.
BD3D2MK3D can encode and configure x265 in a similar way than x264, please use this thread for specific 3D troubles and the related thread for general configuration.

[Sxc]

So I was having a lot of trouble with intermittent corruption (only on the right eye!) when encoding my Kung Fu Panda 3 BD. Disc plays fine and re-ripped it twice. As usual I was using x265, so tried x264 and exact same issue. I disabled hardware acceleration and voila the problem went away. I noticed it quite quickly at the 20th Century Fox searchlight at the beginning. I was doing the encoding on a i7-6700K CPU with latest drivers.

Just a heads up if anyone else has had weird intermittent corruption appear on their encodes (but no crashes when encoding) to try disabling under Settings / MVC Decoder / Hardware Acceleration.

[r0lZ]

Thanks for the information. It's not the first time that the drivers for the Intel hardware cause troubles, and indeed, disabling the hardware acceleration usually solves the problem.