Re: [Protux-devel] still and rendering farms

[Remon Sijrier]

> Correct.
> But my original idea wasn't based on the idea to render the _whole_
> project, but on render just some small pieces of audio on another machine.
> So, for example, when user notice there is a audio file (maybe a big one
> which would need a lot of time to be filtered) with a _lot_ of noise he
> would like to remove destructive, he just tell protux to do this on another
> machine.

Ah, ok but the problem remains that you have to own another machine to do the 
work on.

>> Maybe "background-rendering" could be the keyword?
>> So it would be nice if protux/user could assign some complex destructive
>> filters to another machine to be rendered in background.

>this the best idea so far , for both rendering the whole project or to render 
>corrective filters (destructive)
>on large files...

I do not have another (linux) computer on the network I'm attached to, and 
this is the same with many (all?) people?
Processing a project in the background by a seperate thread with low_priority 
and go on working with another/same project in the meantime is IMO the 
easiest way to deal with low system resources, but if many people have slow 
computers and more linux workstations on a network, then it is of course a 
different picture, but working on large projects with a slow computer......?

Remon