Hello, I'm currently trying to get better at using Osculator and pd in unison. I'd like to start working on PD tutorials, but I want to always have them running in and out of Osculator. Could anyone with experience in either PD and/or OSC let me know if I have done my code between them effectively and without redundancies...
Osculator file:
I start off in Osculator with creating a manual message "/ya/1" with an OSC Routing of localhost:9000.
PD file:
- receiving code
(object) udpreceive 9000
|
|
(object) unpackOSC
|
|
(object) routeOSC /ya
|
|
(object) routeOSC /1
|
|
(number)
|
|
(object) send hot
- sending code (separated from my receiving code)
(message) connect localhost 9000
|
|
(object) udpsend
(message) disconnect
|
|
(object) udpsend
(object) receive hot
|
|
(message) send /ba/1 $1
|
|
(object) packOSC
|
|
(object) udpsend
...So when i test the /ya/1 message in Osculator with my mouse, I get the /ba/1 message added to Osculator. As I continue to click with my mouse, both of their activity boxes light up green in unison.
I'd like to know if this coding between Oscualtor and PD is efficient enough to move on with practices and tutorials in PD?
Is there a way to code udpreceive and udpsend interconnected rather than separated as seen in my PD file?
Should Osculator have two messages that are OSC Routing rather than one?
Let me know if anything is confusing or in need of clarification. Thanks!