olive
olive copied to clipboard
olive-editor
[EXPORT] Headless export from command line
Suggestion
I had idea today, working on a laptop with on-board GPU. I was thinking that a command line export feature for the app would be great to have.
Use case
The not so average Joe, a developer probably, doesn't have a powerful machine. He creates and prepares the assets up to the point to export. How ever, export is going to take a long time.
Instead he rsync the project and content to his workstation or the cloud server and runs a terminal command to export the video.
olive-editor /path/to/project --export --codec=hevc ...
I can also find this useful to shutdown the computer after export is finish...
olive-eidtor ...; shutdown now;
Hopefully the export can run without a GUI env.
Definitely on the roadmap, this was the main remaining issue from #280 but I think this issue describes it better so I'll fold that into this one.
I would love to see this as well. Being able to queue up multiple export/render jobs is the main thing keeping me using Kdenlive instead of Olive right now. My use case is processing 8-10 volleyball tournament games from a single day of play. I have one camera on the game, and another on the scoreboard and use a transform to overlay the score on the game afterward. These all get handed over to the coach for film study, but that's not useful if I can't turn it around quickly (i.e., the next day).
If I could take 5 minutes per game to create the project, then batch export all of them, I'd be able to spend 1 hour doing all the work up front, and let it chug on exports overnight. As it stands today, the tasks are all serialized where I have to wait an hour (or more) before I can start the next project. Especially when I'm working at night when I get home, this makes it impossible to have the videos ready for the following morning. Batch CLI would solve that.
From https://github.com/sobotka/olive/issues/58:
General TODO Summary
Implement exporting a project from the command line without requiring any GUI or interaction.
Additional Information / Notes
Useful for batch rendering. The code has largely been written to support this at some point, it simply requires a GUI-less code path to execute it.
There's an initial implementation for command line parsing without a display (QCoreApplication/custom parser), so that olive-editor --version works in a Docker container. No true headless code path yet (Olive attempts to use QWidgets).
Has there been any progress on this? As with GranitePenguin, my biggest issue with Olive is that there isn't anyway to queue up files. I know there are probably more advanced features and bugs I haven't encountered since I only use Olive for very basic tasks. Still, I'd really appreciate if this could be implemented since it sounds simple and it seems like all the groundwork is in place based on the previous comments.
I apologize if this is already in active development, but this is one of my personally most important features. I just wanted to make sure it wasn't forgotten, It's been ~3 years since the last direct update on this issue after all. I hope to eventually use Olive with Tdarr for fully automatic exports.
For anyone else that wants to use Olive like me or GranitePenguin, you might be able to get away with lowering the thread count of the export and then running it in the background.