Hi,
This must have been discussed in the list before, but I couldn't find
anything in the archives because it's difficult to generate a
meaningful set of keywords for this..
In a merely fortuitous way, I found out that if you send a message
starting with the keyword "dsp" into an inlet of a s
This is not a good answer for you but you can use this solution to
send the message |dsp 1(.
(see the patch).
++
Jack
inlet_dsp_messages2B.pd
Description: Binary data
Le 1 avr. 08 à 18:05, matteo sisti sette a écrit :
Hi,
This must have been discussed in the list before, but I couldn't
Oops! I'm using "dsp" for objects to intercommunicate, but I had meant
to protect anyone from stumbling on it. Obviously I missed something.
I can suggest many possible workarounds, but will get around to fixing this
someday.
cheers
Miller
On Tue, Apr 01, 2008 at 06:05:37PM +0200, matteo sisti
Miller Puckette wrote:
> Oops! I'm using "dsp" for objects to intercommunicate, but I had meant
> to protect anyone from stumbling on it. Obviously I missed something.
the really bad thing is (as indicated in my other mail):
[dsp(
|
[+~]
weird that i _never_ stumbled across this, even though i
Jack wrote
> This is not a good answer for you but you can use this solution to
> send the message |dsp 1(.
Miller wrote:
> I can suggest many possible workarounds, but will get around to fixing this
> someday.
Thank you both; don't worry for solutions/workarounds: I wasn't using
this message v
matteo sisti sette wrote:
>
> It seems like the inlet itself "catches" it...
>
> I don't know what [inlet] is supposed to do with messages starting with "dsp".
> I thought it may perhaps switch~ off the subpatch, but it doesn't.
>
> Is this a bug or a feature?
> Is it documented somewhere?
i do
