[Vibraphon]

Now we have the fantastic opportunity to use the "Connected Device" option to load songs on several devices. Great!
But actually that is only working, if all devices use the same database, what means the same music sheets.

In real life, the piano player needs another sheet (c-version) than the sax-player (Bb- or Eb- version) or the singer (including text) for the same song.

I would like to have more database functionality for the compainion, using unique device names of all tablets that shall be connected:

• Add the device names to all mobilesheet datasets (additional column)
  
• Load more than one backup file (they have to be stored on the dektop computer)
  
• Create unique ID-numbers for every song
  
• Create a song exchange list:
  •   Device A: "Softly as in a morning sunrise" -  ID-1234567
    
  •  => Device B: "Softly as in a morning sunrise _Bb" -  ID-7654321
    
  •  => Device C: "Softly as in a morning sunrise _Eb" -  ID-0000007
    
  • => ...
    
• Restore and Rewrite to HDD with selection:
  • Restore "Device A"
    
  • Restore "Device B"
    
  • Restore "Device C"
    
  • Restore ...
    
  • Restore "All"
    

The "Open"-command on the devices should only use the ID numbers.
If device B is the "leader" and opens "Softly as in a morning sunrise _Bb" -  ID-7654321 on device A should be opend "Softly as in a morning sunrise" -  ID-1234567 and on device C "Softly as in a morning sunrise _Eb" -  ID-0000007.

At the end, the compainion would become a song-device-manager!
The compainion could restore direct to connected devices or create restore-files for each device to HDD.

It could become even more functionality if an additional parameter "orchestra" would be defined.
Than severeal song exchange lists could be managed for different orchestras, because most musicians are playing in several bands/orchesters.

Just an idea. Theoretically it seems pretty simple.  
Sorry for my bad English!

[Steve B.]

Perhaps I missed a change somewhere?

Doesn't MSP only require the song titles to match on the master and slave devices?
Thus, if the master opens their version of 'SONG XYZ' and it's in C, the slave tablet would open 'SONG XYZ' even if that version is in Bb (unless the title on the slave actually included Bb).

I do see how your protocol could be helpful if someone were managing all the tablets for the whole band.

[Vibraphon]

Perhaps I missed a change somewhere?

Doesn't MSP only require the song titles to match on the master and slave devices?
Thus, if the master opens their version of 'SONG XYZ' and it's in C,  the slave tablet would open 'SONG XYZ' even if that version is in Bb (unless the title on the slave actually included Bb). ...

That doesn't really work.
The sax player has a sopran, an alto and a tenor sax. So he uses sheets for the same song in C, Bb and Eb.
He cannot not name three different sheets the same.

I do see how your protocol could be helpful if someone were managing all the tablets for the whole band.

That would be a great benefit.
Every musician could use mobilesheets individually for different orchestras.
To manage all tablets it would only be necessary to define the exchange list.

[GraemeJ]

That doesn't really work.
The sax player has a sopran, an alto and a tenor sax. So he uses sheets for the same song in C, Bb and Eb.
He cannot not name three different sheets the same.

However, he could combine all three charts into a single PDF (with the appropriate name) and then simply page to the one in the required key