Hello Alexey
I have just downloaded an advance version of the next Cakewalk release which now supports 25ms refresh time via the Preferences\MIDI\Control Surfaces setup and 10ms by updating the Cakewalk.ini file
I have confirmation from the Bandlab team that 10ms is now supported.
I can get the 25ms setting to work but not the 10ms setting.
Let me explain how I did the refresh time test:-
I draw a single track fader volume automation which goes from -INF to +6dB within a 500ms time window.
I then use the AZ controller app to output the fader volume as CC control messages and monitor these via MIDI-OX.
When I set the refresh time to 25ms, then I get 21 CC values within the 500ms window, which is what I would expect.
When I set the refresh time to 10ms (by changing the Cakewalk.ini) then I still get only 21 CC values within the 500ms window, when I should be seeing 51 CC values (500ms divided by 10ms plus one).
I have asked the Bandlab team to double check, but could I please ask you to confirm that AZ Controller (with a Parameter Value Monitor set to 'Ultra') does not have a minimum response time programmed in to the software?
Kind regards
Robert
Hello Alexey,
Thank you for the information and advice.
Once the next Cakewalk version is released, I will set the refresh time to 10ms and try the loop test as you suggest.
I will test:-
1. Response time from Cakewalk event, e.g. automated fade, to MIDI data output.
2. What happens when the number of monitor action messages (within a 10ms window) exceeds the MIDI capacity (so about 10 x 3 byte messages).
I will report back when I have findings.
Best regards
Robert