-
lacuna
posted in technical issues • read more@oid said:
this won't work if you have more than one instance of the middle abstraction
I knew I was missing sth.
Can we do
[savestate]
/
[route menusave]
|
[menusave(
|
[sendcanvas]using the right outlet bang of [savestate] in the middlepatch, then [savestate] in the child as intended.
I agree with @alexandros init state should work, but in an abstraction it doesn't.
-
lacuna
posted in technical issues • read moreif this is the case maybe you could do a work around by sending dirty message to the middle patch, similar to how I did there:
https://forum.pdpatchrepo.info/topic/15732/how-to-save-restore-multiple-0-array-abstractions-in-a-patch/4 maybe with metro instead of ping, this way you get asked to save before closing.[namecanvas $0-parent]
[loadbang]
|
[1(
|
[metro 20000|
|
[dirty 1 (
|
[s $0- parent] -
lacuna
posted in technical issues • read more@witteruis ctrl+click on the red error line to find the error.
Read here below Fig. 2.1.7 https://msp.ucsd.edu/Pd_documentation/resources/chapter2.htm -
lacuna
posted in technical issues • read more[osc~] [osc~] | | [max~ ]or with [min~], this switches the signals themselfs
-
lacuna
posted in technical issues • read moreDecision of using control-rate or signal-rate basicly depends on where the trigger is coming from: signal-rate or control-rate?
(this is the short answer)I'm not clear on what value "le+23" is meant to indicate.
1e+23 is just a very big number (+ - 1e+32 is Pd's 32-bit single precision space). By multiplying the output of [rzero~ 1] to extremes, then clipping with [clip~ -2 0], turns it into a boolean, either -2 or 0.
Here is @jameslo's example of sigrate flipflop https://forum.pdpatchrepo.info/topic/13918/signal-logic-clocks-division-and-sequences/4
rpole~version should be drop-in replacement.I tried those
please share your patch
-
lacuna
posted in technical issues • read moreNow looking at this years later, in hope that I don't miss the point again:
@ddw_music said:
This naïve approach to timestamps will work only if there is ever only one pending message. If the sender spits out 5 OSC messages with different future timestamps, only the last message will be available in [list store].
The reason for this is that there are only one [delay] and [list store] for several messages.
Haven't tested but I think this works: clone [del] and [list store], and feed the clone with|
[list prepend next]
|
[list trim]
|
EDIT: looking further, haven't tried this neither, but in osc lib, which contains [unpackOSC], is also [pipelist].
-
-
lacuna
posted in technical issues • read moreinlet~ helpfile

Connect [f $1] to [inlet~].
Or use [sig~ $1] ? Not sure what you want to do? -
lacuna
posted in technical issues • read more
Try to undestand the patch and read the manual, esp. 2 control.examples / 08.depthfirst.pd