Touchstrip is goin crazy.

[[jur]]

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.

I definitely didn't suggest this could be fixed on the software side of things because:
- I'm not a software dev
- and while I'm not a dev, I'm personally convinced this is a HW issue since this I never experienced it on my unit and didn't hear about this during the beta phase.

But I'd be happy for everyone if this could get fixed within the firmware.

[elbows]

- and while I'm not a dev, I'm personally convinced this is a HW issue since this I never experienced it on my unit and didn't hear about this during the beta phase.

But I'd be happy for everyone if this could get fixed within the firmware.

This is why I spoke about the interplay of firmware and hardware. If the issue is in the area of tolerances and calibration and variations over time, then it is possible to anticipate variations in different peoples experiences due to various factors including differences between different peoples hardware devices but also environmental conditions etc. And it is also possible to imagine that firmware changes could be made to mitigate against the issues that some have experience. Since i am not a developer of this piece of hardware or its firmware I could not guarantee this, but I also have no reason to give up hope on that sort of solution at this time.

[rgarner]

From support today, re touchstrip:

"this is something we have seen more often, and we found the (software) culprit, luckily. There is a fix in place, and we will soon release an update with a fix"

[elbows]

From support today, re touchstrip:

"this is something we have seen more often, and we found the (software) culprit, luckily. There is a fix in place, and we will soon release an update with a fix"

Excellent, thanks so much for passing that info on.

[[jur]]

If some of you are part of the public beta, the new L11.3.10b2 has a fix for the touchstrip issue so please go ahead and let us know if it's solving your problem.

[drez]

There's 5 pages of "Touchstrip is goin crazy". Are any of you folks with this issue using the new b2 and can report if its fixed or not?

[elbows]

Yeah the firmware that came with beta 2 fixed it for me

[dcjams]

Yeah the firmware that came with beta 2 fixed it for me

Good, they're fixing stuff, as predicted.

[lovelight]

Just updated everything Push 3 controller, firmware and Suite.
The touch strips Pithbend function on the touchstrip don't work on any instrument!, vst or Ableton instrument, it keeps being used at a volume on track 1, (audio rack or instrument rack). Modwheel function works, Drumracks function works.

And im not in sequencer mode as the manual says where its the place where it don't work.

But its annoying the touch strip don't work with pitch bend at all, only as a volume for track 1.

Im using original cable directly into computer, no hubs. Mac M1 16 gb, plenty of room.

Kind regards
Tim

[Tarekith]

That sounds like a hardware fault, haven’t heard anyone else with this issue. Might want to contact support:

https://www.ableton.com/en/help/#contact-support

[elbows]

That would be a very weird symptom for a hardware fault to have, especially as it sounds like it works in modwheel mode.

[lovelight]

I did an update with the new beta version with the new firmware for Push 3, now it seems to work, but only after Live suite, not beta, rescan all my plugins as it seems to do every time I start live from the beginning...

[lovelight]

[quote=lovelight post_id=1813995 time=1688921583 user_id=8972]
I did an updated firmware from the new beta version , now it seems to work, but only after Live suite had rescanned all my plugins anyway problem solved with the update, thanks for the group help in here :)