Unusual behavior of performance controllers

Moderator: Solaris Moderators

inaheartbeat
Posts: 39
Joined: Sat May 19, 2012 12:39 pm
Contact:

Unusual behavior of performance controllers

Post by inaheartbeat »

I defined the behavior of the performance controllers for a patch and have it saved with them all set to 0%. When I record a performance in my DAW the first controller (which is controlling filter 1 cutoff) jumps to -38% even though there is no NRPN receive enabled for the Solaris and the midi channel I am recording on is muted. It jumps to the same value when I stop recording also. The actual cutoff value in the filter control window does not change only the performance value.

On a separate note, there should be a way to quickly zero out the performance controller values as a group rather than having to try to get locked on 0 while trying to play. I already read about the bug that prevents you from reassigning the performance controller definitions. The user manual doesn't have any information about how to define the performance knobs. I had to gather this from reading an early forum post.
John Bowen
Site Admin
Posts: 2002
Joined: Sat Apr 07, 2007 3:00 am
Contact:

Re: Unusual behavior of performance controllers

Post by John Bowen »

inaheartbeat wrote:...The user manual doesn't have any information about how to define the performance knobs. I had to gather this from reading an early forum post.
It's on page 15, under Assignable Performance Knobs:

Even though you have five text screens to edit parameters,
doing so will immediately take you out of Preset Mode.
Also, there are parameters in the graphic display for many
different functional groups, and you might want to have access
to these. To give you quick access to any parameter in
the system, the bottom five knobs below the graphic display
can be assigned. You use the Shift button (to the left side
of the lower row of knobs) to assign these knobs.
Figure 16.

Performance Knob Assignment

1. Holding down the Shift button, select which of the 5
Performance Knobs you want to assign by giving it a
turn.
2. Continue to hold down Shift, and select the parameter
you wish to associate with the Performance Knob.
3. Release the Shift button. You should see a descriptive
text string for the assigned knob at the bottom of the
screen.

As shown in Figure 16, you will also see a +/- % value. The
Performance Knobs are relative to the programmed value.
They can add or subtract from the parameter value. Only
a one-to-one assignment is allowed (one parameter per
knob). Since the parameters in the text displays are fairly
easy to reach, usually these Performance Knobs will be
selected from one of the many soft key pages, but they can
be any stored Preset parameter you want, to provide quick
access, and keep the synth in Preset Mode. Performance
Knob assignments are stored with presets.
inaheartbeat
Posts: 39
Joined: Sat May 19, 2012 12:39 pm
Contact:

Re: Unusual behavior of performance controllers

Post by inaheartbeat »

I stand corrected on the documentation. I don't understand how I could have possibly missed it. The bug is still there though unfortunately.
Damo Diggler
Posts: 22
Joined: Fri Jul 26, 2013 5:08 am
Location: Australia
Contact:

Re: Unusual behavior of performance controllers

Post by Damo Diggler »

I've got a slightly different issue with my Performance Value knobs... when I set any of them to a controller (in my instance Filter CutOff) and then play some notes... upon twisting the performance knob, I get congested notes... if I go directly to the Filter CutOff and twist away... it plays without the hiccups, no problem.

I've tried other performance values, unplugging MIDI out (in case of feed back..) but, I don't think I can solve this... it's quite odd. But, if this helps, I do notice swapping between 'Preset' pages [1, 2 or 3], also creates a similar speed bump, and notes hiccup...

-Damo
Damo Diggler
Posts: 22
Joined: Fri Jul 26, 2013 5:08 am
Location: Australia
Contact:

Re: Unusual behavior of performance controllers

Post by Damo Diggler »

Oops, just found another thread resembling a similar issue... no need for a response, I'll anticipate a fix in some future OS update.
Post Reply

Who is online

Users browsing this forum: No registered users and 16 guests