Hello guest, if you like this forum, why don't you register? https://fanrestore.com/member.php?action=register (December 14, 2021) x


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
x264: 32bit or 64bit?
#11
I tried the last and the one before the last, no way to let it work... I'm tired, and lazy, so I downloaded the Simple x264 Launcher, using the "usual" parameters. Encoding right now; indexing is fast - indeed, it seems too fast... Big Grin - second pass is lightning fast as well, around 23fps where I was around 1fps and something on the old PC, hence 15, 20 times faster now...

What can I say? I'm happy! Happy
Reply
Thanks given by:
#12
That is a significant increase in speed Andrea. I'm happy for you too Wink Big Grin
Reply
Thanks given by:
#13
Yep, a definitive quantum leap! Big Grin

x264 64bit is slightly faster than 32bit, but not that much; I noted that, with a two pass encoding, it takes around 3 times the clip lenght, so for The Thing (109min) it took around 6 hours. Not bad, considering it would take two days (and more) with the old PC!!!

Now, time to upgrade to a new internet connection - fiber, here I come! Ok
Reply
Thanks given by:
#14
(2017-02-22, 11:40 AM)spoRv Wrote: Well, I use Simple x264 Launcher every time, apart for final official release;

What do you use for final official release?
Reply
Thanks given by:
#15
(2017-02-22, 09:38 AM)Valeyard Wrote: 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.

Can you give me a cli example of this? I use avs2yuv without pipebuf and it works pretty well but maybe pipebuf works better?

Here's an example of how I would do it only using avs2yuv:

Code:
avs2yuv -raw -o - "input.avs" | x264_64 --input-res 720x480 --fps 24000/1001 --preset=veryslow --crf 14 --ref 3 --bframes 2 --tune film --keyint 250 --sar 40:33 --colorprim "smpte170m" --transfer "smpte170m" --colormatrix "smpte170m" --stats ".stats" --output "output.mkv" -

If simple x264 launcher works as well as you say I might switch over to it. Thanks for the tip!
Reply
Thanks given by:
#16
I use 64 bit x264 for some things unless I'm feeling lazy and want to feed the AVisynth straight into x264.

Another way to get it to work is avfs, which creates avi-files on your C-drive that represent your AVISynth script. Fake uncompressed AVIs basically. You can load those into anything. For example you can open them in ffmpeg, apply a 3D LUT, then pipe the result into 64 bit x264. Smile

Not sure if I noticed much speed increase, I haven't actually looked. I mainly wanted it to use more RAM, as 32 bit is always restricted to 2 GB and I have 32 GB on my PC. I imagine that makes it a bit faster.
Reply
Thanks given by:


Possibly Related Threads…
Thread Author Replies Views Last Post
Thumbs Up x264 BD compliant "perfect" settings spoRv 150 183,019 2023-09-16, 10:08 PM
Last Post: DoomBot
  xvYCC for x264 nightstalkerpoet 10 7,563 2023-03-15, 10:42 PM
Last Post: Falcon
  x264 - filesize output calculator for 2-pass and CRF ? loa 7 4,352 2020-08-05, 10:30 PM
Last Post: spoRv
  [Idea] x264 BD compliant "perfect" settings - faster version spoRv 26 18,614 2020-05-11, 08:36 PM
Last Post: Stamper
  x264 encoding from Adobe Premiere DoomBot 26 17,734 2019-03-25, 08:26 PM
Last Post: jaminmc
  Tools and settings for compressing x264? NeonBible 1 2,299 2019-01-11, 12:01 PM
Last Post: MrBrown
  [Help] DNxHR to x264? Valeyard 2 2,903 2018-12-26, 10:16 AM
Last Post: deleted user
  Avisynth: multithreading, 64bit and more spoRv 2 4,225 2017-03-11, 03:31 PM
Last Post: spoRv

Forum Jump:


Users browsing this thread: 1 Guest(s)