Encoder issue with Tracker+

Tracker
1

I got a Tracker+ a month or so ago. Really excited to use. First thing I noticed is that the encoder/jog wheel was way worse feeling than the OG tracker. At first I thought it was just because the Tracker+'s encoder had a “slippery” material to it, largely caused by the circular grooves on the face of it. I adjusted how I used the encoder by only gripping it on the outside of the encoder. It helped, but I still get big “jumps” when using the encoder.

This is most obvious when using the encoder to select a note to enter. This allows me to see the “jump” by also looking at the pad lights. At first I thought that the jumps must only be occurring when I was increase the rate I was turning the encoder, causing the Tracker+ to increase its “scroll speed” or something like that. After using it for a bit, that doesn’t appear to be what is happening. Whether I am turning the encoder quickly, slowly, consistently, or with rapid changes in speed, I get frequent “jumps” in the value the encoder providing. I can see the pad lights jump up or down by an octave or more

The issue isn’t exclusive to note selection. It happens whenever I am using the encoder for anything. Scrolling through a pattern, adjusting synth parameters, whatever. There is always a random chance my encoder will “jump” unexpectedly. It makes it rather annoying and difficult to fine tune values when its acting up.

My OG tracker had the “encoder” issue as well. I got the encoder kit from Polyend. At first I tried to fix the issue with the instructions Polyend provided by gluing in that plastic piece and adding the teflon disk. That didn’t do much except add more resistance when turning the encoder.

The issue wasn’t fixed until I replaced the top half of the encoder with the new one sent from Polyend following these instructions:

Unfortunately, that doesn’t look to be possible with the Tracker+ since the top half of the encoder can’t be removed.

I’d love to get this fixed, but 1.) I bought the tracker+ used so I doubt Polyend would fix it for me and 2.) I’m in the US so I have no idea how long it would take to get to Poland and back or if it ever make it back given the new “climate” here… Regardless, I did send a message to Polyend’s support.

Is there anything else I can do to try and fix this issue? Something obvious I am overlooking? Am I just being dumb and this is expected behavior or a setting I need to change?

The Tracker+ is on firmware 1.0.3

1 Like
2

The jog wheel on the Tracker+ definitely overshoots in ways the original never did. I sure hope this is a software issue that can be fixed.

Below I’m scrolling through notes on the Plus and the OG with pretty much the same scrolling speed. On the Plus, you can clearly see values being skipped, which on the OG rarely ever happens.

2 Likes
3

Glad to see I’m not just crazy and this is all in my head. Or maybe we’re just both crazy.

But, yeah, never experience this issue on the OG Tracker. I really hope this is just a software issue where the “speed up” threshold is very sensitive. I hope that it’s something that can at least be disabled in future firmware or at least let you adjust the sensitivity for it or something.

4

Hi, I can confirm this exact behavior on my unit (T+) as well, while I didn’t experience this on the tracker OG.

1 Like
5

The difference between the PT OG (from mk2-mk4 i think, the ones with the detented pots) and the PT+ is an acceleration curve. It depends on how fast you turn the dial or more precisely how much time there is between the contacts of the encoder rail.
It feels more premium when you can reach 0-100 on faders with a fast half turn although it is less exact when you turn it slowly because its very difficult to constantly turn the wheel with the same speed and the resistance of itself.
Possible solution would be a greater deadzone before the acceleration code kicks in or an option to disable it (pt og behaviour).
Perhaps some Polyend Crew can explain it better.

2 Likes
6

Yeah, if this is a feature and not a bug, having the ability to disable this or adjust the “acceleration sensitivity” in settings would be great. This was never something that I felt was missing from the OG Tracker, and at least in my experience is not something that has proven to be useful for me on the Tracker+.

If Polyend would like me to make a feature request on Backstage for this, I can.

7

I created a feature request for this since support said this isn’t a bug or issue with the device.

Not sure how this works but here is the link:

I guess if anyone else has this issue or rather doesn’t enjoy this feature you can post in there to try and get it looked at by Polyend.

1 Like
8

As a user of both PT and PT+ i find the behaviour of the new jog dial much better. Its much easier to dial in parameters, scroll through the sample library or set loop points.
As i remember, certain parameters have a shift modifier for the PT OG to faster dial from 0-100, was it in fw update 1.8?
As this should be redundant for the PT+ perhaps devs can agree to bypass acceleration via shift key+dial for the old linear scrolling speed whenever needed?

9

Sure, I imagine some users like this new behavior better. The feature request is just for the option to disable it or to be able to adjust the sensitivity of it

Maybe I am just too used to how I worked on the OG Tracker to use the Tracker+ “as intended” or whatever, but the encoder has become an annoyance to the point I wish I never sold my OG for the +

10

Yup, experiencing the same thing.

I’m okay with the acceleration for changing most values like synth parameters. It’s nice that I don’t have to strain my hands and fingers with the wheel.

But it’s a big issue with changing mixer levels. It’s so easy to overshoot and suddenly get a loud volume, which could damage ears.

It might be nice if we could toggle it off while holding Shift. In addition to being able to permanently disable acceleration in the settings as others suggested.

Currently the way I work around it is to always use the arrow keys when changing mixer levels, and the wheel for everything else.

1 Like
11

I also thought it was probably caused by poorly implemented acceleration, but I’m not 100% certain. It also happens when I turn the dial relatively slowly, which I deliberately did in the videos. There’s no need for acceleration to kick in at these slow speeds, but still large ranges of values are being skipped, as can be seen in these edits (purposely slowed down the originals to better see the effect):

Skip1

Skip2

2 Likes
12

I see no unusual behaviour. When you think its your unit then please contact support@polyend.com.

And thanks for the slow frames. Here you see clearly that you turn 3 clicks before the next value is registered. Thats acceleration. When you turn it really slow one detent is one step value.

13

I mean, if that is supposed to be “Acceleration” it is something that is very hard to tell as a user. I watched back Wolfshoek’s original video at realtime speed, and there was nothing that indicated to me that they “Accelerated” their turning speed. I’m sure in a literal sense they did, but the change in speed appears to be so small that it isn’t being perceived by the user.

That’s the issue I am having. The threshold for when the Tracker+ detects you “accelerating” your turning speed is so small that I, as a user, am not perceiving any acceleration so I am not expecting any big jumps from the encoder. I believe that is where the disconnect is coming from.

I’m sorry if I am just repeating myself at this point.

14

For reference, another PT+.
Turn slowly one detent is one value. As soon as you’re above the threshold, the acceleration kicks in. In my opinion its totaly fine and better than the PT OG.

15

Sorry I keep harping on this, but they way it looks in your example video is totally different than my own experience. When I turn the dial like you did, I’m sure to overshoot by a huge margin. I even dare to claim that in my videos, I’m turning the dial more slowly, and still it overshoots.

As a matter of fact, in my case one dent is quite often more than one value. Here I’m just stepping though values one click at a time, but on the grid you can clearly see values being skipped.

Since one Tracker can apparently differ so much from the other, I’m starting to get the feeling mine might be defective.

16

Patrick has that little bug icon that says they’re in the Beta Testing program. Could the beta firmware make a difference?

I’ll try and join the beta program and see if it does. I didn’t think I saw anything about changes to encoder behavior on the beta page so I didn’t think to try it

17

Beta program doesnt exist anymore. You can download the latest beta without registering. Beta doesnt affect jog dial though.

18

Ive updated my profile pic, now its Deckard with a cheeseburger to avoid confusion.

2 Likes