Hi all. I'm new at the forum and new with Axoloti so bear with me.
I'm trying to connect my old Novation Nocturn 25 with no luck. Is there something I need to do to connect an external device or can I use the same midi/in/keyb as for the software keyboard?
Thanks.
Anything appearing in the Axoloti main/log window when you plug in the Nocturn25?
Yes, same midi/in/keyb is fine.
Ive moved this to a new topic, to get a bit more visibility, as others may have tried it.
(Ive not found info, one way or another if its USB midi class compliant yet)
@pmj you mentioned the Novation Nocturn 25 before, did you try it?
Id like to see the console log BUT...
https://cycling74.com/forums/topic/novation-nocturn-usb-protocol
this and the associated code for linux, would seem to imply it is not USB MIDI class compliant but uses its own midi protocol.
note: they seem to refer to the 'novation nocturn controller' its not 100% clear there weren't different models (which i believe there were), and if so if they all followed the same protocol.
EDIT: @johannes, the following linux commit is quite interesting....
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dab9981756dbc3c50c194811f176f0d658c171af
it adds the nocturn to the 'quirks' list, and that quirks header is really interesting, basically lists quite a few devices, where they aren't conforming, but seems with some 'little twists' they can be catered for.
for midi there seems 2 popular 'use-case' quirks, MIDI_RAW_BYTES (old novation products), and fixed end points.
(of course the issue is catering for quirks for devices could easily get out of control... and impossible to test if a developer doesn't have the device to test with... but its interesting to at least 'know about')
EDIT2: after a quick look at the linux midi code...
ok, it looks like, on first glance, raw midi quirk, basically is just treat the usb data as midi... so none of normal CIN/port packet header that is required of the USB MIDI class compliant.
there is also another 'novation' quirk, which again is without header BUT have to strip length data from the usb data.
again, this is just 'scan' of the source code....
(oh, and the novation products with this quirk also appear to need the fixed endpoint quirk)
as i said though, this doesn't solve the 'how to deal with this reasonably' , as i couldn't implement, as I cannot test... and adding lots of quirks for various controllers, could lead to quite alot of firmware 'bloat'.
(its ok for linux, which is most often run on a full-fat computer 
)
Wow, thanks @thetechnobear for the help. I didn't understand half of what your explaining, but what I can read from your reply is that my old nocturn controller probably won't work.
The console log says:
Axoloti says: USB Device Attached
Axoloti says: USB Device Attached
But nothing happens when I press the keys on the controller.
So... maybe buy a new controller then?
Thanks again for the quick replies.
The effort to support non-MIDI-class compliant devices seems disproportional here. I believe Novation could support their customers by releasing an updated firmware that is MIDI-class-compliant, not only relevant for Axoloti... Maybe ask on their support forum.
@PlayDesigner it gives a lot more info than just "USB Device Attached" when the attached device matches a recognized device profile.
Yeah, I recommend ebay-swapping your Nocturn with a different controller. Here's a list of known-working controllers: https://sebiik.github.io/community.axoloti.com.backup/t/usb-midi-controllers/19