I was once suggested the following hack:
In your patch (probably abstraction), put this:
When you're done with your abstraction, open it in a text editor, and at the very bottom of the file add the following line:
Mind that you shouldn't put any characters like
#Xor anything like that, just the line above.
Note that whenever you edit your abstraction, this line will be deleted, so you'll need to write it every single time you change something.
Also note that
[initbang]is available through deken in the iemguts library.
Youd patch used only a UDP connection, no OSC format in messages sent. Even though you typed an OSC-style address in a message, that's not an OSC format. OSC format is bytes that are not so human-readable. You need to incorporate the native OSC objects that come with vanilla,
Here's a screenshot that does what you probably want (note that the OSC address in
[oscformat]can omit the forward slashes, but since this is a standard OSC-style address, I kept them there):
If I got it right, you want [clip]s to bang only when a value is within these two ranges, right?
Check this arduino-test.pd
I've changed one [change] with two comparison objects,
[<= 55], a
[&& ], and a
[sel 1]This will bang only when the incoming value is between 50 and 55. Do the same for the other range and you should be good to go. Take care to use [t f f] correctly (like in the patch I've uploaded).
[Edit]: Add a
[sel]so you don't get massive bangs, since the Arduino will be sending data in the set baud rate.
Either upload a screenshot of the patch (helpful if the patch is not very complex), or upload the patch (if it's rather complex), or you can even post an ASCII version of it. An ASCII example is this:
[osc~ 440] |\ | \ [dac~]
This is an oscillator object connected to a dac object.
Messages in ASCII look like this:
[this is a message(
And numbers like this:
Well, there might be some program around that does what you guys want without needing to deal too much with programming. Since you're a programmer though, you shouldn't have problems with programming concepts. Still, Pd is a visual programming language that quite some "traditional" programmers don't like.
Sure Pd can do what you want, but you have to learn a bit of Pd programming before you can actually make what you want.
Cyrille Henry has made a very nice abstraction for cue lists. You can find it here http://www.chnry.net/ch/spip.php?article291
Haven't used it myself, but it looks pretty good for this kind of stuff.
There are quite some on Pd's website. Check these:
Even though in the last one I couldn't see the images.