Page 1 of 1

The SOPCAST Dilemma

PostPosted: Thu Aug 23, 2012 4:41 am
by jhb50
SOPCAST offers streams in various formats, so when you switch a stream, the codecs will likely be different. All streams however use the same address http://127.0.0.1:8902, and Serviio will cache the codecs used by the stream being played the first time that URL is added to the console as a livestream, and use those values to transcode every SOPCAST stream, which leads to errors.

Since there is no way to update the cached values once they are established, the only solution I can see is to put the URL in a LiveFeeds folder, and give it a cachekey like timestamp that is different each time it is used . That will force the codec to be detected each time a SOPCAST stream is played, resulting in the correct transcoding.

Is there any other way to handle this?

Re: The SOPCAST Dilemma

PostPosted: Mon Aug 27, 2012 10:23 pm
by zip
yes, you will have to figure out how to generate new cacheKey every time the stream changes.

Re: The SOPCAST Dilemma

PostPosted: Mon Aug 27, 2012 11:56 pm
by jhb50
yes, you will have to figure out how to generate new cacheKey every time the stream changes

As I said that only happens each time the plugin is used, rather than dynamically, so I guess a plugin time stamp will do the job.