2025-06-14, 08:49 PM
(2025-06-13, 04:23 AM)Efficient_Good_5784 Wrote: Considering that the server stops the current ffmpeg process and creates a new process with the updated settings, maybe making it launch a new ffmpeg process while the old one is still running can solve the issue.
Then, it would just be a matter of timing the new transcode to align with the old one, switching to the new one, and finally deleting the old process when done.
Thanks for taking the time to chime in!
I already tried via ffmpeg but for some reason it did not work out. I think it was because there is only a ffmpeg process when transcoding so updating users in a direct play session would not work.
With a bit of tuning I might get this working without it being too intrusive:
- change bandwidth limit
- get current episode and timestamp
- stop playback
- start playback
- jump to timestamp
All of this is already working in my current build but it somehow is pretty hard to really allign the timestamp correct. Another unforeseen challenge is getting a good reading of jellyfins outgoing traffic (excluding streams of local users) due to flow offloading but I already have a few ideas on how to get a reliable reading on that.