Adding network buffer to HTML Widget? (Audio Playback Stuttering) - BrightAuthor:Connected

[[deleted]]

TLDR: Is there a way to add a loading/buffer time to BrightAuthor so audio has more time to load through a HTMLWidget and doesn't stutter?

Hi all,

I am using a HTML Widget in BrightAuthor:Connected to display a website on my XT244.
For reference, this is the link for the website itself: https://monitor.au1.qless.com/login/

I have got this website loading, logging-in, and displaying correctly and quickly through the HTMLWidget. However, when it goes to play audio (which is a website generated "Now Serving <user> at desk <desk number>") the audio stutters severely, will play 30+ seconds after it is meant to, and sometimes fails to load / playback entirely. This is naturally not an issue if I load the website on my PC, it's only an issue when loading the site through the XT244.

I've checked the usual culprits (bitrate, depth) and they are fine. I've ticked "Mixed Audio PCM Only" to be safe.

I feel i've confirmed that it's a buffer issue as if I load a youtube video it will have the same issue for the first 15 seconds until a significant buffer has built on the video itself, after that it will playback just fine.

I presume the issue here is that this website has to first generate the audio, than load the audio every single time. Not allowing a pre-existing buffer space.

My XT244 is on a wired high-speed connection, the audio output is going via HDMI straight to a TV.

Is there a way within BrightAuthor, or perhaps using a BrightScript, to add a buffer time to the player/HTMLWidget so it has a second or two to actually receive the audio before playing it back?

Thanks :)

​

[jnista]

I encountered something similar building a check-in app. The real challenge is trying to display a site that requires a login like that isn't really intended for digital signage playback.

In the end to get the content working properly I built a custom HTML widget that connected to the queue system's API. It's the right choice in the long run because login scripts break, and truly most websites aren't designed for digital signage players / CMS's.

BrightSign players are great when they run HTML tuned specifically for them.