Hi Alexey
I have spent some time testing the custom build of Cakewalk with added caching in the main control surface handler.
It works well except for one unforeseen issue which I have discussed with Mark McLeod, as follows:
The track Record Arm function is part of what is called the topology graph, which is basically the audio routing graph. So pressing a track Record Arm button causes the cache to be reset.
The effect is a very slow reaction time from pressing a track Record Arm button to that button being fully illuminated. (about 1 second). The impact on the global 'Arm (UnArm) all tracks' button/indicator is even worse (about 2 seconds). It is not a disaster but you end up double checking to see if a record arm action has actually happened.
I tried, temporarily, removing the track to output feedback actions in my AZ preset and the Record Arm response is fast again, so it is the requirement to monitor track to output status which slows down the cache refresh. I also tried changing the controller refresh frequency from 25ms to 75ms. It does not improve the cache refresh time.
There is nothing that Mark can do to fix this problem as the cache is across the whole audio routing graph.
The issue does not impact on any other important track functions, e.g. SOLO, CUT, Fader, Pan. These are not part of the audio routing graph.
But I wanted to ask if there was any way we might deal with this issue in the AZ app? Let me explain my small hope!
I use two instances of AZ Controller with Cakewalk, each with one preset.
'REPLAY' I use when I am mixing, so it includes the track to output monitoring. It does not include the track Record Arm buttons.
'RECORD' I use when recording. It does include the Record Arm buttons but does not include any requirement to monitor track to output routing status.
I do switch between these two operational modes often (using two screen based buttons), so I want to keep both instances enabled.
So, is there anyway to either:
1. Make the monitoring of track/bus to output feedback actions conditional on another control state (so I mean a supplied MIDI code). It would have to be a way which temporarily removes the feedback actions from being 'seen' by Cakewalk.
2. Within one instance of AZ Controller, switch off the preset 'on the fly' so I mean again by the application of an incoming MIDI command.
3. Turn on and off an instance of AZ Controller 'on the fly' (same idea as point 2).
Any of these methods would provide a way to switch off the track/bus to output monitoring when it is not required, This in turn would speed up the Record ARM button response.
Or any other ideas to fix the issue?
Best regards
Robert