x264 progress indication

[Warpman]

Simple - it used to decode streams containing x264 encoded video
in AviSynth script (via DirectShowSource)

this makes no sense at all

[Chabb]

this makes no sense at all

What makes sense then? Tell me please.

[Warpman]

What makes sense then? Tell me please.
Well how should coreavc that runs to decode a file via directshowsource interfere with the cmd window that x264 uses?

[Inventive Software]

It depends on how CoreAVC interfaces with other windows generally. Does it interfere when you run something else in the console, for example?

[Chabb]

Well how should coreavc that runs to decode a file via directshowsource interfere with the cmd window that x264 uses?

I don't know how exactly they can interfere, but here are the facts:
when CoreAVC 1.8.0.0 used - the bug appears
when older CoreAVC used - no bug
when FFDShow used - no bug

Think whatever you want. :)

[Chabb]

It depends on how CoreAVC interfaces with other windows generally. Does it interfere when you run something else in the console, for example?

When x264 encoding runs in console with CoreAVC 1.8.0.0 as decoder,
there is something wrong with task priorities or something like that:
all other non-console windows are functioning well
(especially when x264 task runs in lower priority)
but nothing happens when in the same time
I'm trying to open another empty console window
(and the task of new console is present)

And I think it's not the right thread to continue this discussion

[Quark.Fusion]

Do you get 100% cpu usage on encode? And other way to do that is with frameserving (TCPserver or AVFS), but that eats some cpu time. (I using that on preprocessing to solve problem with 2GB virtual memory limit)

And yes, it's not the right thread to continue this discussion as x264 is unrelated to that behaviour. Sorry for my post.

Try --verbose instead of --progress — will it freeze?

[Chabb]

Do you get 100% cpu usage on encode? And other way to do that is with frameserving (TCPserver or AVFS), but that eats some cpu time. (I using that on preprocessing to solve problem with 2GB virtual memory limit)

And yes, it's not the right thread to continue this discussion as x264 is unrelated to that behaviour. Sorry for my post.

Try --verbose instead of --progress — will it freeze?

I'm getting almost 100% CPU usage usually.
I'll better try to change decoder, because x264 obviously "not guilty",
but thanks.