Technical feasibility of a MS-community perpetual performance

• Jul 13, 2019 - 22:56

I had the following idea and I wonder if it's technically feasible: people submit their MS orchestration of Terry Riley's "In C"--observing its rules within their individual score, choosing instruments, entries and exits, and (thus) number of repeats of each phrase--and one (or more if required) server-instance of MuseScore performs them--broadcasting the result for anyone to stream--subject to the provisos: no more than 55 (the number of phrases in "In C" if I recall correctly, or is it 54?) phrases are to be played simultaneously; and "first come, first served," i.e., submissions enter a queue in the order received, and phrases from a new submission don't start until a "slot" among the 55 becomes available (at first, this will produce some amount of predictability as to when any given phrase will come in, but as time goes on, as people submit different lengths of time to repeat the various phrases, eventually entries and exits will be apparently random, but there will never be more phrases being played simultaneously than Mr. Riley intended, and the performance can go on uninterrupted, theoretically, as long as people continue to submit orchestrations). Is this technically feasible, modulo setting up the required server instance(s) and broadcast/streaming infrastructure, given the current capabilities of MuseScore?

Do you still have an unanswered question? Please log in first to post your question.