However, I'll absolutely stand behind what I said, since this is a feature which really does not affect the usability in any significant way. It's great when it works, and if you're having a problem with it not working then you can use the standard > < tuner, and obviously your ear. If that offends you or makes you think me insensitive, so be it.
I take your point, but I disagree: it does significantly impact usability for me. The tuner without the spinner was not accurate enough for my preference. This is reinforced by the fact that the tuner display on my Liquid Foot, which uses the arrows but not the spinner, has me turning around during shows to look at the AFX display until recently. So I was delighted when the 8 ball came out. Unless there is some version of the tuner that has as accurate a display as my Peterson or my Turbo Tuner, I'll probably just go back to using them. And that's an option, as you point out. But it affects usability and utility. In normal practice during a show I cannot just use my ear between songs or sets because it is loud and obnoxious.
You were not the first to call me a complainer, so forgive me for responding to you as the straw that broke the camels back for me. But you were unintentionally feeding the fire by labeling me as such. The little rant that follows is not directed at you, steverosburg...
This is a bug report forum. In fact, it is one of the primary channels that the manufacturer has chosen for that very purpose, apparently. Nobody will ever know whether an issue is a "minority" issue or not until data is collected. If every time the start of a data feed is shut down because (by definition) it is still the "minority" of the data, then nothing would get fixed.
It would be one thing for FAS to say "I'm sorry you are having an issue. We have no explanation at this time, but we will see if other people report a similar experience" and then hopefully they would ask for input from other users. Maybe only users who are using LF pedalboards have this issue, in which case (shock!) there might be a fix. But here, they seem to have responded in what looks like a petty way. Like I said, maybe Cliff just had a bad week...happens to the best of us. Or maybe he was just joking. But if anyone deserves to be called out, it would be a manufacturer who responds to a bug report like this by basically saying "Fine...that feature is gone now. Happy? Now you ruined it for everybody!"
THIS IS A BUG REPORT FORUM! Anyone, including Cliff, who is reading here and not expecting to see "complaints" for issues that often only affect "the minority" is missing the boat, IMO. And a manufacturer who responds the way I am reading this response risks losing customer loyalty. Blaming the user, especially on a public forum, is not a smart move even when the majority of people don't have the issue. There are too many variables involved to be dismissive of the experience of a few people, variables that might just make for a legitimate bug.
