phadedvision wrote:Sup ko1N,
Glad you noticed this too.
At first I thought it had to do with the actual effect itself rather than a bug. (ex. if knob 3 = decay for X effect and was MIDI learned for knob A, then knob A would only work for X effect, decay setting) Hope that little explanation made sense, but that's what I think what happens? I'm pretty sure I'm wrong about it.
Well thats not exactly whats going on (if i got you right)...
If you learned a certain poti on a poti for the effect it works for every effect. The effect only affects what the knob actually changes within the effect. It doenst matter how many potis the effect uses, they can always be rotated.
The issue is that I asigned a certain poti to the second or third rotary in the software and if I turn it on my MIDI controller it just changes the first poti of the effect.
I can't confirm if this is actually a bug through a failed MIDI definition or they simply can't be assigned.
Here is the relevant part of my MIDI configuration:
- Code: Select all
; change the effect volume of channel 2
#b9 5 EFFECTVOL 2 0
; change the effect slider no. 1
#b9 47 EFFSLIDER 2 0 0 0
; change the effect slider no. 2
#b9 54 EFFSLIDER 2 0 1 0
; change the effect slider no. 3
#b9 48 EFFSLIDER 2 0 2 0
...
I just tested it and now the Effect sliders 2 and 3 have no effect at all anymore. Nothing moves if i turn them. Though it's asigned correct.
Maybe it's just an issue with the MIDI script itself. If so any help will be appreciated!
I hope i could explain it in a little bit more detail.
Here is my configuration report to complement this:
I'm using Windows XP SP2 with a Core2Duo 1.6Ghz, 1gb Ram laptop!
Thanks in advance, Patrick.