jellyfin 10.9 cannot playback recordings - sid=jellyfin told not valid

[mvallevand]

I have been doing more testing and with the logs I think I see the reason why streams are being transcoded.  What I have noted is that Jellyfin doesn't provide a proxy server to NextPVR, instead direct play simply passes the URL to the client.  For Live TV to work you would need to to have unauthenticated access on the server off and also a private IP address.  I have a new test version of the client that has many changes and that is one of them if you want to test it.

Here is a direct play Live TV stream  > 20Mb so it is possible.



Martin

[prahal]

  nextpvr-logs-20240604-1752.zip (Size: 1.6 MB / Downloads: 1)

Edit: I am unable to attach the jellyfin log to the post. The log is zipped and takes 4.5MB. It uploads fine but for one I get no insert button below. On my first edit, I had both the nextpvr and jellyfin logs uploaded and only the nextpvr one showed up (it is 1.7MB)

I have been doing more testing and with the logs I think I see the reason why streams are being transcoded.  What I have noted is that Jellyfin doesn't provide a proxy server to NextPVR, instead direct play simply passes the URL to the client.  For Live TV to work you would need to to have unauthenticated access on the server off and also a private IP address.  I have a new test version of the client that has many changes and that is one of them if you want to test it.

Here is a direct play Live TV stream  > 20Mb so it is possible.



Martin

Interesting.
Which client ? A desktop one ?
I did my test in the jellyfin-web client in Firefox Linux (and sometimes Android jellyfin app).
Might be why it is hard for me to find out if the transcoding happens in the jellyfin client or the server as I believe jellyfin-web client is transcoding in the same container as the server.

Note that in my last tests, I had the private IPv4 IP of the NextPVR server hardcoded into the jellyfin server host (hosting jellyfin-web client).

The previous "Playback data" from jellyfin-web was from the 29th of May, I believe it was jellyfin 10.9.3.
Even though I don't know if any change related to live stream has been introduced in jellyfin 10.9.4
I since upgraded to jellyfin 10.9.4 and have a different transcoding reason, which is formats not supported by the client (which seems weird to me as the container is mpegts, and the codecs are h264 and AAC - "France2" channel)

Code:

Media
Administration
User
Tennis: Roland-Garros - Part 2
Reading information
Drive
Html Video Player
Reading method
Transcoding
Protocol
http
Flow type
HLS
Video information
Drive size
1920x963
Video resolution
852x479
Lost images
162
Corrupt images
0
Transcoding information
Video codec
H264
Audio codec
AAFC
Audio channels
2
Speed
20.3 Mbps
Transcoding refresh rate
23 fps
Reason for transcoding
Container is not supported
Video codec is not supported
Audio codec is not supported
Original media information

Container
mpegts
Speed
20.1 Mbps
Video codec
H264 High
Video bitrate
20.0 Mbps
Video track type
SDR
Audio codec
EAC3
Audio rate
128 kbps
Audio channels
2
Audio sample rate
48000 Hz

[mvallevand]

The forum upload storage limit is 2MB other than that external storage is required. If you don't like OneDrive or Google Drive I suggest a site like filetransfer.io Unfortunately the changes in 10.9.4 did change a bit of behaviour for a point release.

That was the Windows Desktop client but Flatpak also works since they both use the libmpv. Android worked too but I needed to use the VLC library, they didn't enable it with ExoPlayer

Here you can see your server using ipv6 and the client request was using ipv4 which is failing, but that might be because of another thing I have changed in my build.

Code:

2024-06-04 17:15:05.695    [DEBUG][5]    Got request [fc00:10::95d0:9841:2f1:aaf8]: /service (recording.lastupdated)
2024-06-04 17:15:05.695    [DEBUG][5]    method=recording.lastupdated
2024-06-04 17:15:05.695    [DEBUG][5]    parameters:
2024-06-04 17:15:05.695    [DEBUG][5]       method: recording.lastupdated
2024-06-04 17:15:05.695    [DEBUG][5]       ignore_resume: true
2024-06-04 17:15:05.695    [DEBUG][5]       sid: 6229733b312246de8006d46542dc64fb
2024-06-04 17:15:05.695    [DEBUG][5]       format: json
2024-06-04 17:15:05.695    [DEBUG][5]       client_ip: fc00:10::95d0:9841:2f1:aaf8
2024-06-04 17:15:05.695    [DEBUG][5]       user_agent: Jellyfin-Server/10.9.4
2024-06-04 17:15:05.695    [DEBUG][5]       host_callback: ...
2024-06-04 17:15:05.695    [DEBUG][5]    LastUpdated
2024-06-04 17:15:05.695    [DEBUG][5]    {"last_update":1717459927}

2024-06-04 17:15:05.888    [DEBUG][5]    Got request [192.168.10.48]: /live
2024-06-04 17:15:05.888    [DEBUG][5]    /live?channeloid=7148&client=jellyfin.10&sid=6229733b312246de8006d46542dc64fb
2024-06-04 17:15:05.888    [DEBUG][5]     - channeloid: 7148
2024-06-04 17:15:05.888    [DEBUG][5]     - client: jellyfin.10
2024-06-04 17:15:05.888    [DEBUG][5]     - sid: 6229733b312246de8006d46542dc64fb
2024-06-04 17:15:05.888    [DEBUG][5]    range: bytes=0-
2024-06-04 17:15:05.889    [ERROR][5]    Rejecting sid. Different IP address. (192.168.10.48 vs fc00:10::95d0:9841:2f1:aaf8)
2024-06-04 17:15:05.889    [ERROR][5]    Unauthenticated Stream Access is disabled. Invalid sid=6229733b312246de8006d46542dc64fb

Martin