Where Even a Good Chord Finder Breaks
Every chord finder nails an open C. Push past beginner shapes into altered dominants and slash chords and some return "no chord found." Here is where they break.
What Makes a Good Chord Identifier?
A rubric for judging any reverse chord lookup - check it yourself in 30 seconds. Plus a blind test where two independent AIs scored seven tools against theory.
What Key Is This Progression Actually In?
Most key finders match scales and give you a confident-looking answer. Fretscape asks what the progression actually suggests - and tells you how sure it is.
The Wrong Name, Ranked First
Hand a reverse chord lookup three notes and it leads with C6(no3) over the obvious Am7 - then warns about its own answer. Lookup isn't the problem. Ranking is.
Technically Correct Isn't The Same As Expected
I was taking a screenshot of Am7 when I realised my ranking had been getting it wrong for months. The voicings were correct. The order wasn't.
The Optimiser That Was Quietly Ignoring Me
I sat down to take one screenshot for the Play Store. Three hours later I'd fixed three bugs in the optimiser - and was very late for a family day out.
I Built a Chord Optimiser That Proved Me Wrong
I was sure Fretscape had picked the wrong F fingering. Twenty years of guitar instinct told me so. Then I looked closer - and the optimiser was right.
How Fretscape Thinks
A short intro to a five-part series about the small decisions that built Fretscape. The easy answer and the right answer aren't always the same.
まだご質問がありますか？
すぐに答えが欲しい場合は Fretscape Assistant にチャットで質問するか、サポート方法やナレッジベースを案内しているヘルプページをご覧ください。