Maestri:
I would like a special message (let's call it "noop") which when sent
does nothing. (That is to say, sending it would be like not sending
it.) This would be useful in automation. For instance, I may have
a program which generates a bunch of events which I will trigger
using [textfile]. Some of the fields will not be updated in a given
event. In that case, it would like to be able to write "noop" in
that field.
Surely such a thing exists and I haven't found it yet. Feel free to
berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
You could use "bang" for the empty message and have all fields filtered through [float] or [symbol] or [list] or whatever. Then if they receive "bang" they just output their existing value.
-Chuckk
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I can't say much for special message status, but you could use a select object on the recieving end of your messages. [select noop] would have two outlets and output a bang from the right outlet for any message other than "noop" (and a bang from the left inlet for "noop") Chuck
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On the same token, [route noop] would output the original message from the right outlet if it's not noop. I guess, depending which object was doing the receiving, the left outlet wouldn't have to be hooked up at all. If it was going into [pack], for instance, or [append], I believe they store old values for cold inlets. Otherwise I think you'd still need to go through a [float] or [symbol] to send the previous value with the bang from route or select, in which case just using "bang" in place of "noop" might be faster, no?
-Chuckk
On 2/17/07, Charles Henry czhenry@gmail.com wrote:
I can't say much for special message status, but you could use a select object on the recieving end of your messages. [select noop] would have two outlets and output a bang from the right outlet for any message other than "noop" (and a bang from the left inlet for "noop") Chuck
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Actually, you will have trouble with any of these, as just about any object that expects a float (number) will not pass anything if it gets a symbol (word). I'm looking for a way to do it with a couple of list objects, but it could be ugly.
-Chuckk
On 2/17/07, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
On the same token, [route noop] would output the original message from the right outlet if it's not noop. I guess, depending which object was doing the receiving, the left outlet wouldn't have to be hooked up at all. If it was going into [pack], for instance, or [append], I believe they store old values for cold inlets. Otherwise I think you'd still need to go through a [float] or [symbol] to send the previous value with the bang from route or select, in which case just using "bang" in place of "noop" might be faster, no?
-Chuckk
On 2/17/07, Charles Henry czhenry@gmail.com wrote:
I can't say much for special message status, but you could use a select object on the recieving end of your messages. [select noop] would have two outlets and output a bang from the right outlet for any message other than "noop" (and a bang from the left inlet for "noop") Chuck
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[route noop] and keep only the rest.
a
2007/2/17, Chuckk Hubbard badmuthahubbard@gmail.com:
Actually, you will have trouble with any of these, as just about any object that expects a float (number) will not pass anything if it gets a symbol (word). I'm looking for a way to do it with a couple of list objects, but it could be ugly.
-Chuckk
On 2/17/07, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
On the same token, [route noop] would output the original message from the right outlet if it's not noop. I guess, depending which object was doing the receiving, the left outlet wouldn't have to be hooked up at all. If it was going into [pack], for instance, or [append], I believe they store old values for cold inlets. Otherwise I think you'd still need to go through a [float] or [symbol] to send the previous value with the bang from route or select, in which case just using "bang" in place of "noop" might be faster, no?
-Chuckk
On 2/17/07, Charles Henry czhenry@gmail.com wrote:
I can't say much for special message status, but you could use a select object on the recieving end of your messages. [select noop] would have two outlets and output a bang from the right outlet for any message other than "noop" (and a bang from the left inlet for "noop") Chuck
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- http://www.badmuthahubbard.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
float won't take "noop".
On 2/18/07, hard off hard.off@gmail.com wrote:
with a list, route only works on the first element<<
yeah, so unpack the list first, and route each output individually.
like:
[unpack float float float] | | | [route noop] [route noop] [route noop] | | |
I mean, [unpack float float float] won't take "noop"
On 2/18/07, hard off hard.off@gmail.com wrote:
with a list, route only works on the first element<<
yeah, so unpack the list first, and route each output individually.
like:
[unpack float float float] | | | [route noop] [route noop] [route noop] | | |
That works for floats, but again, [unpack s] won't take -1. David hasn't said much about what types of arguments he expects. -1 for floats and noop for symbols would seem to work.
-Chuckk
On 2/18/07, hard off hard.off@gmail.com wrote:
oh yeah, sorry. that's why i would use -1 or another integer instead of noop.
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
That works for floats, but again, [unpack s] won't take -1. David hasn't said much about what types of arguments he expects. -1 for floats and noop for symbols would seem to work.
[route noop] accepts everything and will only block, if it gets "noop"-messages like "noop" and "noop blocked ..." See attachement.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
On 2/18/07, Frank Barknecht fbar@footils.org wrote:
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
That works for floats, but again, [unpack s] won't take -1. David hasn't said much about what types of arguments he expects. -1 for floats and noop for symbols would seem to work.
[route noop] accepts everything and will only block, if it gets "noop"-messages like "noop" and "noop blocked ..." See attachement.
He wants certain fields to stay blank, not certain lists to be ignored.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
This works. Ugly error messages, if that bothers you, but no messages passed on "noop".
-Chuckk
On 2/17/07, David F. Place d@vidplace.com wrote:
Maestri:
I would like a special message (let's call it "noop") which when sent does nothing. (That is to say, sending it would be like not sending it.) This would be useful in automation. For instance, I may have a program which generates a bunch of events which I will trigger using [textfile]. Some of the fields will not be updated in a given event. In that case, it would like to be able to write "noop" in that field.
Surely such a thing exists and I haven't found it yet. Feel free to berate me if it is right under my nose.
Cheers, David
--o-------o-o-o---o-o-o--- David F. Place mailto:d@vidplace.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
quick edit to make no errors (i hope!)
i mainly like this thread cos it has given such life to the word 'noop' ;)
Brilliant solution. I knew there was one. Pd still confuses me with lists and identifiers.
-Chuckk
On 2/18/07, hard off hard.off@gmail.com wrote:
quick edit to make no errors (i hope!)
i mainly like this thread cos it has given such life to the word 'noop' ;)
-
Alexandre Quessy -
Charles Henry -
Chuckk Hubbard -
David F. Place -
Frank Barknecht -
hard off