Did you try your script *without the loop* ?
e.g. just render one csd and then quit.
If that works (or not) it will be easier to chase down the problem.
best
Oeyvind

2007/10/26, Tim Mortimer <timmortimer@d2.net.au>:
>
> Oeyvind, Michael, everyone.
>
> There is no need for threads or anything fancy i shouldnt think / hope
>
> all i want to do is call a bunch of csd's in a folder (that as it happens
> have been generated & assembled using python), & render them to their -o
> "xyz.wav" as already hard coded / flagged / defined in each <CSoptions>
> within each CSD.
>
> one after the other is fine. if i have a piece based on 16 separate phase
> vocoder instruments, each pushing up around the 100% cpu mark, it's gonna
> make a lot more sense for me to just render all my "material" & then have a
> very simple arrangement csd to tie it all together & play it back with. That
> way if i change 1 instrument part, i don't have to worry about rendering a
> whole performance. & it will save me typing "csound joebloggs.csd" a million
> & one times....
>
> i'll even settle for a .bat file if it comes down to it!
>
> but all i've managed to suss out about that is
>
> for %f in (*.csd) do csound .... ???
>
> can anybody complete that statement? (windows)
>
>
> --
> View this message in context: http://www.nabble.com/batch-processing---rendering-CSDs-using-Python-tf4675931.html#a13421839
> Sent from the Csound - General mailing list archive at Nabble.com.
>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>