keg247

> Thanks for the information, with version 4.2.0 it works satisfactorily, I did exactly what was mentioned with version 4.8.0 of FFMpegCore, and it didn't work (so you don't waste...

Adding another data point. I got the same issue on 4.8.0, and downgrading to 4.7.0 fixes it. I'm running Windows 10 Pro, targeting .NET 6, and using ffprobe/ffmpeg version 4.2.

I think this is caused by ffmpeg outputting to standard error. Looks like 4.8.0 separated the handling of standard error from standard output. According to some of the answers [here](https://stackoverflow.com/questions/35169650/differentiate-between-error-and-standard-terminal-log-with-ffmpeg-nodejs)...

Same here. Docker run fails. And the log has an entry that says "unknown flag: --gpus all". Looks like --gpus was introduced in API v1.40: see, --gpus entry at https://docs.docker.com/engine/reference/commandline/run/...

I just used "-gpus=all" (notice use of equals) in the runArgs and it created and attached the container without error. I used it on the kaggle gpu image and have...

I have the same issue for the 0.2.5 windows ncnn release for all scalings (-s 2, 3, and 4).

Seems like I have the same issue. I have both integrated and discrete graphics. If I run on the CPU, inference works fine. But If I try to use either...

I ran into the same issue, and developed a work around. Sharing here in case it is helpful. I created a new component that uses the Mud Component I want...