RemoteChannelStreamConverter issues
#1
Geplaatst op 19 december 2014 - 11:52
Say RCSC makes a copy of bouquet "userbouquet.jazz.radio", resulting in a bouquet with the same name. A second time I run RCSC the plugin sees that the name already exists, and makes a copy with the name "userbouquet.jazz_remote.radio". So now I have the old and the new bouquet in my box. The original one will never be updated.
Solution seems to be to force RCSC to create it's own, unique names. A name like "userbouquet.jazz_remote.radio" or in general "userbouquet.<original-name>_remote.tv" would be fine. This name will be recognised by RCSC itself, preventing a double bouquet on a next run.
Would it be possible to overhaul RCSC in this area>
Re: RemoteChannelStreamConverter issues #2
Geplaatst op 19 december 2014 - 12:48
I'd like to second this proposal. I have a slightly different issue, though, in that RemoteChannelStreamConverter takes the original name of the bouquet from the server box. This is problematic in the case where autobouquets are present on both server and client boxes and makes it difficult to distinguish. A unique name on the client would be useful.
Re: RemoteChannelStreamConverter issues #3
Re: RemoteChannelStreamConverter issues #4
Re: RemoteChannelStreamConverter issues #5
Re: RemoteChannelStreamConverter issues #6
Geplaatst op 24 december 2014 - 12:37
Also apart from the fixes mentioned in the pull request it also contains other earlier OE-Alliance fixes for things like Dreamset format.
https://github.com/R...2c92dbf2070d92b
But so far it looks like no one is interested. Not sure why.
Veranderd door Huevos, 24 december 2014 - 12:39
Re: RemoteChannelStreamConverter issues #7
1 gebruiker(s) lezen dit onderwerp
0 leden, 1 bezoekers, 0 anonieme gebruikers