'Automation lane: set active fader' action bug in absolute mode
|
11-02-2009 09:05 AM
|
Human being with feelings
|
|
'Automation lane: set active fader' action bug in absolute mode
'Automation lane: set active fader' action goes wild in absolute mode
- assign a MIDI CC to the 'Automation lane: set active fader' action in absolute mode
- select an envelope
- start using the MIDI controller
In trim/read mode, instead of going smoothly from -50% to +50% with MIDI values 0 to 127, I get:
MIDI val=0: -50%
MIDI val=1: +50%
MIDI val=2: +150%
...
MIDI val=127: +12650% !!!
Other automation modes are buggy as well.
|
|
Issue Details
|
Project
Deprecated REAPER issue tracker
Category Editing behavior
Status Fixed
Priority 3
Affected Version 3.13
Closed Version 3.14
Yes votes
7
No votes
0
Assigned Users
(none)
Tags
(none)
|
|
11-02-2009 12:36 PM
|
|
Human being with feelings
|
|
|
Confirmed hear ............
Completely unusable in all automation modes.
|
11-02-2009 11:39 PM
|
Human being with feelings
|
|
|
Suggestion to Cockos devs: probably just a /127.0 missing: looks like absolute mode is taking directly the CC value 0-127 without normalization to 0.0-1.0
|
11-03-2009 07:43 AM
|
|
Administrator
|
|
|
it's already marked "fix coming soon"...
|
11-03-2009 08:03 AM
|
Human being with feelings
|
|
|
Hadn't noticed... great news!
|
This petition for a change to Fixed was accepted
11-09-2009 02:38 AM
|
Human being with feelings
|
|
|
Fixed in 3.14, thank you!
|
All times are GMT -7. The time now is 04:01 AM.