Quote Originally Posted by ColinE66 View Post
Hmmm, that does look interesting as I've recently replaced a lot of my code with equivalent FFmpeg functionality. I should be able to read image byte streams from StdError (where FFmpeg writes to, for some unknown reason) via a pipe with this WScript shell thingy, if I've understood that right?
To be precise, it's not the WshShell-Object I'm talking about,
but the (Process-representing) Object, which is returned by the .Exec-Method of the WshShell-Object.

In the example further above, I've added these Process-Objects into a normal VB-Collection:
Processes.Add Wsh.Exec(CmdLine)

But you can of course experiment with it in an isolated fashion as well:
Dim P As Object
Set P = Wsh.Exec(CmdLine)
...
VBByteArray = P.StdOut.ReadAll
or
VBByteArray = P.StdErr.ReadAll

should work IMO ... never used these Pipe-reading capabilites in a production-app,
so cannot tell where the quirks are... only tested StdOut at some time with a simple Ping-Command.

There's some examples, when you google around - e.g. here:
https://stackoverflow.com/questions/...ut-from-stdout

The StdIn/Out/Err-Props and methods seem to be compatible to the TextStream-object:
https://docs.microsoft.com/en-us/pre...28v%3dvs.84%29

Regards,

Olaf