Multiple/Queued Rendering: Wishlist

Hello Michael,

There are a number of OpenSource render farm packages available.

An example is farmerjoe.

These render farms can handle systems like Blender, Yaffray, Povray, etc, so I don't know of any reason why you shouldn't be able to adapt them to work with OpenShot.

Helen

It might not be that hard to have a separate thread which handles the rendering. Each time a user renders a project, it would add it to the bottom of the "queue", and the thread would just work through the queue of OpenShot renders 1 by 1. This would allow the interface to be un-coupled from the rendering... so a user could continue making edits, or load another project, etc... It's not a version 1 feature, but a good idea for sure.

i don't think anything like farmer joe could be implented with OpenShot. But i agree on a queue. I have two things to say related to this.

* Network Rendering: allow other computer to render over the network. OpenShot could have a "Sever Mode" where there is no editing GUI, just a a setting for what ip to connect to the master. (the master would be the machine editing.)

* Background Rendering: while editing the video render the whole movie. When ever a change is made to a clip it render that clip again. So exporting would be just saving the prerendered movie.

These two features together would make rendering a long movie much faster.

P.S. Jonathan, have you ever thought of having a normal and advanced interface once OpenShot get more and more advanced features. (ex. I don't think a noob will know or need these two features, but a more advanced user (many linux users) will probably have more than one computer available for them to render on.)

jafapt on 2010-01-17

My idea was to have a program that does this function (rendering) separately, leaving the user free to continue working while the program performs its function to export the video independently.
Thus maintaining the focus on the issue and increasing productivity, without wasting time having to wait the file to be rendered.

Nice ideal(s). How about adding a networked rendering farm feature to the rendering master. Or, use BURP/RenderFarm distrubited computing projects.