Control & GUI issues going from GP4 to GP5

Howdy y’all,

I’m sorry if this has been addressed already, but I’m not getting good results from searching the forum (not even really sure how to frame the search terms, tbh).

The problem has to do with variations within a song. A pretty simple GP file that works as expected in GP 4 is NOT working as expected in GP 5. I can only assume I’m missing some new option or intended change in behavior.

As mentioned, the file in question works as expected in GP 4 - I’ve got 2-ish years of touring on this rig with no issues.

However, in GP5, choosing a variation does not send the CC message for preset changes to Pianoteq, but it DOES send other CC messages as intended. FWIW, I have CC119 enabled in Pianoteq for preset changes, CC22-24 for tremolo control.

And, some of the GUI elements that are supposed to update based on the variation work as expected, some don’t.

Here’s a video that shows the problem more clearly than I think I can explain: https://youtu.be/Gq_vO9cA8i0?si=XCbtLXXRH52MVISH

I’ve got both versions up side by side, and I don’t see anything in the options that looks like it’s the root of the problem, but I must be missing something.

If I go into edit mode on a panel for a given variation, setting the value for the widget associated with the CC for presets actually sends the correct data to Pianoteq as I’m changing it. Once I go out of edit mode, changing variations does NOT send the data from the widget as expected, and the presets don’t load.

Testing with a different kind of widget (a knob instead of a text label) produced a happy ending, but it still begs the question as to why the previously functional set up is no longer functional.

What’s more, as you can see from the video, I’m not getting consistent behavior for how other GUI elements are changing from variation to variation. Some widgets seem to behave exactly as they should, some don’t, but when I go into panel edit mode to look at their parameters, they all seem to be set correctly.

I built a simple file to make sure I didn’t bork something up: just the MIDI in to Pianoteq, and straight to the main outs. I added two text boxes to a black rack space and made two variations within one song. Variation 1 has the value for box 1 at 100 (fully visible), box 2 at 0 (basically hidden). Variation B has the value for box 1 at 0, box 2 at 100. I would expect var. A to show box 1, var. B should show box 2.

In GP4, with the widgets set to load an explicit value, I get what’s expected. In GP5, I’ve tried all the combinations of settings (explicit value vs last saved, reset, etc.), and the box’s visibility persists once I make a given setting.

I’m 100% sure I’m missing something that’s staring me in the face, so I figured I’d toss my stupidity in the ring and see if anyone can bail me out. GP4 is still working beautifully, and I thought it would be an easy jump to v5, but…

Thanks in advance for any help, and sorry if this has been answered 100 times since GP5 came out :slightly_smiling_face:

cheers

Conrad St. Clair

How are you sending CC messages into Pianoteq? Do you have a widget mapped to the CC message parameters of a MIDI In Block?

If you are using Text Label blocks to send different CC messages per variation, I think this might be the key setting you need to check:

If your text labels have ‘Lock’ enabled, then disable this on all the widgets in each rackspace and see if that fixes the issue.

3 Likes

After unlocking the widget, you might have to re-enter the CC changes (widget values) if you were using the text labels to change them.

This change was introduced in GP 4.7. Are you upgrading from an earlier version of Gig Performer 4?

2 Likes

Yes!!! I knew there had to be something simple…

And also yes, I was coming from v4.1. We’ve been active enough and things were working fine, and upgrading isn’t something I like to do if there’s a deadline :wink: Got some down time before the next tour, so I figured now was the time to go through the growing pains…

Thank you SO much!!

4 Likes