This is a forward slash: /
This is a back slash: \
Forward slash doesn’t work, back slash does, it escapes the next character, essentially “removing it’s special meaning and treating it like any other regular character”
2 Likes
Thank you! yes… I’ve used my fair share of forward and backward slashes in life up to now. 
I am also pretty familiar with escape characters.
However it’s still not working. It escapes the ‘newline’ in the message from the semicolons but it sends the message with the forward slashes so ORCA won’t receive it. At least I think that’s the issue…
At any rate, nothing is happening in ORCA when I send the message.
1 Like
Ok. Good luck getting it working…
2 Likes
sorry, if I came across as short. I know you have no way of knowing where I’m at and I appreciate your help.
Mostly I’m finding this particular exercise frustrating but I’m still learning things and I think I might still be able to get some interesting results from what I’ve gotten to work so far.
1 Like
Do you know your way around node? Could you try this script and send PD data to it to see what Orca receives.
1 Like
Just mocked this up and it all works for me. Hope it helps.
4 Likes
Thank you so much!!!
Ok so, I have been experimenting with the semicolon thing for quite a while now. I found that no matter how I would compose the write function for a semicolon, I was unable to. So I thought I would see if it was at all possible to write semicolon in ORCA’s own console. While I was able to write colon : for MIDI and equals = for OSC I was unable to write semicolon ; for UDP message thing. It seems that it is just impossible in general to use the write message for the semicolon operator at this point in time. I know this is such a minor thing, and I don’t know who would really need to be able to write semicolon using a write command, other than me in this very particular case. Well at least we know one of ORCA’s limitations now I guess hehe 
If I could suggest something radical here. What if we changed the symbol for UDP “;” with the old symbol for recieve midi the “&”? I bet that would solve the problem
Mhmm, that’s an interesting bug, you can’t write the udp operator with the udp operator. Let me think about this for a little while, I think I can find a way to make it work… stay tuned.
2 Likes
I am new here, how do you draw this? looks interesting to me.
Thank you! is a great tool
Okay, still not working. Here’s what I have.
here’s what get’s output when I try to bang those messages:
it’s silently commenting out the dollar signs as well?
I should also make it clear here that although I’ve done a little programming this is really my first time trying to make something with PD.
HOLD THE PHONE! Now the ‘send write’ message is working but not the select message
I had that same issue when I was developing it, but I never figured out exactly what caused it. If you take one of the f’s out of pack, you’ll see that you get the same error message. This is due to the fact that the message is expecting more variables than it is receiving.
I believe it’s likely an order of operations issue(for some reason pack isn’t getting 2 values, or isn’t sending 2 values to the message?). You can read about PureData’s unique order of operations here: http://write.flossmanuals.net/pure-data/order-of-operations/
and if I figure out exactly what’s causing it I’ll share.
I haven’t tested this in PD yet but in Orca select requires 4 arguments. It won’t do anything with select:1;2 but select:1,2,3,4 will immediately jump and select an area.
Yep! This isn’t working exactly right. The second inputs don’t update until you change the first two but it works. You just need 4 arguments
Yes, I’ve just been using 2 arguments for select and it works fine to move the cursor around. Which is honestly useless to me, but it proves that it works.
As for the values not updating unless you change the first 2 values. That’s why I have that weird interconnected [bang]. Pack only updates its output when the left most inlet is changed. So I made it so that anytime the 2nd/right number is changed, it also forces an update on the left/hot inlet. To make this work with your new version, you need to make the outputs of all your numbers(except the first/left one) go to the top of the bang for that part. Looks like you did this for the rightmost one.
1 Like
well now I that we’ve got these two working how about the ‘find’ command. It works from console in Orca but ‘send find:aV’ from pure data does not.
It seems like being able to jump around to different variables and effect them with pure data would be pretty neat!
1 Like
I can implement that, gimme a day or two We’re doing big boat projects right now, but I’ll add this as soon as we’re back in the water.
4 Likes
Thats nice, are you planning to make more travel videos again soon? I really like the once you have made, truly inspiring
2 Likes
Hey,
Another thing to look at if you have the time is that the command “bpm:” also doesn’t seem to work when sending from Pure Data
1 Like