----- Original Message -----
> From: Phil Stone <pkst...@ucdavis.edu>
> To: Mathieu Bouchard <ma...@artengine.ca>
> Cc: pd-list@iem.at
> Sent: Sunday, February 26, 2012 1:53 PM
> Subject: Re: [PD] OT - C++ for reusable dsp lib - or better use C?
>
> On 2/26/12 10:29 AM, Mathieu Bouchard wrote:
>> Le 2012-02-25 à 14:29:00, Phil Stone a écrit :
>>> IMO, Pd *approaches* this potential of live-coding, but isn't there
> yet. The edit/play dichotomy,
>>
>> The Edit/Play modes are there just to allow more different mouse commands.
> It's not really a feature of the engine, it's just for switching between
> two sets of mouse behaviours in the GUI, because there are not enough buttons.
>
> That's a good point, but the other problem I mentioned -- audio dropouts
> during editing, especially if the dsp graph needs recompiling
When does the recompiling actually happen? In pd-extended 0.43 If I start
editing a patch with a subpatch
that's already full of 700 or so [osc~] objects that are outputting to a bus, I
can continue
patching in the main canvas (with the subpatch unvis'd) and creating signal
objects there,
connect those signal objects to the [dac~] and ramp up and get no dropouts at
all. I also
don't get dropouts if I remove a signal object that was instantiated before all
the signal objects
in subpatch were instantiated, and rapidly redo/undo.
Is Pd recompiling the graph every time I create a new tilde object?
-Jonathan
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
