Plugin uses more CPU than gphoto2/v4lloopback

[mjg]

First of all thanks for a great plugin which has the potential to make things much easier.

So far I have been using a pipeline like gphoto2 --stdout --capture-movie | gst-launch-1.0 fdsrc ! decodebin3 name=dec ! queue ! videoconvert ! v4l2sink device=/dev/video11 and the v4l source in obs. In sum this uses up rougly 40% to 50% CPU time on my system (including obs), about half of that for gphoto2.

The plugin is much more convenient (and potentially gives more controls), of course, and I expected it to be more efficient because it bypasses v4l. Alas obs uses up rougly 50% with it. This is not much more but still surprising. Is ImageMagick the bottle-neck here?

[mjg]

Meanwhile I've discovered dunkelstern's fork which replaces ImageMagick by jpeg-turbo and brings down CPU usage to a little over 40%, bringing the plugin in on par with the pipeline solution. I guess this is a testament to the efficiency of v4l.