We are experiencing a critical issue with our local CCTV streaming setup immediately after updating our Windows Players from R405 to the new R406.
Our Setup: We run a local Linux server using Docker with FFmpeg (jrottenberg/ffmpeg image). This server pulls RTSP feeds from our cameras, transcodes them in real-time, and provides a local stream that Xibo consumes via the “Web Page” widget.
The Issue:
Player R405: The streams worked perfectly. Autoplay worked, video was fluid.
Player R406: The exact same layout results in a black screen. The player loads, but the video stream never appears.
Diagnosis & Attempts: We noticed R406 updated the CEF Webview engine. Suspecting strict autoplay policies or GPU conflicts, we manually verified XiboClient.xml:
Has anyone else noticed broken streams on R406? Is there a new setting or argument required for the updated WebView engine?
For now, we are forced to downgrade back to previous versions.
You’re right in that we went from 134.3.90 to 141.0.110, although we do check through the release notes and there wasn’t anything specific noted about video playback, etc.
That’s interesting - CEF hasn’t ever shipped with a H.264 decoder due to licensing - I think it only supports WebM. I can’t explain how that would have worked previously.
Can you try using a browser tag to switch your webpage widget to use Edge instead of CEF?
That is strange because H.264 is the industry standard for CCTV RTSP streams. It definitely worked flawlessly on Player R405 (and R3xx), likely because it was utilizing the underlying OS codecs or GPU acceleration which seems to be bypassed or blocked in the new CEF 141 build in R406.
Regarding your suggestion: “use a browser tag to change your web page widget to use Edge instead of CEF”
Could you please clarify specifically how to apply this tag?
Do you mean adding the URL to the “Edge Browser Whitelist” inside the Display Settings Profile? (We have already tried adding * (wildcard) and the specific URL to the Whitelist, but the screen remains black).
Or do you mean adding a <meta> tag inside the HTML of the page itself? (Something like <meta http-equiv="X-UA-Compatible" content="IE=edge">?)
We really need to get this working on v4 as sticking to v3/R405 is not a long-term solution.
Really strange, I don’t have a good explanation i’m afraid. CEF hasn’t ever supported H.264 (see this issue). If you’re happy to DM me the web page I can try it in a development environment.
Xibo supports swapping to edge by putting a tag at the top of any embedded widget (which is Chromium based too, but Windows build in H.264 support as they have a licence for it).
<!-- BROWSER=edge -->
You can also switch to edge for all web content via the config.xml file in the player installation folder. There is a setting in there <FallbackToEdge>True</FallbackToEdge>.
I found the configuration file you mentioned, changed the <FallbackToEdge>True</FallbackToEdge> flag, and it started working correctly. How do I send this parameter via CMS?
Unfortunately you can’t send that one via the CMS.
It should be possible to do what you want to do using the Edge Browser Whitelist - you can put any part of the URL in there, e.g. rtc_simple and it should match (it does a “contains”).
Yes, that’s right. * isn’t a valid field in there. We separate the string you put in there by a , and then check if the string is inside the URL we’re trying to load.
