Posts: 4
Threads: 2
Joined: Dec 2024
Reputation:
0
Hi,
For a given song, I have several files : lyrics, chord charts, melody score, bass line, etc.
For a given concert, I create a setlist with the selected songs.
When I turn the pages, I have to skip all the ones that are not used that day.
For example, when I'm the bassist, I'm not interested in the other files.
I could imagine a solution with a check box to make the files visible or not, but without needing to detach them.
But you may have other ideas.
Obviously, I don't want to duplicate songs!
NB: I saw the topic "Song page selection inside set lists", but it's not really the same need
Thanks
Posts: 13,539
Threads: 302
Joined: Apr 2012
Reputation:
241
It's not currently possible, but one potential option when song versioning is available is you could set up a single song with multiple versions where each version uses different PDFs (depending on which files you need for that day).
Otherwise, this would require some significant changes to make songs effectively optional in a setlist. This would effect almost every feature related to setlists throughout the app, and require UI changes to the setlist editor to support that concept. So I'm not excited about making that kind of a change unless a lot of other users express their need for this.
I don't have insight into what your setlist looks like exactly, but I do think song versioning with my concept of "roles" or "instruments" would solve this. My idea is that, for a given song, you can have multiple versions and each version can be assigned to a specific role or instrument. If the user selects that role or instrument on the library screen, MobileSheets will always load the appropriate version of a song for that role or instrument. This means that every user can have a song in their library with the same name, but they would load a different version specific to their instrument depending on their role/instrument selection. I've been wanting to implement these changes for a long time, but haven't had time to work on it yet.
Mike
Posts: 4
Threads: 2
Joined: Dec 2024
Reputation:
0
I don't really understand you proposal with "roles", but I was thinking about a boxchek in the files tab (inside song parameters) to make each file visible or not.
Posts: 13,539
Threads: 302
Joined: Apr 2012
Reputation:
241
That does not fit in with the architecture of the application very well. It will cause all sorts of potential bugs.
Mike
Posts: 1,903
Threads: 296
Joined: Sep 2014
Reputation:
33
create separate songs and set a tag to identify them e.g. by adding them to different collections or by setting a source type