[ChristianKeymaster]

Hi Scott,
thanks for your detailed bug report!

First of all I´m sorry to hear that you´re encountering this problem.
During the two years of development and also the Beta phase we´ve never experienced this behaviour before. The only minor thing that can very seldomly happen is that an encoder is physically right on the border of registering the next turn increment, so it might jump 1 value. We´re already filtering the input to prevent errouneous or stray values, but can only go so far. But that´s it. From your description it sounded that the ‘ghost’ encoders are making bigger turns?

It sounds to me like it might actually be a hardware issue specific to your device, the multiplexer of the controls somehow acting up (somewhere along these lines: http://ricardo-dias.com/2013/07/19/repairing-a-behringer-bcf2000/). Do you have Ghost lights in the LCD display? Segments that slightly light up even though there is nothing displayed in them? This can be an indicator of problems with the multiplexer.

I will keep an eye out for this behaviour though and also am interested to see if more users experience this. Maybe you can also post back here after watching it for some more time?

EDIT: Also, do you use note name or note value display for notes? The multiplexer error is connected to the display as explained in the above link. Depending on what is shown in the display, it might occur or not. That might explain why it´s not in the other modes (velocity etc…)

• This reply was modified 10 years, 2 months ago by  Christian.

[ChristianKeymaster]

Wieder auf englisch, wie im anderen thread:
To include a full blown controller functionality (programmable, customizable etc) is at this point unfortunately impossible.
Please consider using a cheap dedicated Midi Controller for this and hooking it up somehow with the Zaquencer´s Midi through capability.

What´s already possible now are the 2 Midi controls Alpha & Beta (can be CC, Aftertouch, Program change, Pitch bend – set in the global menu). If you don´t use them for sequenced Midi Control Changes, you can set them all to the same value and then hold the button to affect all steps at once. This way you have two live tweakable Midi controls for every track!

[ChristianKeymaster]

This is noted for future development.
Can´t say if it´ll be possible, because it would take up quite a lot of Flash memory as it would be a per-step setting and the Flash is already maxed out. But maybe I´ll get an idea.

[ChristianKeymaster]

Hi Citric,
bitte lieber wieder auf englisch, damit alle etwas davon haben!

Note name instead of values is already implemented!
You can switch the note display in the global menu. That has two settings for the LED ring (octave/all) and two settings for the LCD (note name/value). A setting is always a combination of those two, so you have 4 possible settings (I was running out of encoders for the global menu ;))

[ChristianKeymaster]

Email with the firmware sent. Will look into the download problem as well.

EDIT: For anyone else running into this problem, in the meantime please try Google Chrome which is reported to work fine with the downloads.

• This reply was modified 10 years, 2 months ago by  Christian.

[ChristianKeymaster]

Thanks for the detailed description of the bug (especially with the follow-up post)!
I was able to reproduce it immediately and it goes on the to-do list for V1.01.

Cheers!

[ChristianKeymaster]

Thank you so much for the kind words!
I have been very excited about this project during the whole development phase and I am very happy to see that this excitement translates to you as the users as well!!

[ChristianKeymaster]

Hi guys,
thanks for the suggestion!
Actually the version that you suggest is the one we had at the very beginning.
This then felt not right anymore out of two reasons. First, there is the activity monitor of the track which is now blinking “on” when a note is played. When you imagine an always lit LED for an active track then we would have to blink “off” for activity (a note playing). This felt really off to us. And secondly, try to extrapolate this behaviour in your mind to the 16 drum instruments in mixer mode and it gets really apparent. In our minds, they have to have the same behaviour as the track buttons, and they need to flash “on” with a drum hit and not “off” from the always-on-state.

Try to think of the mixer buttons as “mute” buttons from a classic mixing board (that also lights up when the track is muted) and it will get second nature to you in no time!

Cheers!

• This reply was modified 10 years, 2 months ago by  Christian.

[Author]

Posts