Quote:
WINE, although whether WINE would provide access to the capture device could be pretty iffy. However...
Quote:
|
Or if that’s not possible is there any sort of workaround?
|
FFmpeg can grab from an assortment of capture devices/protocols, so that can likely be done natively. I'm sure there are dedicated GUI tools for doing captures, but *shrug*.
AviSynth+ is cross-platform, so you don't even need WINE for that¹, especially if it's largely just stuff in the core itself. The caveat, at least for Debian-based distros, is that there is no package in the repos (the most prominent group of distros that
do provide a package for AviSynth+ is Arch,
btw). The deb-multimedia 3rd party repo has builds of AviSynth+, ffms2, and the ffmpeg in there
might have had the AviSynth demuxer enabled, but I'm not sure.
That said, AviSynth+ is very easy to compile yourself, and so is avs2yuv - at which point you can at least pipe into FFmpeg. It's if you want it enabled directly in FFmpeg and mpv (not to mention having the FFmpeg-based source plugins so you aren't limited to importing stills/image sequences with ImageSource) that things get more involved, to a greater or lesser extent based on personal preference.
¹any plugins you use that haven't been ported yet notwithstanding