I have just updated GP from 4.5 to the latest version 4.8. Now I have an issue with the MIDI In block transpose function regarding the usage in rackspace variations.
Example:
I have a Piano-Rackspace with variations which are individually transposed.
Like this:
Rackspace 1 Var. 1 - Piano T+00
Rackspace 1 Var. 2 - Piano T+04
Rackspace 1 Var. 3 - Piano T-03
I used the MIDI In Transpose function for that and the values were stored in each rackspace variation.
It was working fine in GP 4.5, but after updating GP this is now gone somehow. If I change the MIDI In transpose value in a variation, it is changed in all existing variations.
I would like to avoid changing global transpose and stay with this MIDI In transpose functionality. I liked this way to keep a single rackspace and just give the variations some transpositions when needed.
Is there a way to keep this, or is it completely gone with the update?
How did you transpose the MIDI in blocks?
Can you upload a small gig file, so I can check the issue?
I am sure that a transpose without using widgets is global for the rackspace.
I’m using the Midi In block by changing it’s transpose parameter with using up and down buttons.
It was working with GP 4.5 to have in every rackspace variation a different transpose value.
Now it’s like I change it in one variation, all variations are following the same new value. I did not change anything other than updating GP 4.5 to 4.8. Looks like something was changed in 4.8 (or 4.7).
I can upload a reduced gigfile if that helps, but I can’t recreate the GP 4.5 behaviour after the 4.8 update.
A) those transpose values are remembered by widgets so do you have a widget attached to the transpose parameter?
B) Assuming you do, did you make sure that the widget is not set to ignore variations?
You have to unlock the text widget, then all is working.
To Lock Widgets is a new feature.
In the past there were some issues with displaying parameter values in text widgets, this has been solved with the new “lock” feature.
No - only text widgets - because they have a new feature, the ability to change values rather than their just being read-only when you click on them - per the help message that appears when you unlock one.