I'm aware that direct avisynth 32bit -> x264 64bit encoding is not possible - but there are some workarounds for this; not so important, as I always encode lossless before.
x264 64bit seems a lot faster than 32bit - from 10%, to 40% and more with slow settings. I can't see anything that may lead me to NOT use the 64bit version; or, at the contrary, there are problems in the 64bit in comparison to 32bit?
(2017-02-21, 04:55 PM)spoRv Wrote: are there problems in the 64bit in comparison to 32bit?
Yes, don't use its latest version! https://forum.fanres.com/thread-1265.html
Aside from that, why would you even dream of using 32-bit now that you have that monstrous 64-bit CPU? 
(This post was last modified: 2017-02-21, 05:03 PM by Evit.)
(2017-02-21, 05:01 PM)Evit Wrote: Yes, don't use its latest version! https://forum.fanres.com/thread-1265.html
Indeed I wat thinking the same; but, how many previous versions should I skip?
(2017-02-21, 05:01 PM)Evit Wrote: Aside from that, why would you even dream of using 32-bit now that you have that monstrous 64-bit CPU?
Because, for example, Avisynth 64bit doesn't work with 32bit plugins - which are the larger part of the available ones. But I think it seems not a problem for x264.
I don't know your usual workflow but if it's only about converting a finished uncompressed avi into BD compliant x264 then I imagine all the work on video has been done prior to producing the avi.
About the version, try go back one release (can't find the list of previous release right now) or download the one that was shared in that thread.
(This post was last modified: 2017-02-21, 06:15 PM by Evit.)
I really don't know why you guys don't use simple x264 launcher. You have full control over the options, and it's a lot better than typing it into the command line.
The x64 version is good if you are using x264's internal frame server (I probably needs to be an older version, but I can't remember how old or what the conditions are that you need to switch to it. There was a long discussion on BD Rebuilder's thread at one point about a speed issue. The problems might even be fixed by now.). If you are not using the internal frame server, then switching to 64-bit avisynth can be a bit sketchy. IIRC it isn't really official, completely stable and all your plugins must be 64-bit.
Best bet if you work losslessly then create your finished lossless file and then encode to x264 using the x64 version.
(This post was last modified: 2017-02-22, 08:13 AM by Doctor M.)
This is why I keep saying use Simple x264 Launcher - it will use the x64 version of x264 with the x86 version of Avisynth. It uses avs2yuv as the frameserver. To do it on the command-line you need to pipe the output using pipebuf or similar.
Well, I use Simple x264 Launcher every time, apart for final official release; I have always the sensation that any GUI/intermediate programs adds or modifies something... but probably I'm wrong... anyway, it's a very nice piece of software - even if I was not able to let it work with avisynth->x265 until now!
Time to try x264 64bit: I'm impavid tonight, so I would try the latest revision found here: http://download.videolan.org/pub/x264/binaries/win64 - I'll post results in this thread.
r2705 works good, r2744 was the messed up one. r2762 is new (30th Jan), perhaps they fixed it, I haven't tried it out yet.
|
