• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
chordpro - setlist specific transposing
#7
As itsme wrote, making copies has several advantages. You can change the key per setlist, but also other annotations like how the song should be performed etc. Changes to the ChordPro file contents still end up in all copies.
But I guess your 'problem' is a bit more subtile, given the phrase "I wanted to get away from the 2-4 different db entries per song."
Yes, making copies will imply that you'll get more than one db entry. And you must not forget to make a copy first before starting to adapt the metadata.
So, what I think would be the most elegant and user-friendly (but probably hard to implement!) approach is a sort of copy-on-write: When you try to change metadata or annotations, MSPro will ask "This song is used in different setlists, do you want to keep your changes local to this setlist?".
As a consequence, when removing a song from a setlist, all local changes will be lost.
And this not only applies to setlists, but also to collections, albums, and so on.
Johan
www.johanvromans.nlwww.hetgeluidvanseptember.nlwww.howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 11.0, AirTurn Duo & Digit.
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (non-MSPRo, backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
Reply


Messages In This Thread
chordpro - setlist specific transposing - by rs68 - 11-27-2016, 08:23 AM
RE: chordpro - setlist specific transposing - by sciurius - 11-29-2016, 06:17 AM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


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