The magic is in the rackspace script.
The buttons control the knob
//$<AutoDeclare>
// DO NOT EDIT THIS SECTION MANUALLY
Var
TP : Widget
UP : Widget
DOWN : Widget
//$</AutoDeclare>
// Called when a single widget value has changed
On WidgetValueChanged(newValue : double) from DOWN
if newValue == 1.0 then
TP.SetWidgetValue(TP.GetWidgetValue()-1.0/24.0)
end
End
On WidgetValueChanged(newValue : double) from UP
if newValue == 1.0 then
TP.SetWidgetValue(TP.GetWidgetValue()+1.0/24.0)
end
End
Ah, ok, I found this place and inserted and compiled it in my rackspache. Now it seems to work properly.
I will test this finally again next sunday. Thank you very very much for your help!
I can only test this on sunday at the stage, where my Kronos is located. I thest this with a seperate Rackspace befor the sunday service, so nothing can happen to my live work in the service
And if this works, what I expect, I will build this into all my rackspaces.
Since the update from GP 4.5.8 to 4.7 I have a very strange effect. I have put together the script and the widgets so that whenever I transpose the Midi In (Omni) blocks in semitones using Widgets Up and Down, the corresponding SysEx commands are simultaneously sent to my Kronos to set the global Transposition can also be changed in semitone steps. This worked great until 4.5.8. Since 4.7, the SysEx command is sent correctly and is transposed in semitone steps on the kronos. At the same time, in GP the semitone step becomes a whole tone, even though a semitone is displayed in the Midi in (Omni) block. Does anyone have an idea as to why this might be, or whether this might be a bad bug in the current version?
@joarnstadt I know there were some modifications made in 4.7 to the way transposing works in certain cases. You can check the release notes and see if something there seems applicable to your situation.
The strange thing is that this effect only occurs when the Kronos is also connected. At home, where I only have my SL88 connected as a midi keyboard, the effect does not occur when transposing.
I currently even have the latest version 4.8.2, where the effect is still there, but as I said only when the Kronos is connected. I canāt find anything obvious in the release notes that could explain this behavior.
The only change that was made related to transpostion was in setlist mode where the transposition values in a song part is added to the current transpose amount rather than actually changing the global transpose.
I donāt understand your setup ā are you playing notes on the Kronos that are coming out with the wrong transpose amount or are you playing notes on some other controller that are being sent to the Kronos - where are these SysEx messages being generated?
Without knowing more, it sounds like the sysex messages you are sending to the Kronos cause the Kronos to send MIDI notes into GP transposed by a semitone ā your MIDI In Blocks also have a semitone transpose amount and so whatās actually coming OUT of the MIDI In Blocks are the sum of those two transposes.
No, I have the Kronos on stage as a sound generator and as a midi master that sends notes to gig performers. In the GP I have various VST instruments that I use in parallel. In GP, with the help of Pianopaul, I built a function that allows me to simultaneously transpose the currently active Rackspace in GP and from GP also the Kronos in the Global Transpose generated by the GPScript in GP using a SysEx command. The Kronos transposes correctly, only the VST instruments in the GP are transposed a whole tone instead of a semitone. But this only happens if the Kronos is connected to GP via MIDI. This doesnāt happen at home with the SL88. Without Kronos connected, GP transposes the VST instruments correctly. The setup has only shown this behavior since version 4.7. Previously it worked as planned.
Seems to be some kind of āMIDI echoāā¦ you send a transpose to the plugins and to the Kronos, and the Kronos then sends the same back again into Gig Performer. Obviously your other keyboard behaves diffrently!
So, one way would be to switch the Kronosā LOCAL to OFF and do all the routing within Gig Performer (this should be the most flexible solution, but i guess, you would have to change quite a few things in your setup).
A look into the Kronosā manual showed me that there are two diffrent operation modes for the internal MIDI processing to happen: Pre-Midi (default) or Post-Midi.
Maybe setting the āConvert Positionā parameter to āPost-Midiā could be the solutionā¦ KRONOS/KRONOS X Parameter Guide (korg.com)
Page 770 / 1-1a
Based on what you just said, you are in fact sending MIDI notes from Kronos into GP. So we need to see exactly what is coming from your Kronos (open the Global MIDI Monitor to see this) and what is coming out of your MIDI In block (attach a MIDI Monitor plugin to the output of your MIDI In block to see this)
I can check this on sunday when Iām at the Kronos. I donāt have the machine at home. But Iām wondering, why it worked 'til Version 4.5.8 and since 4.7 not. I have nothing changed in the setup in GP or at the Kronos, except the upgrade of GP.
