[sejtam]

I think the app mentioned above does something like that, ie show an Android screen on another Android/valid receiver.

But I do agree that it is likely better to only have to send page commands and load the relevant pages from local storage etc.

In fact, it might be best to abstract the whole thing so that the local documents/scores don't need the same layout (what is on what page), but that the master sends instructions what section of what piece of music to display (next) and then the local copy of the app can translate that to what it can display. That would allow different musicians/readers to have different score layouts (some may prefer to see only their staff or voice, others need to see the whole score or other parts) and those may not always be on the same page. This would require everyone to define the same links (repeats, D.C, D.S etc) but will also allow the master/maetro to centrally select which of those to play, and the master app then simply sends that info (possibly queuing the upcoming parts early, so that it can then execute the next change with a single short command)..?