![]() ![]() To be able to possibly help, we need more info: it could be your patch is not setup correctly, which is much easier to fix. please test your patch with another midi controller (din/computer) first, or at least test with the demo patch first e.g.if you need to load drivers, its likely not to be class compliant. ensure your device is class compliant, so test on a computer *without any** manufactures device drivers loaded.some devices draw too much current to be bus powered. if the device accepts external power, try with external power.please check you are using the latest firmware (etc) for the device.ensure your device is connected directly to axoloti NOT via a hub.This is why, Axoloti should (and does) just work with most controllers, as long as they follow the specification. ![]() midi/in/keyb) do we start splitting messages up. USB devices can share a number of ports (as opposed to channels which are different), it then sends all messages as 4 bytes (yes, even 2 byte midi messages, and sysex are also split up), so if you get one message type, then this shows Axolotis hosting is working. Some basic info, about the USB hosting provided by Axoloti IF you need to installed a driver on a computer to get it to work, it probably is not class compliant, so will not work with Axoloti. most (not all!) modern midi devices with USB are class compliant, but this was not always the case, older hardware very often is not.Also it should be noted, many controllers have 'modes', some of which may need midi messages to be sent to the controller to activate. Its obviously impossible to test every controller, there are 1000's of them, so its a community effort, and helps to find someone else who also has the same controller to see if they have similar issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |