That's interesting. I did have slowdowns and stuff before - even Jellyfin itself said as much in it's own logs xD - but that is a whole different level of "slow". o.o
Let me think... Considering you have SBC experience, I probably don't have to ask "How are you storing this?" - chances are, you know what you're doing :)
What could be a problem though is the client you are using. In most situations, Jellyfin will actually serve the real file to you without transcoding (which, by the way, is well documented but almost as hard to set up as Lightning. ^^;) granted your browser or client supports it. Since it seems to crash after a few minutes, here's two things that came to mind:
Try to create an SMB or NFS share that contains the file you are trying to play through jellyfin - but the share itself is hosted on the same maschine. Point MPV at it, and see what happens. Might give you a pointer. If MPV buffers it right away and immediately, you can 100% rule out an FS problem. The other thought is your client.
Jellyfin has their own client software aside from the webview: https://github.com/jellyfin/jellyfin-media-player/releases
Give it a shot, see what happens.
Sometimes, the Jellyfin logs themselves *can* help, but I hardly ever found them any useful. Literally, 99% of it's logging output is pure junk. I have to tail -f and cheat by pressing enter to artificially create newlines immediately before doing what I want to "debug", to see the relevant log output, before it gets covered up by background process output, in which case i can ctrl-c out and observe what was logged that would be relevant to me.
Personally, I don't believe in the "But it works for me" paradigm. Humans make errors and humans made Jellyfin. So, chances are, you simply found an edge case that nobody knew of... yet. :)
That's all I could really think of. I've been using Jellyfin since several years at this point to share a collection of stuff with my friends. Like we'd go to a convention and buy our anime, then use MakeMKV and drop them into a shared place, so the others can also watch it. And so far, it has indeed worked. Though I am not the most happy with it's actual performance sometimes. It's kinda snail-y most of the time.
I hope I could give you some useful pointers there! ^^
IngwiePhoenix / Ingwie Phoenix
npub1tc…hjmky
2023-08-03 12:12:14
in reply to nevent1q…xxpj
Author Public Key
npub1tcekjparmkju6k83r5tzmzjvjwy0nnajlrwyk35us9g7x7wx80ys9hjmkySeen on
wss://relay.noswhere.comPublished at
2023-08-03 12:12:14Event JSON
{
"id": "58cd9bdce1d08802bc54fd36b1603f543edee331ca9ba716c1f03633a9b7a66d",
"pubkey": "5e336907a3dda5cd58f11d162d8a4c9388f9cfb2f8dc4b469c8151e379c63bc9",
"created_at": 1691064734,
"kind": 1,
"tags": [
[
"e",
"352debb36e432e30d1191ba18944860a925fa6678fb6117429cf460c8e67f3c6",
"",
"reply"
],
[
"p",
"7046b61ca13784ae2df56301c8603b22782660cb5b88ac419fed3ec712477f80"
]
],
"content": "That's interesting. I did have slowdowns and stuff before - even Jellyfin itself said as much in it's own logs xD - but that is a whole different level of \"slow\". o.o\n\nLet me think... Considering you have SBC experience, I probably don't have to ask \"How are you storing this?\" - chances are, you know what you're doing :)\n\nWhat could be a problem though is the client you are using. In most situations, Jellyfin will actually serve the real file to you without transcoding (which, by the way, is well documented but almost as hard to set up as Lightning. ^^;) granted your browser or client supports it. Since it seems to crash after a few minutes, here's two things that came to mind:\n\nTry to create an SMB or NFS share that contains the file you are trying to play through jellyfin - but the share itself is hosted on the same maschine. Point MPV at it, and see what happens. Might give you a pointer. If MPV buffers it right away and immediately, you can 100% rule out an FS problem. The other thought is your client.\n\nJellyfin has their own client software aside from the webview: https://github.com/jellyfin/jellyfin-media-player/releases\nGive it a shot, see what happens.\n\nSometimes, the Jellyfin logs themselves *can* help, but I hardly ever found them any useful. Literally, 99% of it's logging output is pure junk. I have to tail -f and cheat by pressing enter to artificially create newlines immediately before doing what I want to \"debug\", to see the relevant log output, before it gets covered up by background process output, in which case i can ctrl-c out and observe what was logged that would be relevant to me.\n\nPersonally, I don't believe in the \"But it works for me\" paradigm. Humans make errors and humans made Jellyfin. So, chances are, you simply found an edge case that nobody knew of... yet. :)\n\nThat's all I could really think of. I've been using Jellyfin since several years at this point to share a collection of stuff with my friends. Like we'd go to a convention and buy our anime, then use MakeMKV and drop them into a shared place, so the others can also watch it. And so far, it has indeed worked. Though I am not the most happy with it's actual performance sometimes. It's kinda snail-y most of the time.\n\nI hope I could give you some useful pointers there! ^^",
"sig": "dabe29422d4b9fa1835fd7bc6a1bc1a4a20a9aba096413dfe214137c57d6ef1ab5f56045fc40128096fcd1cee5afa9a5ff07b1abcda204a73d124a2ddf029db9"
}