VSPipe disc I/O writes?

[asarian]

Why does VSPipe use disc I/O? (At least it shows up heavily in the 'I/O Writes' section of the Task Manager). Pipes shouldn't use discs, should they?!

Reason I ask, is because VS is installed on my SDD, and I've been careful not to to any vide-encoding on the SSD itself. Or so I thought. And now VSPipe seems to write to disc, after all.

And x264 doesn't accept vpy scripts directly (at least not that I know of).

N.B. Could just be the Task Manager marks pipes as disc I/O, but I just like to be sure.

Thanks.

[Myrsloik]

Why does VSPipe use disc I/O? (At least it shows up heavily in the 'I/O Writes' section of the Task Manager). Pipes shouldn't use discs, should they?!

Reason I ask, is because VS is installed on my SDD, and I've been careful not to to any vide-encoding on the SSD itself. Or so I thought. And now VSPipe seems to write to disc, after all.

And x264 doesn't accept vpy scripts directly (at least not that I know of).

N.B. Could just be the Task Manager marks pipes as disc I/O, but I just like to be sure.

Thanks.

It doesn't use it unless you output to a file. Look at the source code yourself if you don't believe it.

[asarian]

It doesn't use it unless you output to a file. Look at the source code yourself if you don't believe it.

Oh, I believe you. Just not so sure about Windoze, though. :) I read that, especially with frame-seeking, Windows pipes can start to use disc I/O after all.