-
Notifications
You must be signed in to change notification settings - Fork 29
Pan values feel reversed #509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is not really much of an concern with the current pT UI BUT will be once the coming MIDI input support improves as this would be a candidate for a CC and as things stand now I guess me might end up doing a inverse value mapping to make it work sensibly as is |
For me, this hasn't been a concern / I haven't noticed it yet, and I use panning quite a bit, but if this improves UX for people then I fully support it! |
Thanks for the feedback @wynwynyn 👍🏻 |
I don't think it'd annoy me, but having said that, I usually use panning just to add a bit of stereo depth to things, rather than thinking whether something should come out of the left or right channel specifically... In that case yeah, I can imagine it being slightly annoying, but not that big of a deal! |
I don't think this should be changed, specially if it comes from LGPT legacy, there are some expectations on how it works, etc. |
Yeah same, there's just a weird cognitive glitch with it being backwards. Easy to get used to but initially confusing.
Shouldn't we move forwards? picoTracker is a different beast after all... A reversed UI widget would be OK, just seems a bit backwards lol |
Given the feedback so far, I think we can go ahead and fix this without too big an impact on existing users. |
Currently a value of
00
is right pan all the way while left pan ofFE
and if you were to map these to a dial0
would normally be on the left while max value on the right.This would be easy enough to change BUT I'm not sure if it will be possible to change this at this point or maybe its not that big a deal to break backwards compatibility on this, would love to hear what others think about this?
The text was updated successfully, but these errors were encountered: