atom feed5 messages in at.iem.pd-listRe: [PD] Feature suggestion: pd non-r...
FromSent OnAttachments
Johannes TaelmanNov 8, 2002 3:05 pm 
Krzysztof CzajaNov 14, 2002 4:04 am 
Krzysztof CzajaNov 14, 2002 5:31 am 
Miller PucketteNov 14, 2002 8:38 am 
Johannes TaelmanNov 14, 2002 10:09 am 
Subject:Re: [PD] Feature suggestion: pd non-realtime
From:Krzysztof Czaja (cza@chopin.edu.pl)
Date:Nov 14, 2002 5:31:06 am
List:at.iem.pd-list

hi Thomas,

such decoupling, while very useful, looks a bit tricky. How to interface the decoupled part with the outside world -- in particular, with the main signal chain? Are i/o objects, like inlet~/outlet~, throw~/catch~, and send~/receive~, to be disabled, and if so, how to ensure disabling all such interface objects, possibly externals?

What I was talking about (several times already), i.e. doing it system-wise, is very simple, and does not involve touching anything other in the code, than the scheduler and the command-line parser. If available, one could try to run separate, out-of-time and guiless Pd processes, and interface them with the main, full-featured (audio and gui) Pd process.

Krzysztof

btw, what is pd-l@dergeheime.goldfisch.at?