• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ChordPro: "Keys" defaulting to C is wrong
#2
My internal logic for transposing was changed to require a key (instead of potentially storing an invalid flag that meant no key existed). This eliminated a number of errors that were occurring in earlier versions of the software. I'm always going to detect a key using the "Detect Key By" method in the text file settings. It seems like what you are asking for here is a change in behavior. You are saying you don't want the key set in the song unless the key directive is used in the chord pro file to explicitly set a key. This means that a key wouldn't be set when using text files instead of chord pro files. If this is really a big deal for you, then I would need to add a new setting for chord pro files that basically says "Only populate key metadata from key tag" or something along those lines. You could also just turn this off under Text File Settings->Use Text Fields During Song Creation.

If people think it's better not to populate the keys field of the song using the detected starting key, and it's better to require an explicit tag in the file ("Key:" for text files and {key:} for chord pro files), then I can certainly make that change.

Mike
Reply


Messages In This Thread
RE: ChordPro: "Keys" defaulting to C is wrong - by Zubersoft - 02-04-2017, 05:11 AM



Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2024 MyBB Group.