Strange Knob Behaviour

Edit: just experimented a bit more and the problem seems even stranger: in the "layout" view, when I've just learned the controller and twist and turn it, it seems to behave properly (clockwise/counterclockwise turning of the hardware knob gives the same result on screen). It's only when I switch to "edit" view (where you map the controllers) that it suddenly behaves completely wrong (as described above).

Any clues? My mapping parameters seem normal (range min: minus infinity, range max: +6db, not inverted, graph is diagonal)...

Hi,

thanks for your suggestion but unfortunately that doesn't help... It's really strange: in layout mode I can twist and turn my knob perfectly, in edit mode I can only twist my knob clockwise (increase a value). When I try to decrease (turn counterclockwise), the software-knob immediately jumps to maximum value...
When I increase, I can read of the screen a midi value of 65 (or a little more if I turn the knob faster), decrease is midi value 63 (or a little less)... Does it have anything to do with value 63 being the "middle" value (between 0 and 127)?

I agree, it's insane 🙂

I already tried that (creating a blank patch and assigning controllers from scratch: I get the same thing)... I even created a new template in my MIDI controller... No change.
I'm really stuck here; can't figure out why a controller behaves normally in one mode (layout) and goes completely crazy in another mode (edit)...

Any other ideas?

Well, maybe together we can sort it out 🙂 Thanks already for your help!

Tried the two things you suggested: assigned a Novation relative knob controller in Logic Pro, worked like a charm, no problems.
I happen to have a Behringer BCR2000 (of which I never thought I would use it again 🙂, learned a relative-knob controller in Mainstage, turned it clockwise, everything ok, turned it counterclockwise... and surprise surprise, it also jumped immediately to maximum value... ONLY in edit mode, it works fine in layout mode.
Also: I don't have the problem with absolute knob controllers, not with the Novation nor with the Behringer controller. But I don't want an absolute knob controller, I want a relative controller to adjust volume in real time without the software volume jumping to an abslute value...

Anyway, what we know now is that the problem is definitely NOT the Novation Controller, but something very strange inside Mainstage... Leaves us with the question: what? 🙂

Hi,

thanks also for your help! In theory that should work indeed and I tried it but Mainstage still behaves stranges. Upon some patch changes the software volume knob doesn't "pick up" unless I twist and turn my hardware knob several times back and forward untill (it seems) one specific MIDI value "wakes up" the software knob and from that moment I'm able to control the volume... But of course, in a live situation that's not what you'd want...

Seems to me reinstalling Mainstage is the best option, no?
The thing is: I've got 2 Mainstage-apps in my Applications (one called "Mainstage 2.0.1" and one simply called Mainstage (and that is the 2.1.1 version; same goes for Logic by the way). What do I do? Trash them both? Or is there some kind of uninstaller on the Logic installation disk? Any pref/system files I have to manually remove?

Thanks already for all your kind support.
S

Hi,

ok, thanks, I'll try that tomorrow. Yeah, looked around on the internet, couldn't find anything about possible Novation/Mainstage conflict, but don't know if that's the case, since the Behringer BCR2000 gave the same strange results, remember... So I'm hoping it has something to do with Mainstage and that reinstalling helps...
I'll tell you tomorrow 🙂

Hi all,

time for an update. I reinstalled Mainstage as you suggested and BEFORE updating to 2.1.1, I tried a new concert, created a software knob, learned it to my Novation Midi Keyboard and... it behaved normally! However, when assigning the relative hardware controller in layout mode, Mainstage kept "seeing" it as an absolute controller. I had to set the type to "Relative (sign magnitude)" myself before it worked correctly but once I'd done that, I could twist and turn my hardware knob clockwise and counterclockwise in layout AND edit mode and Mainstage followed without a problem.

Then I updated Mainstage to 2.1.1. I noticed that, when learning the controller in layout mode, Mainstage now "sees" it correctly (as a relative controller) BUT! ... switching to edit mode caused the same problem as originally adressed in this topic: turning the knob counterclockwise in this mode resulted in an immediate jump to full scale 6 dB...

So still not fully solved, but maybe we're getting a little closer? It clearly has something to do with the update tot 2.1.1. I re-opend my original concert in which I had the problem in Mainstage 2.0.0 and the knobs behave ok, so it would be a (temporary) solution to keep working in 2.0.0 (hoping that their aren't too many other bugs in this first version 🙂

Any other ideas or solutions are always welcome!

Message was edited by: CurlsOnKeys

Hi,

well unfortunately I don't know exactly which version since I went straight from 2.0.0 to 2.1.1 Is it possible to download the installers for 2.0.1 or 2.1.0? Maybe one of these two versions are also ok, since I'm not very keen on using 2.0.0 for live performances (since there are quiet a few other bugs in it).

Already thought of the 64-bit, 32-bit problem so that was a thing I also tried, but starting MS in 32 or 64 bit doesn't make any difference...

I've got MS installed on an iMac aswell; I'm going to try it there to see if that makes any difference.

Since this problem also happens with my Behringer BCR2000 and apparently also with an Edirol PCR-800 I'm surprised no-one else has had this same problem (well maybe they have, but they didn't share it online :-)), so maybe it has something to do with conflict with other programs... Just guessing around here...

Thanks for the help.

Still, if this doesn't get solved: I need to be able to control my volumes in live performances. Can you think of a workaround?