Nic G (Audeonic Apps)unread,
May 3, 2013, 5:27:07 AM5/3/13
The Dock is a CoreMIDI physical device, so you don't need to do anything different from other physical devices.
How are you determining the list of inputs you display in iFretless? I would have assumed you were scanning the source endpoints which would include all endpoints (virt, phys and net) so I would have thought it would have been effort to exclude the physical ones?
Assuming that iFretless does already handle physical endpoints, then there is probably some issue where the messages from the Dock (maybe bunched into one packet or multiple packets) are being presented in a way you are not expecting?
An immediate workaround for your customer if your app does not currently support physical devices is to use a bridging app that will route from the Dock to iFretless.
I have heard (but have not witnessed this first-hand) that the Dock has issues with sysex messages but I don't think this is your issue.