Touchstrip is goin crazy.

[randi]

For me the issue definitely also occurs with only headphones plugged in and nothing else

[dest4b]

as i sayd. i disconnected all.. at least all that was connected.

[TheEntireRobot]

This has happened to my Push standalone with no cables or devices connected.

[imagovrn]

Exactly the same issue here. Standalone, only headphones connected.

> Ah yes I've now tried a headphone adaptor resting in that area and it works, as does a cigarette lighter.

USB cable works too.

[hessproject]

Having the same issue, happens in standalone and connected mode, regardless of what is plugged in

[elbows]

Please see the following post in another thread, which contains provisional good news:

viewtopic.php?t=247613&sid=4924e62823b0 ... d#p1812698

[bodom76]

I think I have a similar issue except for me it is the volume knob and tempo knob just randomly popping up and displaying over what im working on. Sometimes it wont go away for hours, so seeing the graphics for the EQ..etc is super hard. It's super annoying.

[rgarner]

Well, just received my replacement in the post. Turn it on, update firmware, fire up Drift...

... and bam, touchstrip is locked flashing to the top again. Aaargh...

[dest4b]

omg.

[rgarner]

omg.

Hey, at least this one doesn't have the "wrong pad trigger crosstalk" issue, so there's that. And it seems slightly more amenable to the "headphone jack adapter hovering over the touchstrip" fix, so maybe I can hang on until they fix it in software? Fingers crossed, because the returns process was *painful*.

[vertgrall]

I'm afraid this might be a hardware issue. And if that's the case. This is a huge problem.

[rgarner]

I'm afraid this might be a hardware issue. And if that's the case. This is a huge problem.

That's what they first said when the problem came to light, but admins here have suggested since that it might be fixable in software.

[elbows]

I'm afraid this might be a hardware issue. And if that's the case. This is a huge problem.

That's what they first said when the problem came to light, but admins here have suggested since that it might be fixable in software.

Admins may have repeated it but the original source was actually a user reporting what someone from support had told them, that it was a bug they think they can fix in firmware.

My standalone pretty consistently displays this behaviour on first boot, typically within 5 minutes, but if I then switch the unit off and back on again, the problem does not occur during this subsequent session. So I'm using this workaround far more than the 'balance something metallic near the top of the strip' workaround.

I do take the pattern I observe of it only doing it at first boot as a sign that its some calibration issue, with some variable that changes after initial minutes of use. So something calibration related, something related to interplay of hardware and firmware, and that this makes a firmware workaround more likely to be successfully implemented rather than it being a more random hardware issue.

[Glasside]

I just updated to the beta version of Push this evening and the touch strip started - was working normally til then. May just be a coincidence, but I'am about revert back to the main release to see if it changes anything..

[rgarner]

My standalone pretty consistently displays this behaviour on first boot, typically within 5 minutes, but if I then switch the unit off and back on again, the problem does not occur during this subsequent session. So I'm using this workaround far more than the 'balance something metallic near the top of the strip' workaround.

My first (returned) unit was a lot worse than this. If it started doing it, you might only be able to stop it with the metallic balancing act. The second seems mild by comparison and now I do the same as you — it'll happen once, you'll reboot once, and if you're lucky it might not happen again. Seems to be a problem of degrees.

I'd rather not have it at all, of course. It makes me not want to turn the thing on.