[Zubersoft]

I'm not opposed to it, but that would require some very interesting changes to track the transposed value for each song independently for each setlist and/or collection. It would basically mean several new database tables dedicated just for that purpose and some minor updates to the logic to look up the transpose key tied to the setlist/collection for a given song versus just being able to look up the property of the song directly. The question is, is this approach better, worse, or just different than the song versioning changes that I already plan on making? If you can set up multiple versions of your song, each one transposed to a different key, and just specify for a given setlist or collection which version/key of the song to load, would that be an acceptable solution? It's a little bit more of a heavyweight solution as each version of a song will essentially contain a copy of everything related to the song, so if you'd prefer that I modify the transpose logic to be independently set for each setlist or collection, I can look into that. The only thing I don't know if I like, is that, if a user has a song in multiple setlists/collections, and they transpose the song after loading it on the Songs tab, they would then have to go into each collection/setlist and transpose it manually to get it to match (unless I add additional options to control updating of all setlists/collections tied to the song, making the UI a little more complicated and confusing). One way to get around that is for each setlist/collection to just use the default transpose value unless the user overrides it for that collection/setlist, and then I have to track that and figure out when I should or should not be mirroring the song's default transpose key, but that just starts making things more complicated and I'd have to have a way to reset the setlist/collection transpose value back to the default if the user wanted to clear an override. At least with the song versioning approach, if you change the transpose value for a given version of a song, you know that it will be updated in every setlist/collection that is set to use that version, so it's a little more intuitive (I think).

I welcome feedback and thoughts on all this.

Thanks,
Mike