Thanks David! Point noted!
1 Like
Before I post my simplified explanation…I’ve come across a problem that may well be a lack of sufficient design in the Kronos midi structure… When I hook up the Kronos via USB it is indeed recognised as a midi device in GP both for In and Out duties. I had been testing this scenario via its midi dyn connectors however in order to now patch change the A-50 I need to have the Kronos attached by USB as the A-50 annoyingly repeats whatever data is coming in to its midi IN to its midi OUTS! Hence in order to send a single program change message from the Kronos I need to have the Kronos set up as a midi device instead of it sat the way it has been in the past as a dual generic midi controller merged with the A-50. Thhis is is not easy to ex[plain! However the long and short of it is that when I try to have the kronos midi device block sending data the key off works to delay the patch change (triggered by either CC89 up or CC90 down) but the sustain mechanism to hold the change no longer works! Could this be a limitation of the USB midi driver for the Kronos or is it somethin in GP?