Closed askvictor closed 1 year ago
Yes, it is likely an issue with the podcast provider web server. Cast devices tend to have very large buffers and they initially acquire a large portion of the podcast and then can be idle for a long while before requesting more data. Some servers tend to think that the connection went stalled and close it. In fact, a lot of servers expect clients to download the whole podcast at once and play it at their own pace, they don't want to "live stream" podcasts for very understandable reasons.
This problem is a general issue with LMS but it can be less visible with some players that either have smaller buffers or tend to grab a large initial amount and then regularly require small chunks when their level is depleted enough. But that "high/low water" mechanism can happen with a very large difference between high and low water.
So, to cut the long story short, I did implement directly in LMS two options to work around this. You'll find them in the "Settings", tab "Advanced", option "Network". It's the "HTTP(s) streaming mode" option. It speaks for itself.
Thank you - I've set it to cache mode and that's fixed it. I had been poking around the Cast Bridge options thinking it was specific to that, but hadn't thought to look elsewhere.
When I play long tracks (e.g. podcast) over an LMS-Cast device, it stops playing after about 13-14 minutes. The same track played on a Squeezebox Radio plays fine all the way through.
Below is a snippet of the
castbridge.log
file:The issue seems to be the "Track shorter than expected" - any ideas?