[mcrossy]

Only if you utilize the song ID field (as that will override the matching on title). Otherwise the title must match exactly. There is no option to change that at the moment.

Mike

Ooh, it is not useful for us... I guessed that it could be something like the title were similar if not identical (in our case the first part is identical, and there are some words as notations about the kind of sheet, for example: "MY WAY lyrics" or "MY WAY chords"). Adding an ID to hundreds of songs is not praticabile in our case...

[itsme]

SongID usage has been discussed here: https://www.zubersoft.com/mobilesheets/f...12844.html
Otherwise you can export a list using "Generate Song List"

[Swiss1000]

Hi, 
I'm wanting to share a setlist with the members of my band. Every member has its own versions of the sheets, and a slightly different title of the songs (The songs are named with songname plus a custom text saying for example "chords" or "lyrics" and so on). My question is: when sharing setlists, is it possibile that MSP can find the songs even if the songtitle is not exactly the same in every tablet? In other words, is there an option for MSP to find songs with similar name even if not exactly the same?

OK, AI will solve your problems, especially by replacing the musicians AND the conductor... For now, asking musicians to respect a song name seems to me to be the minimum... 

Moreover, this is not the subject of this post. What the musical director wants, for now, while waiting for AI and its vague promises, is to be able to deliver 3 to 5 scores to his groups and for the musician to be able to say "I am a saxophonist" or "I am a singer..."

[bjcomposer]

Hi Mike

A big +10 for the work you are planning/doing on versioning. I think this will bring many more ensembles into the MobileSheets universe, especially those in community organisations and bands that need to bring their own devices. I have just pulled our big band out of a trial of Dimusco, which is cloud based and not yet stable enough to rely on for a gig. Also Newzik is cost prohibitive, being tied to more expensive apple devices. I really appreciate the cross-platform capability of MobileSheets. 

For now, we will start trialling MobileSheets with the separate file mss workaround. Please let me know if you would like us to do any beta testing of versioning. Keeping all the parts and annotations in the one pdf will be a game changer, eliminating file splitting and management. 

All the best

Ben

[Swiss1000]

Hi Mike

A big +10 for the work you are planning/doing on versioning. I think this will bring many more ensembles into the MobileSheets universe, especially those in community organisations and bands that need to bring their own devices. I have just pulled our big band out of a trial of Dimusco, which is cloud based and not yet stable enough to rely on for a gig. Also Newzik is cost prohibitive, being tied to more expensive apple devices. I really appreciate the cross-platform capability of MobileSheets. 

For now, we will start trialling MobileSheets with the separate file mss workaround. Please let me know if you would like us to do any beta testing of versioning. Keeping all the parts and annotations in the one pdf will be a game changer, eliminating file splitting and management. 

All the best

Ben

Having all the parts in a single PDF is an option that will be cumbersome to manage. 

My experience is that, often, there are minor corrections made by the conductor to a part (for example, brass instruments are accustomed to this; depending on their distribution, an arrangement is required to create chords). This would require editing both the master and the individual parts. Often, only the individual parts remain unchanged. 

Furthermore, filtering by section on large PDF files including a master of 5 or 6 sections will inevitably be cumbersome. Having a master PDF and individual PDFs is simpler, especially if we can set the musician filter in the future. I hope we will have separate PDFs, selectable on demand.

[bjcomposer]

Hi Mike

A big +10 for the work you are planning/doing on versioning. I think this will bring many more ensembles into the MobileSheets universe, especially those in community organisations and bands that need to bring their own devices. I have just pulled our big band out of a trial of Dimusco, which is cloud based and not yet stable enough to rely on for a gig. Also Newzik is cost prohibitive, being tied to more expensive apple devices. I really appreciate the cross-platform capability of MobileSheets. 

For now, we will start trialling MobileSheets with the separate file mss workaround. Please let me know if you would like us to do any beta testing of versioning. Keeping all the parts and annotations in the one pdf will be a game changer, eliminating file splitting and management. 

All the best

Ben

Having all the parts in a single PDF is an option that will be cumbersome to manage. 

My experience is that, often, there are minor corrections made by the conductor to a part (for example, brass instruments are accustomed to this; depending on their distribution, an arrangement is required to create chords). This would require editing both the master and the individual parts. Often, only the individual parts remain unchanged. 

Furthermore, filtering by section on large PDF files including a master of 5 or 6 sections will inevitably be cumbersome. Having a master PDF and individual PDFs is simpler, especially if we can set the musician filter in the future. I hope we will have separate PDFs, selectable on demand.

Thanks Swiss1000
To clarify, I like the elegance of having a single master pdf per score and parts, and having a version with a specified page region available for each part. I don't think I could deal with a master pdf for each section! Versioning will reduce the number of files per song by about 20 in a big band. All positive vibes and encouragement to anyone working on the versioning feature!

All the best 

Ben

[BRX]

Hi Ben,

I share your preference for a single master score and parts in one file (mostly prepared with PDF bookmarks for the parts) and agree versioning will be a big improvement.
But to make sure: You know that you already can make "snippets" for parts from the master file which are kind of a link to an "extracted" page range of a part which you can rename and annotate separately as separate song without creating an additional PDF file on the tablet?

[Swiss1000]

Hi Mike

A big +10 for the work you are planning/doing on versioning. I think this will bring many more ensembles into the MobileSheets universe, especially those in community organisations and bands that need to bring their own devices. I have just pulled our big band out of a trial of Dimusco, which is cloud based and not yet stable enough to rely on for a gig. Also Newzik is cost prohibitive, being tied to more expensive apple devices. I really appreciate the cross-platform capability of MobileSheets. 

For now, we will start trialling MobileSheets with the separate file mss workaround. Please let me know if you would like us to do any beta testing of versioning. Keeping all the parts and annotations in the one pdf will be a game changer, eliminating file splitting and management. 

All the best

Ben

Having all the parts in a single PDF is an option that will be cumbersome to manage. 

My experience is that, often, there are minor corrections made by the conductor to a part (for example, brass instruments are accustomed to this; depending on their distribution, an arrangement is required to create chords). This would require editing both the master and the individual parts. Often, only the individual parts remain unchanged. 

Furthermore, filtering by section on large PDF files including a master of 5 or 6 sections will inevitably be cumbersome. Having a master PDF and individual PDFs is simpler, especially if we can set the musician filter in the future. I hope we will have separate PDFs, selectable on demand.

Thanks Swiss1000
To clarify, I like the elegance of having a single master pdf per score and parts, and having a version with a specified page region available for each part. I don't think I could deal with a master pdf for each section! Versioning will reduce the number of files per song by about 20 in a big band. All positive vibes and encouragement to anyone working on the versioning feature!

All the best 

Ben

Yes I know some want a "geek" concept, (sorry not agressiv) but I would like to have a concept as simple as peper shets fors songs.

1 peaer sheet for lyrics = 1 pdf lirycs
1 peper sheet for brass = 1 pdf for brass

Simple to explai, as simpe as the musician have now...

I allerady explait the concept

[markusphobia]

Version 3.11.0 is going to introduce the song versioning.

Just want to bump this thread again:

First I want to ask if their are any updates regarding the roadmap towards song versioning?

Second, are there any further experiences or ideas for how to best realize a shared band song management?

Thanks

[Zubersoft]

No updates yet unfortunately. Lots of different development efforts took longer than expected (it's not easy to support all three platforms). It will be a high priority to get finished next year. I know it's hard to wait for changes that are critical for certain workflows and environments.

Mike

[markusphobia]

Thanks Mike for the fast reply, and thanks that you try to bring it on the roadmap for next year. That is sufficient for me.

Just want to ensure that it hopefully at some time is coming 

Our band started heavily adopting mobilesheets, now more than 10 already use it every week.
When there will be the song versioning at some time, we will be very happy.

[hari]

yeah, very looking forward to versioning. Currently we import each voice/part as separate song, with distinct suffix. But that prevents things like page turning for the whole band via wifi/bluetooth. Also makes things complicated if someone shall pick another voice/part on an ad-hoc basis, e.g. when someone fell sick and the voice needs to be played by anyone else.

br Hari

[RAc]

I am surprised that noone has suggested abcs yet in this thread - seems to be a poster case for abc usage. A single file (normally a multitude smaller than its pdf counterpart) containing all parts and voices, and many possible ways to suppress all but one (or two or three...) of the parts on one of x tablets.

[Vombatidae]

Sorry to resurrect an old thread, but here is our scenario:

1. We have a .pdf library. Every song it has the filename <ID>_<Title>-<Inst>.pdf - for example, J01_NationalAnthem-Tuba.pdf 
2. We need a sub for a gig. They get a .zip file with just their parts needed for that gig.
3. We would LIKE to give them an .mss file with the setlist(s) (...and .4ss, but that's a different forum with different problems

...but we have no clue what the Title will be once they import it, since the guess name algorithm inserts spaces in ways that are tough to predict. I know, we could tell them to use "filename" instead of "guess", but that's prone to user error.

Any suggestions or updates?

P.S. If you REALLY want to make my day, allow them to import the .zip in one step and pull out .pdfs, .mss file(s), and a metadata file that names the collection and sets the import option to filename. 

Thanks!

[mdavej]

Whatever the title, it should still be in the ballpark, right? Hopefully your sub can figure it out from there. I just give my subs a text set list and the pdfs. It's up to them from that point on. Most are using Forescore anyway. The less handholding, the better, IMO.