Ribbon Controller Problems on my SG

Hi,

i’ve 2 big problems with the ribbon controller on my SG:

  1. In SPLIT mode the ribbon controller only works with the lower layer. I excpected i can choose the layer it works with by pressing the layer select buttons, but that is not the case.
    Is that an error on my SG?

  2. If i set the ribbon controller on the lower layer to controll something different than pitch, it is still controlling the pitch plus the new assigned parameter. I’m sure that is an error!
    The question is can this be fixed by a firmware update or is this a hardware problem on my SG?

The SG is on Firmware 1.25.
Does anybody have the same problems or knows a solution?
Thanks!

Hi there, thanks for reaching out. As this is a support enquiry, we would be happy to answer your questions via our support channels. Just email us on support@udo-audio.com.

But while i’m here…

  1. It sounds to me like you haven’t adjusted the switch which determines which layer the ribbon is active on. Next to the portamento slider is a 3 position switch. Amoung other things, this controls whether the ribbon effects the lower, upper, or both layers.

  2. The ribbon on the Gemini is programmed to use pitch as the default mapping. As soon as you apply a mapping to the Ribbon via the matrix, it overwrites the default pitch mapping with whichever parameter/s you have assigned it to. May I ask which control you’re trying to map it to? What are the keyboard settings when trying this, ie Dual, Split, Single?

Cheers,
Ben

Hi Ben,

and thanks for taking the time!

to 1. You are right! Adjusting that switch was the solution! I didn’t knew it works that way, just expected to select the layer via the layer select buttons is the way to go.
Is that behaviour somewhere explained in the manual? I’ve searched for “ribbon controller” in the newest version of the manual, but couldn’t find anything.

to 2. It seems it doesn’t matter wich control i choose, Mix, Res, Wave … it’s always the same.
I used Single and Split keyboard setting.

I just did some further testing (i usually stick to a single performance until i finish my current project. That’s why i haven’t tested different patches so far.).
I checked the behaviour of an init patch and in manual mode: everything works as it should, no pitch bending if i modulate a different target.
Then i checked some old patches, and they also behaved as they should.
So it seems only the patch i’m currently working on shows that faulty behaviour. I created that patch before the last firmware update. Maybe that could be the reason for that issue?

As only this single patch is affected, i don’t need further exploring. In case i stumble again over such a problem, i would reactivate this thread.
Sorry for not testing this sufficient before posting this here!

Thank you for solving 1. Ben!

1 Like