You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to choose what profile is used for streaming, not just the DVR ?
I have an issue unrelated to this plugin (jellyfin/jellyfin#5248) that makes low def channels not work in jellyfin when hardware transcoding is enabled.
Since I need to keep it enabled for the rest of my library, I'm wondering if I could get tvheadend to do the transcoding instead of jellyfin, and just point it to a profile that does not have hardware enabled.
Thanks
The text was updated successfully, but these errors were encountered:
Hi, I have the same request.
I want to use a specific streaming profile in tvheadend but there is no way to tell to "jellyfin-plugin-tvheadend" to use a streaming profile instead of plain htsp pass.
I also tried to make an user on tvheadend that can only use a specific profile, but the plugin seems to ovveride this and use htsp regardless.
Using this: http://user:password@IPADDRESS:9981/playlist/auth/channels.m3u?profile=SPECIFIC-STREAMING-PROFILE
I can get a .m3u playlist file with all the channels for the specific streaming profile I want to use and then import this playlist in jellyfin LiveTV/M3UTurner but in this way I loose the ability to timeshift/record/schedule records on tvheadend side.
So is possible to implement profile for the streaming in the tvheadend-plugin? Thanks
Hi,
Is there any way to choose what profile is used for streaming, not just the DVR ?
I have an issue unrelated to this plugin (jellyfin/jellyfin#5248) that makes low def channels not work in jellyfin when hardware transcoding is enabled.
Since I need to keep it enabled for the rest of my library, I'm wondering if I could get tvheadend to do the transcoding instead of jellyfin, and just point it to a profile that does not have hardware enabled.
Thanks
The text was updated successfully, but these errors were encountered: