Author |
Topic: is there a bug with note mapping ? (Read 117 times) |
|
mmelon
New Member
MIDI-OX Rules!
Posts: 3
|
 |
is there a bug with note mapping ?
« on: Dec 27th, 2023, 4:28am » |
 Quote  Modify
|
i am mapping a note on. When i tick use input value 2 (pull) the note on produced is 1 note higher than the input note. I am sending a d4 and getting an e4 from the input value 2. very odd. i'm sure it must be me as this program is super solid.
|
|
 IP Logged |
|
|
|
mmelon
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: is there a bug with note mapping ?
« Reply #1 on: Dec 27th, 2023, 4:46am » |
Quote Modify
|
ok. so when i untick use input value 2, it works. I assume it works because -1 is still in the input values. When use input value 2 is ticked, it is reporting 64 as e4 at the output stage.
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1015
|
|
Re: is there a bug with note mapping ?
« Reply #2 on: Dec 27th, 2023, 7:55pm » |
Quote Modify
|
OK, it is a bit hard to work out what you are trying to do.
Note On -> what?
You normally use the pull function only to swap the values.
Without the check marks the default is
Key -> Value #1
Velocity -> Value #2
Map note 24 (C1) to patch change with the patch number to be the velocity
Note On : Note= 24 to 24 Velocity= 1 to 127 (velocity 0 can be used for Note Off on some synths. To prevent hanging notes use 1 to 127)
Prog Change : PatchNum = -1 -1 : second value not used
Tick 'Use input value 2'
Hit the C1 key to change patches sort of randomly. The velocity value will be the new patch number.
All the best
Royce
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print