MP_Pipeline and Win10

[gispos]

I can't get MP_Pipeline to work on Win10.
What does M_Pipeline need? I installed all runtime files. I think.
I installed 2, 3.5 and the latest 4 of the net framework.

Is there still something missing? Framework 1?

There is no error message and only one MP_pipeline.dll.slave.exe can be seen in the task manager with 0% utilization

Thanks

[patul]

Which version are you trying to install? I can run latest version from pinterf just fine on my Windows 10.

Can you try to run this simplest script in AVSMeter to see if there's any error message there?

MP_Pipeline("""
ColorBars()
### prefetch: 16, 0
### ###
""")

ScriptClip("Subtitle(string(current_frame))")

[gispos]

Had it only tried with LWLibavVideoSource.
With DirectShowSource and FFVideoSource it works, very strangely because LWLibavVideoSource works properly without MP_Pipeline with 32bit and 64bit.

Also AVSMeter or VirtualDub show no mistakes but just wait for Avishynth.

Why? This can not be, LWLibavVideoSource works flawless without MP_Pipeline :confused:

[gispos]

Found out why.
If an index file exists there are no problems, but if I start LWLibavVideoSource(SourceFile, cache=False) in MP_Pipeline, Avisynth does not return.
But that works under Win7. Why is cache=False ignored?

Edit
Or better asked, why does LWLibavVideoSource not start in MP_Pipeline without an index file?

[StainlessS]

Anything in Windows Logs [Application or System] ?.

[gispos]

Have already looked and found nothing. Comodo firewall turned off, virus scanner deactivated nothing helps.

How do MP_Pipeline and LWLibavVideoSource behave on other Win10 computers?
Can be used without an index file, i.e. LWLibavVideoSource(SourceFile, cache=False)

Edit:
What else comes to mind are the services I disabled in the Comodo firewall.
Does MP_Pipeline communicate with its processes via remote or something else?

[gispos]

I tested it in a VM, same result.
Under Win10, LWLibavVideoSource cannot be used in MP_Pipeline without an index file.
That still worked with Win7.

Is it the same for other users?
It would be nice if someone could confirm this, so that I can stop looking for the problem.

[patul]

Yes, the same issue(s) happened here too:


Creating lwi fails (but the lwi file is actually created, although not a complete index file)

AVSMeter 3.0.2.0 (x64), (c) Groucho2004, 2012-2020
AviSynth+ 3.7.0 (r3382, 3.7, x86_64) (3.7.0.0)

Creating lwi index file 35ate slave process. Message: Creating lwi index file 0
(D:\App\AVS\AVSMeter290\mp.avs, line 5)
cache=false doesn't help
AVSMeter 3.0.2.0 (x64), (c) Groucho2004, 2012-2020
AviSynth+ 3.7.0 (r3382, 3.7, x86_64) (3.7.0.0)

[gispos]

patul thank you for the confirmation. It was apparently too difficult to test for the long-established.:sly:

[StainlessS]

This long-established has never used it, sorry. :(

[gispos]

This long-established has never used it, sorry. :(
Then you were not meant.;)