Hello, Bindings Brothers.
After a MIDI USB port name clearout, I decided to reassign MIDI to ‘real’ ports and then rebuild assignments and aliases from a clean slate.
Some bindings took a hit, There are several Controller Bar color assignments which flip the buttons from red to green - that’s values 1 and 4 FWIW.
EDIT - it looks like most aspects of the programming got blown out with the exception of, ironically, the source.
Any idea why the result would have been torpedoed, @brad?
I’m not sure what might have happened here but I’d like to investigate. If you can put together a set of steps the reproduces the issue I’ll check it out.
fwiw: the easiest way to remove/replace audio or MIDI ports is by using the aliases feature.
There a few discussions about this already - see here, but basically by setting an alias on a port you’re telling Cantabile to rename anything that references that alias to the new main name of that port. By leaving the alias in place you don’t need to update your songs/racks as they’ll get renamed each time you load them - until you save them when they’ll get saved with the new main name.
Brad
Hi @brad
As removing redundant ports acquired over the years can result in some work to reconfig, I have reproduced the issue by opening the song into another computer where I was happy to remove and reintroduce MIDI ports according to a scheme which I hope will translate as and when hardware changes happen.
This is the correctly presented binding, with the source, target and mapping correctly functioning.
And after importing the same song into another computer, using different interfaces, with the MIDI ports named appropriately, the mapping is blown out. The source and target are presented correctly.
Interestingly, where the blank mapping value is presented, once a value is manually entered, it cannot be deleted and returned to its blank state. It defaults to 1.
Maybe irrelevant, but it caught my eye.
I can understand how a source could be missing, but why the mapping should be the victim is certainly strange to me.
Hope this illustration gives you enough to work on.
Best
Adrian
Hi @Ade,
If the source port existed at the time the binding was loaded then I’m not sure why the mapping value would be lost. If the port wasn’t defined then the mapping should be preserved, but there could be an issue there with it getting lost.
I’m away from my main dev PC for the next couple of weeks, but will check it out when I get back.
Also, are you using Alias to do port remappings? I’m wondering if this is an issue related to that.
Brad