@whale-av thanks for that, will give it a test once I return to the studio.
There is actually no specific need to use PdParty, as all I actually need in this instance is a wireless controller. I assume that I'll have the same issues with TouchOSC if they use MrPeach objects too?
To be blunt, this is almost the straw that breaks the camels back... I've been struggling with issues like this and PD Vanilla for awhile, and I'm close to just giving up and trying to save for something to run Max/MSP on instead as I have less issues and faster workflow when using that (like running it on a Latte Panda for instance).
Is there any easy way to communicate wirelessly through IOS with PD Vanilla? Maybe I should look at a basic wireless / bluetooth Midi Controller instead? Very open to suggestions here before turning into a version of the Incredible Hulk....
All I'm currently trying to do is set up PdParty on an Iphone to control Pd on another computer via Wifi, not exactly rocket science I know, but I'm willing to admit that it's beyond me right now...
I have spent the last hour or two looking through the PdParty test libraries as the documentation mentions a basic test send/recieve patch that can be used, but I can't seem to find it at all.
Can anyone attached the basic pair here so I can figure out how it works?
And because I'm continuing my ongoing understanding of networking, does OSC use specific IP address for communication like netsend/netrecieve, or is it a different beast based upon just using a port and then an associated name and value, with the name being used later to filter the value back out at the other end?
I'm just trying to begin to understand how to use netsend and netreceive objects between two computers to transmit OSC messages (needs to be using PD vanilla for this project).
I'm still very much learning networking, so am trying to limit myself to a basic example. But when I try these to patches, the one running the send patch bring up the messages:
recv: Connection refused (61)
netsend: Bad file descriptor (9)
Warning: 19 removed from poll list but not found.
Can someone help me to understand these errors, and then what to do to get these patches to talk to each other?
The overall plan is to get get wireless control over a RPI running PD, and control it using PdParty on IOS.
@whale-av Thanks again for your help, and for explaining your patch further.
I ended up just using flags in the startup for the rpi, which to my amazement worked first go, and seems to be a solid solution for the time being. Good to know there are other options thought!
I'm working my way through the process for uploading firmata onto my arduino uno, using the Floss guide
I just downloaded the latest version of the arduino program from the arduino website, and then went through the process of deleting the old 'firmata' folder, and replacing it with the new one downloaded from: https://at.or.at/hans/pd/objects.html (running mac os 10.9,5).
However when I try and open the the arduino application, it comes up with an error that reads '"Arduino" is damaged and can't be opened. You should move it to the trash'."
I assume it has to be that specific Firmata in order to work with the Pduino objects? And is there any other way to upload it ? Or am I missing something obvious here?
I did think about rather than deleting the older firmata folder completely, just deleting the individual files and replacing them with those from the downloaded folder, but not sure if that's a good idea or not....
Hey David thanks for the reply.
I'm running Raspbian as its running on a raspberry pi, and using Vanilla PD. I opened your patch, but the 'mediasettings/audiosettings' doesn't seem to work on Vanilla.
If I bang the settings in the bottom right hand corner, it does open up the same settings as the last time I used the patch. But I'd like a way too make it a definite rather than a potential unknown (this will be operated as part of an installation and I won't be there to start up each day).
I think I can use flags when opening through terminal to get it to boot the way I need to, similar to your suggestion. I was just hoping I could keep everything within PD, as I find that much easier if I need to run patches on different systems
I'm just working on a patch that needs to start automatically when opened, which is working fine so far. The only thing I have to continually set is in 'Audio Settings' whereby I always have to change the input and output to read:
'USB Audio CODEC (hardware)'.
I assume there is a message that can be sent internally to get this to happen, but I've got no idea what it is. Can anyone help?