Perhaps not an actual programming mistake, but a use-case that stymies users from success using cakewalk. Personally, i think this is a use-case-bug. Additionally, it separates you in time from the triggering change, making it harder to associate the action with the outcome. This prevents you from using that input for a midi track but not from selecting that input on the midi track. Cakewalk will assign the next midi input to that controller on cakewalk restart. The above is what I worked out to fix the condition of a USB port mapping for my midi controller having internally changedįor me, this is almost always caused by cakewalk having the midi mapped to a controller in preferences. I do not have a foolproof resolution to the above, if that is what has happened on your system, but what I end up doing is the following, and please note that I have to keep doing this whenever I open up an existing project, because those projects were saved using the old and invalid internal association between the midi controller and the old USB port:Ġ2) Go to Edit > Preferences > MIDI > DevicesĠ3) Remove the midi controller from Inputs and the Outputs sections, by removing the X from the check boxes for that midi controller, and click ApplyĠ6) Go to Edit > Preferences > MIDI > DevicesĠ7) Declare the midi controller again as a valid Input and Output midi device, and click Apply, and exit PreferencesĠ8) Immediately save the project, so that it has the above changes saved.
When the above occurs, even though you see the device in Preferences > Midi > Devices, it really is not mapped to the current Windows internal association to the new USB port, and so Cakewalk won't detect any midi activity for that midi controller. When the USB port mapping changes for an audio interface or midi controller, Windows creates a new internal association between the device and the USB port, and because all you see, in both Cakewalk and in Device Manager, is the NAME given to that device, you cannot readily tell that its internal association to a USB port has changed.
SO, those ghost entries are showing you that there are drivers from other USB ports, but they are not currently active. If you go into Device Manager, then click on View > Show Hidden Devices, and expand the Sound, Video, and Game Controllers category, if you have multiple drivers for your midi controller/keyboard, where there is one entry that is darker than the duplicate ones (like those would show a fainter gray color), then that means you have what are commonly called 'ghost entries', and what that is evidence of, is that your device drivers for that midi controller were at one time plugged into a different USB port.