You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Vingester 2.8 on Linux Mint 20.3 Cinnamon if using headless/ffmpeg->file you cannot restart a browser. Headless/NDI and Frameless are OK. This happens even if you change the output type/sink before attempting to restart. You have to restart Vingester.
I note that before initially starting the browser Vingester CPU is ~2.5% which rises to about 70% on my old laptop. However on stopping the browser the CPU only drops back to around 25% usage.
Htop confirms that a Vingester thread with a --type=renderer parameter is the culprit. Ffmpeg quits shortly after the browser is stopped. After about 10 minutes (using the sample expert-1 browser) this thread stops and CPU usage drops back to ~7%. However it is still not possible at this point to restart the browser.
I tried enabling the console to see what was going on but no separate console appeared or anything in /var/log/syslog.
The text was updated successfully, but these errors were encountered:
In Vingester 2.8 on Linux Mint 20.3 Cinnamon if using headless/ffmpeg->file you cannot restart a browser. Headless/NDI and Frameless are OK. This happens even if you change the output type/sink before attempting to restart. You have to restart Vingester.
I note that before initially starting the browser Vingester CPU is ~2.5% which rises to about 70% on my old laptop. However on stopping the browser the CPU only drops back to around 25% usage.
Htop confirms that a Vingester thread with a --type=renderer parameter is the culprit. Ffmpeg quits shortly after the browser is stopped. After about 10 minutes (using the sample expert-1 browser) this thread stops and CPU usage drops back to ~7%. However it is still not possible at this point to restart the browser.
I tried enabling the console to see what was going on but no separate console appeared or anything in /var/log/syslog.
The text was updated successfully, but these errors were encountered: