Is your feature request related to a problem? Please describe.
On some smart devices, especially smart TVs that do not run Android or Roku as their OS but rather a proprietary OS, when using Plex and trying to browse the guide past roughly 50-60 channels, in the case of my new Samsung smart TV, this can cause Plex to slow down and even stop responding.
Describe the solution you'd like
The best solution to this would be to provide multiple "devices" that can be created by using group names without the need to run multiple instances of xTeVe. Such that when adding a device to Plex adding a URL parameter for the device IP/URL such as 127.0.0.1:34400/?groups=agroup,bgroup will return a new "device" for those group(s) and only provide those group(s) in the channel lineup for that "device". This prevents the need to run multiple instances of xTeVe to split out the channels.
Describe alternatives you've considered
Running other instances of xTeVe to do this is possible, but requires moving and editing the channels for that specific instance of xTeVe where as this method allows all channels to be setup under 1 instance of xTeVe and simply split them out from the client end by providing the URL parameter for which group(s) to use for that "device".
Additional context
Currently working on implementing this on my development branch and testing it.
Is your feature request related to a problem? Please describe. On some smart devices, especially smart TVs that do not run Android or Roku as their OS but rather a proprietary OS, when using Plex and trying to browse the guide past roughly 50-60 channels, in the case of my new Samsung smart TV, this can cause Plex to slow down and even stop responding.
Describe the solution you'd like The best solution to this would be to provide multiple "devices" that can be created by using group names without the need to run multiple instances of xTeVe. Such that when adding a device to Plex adding a URL parameter for the device IP/URL such as 127.0.0.1:34400/?groups=agroup,bgroup will return a new "device" for those group(s) and only provide those group(s) in the channel lineup for that "device". This prevents the need to run multiple instances of xTeVe to split out the channels.
Describe alternatives you've considered Running other instances of xTeVe to do this is possible, but requires moving and editing the channels for that specific instance of xTeVe where as this method allows all channels to be setup under 1 instance of xTeVe and simply split them out from the client end by providing the URL parameter for which group(s) to use for that "device".
Additional context Currently working on implementing this on my development branch and testing it.