I am not able to get chrome capture to function reliably. The problem is that the stream frequently freezes or buffers, and sometimes the video stops while the audio continues for a long period. I noticed these log entries every time the stream freezes:
2025/01/15 20:09:02.907164 [HLS] ffmpeg: chrome-MSNBC: [matroska,webm @ 0x1889a180] Unknown element 7C34 at pos. 0x1735b80 with length 0x70651 considered as invalid data. Last known good position 0x16b829d, 7 unknown elements in a row
2025/01/15 20:09:02.907198 [HLS] ffmpeg: chrome-MSNBC: [matroska,webm @ 0x1889a180] Seek to desired resync point failed. Seeking to earliest point available instead.
These are always in pairs, the first one indicating invalid data, the second one indicating a resync failure. (I've tried both HLS and MPEG-TS, same behavior with either one)
I have been getting the same behavior with the Channels server hosted in Windows as well as Linux, and with the chrome capture program running on the same server as Channels, and on a separate Windows box.
The Channels server is version 2025.01.10.0336 on an Intel Core I7-7700k system running Debian Linux, and the chrome capture program v0.1.10 is on a Lenovo Yoga 900 running Windows 10. Both are ethernet-connected and have 16G memory. The Channels server barely registers any CPU usage except when comskip is running. The laptop runs about 40% utilization when CC4C is active.
I think that probably eliminates hardware as the root cause, especially since I've tried multiple configurations. So, that leaves Channels and/or chrome capture software configuration? Or, maybe a problem with ffmpeg? I notice that it's ffmpeg that is reporting the errors. It starts up on the Channels server when a cc4c program is active, but it's using less that 1% cpu.
I noticed one previous report of this problem from @scottuf Chrome Capture for Channels - #424 by scottuf
any ideas?
Thanks,
-Jay