Good evening community,
at the moment I have a serious problem that really drives me nuts. During the last weeks I have been fiddling around with some midi hardware components and tried to integrate these into cantabile with total recall capabilities.
To do so I tested several solutions to reflect the settings of the hardware inside cantabile, store them in host automation parameters and recall them when calling up a new rack state and finally song of course.
All this works well so far. My latest attempt uses simple audio routings where I misuse the audio
fader as memory element, indicator and control unit. Wrapping several of thee into a rack does the trick.
My problem occurs when it comes to the midi control parameter CC66 (sostenuto). Whereas this works flawlessly when simply selecting different rack states by hand I get a strange effect when putting this rack into songs and switch from one to another.
As long as CC66 is not part of the parameter set
everything is fine. If CC66 is active the stored value is correctly sent but followed by a second
instruction CC66 = 0 each time (independently from the stored value).
I tried several things to get rid of this effect (f.e.: I changed the control value for the input signal from
66 to 67 with a midi filter and reverted it back on the output of the rack) without any success.
It seems that cantabile takes note if CC66 is sent when switching songs and persists in adding CC66 = 0 each time (seems to happen outside the rack).
I had a look inside the background rack but found
neither routings nor bindings being capable of producing something like that.
So, my question: any ideas? Any help warmly welcome
Thanks and regards, humphrey