Piping 16 bit -> x264 10bit (Piping Slow?)

[zerowalker]

Okay not sure if this is the right place, but anyway.

Thing is, i have videos that are at 16bit, they have been filtered and all that and saved to that bit depth as a new avi file.

Then i use a normal Avisource script to feed that to x264 10bit using Megui.

The settings tell that it's 16bit , and it's automated 2 pass.

So the thing that confuses me is that the first pass is Very Slow.

Now, the preset is Very Slow, but that's not what i mean here, it's slow, first pass should be super fast compared to second pass.

When i look at Task Manager, avs4x264mod takes about 60% CPU (quad core), while x264 takes around 5%.

My first guess was, can it be the HDD as the files are big?
But nothing to report there.

So i am wondering, why is it so slow, what resources does the avs piping take that leaves x264 behind. The script should only be decoding as the file is pre-filtered and done.

Thanks

[colours]

Is your "new avi file" raw or losslessly compressed?

It's quite possible for some of the slower lossless formats to require more CPU resources than x264's first pass (which is by design fast, unless you use --slow-firstpass).

[zerowalker]

it's lossless, MagicYUV.

Decoding can't be the issue, it can clearly play realtime using about 7% CPU (4 cores) which is 30fps.

Megui/x264 is at 10-11fps, which seems extremely slow.

program --preset veryslow --pass 2 --bitrate 200 --stats ".stats" --colormatrix bt470bg --input-depth 16 --input-res 640x480 --output "output" "input"

slow first pass is NOT checked.

As you can see, there is really nothing special here. And x264 can't be at fault as it's the piping that's slow.
So it's either Decoding (which i doubt), the Script (nothing there except Avisource?) or the HDD (it barely reads anything).

So, i am confused:(

[zerowalker]

Okay solved it. It was just me confusing two folders, both had the same name and i didn't check the path, so i accidentally used the script for the "new avi", so it did the entire script thing, which explains the CPU usage.

Like 99% of my posts are my own mistakes -_-

Thanks though:)