Midi Abbreviations (port) issue
Hi there,
I'm having a slight issue with midi device abbreviations. After setting an abbreviation (port) in midi setup, if I use an argument on midi objects (such as notein /ctlin) to specify the port (a-z) it seems to still accept all input regardless of the port argument.
i.e. my LPD8 device is given the abbreviation 'b' for both input & output in midi setup, then I create a ctlin object with the argument 'a'. The object still sends out data from the LPD8 even though port 'a' has been specified. Am I missing something obvious?!
Thanks in advance,
Sam
Hello.
In my own expérience I prefer to do not use the abrevation way to feed midi object. I think that using the entire name (the exact name appeating in your midi setup) between quotes is working better and avoid misorder of abbreviation that can occure sometimes.
Try : [notein "name of my controller"]
I find that strange. I have 14 midi ports defined with letter abbreviations in my current mega-project and they all work fine.
I don’t suppose you could post your patch and a screenshot of your midi configuration page as it’s a bit difficult to say where the problem might be otherwise?
Hi guys, thanks for taking the time to reply...
Just figured out what the problem was. Silly of me really but didn't realise that a midi port actually has to be assigned to a device in order for it to become active within Max. I was using an unassigned port as an argument thinking it would block my device but instead it seems to just ignore the argument and therefore pass all data through. Well I've learnt something today :)
Thanks again!
I did wonder if you had the MIDI configuration page set up correctly. It's one of the big differences between Max and Max-for-Live - Max requires some configuration if you want to use abbreviated port identifiers (a-z) but allows you to connect freely to any device, whereas M4L links the MIDI ports directly to individual tracks and allows no (or precious little) other flexibility.
Make sure you have the Max 8.2.2 update as it now copes with devices being connected/disconnected dynamically without forgetting how the ports were configured in the past.