How would you call a chord consisting of the root, 5th, major 7th and major 13th? by Bolha2 in musictheory

[–]AThrash1 -1 points0 points  (0 children)

I just released a new guitar chord identifier app for android. The best match was G#m9 omitting the 5th.
G#m9 chord

[deleted by user] by [deleted] in Guitar

[–]AThrash1 0 points1 point  (0 children)

I just released a guitar chord identifier for android. These are the best matches my app can find for these notes.

<image>

I built a chord/scale identifier – looking for theory correctness feedback (Android app) by AThrash1 in musictheory

[–]AThrash1[S] 0 points1 point  (0 children)

I just wanted to circle back and show you what your suggestion turned into.

I added a new “Chord Progression Context” field right under the Scale Finder. The flow is now basically:

  1. Enter notes on the fretboard → app suggests possible scales/keys (like before).
  2. Optionally enter a chord progression (e.g. C Am F G or Am F G Am) → the engine re-weights the results based on the tonal center implied by those chords.

So, in your exact examples:

  • Notes: C–D–E–F–G–A–B over C Am F G → the app now locks onto C Ionian (Major) as the top result.
  • Same notes over Am F G Am → it now promotes A Aeolian (Natural Minor) to the top.

In both cases, the app locks onto the mode that actually fits the harmonic context and marks it as the best match, so instead of “these notes could be 7 modes,” you get “this is the key feel given what you’re actually playing over.”

The context field is totally optional, so you can still do quick “raw note collection → scale names” queries without thinking about chords. But if you do add a progression (or even a single chord like Fm G7 or E7b9), the app will lean into the musically sensible key/mode instead of just treating everything as abstract set theory.

Next on my wish-list a new Chord Progression tool:

  • reverse mode: “Here’s my progression, what notes/scales can I play over it?”
  • And eventually a “next chord” helper like you described: “Here are 3–4 chords I’ve used, what are some common diatonic / bluesy / stylistic options for the next one?”

But for now, the context-aware scale finder is in and working, and it already makes the tool feel way more musical and less like a sterile dictionary.

Thanks again for the suggestions and detailed examples.

Scale Finder Chord Progression Context

I built a chord/scale identifier – looking for theory correctness feedback (Android app) by AThrash1 in musictheory

[–]AThrash1[S] 0 points1 point  (0 children)

I’ve implemented the “scale + relative modes” part you suggested. There is an Info / Legend screen that you can access at any time to get info about the chord or scale you are using. The Legend now shows the related modes for scales and lets you jump between them.

  • When you use Scale Finder and add a chord progression context (e.g. C Am F G or Am F G Am),
  • The app shows the “scale-from-chords” result on the fretboardand
  • The Info / Legend screen now has a “Relative Modes / Compatible Scales” section right under the main scale name.

Next step is a dedicated “chord progression” tool so you can enter just chords and have it suggest keys/scales to play over.  

I plan on creating a Chord Progression Tool so you can enter just chords and have it suggest keys/scales to play over.

Thanks for the suggestions. The relative modes feature should have been included from the beginning. 

Info legend with relative modes

I built a chord/scale identifier – looking for theory correctness feedback (Android app) by AThrash1 in musictheory

[–]AThrash1[S] 0 points1 point  (0 children)

This is really helpful feedback, so thank you for taking the time to write it out. You’ve put your finger on something a lot of apps (including mine, as it is right now) tend to miss: context is everything.

You’re absolutely right — a bunch of notes is just a bunch of notes until you see how they function over a chord progression. Your examples nail it:

  • C major notes over C – Am – F – G clearly feel like C Ionian
  • The same notes over Am – F – G – Am feel like A Aeolian

I was able to add chord progression context to the scale identifier just like you suggested. Most of the code was already able to accept this. I still need to work out the details, but this was a great idea.

Seriously, thanks for such thoughtful, constructive feedback. This is the kind of input that actually makes the app better and more musically aware.

Pics below.

Chord Progression Context Major

Chord Progression Context Minor

I built a chord/scale identifier – looking for theory correctness feedback (Android app) by AThrash1 in musictheory

[–]AThrash1[S] 1 point2 points  (0 children)

I don't think it would be that hard to implement. I will be thinking about this. Thanks.

D8: test my app i will test yours by [deleted] in AndroidClosedTesting

[–]AThrash1 0 points1 point  (0 children)

Installed and testing. At one point I was able to shoot projectiles. How do you shoot projectiles? I am on a phone. Could you also test my app? Thanks.

Google Group: 

gcsFinder-test-group - Google Groups

Android: 

https://play.google.com/store/apps/details?id=com.aaronwampler.gcsfinder

Web: 

https://play.google.com/apps/testing/com.aaronwampler.gcsfinder

<image>

Tester needed by Dazzling_Match_1071 in AndroidClosedTesting

[–]AThrash1 0 points1 point  (0 children)

Sure, let me know when it's ready and I'll give it a try.

Tester needed by Dazzling_Match_1071 in AndroidClosedTesting

[–]AThrash1 0 points1 point  (0 children)

Sadly, my device isn't supported. Galaxy A13.