Hi,

I'm just wondering if you had a bunch of networked lightworks systems, is it easy to set up a machine to do all the project exporting en masse? Would be handy to be able to add batches of exports to an ongoing list, rather than have to do it piecemeal.

Any info on this would be much appreciated.

You can certainly export numerous item at once - the contents of a bin for example - but at the moment you'd be exporting them all using the same settings (ie. you wouldn't be able to export the same edit multiple times as SD, HD, etc, in one go)

Only being able to export one format at a time would be ok, can transcode using other tools, but is it possible to add to the render queue before the current job has finished?

If not I guess I need to look at exporting procedural files from Lightworks and rendering with other software that has queuing functionality. I don't suppose you have any knowledge of this particular usage of Lightworks?

Thanks

I think this is where the Open Source release comes in. From the code, someone could create a LW Render Server and LW Render Client. Basically the server could import projects, select what needs to be rendered (edits, bins, etc.) and tell the clients what to render and the export format(s) required. Each client could be rendering to a different format or if image sequences are being rendered, which frames to render.

That would be sweet.

The best I can up with so far is exporting Lightworks as EDL, importing to FCP 7, and then using FCP / Compressor for the render queueing.

If anyone has any better ideas, please do enlighten me!

I still pine for a render queue...

Using the shared project feature of the Pro version of Lightworks, you can set up multiple systems to enter the same project at the same time. This would allow you to edit on one system while the other system did any necessary rendering/exporting Any new files created in the project would immediately be accessible to all the other systems in the same project.

What I want to be able to do is create lots of projects on multiple edit computers, and then export them on one big hefty computer.

The thing with doing that, we would need a queueing system for the rendering, so that new projects can be added to the queue, and indeed moved to the front of the queue if they are a priority.

I'm trying to find a good system for using lightworks as the editor. Seems like I will need to export from lwks and use another system for the export queue... FCP Studio 3 or Adobe CS6 look like the most viable options so far, but would be amazing to be able to do it from lwks.

Once Editshare releases the code, a freeware/commercial developer could create a system you describe. The rendering application on your hefty machine would have a minimal gui (just enough to manage queues), full effects capabilities and access to each edit machines project folder or the edit machine would send the rendering machine copies of the required project files, and the edit machine would sent instructions on which timeline(s) to render and where to render them to.

Here's another scenario. Having one editing machine (the server) and a render farm of multiple client machines where after the edit is complete you want to render out to TIFF or JPEG2000 or other image sequence frames and WAV audio for DCP package creation or import into a compositing application. The server edit machine would send instructions to the client machines to render only certain frames of the edit, dividing the project up between multiple machines thus speeding final delivery.

Stop tantalising me!



I don't suppose you know any NLEs with good export queuing do you?