Happened to me in a gig this evening, the tuner froze - or to be more accurate, I couldn’t access the tuner. And this was right before the one song that has an unusual tuning, where I need to tune 3 of the strings to different pitch, some of them down 2 whole tones.
Has anyone else had issues with the tuner post 3.1.0?
Learnt a major lesson there of course, always have a spare tuner!
No I haven’t so far. Can you do a reset but make sure you back up everything first.
Oh no! Thanks for posting this. I have a show tommorrow, and I will be sure to take my clip on!
Ok, I had to go check this out, and fortunately (for now) I don’t appear to have this issue. I still plan to take my clipon strobe though.
Yes, I learnt a lesson there for sure.
It works ok having restarted it at home later - I didn’t want to restart during the gig, even in a break.
I had exactly the same issue happen to me at a show last night - couldn’t access the tuner and had to reboot (which takes a minute or 2 so in the middle of a gig is far from ideal !!!)
Has this been reported? Anyone else having this issue?
+1 tuner sometimes doesn’t work. Only reboot solves it which btw takes longer then booting up a helix and a fractal and a Headrush one after another.
Sounds like we need to report this - anyone able to do so, I’m not able to this evening I’m afraid…
Already did. But so far no answer. Not surprising though, as they don’t answer most of the time or simply reply with „unfortunately we can’t reproduce this issue“.
Guys, keep patient and let them know.
If 2-3 people in the forum are reporting this, then surely there are far more people with the same issue. Hopefully we’ll see a hotfix in the next week.
That said, I have not experienced this issue with my own QC after updating to 3.1.0.
has anyone experiencing this issue tried changing the access method?
I have mine on ‘double-tap’ to open and it’s working fine.
Maybe try toggling modes for how the Tuner opens to see if that makes a difference?
Yes, I tried that (mid-gig, rather than rebooting) and that didn’t fix the issue…