17.01.2023, 22:06
Argh, using vsViewer with something using the gpu while encoding can cause tons of issues.
If you run multiple encodes in a queue, encoding might simply fail, since the vram is already occupied by vsViewer.
I'll think about adding an option to not run vsViewer in 'idle', but for me the time to build the tensor RT file isn't that important, since it is often less than rendering a few frames in the script. I will not change the default behavior of Hybrid to lower the priority of vsViewer to idle.
Cu Selur
If you run multiple encodes in a queue, encoding might simply fail, since the vram is already occupied by vsViewer.
Quote:Given the typical use of vsViewer.exe I don't see any danger of slow down if it is launched always with NORMAL priority.We have different views on what a typical use of vsViewer is. For me often vsViewer can take tons of resources. For me rendering the Vapoursynth script, even without ai based filters, can get really slow.
I'll think about adding an option to not run vsViewer in 'idle', but for me the time to build the tensor RT file isn't that important, since it is often less than rendering a few frames in the script. I will not change the default behavior of Hybrid to lower the priority of vsViewer to idle.
Cu Selur