hi, I've been building a MIDI controller (pots and buttons) using an arduino connected to PD. I've got the arduino communicating nicely with PD via a [comport] - [repack] - [unpack] style setup. The unpacked values (which have been divided by 8 during my C++ code in order to step them down from 1024 to 128) are then patched into [ctlout] objects with cc numbers entered as arguments. But for some reason when i try to assign these to controls in either cubase or ableton the cc values all come up the same. ie... all 4 pots register as the same cc value. even though they are definitely set to different values in PD. I'm using loopbe30 as my MIDI routing application and have my 'MIDI out' in PD and 'MIDI in' in Nuendo seemingley set correctly. Any help with this would be very much appreciated as I have been trying to get this working for months and will NOT give up as it feels as though I am so close/. Thanks
-
Arduino MIDI controller - [ctlout] object sending the same cc value for all 4 different pots to Nuendo
-
@liamorourke show us the patch. also there's some midi monitoring client that could be useful.
Cheers~
-
-
This post is deleted!
-
Hello!!! Again... sorry, my previous post was rubbish...
I have tested your patch with Midi-ox, and it is sending the messages correctly (in Windows!!). You must have something wrong at the endpoint (Nuendo?).
David. -
@whale-av that's odd because it's doing the same thing in Nuendo and Ableton. Thanks for your help though... at least I know I'm using ctlout correctly now so I can direct my focus outside of PD. Much appreciated.
-
I've made a small bit of progress. If i set all 4 output devices in PD's MIDI settings to internal MIDI 1, 2, 3, and 4, whilst setting the [ctlout] object's latter argument to 1, 2, 3, and 4, correspondingly and then set the MIDI input in Nuendo to 'all MIDI inputs' it sends the data separately. However, there are only 4 devices available at one given time in PD so this would mean that i can only send data from 4 controls at once... which is very limited. Plus it's VERY CPU heavy. And the data is by no means smooth. In fact it glitches about so much i can't actually use it. Surely... this isn't how it should be done.
-
@liamorourke Just tested the patch that you posted with Fruity Loops, and it works perfectly. I would suggest that you download MidiOx or some similar tool, and investigate whether you have created a midi feedback loop somewhere. What OS are you using? Of course I have not tested with data arriving at the com-port, I have tested simply by turning your dials..... but as you are un-packing through a number gui, I cannot see why the first part on your patch would cause any problems. Try "magic glass" from the edit menu in PD to see whether your internal messages in your patch look "good".
David.