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
When trying to stream any channel from my DVB-S tuner, Jellyfin wants to transcode it into H264 and AAC, even though the channel usually already is.
I think this may be down to this chunk of code, that doesn't return any stream information - only that the video stream is a video, and the audio stream is audio:
// Set the index to -1 because we don't know the exact index of the video stream within the container
Index=-1,
// Set to true if unknown to enable deinterlacing
IsInterlaced=true
},
newMediaStream
{
Type=MediaStreamType.Audio,
// Set the index to -1 because we don't know the exact index of the audio stream within the container
Index=-1
}
}
};
Some of the missing information (stream index, codec, language) is available from Tvheadend, using the /api/service/streams endpoint, so I think fetching that data might help solve this, assuming that missing info is the cause.
The text was updated successfully, but these errors were encountered:
jonjomckay
changed the title
Trancoding occurs even when the client supports the video and audio codecs
[bug] Trancoding occurs even when the client supports the video and audio codecs
Aug 17, 2023
Same for me. Only workaround I found to prevent transcoding and to enable direct stream / remuxing is using the Jellyfin m3u tuner with the TVH m3u channel list (which also support stream profile selection) e.g /playlist/channels.m3u?profile=pass
When trying to stream any channel from my DVB-S tuner, Jellyfin wants to transcode it into H264 and AAC, even though the channel usually already is.
I think this may be down to this chunk of code, that doesn't return any stream information - only that the video stream is a video, and the audio stream is audio:
jellyfin-plugin-tvheadend/TVHeadEnd/LiveTvService.cs
Lines 453 to 475 in 5c29b99
Some of the missing information (stream index, codec, language) is available from Tvheadend, using the
/api/service/streams
endpoint, so I think fetching that data might help solve this, assuming that missing info is the cause.The text was updated successfully, but these errors were encountered: