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

[Giz..]

Thanks for de new version.


Unfortunately I get the error message
can't read "x264bitrate"
with the version.



Under v1.9 no problems.
Tested on 2 PC with 2 images.

I too got this error, went back to 1.9. Also wondering if any testing done with AVISynth+ http://avs-plus.net/

[r0lZ]

Thank you very much for your helpful response (and tebasuna51).

Just one more query please. At some point during the majority of my 3D conversions there is a green flash and the 3D is thrown out of synch. It's is pretty random and can happen once or multiple times, and usually there will be another green flash and the 3D will return to normal.

Do you know why this happens? I wondered if it was something to do with checking the laptop during the conversion process?

Thank you!That may be caused by the laptop going to sleep. x264 (and probably also x265) do not like being interrupted.

Are you sure you launch __ENCODE_3D_LAUNCHER.cmd and not directly __ENCODE_3D.cmd ? Also, be sure to not set your laptop to sleep mode manually during an encoding.

Anyway, normally, you can have a look at the title bar of the command prompt window when you want to see the progress of the encoding. As long as you don't launch another heavy task at the same time, everything should be fine.

Try also to turn the hardware decoding off, as suggested by sneaker_ger.

Personally, I have never has that kind of problem.

[r0lZ]

I too got this error, went back to 1.9. Also wondering if any testing done with AVISynth+ http://avs-plus.net/
Sorry, I have not much time currently. I'll fix that bug as soon as possible...

No, I'm personally not really interested in the numerous forks of avisynth. I prefer to stick to the good old bug free version. But if anisynth+ has the same syntax, you can try it yourself, simply by modifying the file name in __ENCODE_3D.cmd.

[tebasuna51]

No, I'm personally not really interested in the numerous forks of avisynth. I prefer to stick to the good old bug free version. But if anisynth+ has the same syntax, you can try it yourself, simply by modifying the file name in __ENCODE_3D.cmd.

There are nothing to modify, I'm running Avs+ (32 and 64 versions installed) without problems.

Of course the 32 version is used with 32 bits plugins used in BD3D2MK3D.

I can make a test loading FRIMSource64.dll and encoding directly with x264_x64.exe, instead use the intermediate avs2yuv.exe, to see the speed change.

Encoding started 28/08/2019 1:56:10,66
"C:\Portable\Util\BD3D2MK3D\toolset\avs2yuv.exe" "__ENCODE_3D_MOVIE.avs" -frames 158712 -o - | "C:\Portable\Util\BD3D2MK3D\toolset\x264_x64.exe" --output-depth 8 --crf 23 --preset medium --sar 1:1 --range tv --colormatrix bt709 --frame-packing 3 --qpfile chapters_3D.qpfile --frames 158712 --fps 24000/1001 --output "00009_3D.264" --demuxer y4m --stdin y4m -
...
encoded 158712 frames, 42.01 fps, 3536.54 kb/s
Encoding finished 28/08/2019 2:59:09,86 -> 1:02:49,20

Encoding started 28/08/2019 3:03:34,12
"C:\Portable\Util\BD3D2MK3D\toolset\x264_x64.exe" --output-depth 8 --crf 23 --preset medium --sar 1:1 --range tv --colormatrix bt709 --frame-packing 3 --qpfile chapters_3D.qpfile --frames 158712 --fps 24000/1001 --output "00009_3D64.264" "__ENCODE_3D_MOVIE64.avs"
...
encoded 158712 frames, 49.59 fps, 3536.54 kb/s
Encoding finished 28/08/2019 3:56:55,87 -> 0:53:21,75
Can save 18% time with Avs+ 64 bits.

[r0lZ]

Interesting. Thanks for your test ! Maybe I'll implement some support for Avisynth+ 64-bit, but I have to verify first that all plugins necessary for BD3D2MK3D are available.

[r0lZ]

OK, I think the bug with the bitrate variable is now really fixed. Please confirm !

v1.11 (August 28, 2019)
- Fix: Hopefully definitively fixed the bug of the uninitialized bitrate variable
- Updated BDSup2Sub++.exe to the latest version (1.0.3) and modified the link to the BDSup2Sub++ home in the Help menu
- Updated the Mkvtoolnix exes to the latest version (37.0.0 'Leave It')

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

[tebasuna51]

Thanks for the new version.

All plugins (I think LoadHelper.dll is not used now, it is not needed at all) have 64 bits versions (all supported for Avs+):

DGMVCDecode.dll, libmfxsw.dll (http://rationalqm.us/mine.html)
FRIMSource.dll, libmfxsw.dll (https://forum.doom9.org/showthread.php?p=1650646#post1650646)
SupCore.dll, SupTitle.dll (http://avisynth.nl/index.php?title=SupTitle)
VSFilter.dll (https://github.com/pinterf/xy-VSFilter/releases) with a modern VSFilter.dll

Maybe you need these little tool from Groucho2004 to know if AviSynth 64 version is instaled, with both Avs+ (pool (https://forum.doom9.org/showthread.php?t=176505&highlight=Avisynth+version)):
AVSVersion32.exe
32 Bit: AviSynth+ 0.1 (r2772, MT, i386) (0.1.0.0)

AVSVersion64.exe
64 Bit: AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)

[r0lZ]

Fine, thanks ! Indeed, it seems that the 64-bit version of Avisynth+ is stable. At least, it is used by a lot of peoples. I will therefore probably implement it, but that will take some time...

[tebasuna51]

... but that will take some time...

Of course, no problem.

[r0lZ]

OK, I did some tests with Avisynth+ 32-bit, and everything seems to work correctly, without any modification. So, I guess that using the 64-bit version will not be much more difficult.

[tebasuna51]

The selecction of the Avs+ version to use is make by the program than call to AviSynth.

AVSVersion32.exe, avs2yuv.exe, x264_x86.exe, ... call to Avs+ 32 bits
AVSVersion64.exe, x264_x64.exe, ... call to Avs+ 64 bits

For instance the 'BD3D2MK3D-> Help -> AviSynth version' run the avs script "Test_Avisynth_Installation.avs" with LoadPlugin("VSFilter.dll")
Like my default avs player (VirtualDub2_64) is 64 bits I get the error:
"Cannot load a 32 bit DLL in 64 bit AviSynth..."

Changed to VSFilter64.dll work fine.

[r0lZ]

I have understood that soon after having posted my (stupid) question, and I have immediately removed it, so I did not expect an answer. But thanks anyway.

Now, I wonder if I must keep the avs2yuv trick to encode with x264 or x265 64-bit, for the users who have installed only the classic Avisynth 2.6 32-bit, or if I can assume that the users who want to encode in 64-bit have already installed Avisynth+ 64-bit, or will accept to install it ?

In other words, I may replace the current option "Use 64-bit X264 with avs2yuv on 64-bit PC" with a "Force 32-bit encoding" that will be available only on 64-bit PC when a 64-bit version of Avisynth is installed. When this option is enabled, BD3D2MK3D will then generate the project with 32-bit tools only (Avisynth AND X264/X265, without avs2yuv). For me, that will be simpler to implement, as I will not have to mix 32 and 64-bit tools, but that will force the users of a 64-bit PC to install Avisynth+ 64-bit if they want a fast encoding. Since Avisynth+ seems well compatible with the classic Avisynth, I suppose that it's not a problem. What do you think ?

[tebasuna51]

Well, the first question than BD3D2MK3D must know is if are running a W32 OS, then only Avs, x264, x265... 32 bits can be used.
AVSVersion32.exe can be used to know if AviSynth is installed, if not BD3D2MK3D can't work, if yes there are only a way to work.

If a OS W64 is running you can use AVSVersion64.exe to know if Avs 64 bits is installed.
If only Avs 32 is installed you can inform the user about the option of install Avs 64 but you need use avs2yuv with x264/x265.
If Avs 64 is installed you can generate all avs scripts with 64 plugins and not use avs2yuv.

I think the current option "Use 64-bit X264 with avs2yuv on 64-bit PC" is not necesary, always use the best option allowed, only inform than installing Avs+ 64 the encode is fast.

[r0lZ]

Thanks. It's exactly what I have planned to do. But I wonder if I should add an option to force the usage of the 32-bit avisynth even when the 64-bit version is installed, in case of problems with avisynth+ x64 or with one of its plugins.

[tebasuna51]

Ok, is your choice.

[r0lZ]

I don't know QSVEnc or VCEEnc, with NVEnc I can make a equivalent command line encode except for --frame-packing 3 (basic for 3D output) but maybe any NVEnc expert can do it.
What binary do you use ? ffmpeg ? I must admit that I'm a bit lost. There are many web pages about NVEnc, but none with an exe to download.

Can you suggest a command line ? (It is a pity that the FramePacking option is missing, but it is missing for x265 too, so I suppose that it is not mandatory for most users.)

As I have almost finished to modify BD3D2MK3D to support AniSynth+, I'm looking for another thing to do. ;-)

[tebasuna51]

Here there are binary releases and some help: https://github.com/rigaya/NVEnc

[r0lZ]

OK, thanks. I have not been able to find any download link for the exe, but after some googling, I found this (https://onedrive.live.com/?id=6BDD4375AC8933C6%212293&cid=6BDD4375AC8933C6). So now I have the exe. But I don't think that my old Nvidia graphic card supports the NVEnc hardware acceleration. Only cuda. So, it will be difficult for me to test NVEnc. Furthermore, I have read often that the quality of the encoding is very bad. So, I'm not sure anymore that I want to implement it. But I will do some tests anyway. But first things first. I will release a beta with the support for Avisynth+ 64-bit immediately...

[r0lZ]

As promised, here is BD3D2MK3D with support for Avisynth+ 64-bit.

It seems to work fine, but since I have had to modify a lot of things, I may have introduced new bugs, or broken existing features, so this version is a beta. Please test it carefully. In case of problem, you can still download v1.11 here (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D.7z).


v1.12beta2 (September 5, 2019)
- Support for AviSynth+ 32 and 64-bit. It is strongly recommended to install AviSynth+ 64-bit !
- Added the 64-bit version of the AviSynth filters necessary for the conversion to 3D (in toolset\plugins64bit)
- Replaced the old VSFilter 32-bit avisynth plugin with the new and much faster version from the xy-VSFilter Project
- DGMVCSource is now the default MVC decoder again because its 64-bit version is faster than FRIMSource
- Replaced Avs2YUV 0.24 (32-bit) with Avs2YUV 0.24bm2, and added Avs2YUV 64-bit 0.24bm2 (necessary to use AviSynth+ 64-bit with x265 64-bit)
- The Avisynth version is now detected with AVSVersion32/64.exe (Thanks tebasuna51!) and the Help -> Avisynth Version menu has been redesigned.

Download v1.12 beta 2: BD3D2MK3D_v1.12beta2.7z (http://download.videohelp.com/r0lZ/BD3D2AVS/BD3D2MK3D_v1.12beta2.7z)

Of course, to use it, it is strongly recommended to install AviSynth+ (https://github.com/pinterf/AviSynthPlus/releases) 64-bit. However, I would appreciate if someone can test this version before installing Avisynth+ , to check if I have not broken the support for the classic Avisynth 2.6. Also, I have been unable to check this version on a 32-bit PC, so if someone has an antique at home, I would be interested to know if BD3D2MK3D runs still without problem in a 32-bit-only environment.

Thanks in advance. If I don't have negative feedback in a week or so, I will release v1.12 officially.

[tebasuna51]

...So, it will be difficult for me to test NVEnc. Furthermore, I have read often that the quality of the encoding is very bad. So, I'm not sure anymore that I want to implement it...

I can't recommend the encoder, also my cheap nVidia GPU can't work.

I make any test with a powerfull GPU (in gamming PC of my son) and the quality is comparable with Fast presets x264 the is not so interesting for me.

As promised, here is BD3D2MK3D with support for Avisynth+ 64-bit...
Of course, to use it, it is strongly recommended to install AviSynth+ (http://avs-plus.net/) 64-bit.

Thanks for the new version.

Please install AVs+ from GitHub (https://github.com/pinterf/AviSynthPlus/releases) with last stable version r2772, or the last test version r2915 (https://forum.doom9.org/showthread.php?p=1883630#post1883630) in the official Avs+ thread in Doom9

However, I would appreciate if someone can test this version before installing Avisynth+ , to check if I have not broken the support for the classic Avisynth 2.6.

We can install also Avs+, and make easy changes between Avs version, with the Universal Avisynth Installer (https://forum.doom9.org/showthread.php?p=1720988#post1720988) from Groucho2004

[r0lZ]

Indeed, I don't think I'll implement NVEnc. Too much work for a bad result.
Please install AVs+ from GitHub (https://github.com/pinterf/AviSynthPlus/releases) with last stable version r2772, or the last test version r2915 (https://forum.doom9.org/showthread.php?p=1883630#post1883630) in the official Avs+ thread in Doom9
Why ? It seems that http://avs-plus.net/ is the official home of Avisynth+. It may not have the latest beta, but it should have the latest stable version.

Also, honestly, I hate downloading binaries from GitHub. It seems that they like to hide the download. And Avisynth+ is not an exception. I have been unable to find how to download the release for Windows, if it is present. Am I blind ?

[tebasuna51]

Why ? It seems that http://avs-plus.net/ is the official home of Avisynth+. It may not have the latest beta, but it should have the latest stable version.

avs-plus.net is the Home page of 'ultim' the first Avs+ developper, and the owner of the Doom9 thread https://forum.doom9.org/showthread.php?p=1643908

In the first post 'ultim' accept the 'pinterf' fork like next Avs+ developper, there are some other forks (Neo in pool and in Universal Avisynth Installer from Groucho2004) but 'pinterf' versions are accepted now like officials.

You can see also the wiki http://avisynth.nl/index.php/AviSynth+, where avs-plus.net is the original project but the pinterf is the latest relase.

Also, honestly, I hate downloading binaries from GitHub. It seems that they like to hide the download. And Avisynth+ is not an exception. I have been unable to find how to download the release for Windows, if it is present. Am I blind ?

If you scroll down the page until 'Assets 6' you have:

AviSynthPlus-MT-r2772-with-vc_redist.exe 24 MB (installer + M$ libraries)
AviSynthPlus-MT-r2772.exe 4.5 MB (installer)
AvisynthPlus-r2772-MT-filesonly.7z 3 MB
AvisynthPlus-r2772-MT-filesonly.zip 5.27 MB
Source code (zip)
Source code (tar.gz)

[r0lZ]

'pinterf' versions are accepted now like officials.
Yes, it's what I have understood after having discovered that there are several authors. All these forks are somewhat disturbing. I will change the URL for AviSynth+ in BD3D2MK3D.
If you scroll down the page until 'Assets 6' you have: [...]
So, it's official now. I am really blind ! :p

Thanks !

[Sharc]

Indeed, I don't think I'll implement NVEnc. Too much work for a bad result.

Your decision of course, but I found that rigaya's NVEncC constant quality mode (somehow equivalent to x264 CRF mode) produces quite good results with my Pascal GPU, and it is said to be even better with newer Turing GPUs.
So if you should have some spare time it may be worth to do your own testing.

[r0lZ]

The problem is that I don't have a compatible graphic card. And honestly, I don't want to buy a new one. It will therefore be difficult to test if my implementation works correctly. So, if I decide to implement it, I will need the help of someone. You ?

And you tell me that its constant quality is comparable to CRF. OK, but with what CRF value ? For x264, the default is CRF 23, but most users think that it's not sufficient, and use CRF 20 or even lower, down to CRF 16. NVEnc's quality can be compared to CRF 20, lower or higher ?

[tebasuna51]

@Sharc

I think than CRF ([-12-51, default 23.0] Constant Ratefactor. While qp targets a certain quantizer, and bitrate targets a certain filesize, crf targets a certain 'quality'.) is equivalent to rigaya's NVEncC (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--vbr-quality-float):

Constant quality mode can be used by "--vbrhq 0 --vbr-quality <float>".

--vbr-quality <float>

Set target quality when using VBR mode. (0.0-51.0, 0 = automatic)

Maybe you can do some test replacing the encoder in the "__ENCODE_3D.cmd"
For instance if you have:
"C:\Portable\Util\BD3D2MK3D\toolset\x264_x64.exe" --output-depth 8 ^
--crf 23 --preset medium ^
--sar 1:1 --range tv --colormatrix bt709 ^
--frame-packing 3 --qpfile chapters_3D.qpfile --frames 158712 --fps 24000/1001 ^
--output "00009_3D.264" "__ENCODE_3D_MOVIE.avs"

You can change it to
"C:\Portable\Util\BD3D2MK3D\toolset\NVEncC.exe" --output-depth 8 ^
--vbrhq 0 --vbr-quality 23 --bframes 3 --ref 3 --bref-mode each --lookahead 32 --weightp --aq --direct spatial ^
--sar 1:1 --colormatrix bt709 ^
--chapter chapters_3D_delay.ogm.txt --key-on-chapter --fps 24000/1001 ^
-i "__ENCODE_3D_MOVIE.avs" -o "00009_3D.264"
Replacing the path and filenames in bold by yours and the x264 parameters with NVEncC parameters:

--crf 23 maybe can be replaced with --vbrhq 0 --vbr-quality 23
--preset medium is, more or less, equivalent to --bframes 3 --ref 3 --bref-mode each --lookahead 32 --weightp --aq --direct spatial
--range tv seems the default with --fullrange can be equivalent to --range pc
--frame-packing 3 I don't kown the equivalence
--qpfile chapters_3D.qpfile can be replaced by --chapter chapters_3D_delay.ogm.txt --key-on-chapter
--frames 158712 all frames are always the default for NVEncC or x264/x265

[Sharc]

The problem is that I don't have a compatible graphic card. And honestly, I don't want to buy a new one. It will therefore be difficult to test if my implementation works correctly. So, if I decide to implement it, I will need the help of someone. You ?

And you tell me that its constant quality is comparable to CRF. OK, but with what CRF value ? For x264, the default is CRF 23, but most users think that it's not sufficient, and use CRF 20 or even lower, down to CRF 16. NVEnc's quality can be compared to CRF 20, lower or higher ?
My main point was that we should perhaps not be too much discouraged by the "poor quality" reputation of NVEnc alone. The poor reputation of NVEnc is often based on reports from earlier versions and older GPU's. For more recent comparison see for example here (https://forum.doom9.org/showpost.php?p=1881067&postcount=331).
Regarding the quality factor there is no 1:1 relation with x264's CRF, but the same holds for the CRF value between x264 and x265. One has to play with the settings.
I would agree that comparing at the same file size CPU x264/x265 still have the edge, but the say 5 to 10x encoding speed increase of NVEnc (depending on CPU/GPU) is appealing and may compensate the larger filesize for the personally accepted compromise on visual quality.
Anyway, my post was not meant as a feature request. If you should however decide to add NVEnc I would be willing to try it with my Pascal GTX 1050Ti which is - unfortunatley - not the most advanced.

[Sharc]

@Sharc

I think than CRF ([-12-51, default 23.0] Constant Ratefactor. While qp targets a certain quantizer, and bitrate targets a certain filesize, crf targets a certain 'quality'.) is equivalent to rigaya's NVEncC (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--vbr-quality-float):



Maybe you can do some test replacing the encoder in the "__ENCODE_3D.cmd"
For instance if you have:


You can change it to

Replacing the path and filenames in bold by yours and the x264 parameters with NVEncC parameters:

--crf 23 maybe can be replaced with --vbrhq 0 --vbr-quality 23
--preset medium is, more or less, equivalent to --bframes 3 --ref 3 --bref-mode each --lookahead 32 --weightp --aq --direct spatial
--range tv seems the default with --fullrange can be equivalent to --range pc
--frame-packing 3 I don't kown the equivalence
--qpfile chapters_3D.qpfile can be replaced by --chapter chapters_3D_delay.ogm.txt --key-on-chapter
--frames 158712 all frames are always the default for NVEncC or x264/x265
Yes, I did my constant quality encodes with rigaya's NVEnC according to his recommendation (but outside of BD3D2MK3D) and found it to be quite good. Thanks for your hints how to modify "__ENCODE_3D.cmd", so I can try when needed.

Edit:
My NVEncC settings:
--fps 23.976 --codec h264 --profile high --level 4.1 --sar 1:1 --lookahead 24 --vbrhq 0 --vbr-quality 24.00 --max-bitrate 40000 --aq --aq-strength 6 --gop-len 24 --ref 3 --nonrefp --bframes 3 --bref-mode disabled --mv-precision Q-pel --cabac --deblock --preset quality --colormatrix bt709 --bluray

[tebasuna51]

As promised, here is BD3D2MK3D with support for Avisynth+ 64-bit...
Work fine for me.

And yes DGMVCSource seems faster than FRIMSource, with the same sample than before:

encoded 158712 frames, 52.37 fps, 3536.54 kb/s
Encoding finished 08/09/2019 16:17:08,78 -> 50:32,33

And AVSVersion32/64.exe are from Groucho2004, not from me.

[r0lZ]

--frame-packing 3 I don't kown the equivalence
The frame-packing argument is not really necessary. It adds just a flag in the video headers that informs the player of the type of 3D. It is used by my Samsung TV to display the movie in 3D without the need of selecting the 3D mode manually with the remote. But other TVs or players use the stereo-mode of the MKV header or even an extension of the file name (such as "SBS") to do the same thing. So, the utility of the --frame-packing argument depends of your player. It is better, of course, to include it anyway, but if it is not present, the worse thing that can happen is that you will have to press a button on the remote when the movie begins.
--frames 158712 all frames are always the default for NVEncC or x264/x265
This argument is not mandatory either. It is used only by x264 and x265 to display the progress % in the title bar of the command prompt window when the encoding is in progress. You can therefore safely omit it, but an important info will be missing.

[r0lZ]

Anyway, my post was not meant as a feature request. If you should however decide to add NVEnc I would be willing to try it with my Pascal GTX 1050Ti which is - unfortunatley - not the most advanced.
OK, I can admit that a fast encoding can be a good thing, even if the quality is a bit less good. But for me, it will be difficult to check the arguments without the possibility to actually launch the encoding. It's my main concern. But if tebasuna51 or you can help me to build and check a few command lines (corresponding roughly to the different encoding methods of x264), and then test them, I can probably add NVEnc in BD3D2MK3D.

Another method would be to just add the possibility to encode with NVEnc, with just the simpler arguments automatically added (such as the --chapter and --key-on-chapter arguments) and a large text field where the user will have to type the other arguments, related to the encoding mode and quality, under his own responsibility. I can add two buttons to save and load these arguments, so that you can easily define several presets. For me, that will be much easier, as I will have nothing to test, and the user will have to do the hard work without any help. And if some of your presets are really good, I can perhaps add them in the BD3D2MK3D code later, as hardcoded presets for the novice users.
Is it OK for you ?

[r0lZ]

Work fine for me.

And yes DGMVCSource seems faster than FRIMSource, with the same sample than before:
Thanks for that confirmations.
And AVSVersion32/64.exe are from Groucho2004, not from me.
I know that, but you have pointed me to the right direction.

[tebasuna51]

...But if tebasuna51 or you can help me to build and check a few command lines (corresponding roughly to the different encoding methods of x264), and then test them, I can probably add NVEnc in BD3D2MK3D.

My cheap (and silent without fan's) GPU, GeForce GT 1030 can decode but not encode, check here (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix) the ability of GPU's to do so, but maybe I can do some test with the GTX 1060 of my son.

Make test and change parameters is very easy editing your __ENCODE_3D.cmd file befor launch __ENCODE_3D_LAUNCHER.cmd, it is not necesary add nothing to BD3D2MK3D.

[sneaker_ger]

To do it "right" you would need to check for compatible hardware and its features. Features differ not only by hardware but also by codec. (Not that I suggest it must be done "right". Some basic integration with letting the user handle the rest is fine.)
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--check-device
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--check-hw-int
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--check-features-int

For me:
nvencc64 --check-device
DeviceId #0: GeForce GTX 1660 Ti

nvencc64 --check-hw
NVEncC (x64) 4.45 (r1169) by rigaya, Aug 19 2019 11:47:02 (VC 1916/Win/avx2)
[NVENC API v9.0, CUDA 10.1]
reader: raw, avi, avs, vpy, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1,
MPEG1, MPEG4]
Loaded nvEncodeAPI64.dll.
InitCuda: device #0.

Checking Environment Info...
NVEncC (x64) 4.45 (r1169) by rigaya, Aug 19 2019 11:47:02 (VC 1916/Win/avx2)
OS Version Windows 7 x64 (7601)
CPU Intel Core i5-2500K @ 3.30GHz [TB: 3.70GHz] (4C/4T)
GPU #0: GeForce GTX 1660 Ti (431.60)
NVENC / CUDA NVENC API 9.0, CUDA 10.1, schedule mode: auto
cuInit: Success.
cuDeviceGetCount: Success.
cuDeviceGet: ID:0.
cuDeviceComputeCapability: Success: 7.5.
NVENC capabilities: OK.
using cuda schedule mode: auto.
cuCtxCreate: Success.
cuCtxPopCurrent: Success.
cuvidInit: Success.
cuvidCtxLockCreate: Success.
InitCuda: Success.
nvEncodeAPICreateInstance(APIVer=0x70020009): Success.
NvEncOpenEncodeSessionEx(device_type=NV_ENC_DEVICE_TYPE_CUDA): Success.
nvEncDestroyEncoder: success.
Closing perf monitor...
Avaliable Codec(s)
H.264/AVC
H.265/HEVC

nvencc64 --check-features
NVEncC (x64) 4.45 (r1169) by rigaya, Aug 19 2019 11:47:02 (VC 1916/Win/avx2)
[NVENC API v9.0, CUDA 10.1]
reader: raw, avi, avs, vpy, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1,
MPEG1, MPEG4]

Environment Info
OS : Windows 7 x64 (7601)
CPU: Intel Core i5-2500K @ 3.30GHz [TB: 3.70GHz] (4C/4T)
RAM: Used 4099 MB, Total 16337 MB
GPU: #0: GeForce GTX 1660 Ti (1536 cores, 1875 MHz)[PCIe2x16][431.60]

List of available features.
Codec: H.264/AVC
Max Bframes 4
B Ref Mode yes
RC Modes 63
Field Encoding no
MonoChrome no
FMO no
Quater-Pel MV yes
B Direct Mode yes
CABAC yes
Adaptive Transform yes
Max Temporal Layers 0
Hierarchial P Frames no
Hierarchial B Frames no
Max Level 51
Min Level 1
4:4:4 yes
Max Width 4096
Max Height 4096
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding yes
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 65536
Lossless yes
SAO no
Me Only Mode yes
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
Max LTR Frames 8
10bit depth no

Codec: H.265/HEVC
Max Bframes 5
B Ref Mode yes
RC Modes 63
Field Encoding no
MonoChrome no
Quater-Pel MV yes
B Direct Mode no
Max Temporal Layers 0
Hierarchial P Frames no
Hierarchial B Frames no
Max Level 62
Min Level 1
4:4:4 yes
Max Width 8192
Max Height 8192
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding no
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 262144
Lossless yes
SAO yes
Me Only Mode yes
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
Max LTR Frames 7
10bit depth yes

[Sharc]

OK, I can admit that a fast encoding can be a good thing, even if the quality is a bit less good. But for me, it will be difficult to check the arguments without the possibility to actually launch the encoding. It's my main concern. But if tebasuna51 or you can help me to build and check a few command lines (corresponding roughly to the different encoding methods of x264), and then test them, I can probably add NVEnc in BD3D2MK3D.

Another method would be to just add the possibility to encode with NVEnc, with just the simpler arguments automatically added (such as the --chapter and --key-on-chapter arguments) and a large text field where the user will have to type the other arguments, related to the encoding mode and quality, under his own responsibility. I can add two buttons to save and load these arguments, so that you can easily define several presets. For me, that will be much easier, as I will have nothing to test, and the user will have to do the hard work without any help. And if some of your presets are really good, I can perhaps add them in the BD3D2MK3D code later, as hardcoded presets for the novice users.
Is it OK for you ?
Thanks for your goodwill and proposals. It would be certainly OK for me, but unless there is a broader demand don't do anything just for me. I can get along with manual modifications as per tebasuna' hints. I am afraid that you would risk to be flooded with questions from potential users who experience some problems with their HW/GPU or are otherwise dissatisfied. You may not be able to help as you can't replicate the issues with your HW. You may just open a can of worms and you wouldn't do a favour to yourself and to your great software.
Maybe time will tell whether there is a real or broader demand for NVEnc. Thanks again. :)

[tebasuna51]

Using my son PC:

nvencC64 --check-features
NVEncC (x64) 4.47 (r1188) by rigaya, Sep 1 2019 06:07:40 (VC 1916/Win/avx2)
[NVENC API v9.0, CUDA 10.1]
reader: raw, avi, avs, vpy, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1, MPEG1, MPEG4]

Environment Info
OS : Windows 10 x64 (18362)
CPU: Intel Core i5-6400 @ 2.70GHz [TB: 3.09GHz] (4C/4T)
RAM: Used 2459 MB, Total 8119 MB
GPU: #0: GeForce GTX 1060 6GB (1280 cores, 1784 MHz)[PCIe3x16][436.15]

List of available features.
Codec: H.264/AVC
Max Bframes 4
B Ref Mode yes
RC Modes 63
...
10bit depth no

Codec: H.265/HEVC
Max Bframes 0
B Ref Mode no
...
10bit depth yes

Encoding the same sample:

"NVEncC64.exe" --output-depth 8 --vbrhq 0 --vbr-quality 23 --preset quality --bframes 3 --ref 3 --bref-mode each --lookahead 32 --weightp --aq --direct spatial --sar 1:1 --colormatrix bt709 --chapter chapters_3D_delay.ogm.txt --key-on-chapter --fps 24000/1001 -i "__ENCODE_3D_MOVIE.avs" -o "00009_3D.264"
weighted prediction with B frames unsupported.
NVEncC (x64) 4.47 (r1188) by rigaya, Sep 1 2019 06:07:40 (VC 1916/Win/avx2)
OS Version Windows 10 x64 (18362)
CPU Intel Core i5-6400 @ 2.70GHz [TB: 3.29GHz] (4C/4T)
GPU #0: GeForce GTX 1060 6GB (1280 cores, 1784 MHz)[PCIe3x16][436.15]
NVENC / CUDA NVENC API 9.0, CUDA 10.1, schedule mode: auto
Input Buffers CUDA, 44 frames
Input Info Avisynth+ 2.60(yv12)->nv12 [AVX2], 1920x1080, 24000/1001 fps
Vpp Filters copyHtoD
Output Info H.264/AVC high @ Level auto
1920x1080p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control VBRHQ
Bitrate 0 kbps (Max: 24000 kbps)
Target Quality 23.00
Initial QP I:20 P:23 B:25
VBV buf size auto
Lookahead on, 32 frames, Adaptive I, B Insert
GOP length 240 frames
B frames 3 frames [ref mode: each]
Ref frames 3 frames, LTR: off
AQ on(spatial, strength auto)
Others mv:auto cabac deblock adapt-transform:auto bdirect:spatial
encoded 158712 frames, 71.31 fps, 8429.56 kbps, 6651.93 MB
encode time 0:37:05, CPU: 60.5%, GPU: 5.9%, VE: 24.6%, GPUClock: 1674MHz, VEClock: 1505MHz
frame type IDR 671
frame type I 671, total size 110.00 MB
frame type P 42468, total size 3410.40 MB
frame type B 115573, total size 3131.54 MB

Encoding finished 09/09/2019 15:25:54,18 -> 37:08,76

Of course is fast but not to much with parameters like x264 defaults
(with x264 default weightp is mode 2 and lookahead 40).

But the bitrate obtained is near double, maybe the crf equivalence is not the same number.

[Sharc]

Of course is fast but not to much with parameters like x264 defaults
(with x264 default weightp is mode 2 and lookahead 40).

But the bitrate obtained is near double, maybe the crf equivalence is not the same number.
Hmmm, I guess that the encoding speed is probably reduced (halved) by the resizing script (for 3D SBS arrangement).
I think the CRF equivalence is not the same. One has to experiment. How does your NVEncC encode look visually compared with CPU x264?

[r0lZ]

OK, since v1.12beta2 seems to work fine, here is the official release of v1.12.

Nothing has changed, except the version number, the URL to AviSynth+, and a small change in the dialog about the avs2yuv version (to take Avisynth 64-bit into account).

v1.12beta2 (September 5, 2019)
- Support for AviSynth+ 32 and 64-bit. It is strongly recommended to install AviSynth+ 64-bit !
- Added the 64-bit version of the AviSynth filters necessary for the conversion to 3D (in toolset\plugins64bit)
- Replaced the old VSFilter 32-bit avisynth plugin with the new and much faster version from the xy-VSFilter Project
- DGMVCSource is now the default MVC decoder again because its 64-bit version is faster than FRIMSource
- Replaced Avs2YUV 0.24 (32-bit) with Avs2YUV 0.24bm2, and added Avs2YUV 64-bit 0.24bm2 (necessary to use AviSynth+ 64-bit with x265 64-bit)
- The Avisynth version is now detected with AVSVersion32/64.exe (Thanks tebasuna51!) and the Help -> Avisynth Version menu has been redesigned.

v1.12 (September 11, 2019)
- Changed the URL to the AviSynth+ download location to https://github.com/pinterf/AviSynthPlus/releases

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

[tebasuna51]

Thanks r0lZ for the new final version.

About NVEnc I think than advanced users with powerfull GPU's can make tests for fastest encodes, but this thread in not the place to compare encoders.
Also x264/x265 can be tunned with many parameters to obtain more quality or fast encodes at user taste.

@Sharc
I don't see better quality (maybe there are some) with the NVEncC encode at double bitrate, BD3D2MK3D need the avs like this and maybe is not the recommended to compare encoders.

In my test with GTX 1060 6GB (275 € now in Amazon) the GPU usage was 25% and CPU 75%, maybe can be improved. But can't encode to HEVC with B frames (the GTX 1660 Ti from sneaker_ger can do it). I think than we need know the GPU to make the specific command line.

Maybe with a GeForce RTX 2080 Ti FTW3 (1400 €) a user want a return on their investment and use it to encode.
With my GT 1030 (70 €) I need use x264/x265.

[r0lZ]

Thanks r0lZ for the new final version.

About NVEnc I think than advanced users with powerfull GPU's can make tests for fastest encodes, but this thread in not the place to compare encoders.
Completely agree. I don't want to spend much time in testing various encoders. It's why I prefer to just add a way for the user to use any other encoder, without limitation. He will be alone for testing it, and I will have nothing to check or debug, except perhaps fix a bug in my code. And this thread will still be devoted to BD3D2MK3D only.

And thanks for the thanks. ;-)

[r0lZ]

As promised, here is BD3D2MK3D with the possibility to use any encoder, by providing yourself the command line to use. This feature should be used only if you know what you are doing. Novice users should continue to encode with x264 (or x265).

Use this possibility at your own risk. BD3D2MK3D simply copies the command YOU have defined to the encoding script (after having substituted some variables). It is therefore not responsible if something goes wrong. I will NOT provide any help for your custom command lines. If necessary, contact the support of your encoder.

Also, do NOT use this thread to post your custom commands, working or not. If you want to exchange your commands with other peoples, open a new thread, and if necessary, post a link here. Thanks !

Of course, I will fix any bug related to the custom encoder, if it is dependent of my code, but don't expect more.

v1.13 (September 16, 2019)
- Added the possibility to encode the 3D movie with any encoder by providing yourself the command line to use.

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

[bottom]

I would appreciate if someone can test this version before installing Avisynth+ , to check if I have not broken the support for the classic Avisynth 2.6.

Yep, seems to be broken:

Was using BD3D2MK3D from v0.7* till v1.11 without any issues;
after updating to latest v1.13 the 3D encoding script fails
because Avisynth was "not found" ...

=> I'm on Win10, 64bit, but have only installed Avisynth "classic" so far


ps
Does anyone know a Howto article
for the manual installation of Avisynth+?
(The executable installers tend to simply ignore and override any existing installations/settings)

[tebasuna51]

@bottom

The message: Avisynth was "not found" ... was before install Avisynth+?

Please run AVSMeter (https://forum.doom9.org/showthread.php?t=174797) avsinfo and put the output.

About manual installation of AviSynth read Universal Avisynth Installer (http://forum.doom9.org/showthread.php?t=172124)

[bottom]

@tebasuna51

just did what r0lZ asked for:
I've tried to use the new BD3D2MK3D version before installing Avisynth+

(The classic Avisynth is (still) properly installed
and BD3D2MK3D v1.11 working fine with it)

[r0lZ]

Indeed, the new version uses AVSVersion32.exe to check if avisynth 32-bit is installed. Previously, BD3D2MK3D did only a basic check to see if AviSynth.dll is present in the system32 or SysWOW64 directory. So, if the current check fails, it's probably due to a limitation or bug in AVSVersion32. It is used also by the About -> AviSynth Version menu to show the version number of the installed 32 and 64-bit AviSynth.

Can you open a Command Prompt window and launch AVSVersion32.exe, located in the BD3D2MK3D\toolset folder (you can simply drag and drop it from the BD3D2MK3D\toolset folder over the Command Prompt window and hit Enter). Then, copy and paste here the output of the command. Also, can you tell me if you have installed AviSynth classic with its installer, or manually ? In the second case, it is possible that it's the cause of the problem. Thanks!

In the meantime, I will uninstall AviSynth+ and re-install the classic version, to see if I can reproduce the problem.

[r0lZ]

ps
Does anyone know a Howto article
for the manual installation of Avisynth+?
(The executable installers tend to simply ignore and override any existing installations/settings)
IIRC, when you install it, the installer offers to select only one of the two versions (32 or 64-bit). I suppose that if you select only the 64-bit version, it will leave the classic version untouched.

It is not possible to install two different versions at the same time for the same CPU (32/64-bit), but if you want to be able to return easily to the clessic version AND you want to check also the 32-bit avisynth+, use the universal installer, as suggested by tebasuna51. (Honestly, I have not used it myself, so I can't guarantee that it works well.)

[r0lZ]

OK, I did some tests.

There was a little bug in my code, but that bug should not have any impact, except on some warning messages. When the 32 or 64-bit version of AviSynth is not installed, the message in the About -> AviSynth Version dialog was wrong. Instead of "AviSynth **-bit is not installed", the message was "This version of AviSynth **-bit is not supported by BD3D2MK3D. Use it at your own risk." And I suppose (but I have not tested) that the first warning dialog appearing on startup when no AviSynth at all is found was not shown. But anyway, that bug is not related to the problem you have reported. In the worst case, it was possible to generate a project without knowing that it cannot be launched. Of course, I have fixed that bug, but I don't think I'll release a new version just for that little problem. (The dialogs below have been generated after the bug fix.)

That being said, here is a description of my tests.

I have first uninstalled AviSynth+. The uninstaller has correctly restored my old AviSynth classic, and it has been correctly recognized by BD3D2MK3D.

Then, I have uninstalled AviSynth classic. No problem, but of course, BD3D2MK3D cannot work. However, the dialog telling that AviSynth is required was not shown at startup, due to the bug explained above.

Finally, I have re-installed the classic version. There is now only a warning in the status bar and the log window explaining that AviSynth+ 64-bit is recommended on a 64-bit system. And the About -> AviSynth Version menu shows this:

---------------------------
BD3D2MK3D
---------------------------
AviSynth 32 Bit: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (2.6.0.6)
This is the last stable version of the "classic" AviSynth, not developed any more.
There is nothing to update.

AviSynth 64 Bit: n/a
AviSynth 64-bit is not installed.

Please note that AviSynth+ 64-bit is much faster than the currently installed version of AviSynth 32-bit. It is strongly recommended to install at least the 64-bit version of AviSynth+.

Visit download pages for AviSynth classic and AviSynth+ ?
---------------------------
Yes No
---------------------------

So, it seems that AVSVersion32.exe does its job correctly, and if it doesn't recognise your installation, it's probably because it has been installed manually and that something is missing or wrong. I suggest to re-install AviSynth classic with its installer, and everything should be fine.

Finally, I have installed AviSynth+ 64-bit ONLY, and as I suspected, the classic installation has not been modified:

---------------------------
BD3D2MK3D
---------------------------
AviSynth 32 Bit: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (2.6.0.6)
This is the last stable version of the "classic" AviSynth, not developed any more.
There is nothing to update.

AviSynth 64 Bit: AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)
AviSynth+ 64-bit is supported by BD3D2MK3D.

Visit download pages for AviSynth classic and AviSynth+ ?
---------------------------
Yes No
---------------------------


So, it seems that everything works fine. Please let me know if you find the origin of the problem. Perhaps your classic AviSynth.dll is not in Windows\SysWOW64 (where it should be installed on a 64-bit system) ?

[tebasuna51]

There was a little bug in my code, but that bug should not have any impact, except on some warning messages.

Confirmed but without operative problems.

So, it seems that AVSVersion32.exe does its job correctly, and if it doesn't recognise your installation, it's probably because it has been installed manually and that something is missing or wrong.

Yes, for that I request AVSMeter avsinfo, than can detect installation problems.

Install AviSynth (on W 64 bits) manually have two passes:

1) Copy avisynth.dll (and devil.dll) in the appropiate system folder
- the 64 bit version in %WINDIR%\System32
- the 32 bit version in %WINDIR%\SysWow64

2) Add/modify some windows registry keys.
to see the detail please read setavs.bat from Universal Avisynth Installer

If you run setavs.bat the installed versions are show and eleven options are presented. Here are the options and the AvsInfo32/64 output after executed each option:

Installed Avisynth version(s):

32 Bit: AviSynth+ 0.1 (r2772, MT, i386) (0.1.0.0)
64 Bit: AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)

Select the Avisynth version you want to install (or uninstall):
setavs options AVSVersion32/64 output
-------------------------------------------------------- ------------------------------------------------------------------------
1 = Avisynth 2.5.8 (official release) 32 Bit: Avisynth 2.5.8.5
2 = Avisynth 2.6.0 (official release) 32 Bit: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (2.6.0.6)
3 = Avisynth 2.6.0 (built with Intel C/C++ compiler) 32 Bit: AviSynth 2.60 (ICL10) (2.6.0.6)
4 = Avisynth 2.6.1 (Alpha) 32 Bit: AviSynth 2.61, build:May 17 2016 [16:06:18] VC2008Exp (2.6.1.0)
5 = Avisynth 2.6.0 (SEt's multi-threaded build) 32 Bit: AviSynth 2.60, build:Feb 20 2015 [03:16:45] (2.6.0.5)
6 = Avisynth+ 0.1.0 (x86, r2772) 32 Bit: AviSynth+ 0.1 (r2772, MT, i386) (0.1.0.0)
7 = Avisynth+ 0.1.0 (x64, r2772) 64 Bit: AviSynth+ 0.1 (r2772, MT, x86_64) (0.1.0.0)
8 = Avisynth Neo 0.1.0 (x86, r2822) 32 Bit: AviSynth Neo 0.1 (r2822, Neo, i386) (0.1.0.0)
9 = Avisynth Neo 0.1.0 (x64, r2822) 64 Bit: AviSynth Neo 0.1 (r2822, Neo, x86_64) (0.1.0.0)

10 = Uninstall Avisynth x86 32 Bit: n/a
11 = Uninstall Avisynth x64 64 Bit: n/a


All versions must run with BD3D2MK3D.

Note: the setavs.bat from Universal Avisynth Installer must be configured to define the autoload plugin directory of each version, but is not important for BD3D2MK3D because all plugins are loaded explicitely.

[bottom]

Thanks for the elaborate replies and the tips for AvisynthPlus!!!

Really don't want to complain, just wanted to inform about my experience …

Thus here is (hopefully) all the info you have requested (and more):

• 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'

• Here's the AVS-script created by BD3D2MK3D v1.13, which is mentioned in the error above, maybe it's helpful:
(...)
#LoadPlugin("F:\Video\BD3D2MK3D\toolset\plugins64bit\FRIMSource.dll")
LoadPlugin("F:\Video\BD3D2MK3D\toolset\plugins64bit\DGMVCDecode.dll")

##LoadPlugin(F:\Video\BD3D2MK3D\toolset\plugins64bit\VSFilter.dll")
#LoadPlugin("F:\Video\BD3D2MK3D\toolset\plugins64bit\SupTitle.dll")

# Load the two video streams (197643 frames per stream)
#interleaved = FRIMSource("mvc", "00053.track_4113.264", "00053.track_4114.mvc", layout = "alt", num_frames = 197643, cache = 2, platform = "sw")
interleaved = DGMVCSource("00053.track_4113.264", "00053.track_4114.mvc", view = 0, frames = 197643, mode = "sw")
# Current base view: left eye.
# The views are in the common order: AVC stream = left view, MVC stream = right view.
left = SelectEven(interleaved)
right = SelectOdd(interleaved)

# Build Side-by-Side stream
StackHorizontal(HorizontalReduceBy2(Left), HorizontalReduceBy2(Right))
AssumeFPS("ntsc_film")

# Hardcode subtitles
##VobSub(".sub")
#SupTitle(".sup")

# Return the 3D clip.
Return(last)#.Info()


• The Avisynth info dialog of BD3D2MK3D v1.13 showed up exactly as r0lZ has noted. The version shown is the same as displayed by AVSVersion32 ...

• Here's the output of „AVSVersion32“:
C:\Windows\System32>F:\Video\BD3D2MK3D\toolset\AVSVersion32.exe
32 Bit: AviSynth 2.60, build:Sep 18 2013 [17:36:36] (2.6.0.4)

• My old Avisynth 2.6.0 was (I think) installed „manually“, which means:
Both a pre-build batch- and reg-file were executed
for which only the directory of the DLLs had to be entered manually …
(Maybe there was something wrong or missing with this process,
but didn't have any problems until v1.13.)


Give me a note if you want further details ...
... or otherwise just tell me to install Avisynth+

:)

[tebasuna51]

Thanks for the elaborate replies and the tips for AvisynthPlus!!!

My replies and soft recommended are valid for all AviSynth versions, not only Avs+

...
LoadPlugin("F:\Video\BD3D2MK3D\toolset\plugins64bit\DGMVCDecode.dll")
...
BD3D2MK3D think than you have a Avisynth 64 bits installed.

It's a bug, because BD3D2MK3D 1.13 make a .avs for 64 bits when Avs+64 is not installed.

I can reproduce the bug, with:
32 Bit: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (2.6.0.6)
64 Bit: n/a

BD3D2MK3D 1.13 make a .avs loading plugins from plugins64bit folder and
a __ENCODE_3D.cmd with directly x264_x64.exe