Comment on Video transcoding web interface (self hosted)
scrubbles@poptalk.scrubbles.tech 1 day agoThe problem exists of how do you get files to the server. Again for a big video file you need a place to have the original accessible for the entire duration of the transcode, and you need a drop point to place the file when it’s done. And if you’re doing that, more than likely you have something like Plex or jellyfin, so why not just hook it up to your existing file locations?
I run jobs all the time from my cluster, but the issue always comes back to persistent storage. Where are the files you need to act on, and where should the finished results be placed? You’re trying to skip those important steps here.
MajesticElevator@lemmy.zip 1 day ago
It was meant to run on a server with pretty much nothing on it but yea, if uploading big files isn’t possible through a browser, I’ll find other solutions. I was hoping files smaller than like 4GB would be fine.
About the storage, I hoped that it would just either load the file in memory, or store during the transcode, then when done, delete the source file and put the transcoded server for a limited amount of time (1h for example), then wipe it (or just wipe it after download)
Onomatopoeia@lemmy.cafe 1 day ago
Yea, I’d take the approach of having the server monitor a folder, and then just drop files in that folder to be converted.
There are a number of ways to transfer files to that folder, tools like FolderSync (Android), Syncthing or Resilio (every OS) can handle this.
MajesticElevator@lemmy.zip 1 day ago
Mhh, yea that seems like the obvious workaround, but not the ideal solution
AtariDump@lemmy.world 1 day ago
Possible? Probably.
Practical? Nope!