Take 5 module / newest firmware bug ? Select Encoder bug / encoder dead zone

[yuki_the_synth_dragon]

If you have the latest firmware that just got put up or have a new module can you see if you have the following bug ? If this is a software bug I assume the keyboard version has this as well if you update the panel version and firmware. I will try to describe it and I will also post a video. Already opening up support case for this as well. Ok so the issue is the select encoder (left one under the screen) will not register some detents. Yes I know in troubleshooting this is not considered a fault but it is only happening to the value encoder, and only with clock wise movement. Also if I get to a detent that does not work and happen to power cycle the unit and move past the detent that does not work I still get the same issue, so thats why I don't think it's a hardware issue. My teo-5 module does not exhibit any encoder dead zones.

I have tried to illustrate this in my video which is linked below:

https://www.youtube.com/watch?v=3yBb54ZrEGo

[MRCK]

I have this issue on the Take5 keyboard since the beta 2.0.0.13 and also now with the latest official 2.1.0.2.
It affects the following knobs: select, value, osc1 octave, osc2 octave, arpeggiator octave.

[ElecStraTake]

I also have this issue on my T5 keyboard with the Select and Value encoders since I’ve updated to the official OS v2.1.0.2 (and performed a Globals reset).
Within the Global or Program settings :
- when I turn the Select encoder, randomly, the selected setting is not changed. And when I turn it again, the setting that should be selected previously is skipped, and I have to turn the encoder in the opposite direction to have it selected.
- Likewise, when I turn the Value encoder, randomly, the value is not changed.

This is so annoying.
I’d like to revert to OS v2.0.
But I can’t find it anymore and I don’t know if it can be done safely.
I guess it’s time to contact the support team.

[gus]

Thanks for flagging, all! We've reproduced and logged all of the details on our end and our software team is actively looking into it.

[yuki_the_synth_dragon]

Thanks for flagging, all! We've reproduced and logged all of the details on our end and our software team is actively looking into it.

Thanks ! Support just got back with me as well. I had an rma setup with the retailer. I will cancel the rma.

[kpatz]

I have 2.0.0.13 on my 2021 Take 5 and there is one spot on the Select encoder where it skips, but it appears to be that one specific detent where it does it.  I don't know how many total positions there are and there aren't enough entries in the program menu to cross all possible positions, but it appears, at least on my unit, it occurs at a specific rotation point of the knob.

In the mod matrix, it seems to be skippy around every 8th detent.

My Value encoder doesn't have the same issue, and my TEO-5 (also on the current beta but not the production FW) doesn't seem to have the issue, but it's also newer.

To me it seems to be some sort of issue with the encoder debounce algorithm, but maybe depending on the actual encoder in your unit it may occur more or less often?

[yuki_the_synth_dragon]

I have 2.0.0.13 on my 2021 Take 5 and there is one spot on the Select encoder where it skips, but it appears to be that one specific detent where it does it.  I don't know how many total positions there are and there aren't enough entries in the program menu to cross all possible positions, but it appears, at least on my unit, it occurs at a specific rotation point of the knob.

In the mod matrix, it seems to be skippy around every 8th detent.

My Value encoder doesn't have the same issue, and my TEO-5 (also on the current beta but not the production FW) doesn't seem to have the issue, but it's also newer.

To me it seems to be some sort of issue with the encoder debounce algorithm, but maybe depending on the actual encoder in your unit it may occur more or less often?

My select encoder seems to do it every 6th or 8th time. I also have noticed the arp mode encoder, and effects mode encoder also skip one. Hopefully they get it resolved soon !

[ElecStraTake]

I have 2.0.0.13 on my 2021 Take 5 and there is one spot on the Select encoder where it skips, but it appears to be that one specific detent where it does it.  I don't know how many total positions there are and there aren't enough entries in the program menu to cross all possible positions, but it appears, at least on my unit, it occurs at a specific rotation point of the knob.

The issue may be somewhat related to some hardware / encoder aspect.
But with OS v2.0 and prior versions, I haven’t experienced such behaviors.
So some software is definitely involved.

By the way, the support told me that downgrading to v2.0 is not recommended.

[darkestyugo]

I can also confirm that my select and value encoders both skip. It's very frustrating when trying to dial in modulation routings as it sometimes won't move down to the next line in the display and then when it does, it jumps two. I then have to dial back to go up.

This also makes entering patch names difficult as it can take two encoder clicks to advance a single letter.

Apart from that, it's a really inspiring piece of kit!

[gus]

Hi all,

Thank you for your patience with this one. We have just released Take 5 Beta Panel OS 1.1.2, which is pinned to the top of this sub forum. This update includes a fix for the encoder issue outlined in this thread.

If you continue to have issues with your encoders, please don't hesitate to reach out to us via email at support@oberheim.com.

https://forum.sequential.com/index.php/board,45.0.html

[lewisfrancis]

Hi all,

Thank you for your patience with this one. We have just released Take 5 Beta Panel OS 1.1.2, which is pinned to the top of this sub forum. This update includes a fix for the encoder issue outlined in this thread.

If you continue to have issues with your encoders, please don't hesitate to reach out to us via email at support@oberheim.com.

https://forum.sequential.com/index.php/board,45.0.html

Yes! So much better -- thanks!

[ElecStraTake]

Thank you for your patience with this one. We have just released Take 5 Beta Panel OS 1.1.2, which is pinned to the top of this sub forum. This update includes a fix for the encoder issue outlined in this thread.

The Panel OS 1.1.2 has also fixed the encoder issue for me.
Big thanks !

[MRCK]

Hi all,

Thank you for your patience with this one. We have just released Take 5 Beta Panel OS 1.1.2, which is pinned to the top of this sub forum. This update includes a fix for the encoder issue outlined in this thread.

If you continue to have issues with your encoders, please don't hesitate to reach out to us via email at support@oberheim.com.

https://forum.sequential.com/index.php/board,45.0.html

For me now it's fixed with the new panel. Thank you!

[Kusho]

EDIT: Emailing sequential directly about this...

I have a lot of stuck zones in many of my encoders. I bought it secondhand. I don't know if they are hardware or firmware problems. The select encoder does seem to have a dead detent, I've marked the encoder and it skips the detent in the same position consistently.

Other encoders have issues and it's hard to tell if they are hardware or firmware related:
Clock BPM and CLK Divide, Arp Octave, Repeat and Mode, Effect Type.

The VALUE encoder seems to have no issues.

The person I purchased off sold with a good travel case, and it did some gigs I believe but in a church band so a pretty civilized environment. He was very careful with it and it looks new. But the padding in the case was custom made by him and I'm wondering if there were any undesirable forces exerted on the encoders while transported in the case. I purchased directly off the seller in person.

Thanks for any help offered.

[JozefSvorc]

Hello guys,
I have the exact same problem as you describe here, and it's been happening since I bought the synthesizer (as new one). In my case VALUE encoder is affected by this issue. The symptoms are as described here, i.e. stuck zones between steps. Encoder sometimes jump 3-5 times in same position and then jumps to next step value. It seems to happen randomly and only when I turning the VALUE encoder counter-clockwise. I thought a firmware Panel v1.1.2 update will help, but unfortunately the problem still persists. It's very frustrating especially when I enter many values in the modulation matrix.

[Kusho]

Hello guys,
I have the exact same problem as you describe here, and it's been happening since I bought the synthesizer (as new one). In my case VALUE encoder is affected by this issue. The symptoms are as described here, i.e. stuck zones between steps. Encoder sometimes jump 3-5 times in same position and then jumps to next step value. It seems to happen randomly and only when I turning the VALUE encoder counter-clockwise. I thought a firmware Panel v1.1.2 update will help, but unfortunately the problem still persists. It's very frustrating especially when I enter many values in the modulation matrix.

I emailed support and they asked me to test with all cables unplugged. It seems to have stopped. I think I might have had a midi feedback loop issue through the computer via USB midi. So the Take 5 was sending midi to itself through the computer resulting in weird encoder behaviour, double signals etc.
So try that first.

[JozefSvorc]

I emailed support and they asked me to test with all cables unplugged. It seems to have stopped. I think I might have had a midi feedback loop issue through the computer via USB midi. So the Take 5 was sending midi to itself through the computer resulting in weird encoder behaviour, double signals etc.
So try that first.

Thank you for the response and suggestion, unfortunately this is not my case and the problem still persists. Today I did a test with the synthesizer disconnected from the midi cables and without connecting to the computer via USB midi and the VALUE knob behaves exactly the same. Actually, I noticed another issue too. The knob (when turned) not only jumps repeatedly at one value, sometimes it jumps to the previous value (for example, when turning counterclockwise from a value of 100 it should jump to 99, but it jumps to 101).

[kpatz]

Thank you for the response and suggestion, unfortunately this is not my case and the problem still persists. Today I did a test with the synthesizer disconnected from the midi cables and without connecting to the computer via USB midi and the VALUE knob behaves exactly the same. Actually, I noticed another issue too. The knob (when turned) not only jumps repeatedly at one value, sometimes it jumps to the previous value (for example, when turning counterclockwise from a value of 100 it should jump to 99, but it jumps to 101).

If it’s just one encoder doing it, my hunch is that encoder is faulty.  Contact Sequential support for help.

[JozefSvorc]

Thank you for the response and suggestion, unfortunately this is not my case and the problem still persists. Today I did a test with the synthesizer disconnected from the midi cables and without connecting to the computer via USB midi and the VALUE knob behaves exactly the same. Actually, I noticed another issue too. The knob (when turned) not only jumps repeatedly at one value, sometimes it jumps to the previous value (for example, when turning counterclockwise from a value of 100 it should jump to 99, but it jumps to 101).

If it’s just one encoder doing it, my hunch is that encoder is faulty.  Contact Sequential support for help.

That's what I was afraid of.  Anyway, I'll contact Sequential support then. Thanx.