Hi guys: i'm on 1.5.2 (beta, i mean that i have the beta installed and not the release version, but i think they are the same), and i'm having a strange issue with the delay mix and feedback pots.
Before this upgrade they worked flawlessy, but now, when i turn them i have nothing changed in the delay settings.
Thus the monitor says "Delay MIX CC 0.0 [0.0]" and this value grows then i turn it clockwise. Turnin it counterclockwise it goes back to zer.
The same appens with the feedback knob, and i have "Delay feedback CC 0.0 [0.0].
Any Idea?
Issues with Delay Feedback and Mix knobs
- Jimmyno
- Closed
- Thread is marked as Resolved.
-
-
I've not understood....
-
When i turn the quick knobs (the ons on the upper row of controls) i have no changes in the settings.
The only thing that appears on the screen is "Delay Mix CC 0.0" and "Delay Feedback CC 0.0", and this value changes while turning the knobs, but the mix stays fix and the feedback too.
I -
I'd do two things.
1. Take a screen picture and send it to support.
2. Do the update to 1.5.2 again. -
Well, it's probably what i will do (unfortunately I have a gig tonight).
Thank you anyway -
Does it work if you enter the menu and use the dials under the screen?
-
Yes, it works, thanks god, otherwise the delay would have been useless.
By the way i'll try to solve this. -
do you have a MIDI controller connected?
-
do you have a MIDI controller connected?
Nope. It's the same even if there's no midi controller connected.
-
Well, here we have two pics.
[Blocked Image: https://dl.dropbox.com/u/49933432/IMG_1157.JPG]
[Blocked Image: https://dl.dropbox.com/u/49933432/IMG_1158.JPG]
-
we seem to have introduced this issue with firmware 1.5.1.
The two knobs Delay Feedback and Delay Mix are working as long as you stay on the main screen. If you open Delay editing these two know are disfunctional, but you can use the two softknobs for Mix and Feedback below the display instead. Please use this as a workaround for the time being.
Midi Control Change # 68 and 69 are working as well.
We'll fix this in our next firmware.