More sophisticated caching

I think, the caching can be improved by:

• Allowing to specify multiple directories — so that the temporary files can be spread out across multiple disks.
• Splitting output into chunks of, say, 10 minutes each — I think, ffmpeg can do that...

Combined these would not only allow for better space and I/O utilization, it will also let serviio delete the earlier chunks — those, that are, say, more than 20 minutes behind of what is currently being sent to the player...

Agree with kot
+1

Wanna it too.

[zip]

deleting the files early would disable rewinding further than those 20 minutes and it you stop and play the file again you'd have to start transcoding again.

and is it ever possible to stop or pause ffmpeg from transcoding when I stop playing video?

[zip]

No, and even not advisable as someone else might be watching it at the same time on your second TV

deleting the files early would disable rewinding further than those 20 minutes and it you stop and play the file again you'd have to start transcoding again.

By splitting the files into chunks, it will be possible to delete some of the chunks — if, for example, there is a shortage of space...

Yet another benefit may be in helping the filesystem's caching — right now reading the middle of a huge file and sending it to the player competes for the cache-memory and the disk IO with the ffmpeg writing at the end of it... Some large slow disks may not like this.

No, and even not advisable as someone else might be watching it at the same time on your second TV

Serviio would know about that — and will avoid deleting the file, that anybody is currently watching or watched within the last whatever minutes...