I am starting to be comfortable with the mechanics of creating expression maps, setting up endpoints, and creating and applying playback templates. Now the question is how to organize things for both maintainability and performance. My goal is to build a big band playback template that for starters primarily uses Garritan Jazz and Big Band 3 (JABB) for sounds. Over time, I may want to add sounds from other libraries. GPO or their world percussion library would be prime candidates, but it could be any SFZ. Libraries that are not Aria compatible require their own endpoints so my questions mostly relate to how to organize the Aria endpoints.
Endpoint granularity is a design choice with both usability and performance considerations. For maintainability, having separate endpoints for trumpets, trombones, saxes, rhythm, drumset gives me the ability to organize sounds by ‘family’. Or I could get started with the minimal number of endpoints needed to host all of the big band instruments. Is there a performance hit for using sparsely populated endpoints? If you use the minimal number of endpoints, I believe you need to add any new instruments to the end, so that leads to having the instruments for each big band section potentially spread across multiple endpoints. Not ideal from a usability perspective.
JABB contains complete samples for several instruments of each type. E.g. 5 trumpets, 4 alto saxes, etc. If I set up an endpoint that uses one slot for each of the 5 trumpets, will Dorico assign the lead part to #1, 2nd part to #2, etc.? Or is it better to do what I am currently doing: define one trumpet, and then after Dorico assigns the same trumpet to all of the players, change the sample being used on a player by player basis.