It's getting more complex for me.
Owing to world financial conditions, six-piece band gigs are reducing and duo/trio gigs are on the rise. Consequently, various band members are now available in various duo/trio combinations, doing mostly the same songs but with different versions of backing tracks.
These usually come from karaoke-version.com and are mixed as required for each line-up. This is a bit of a nightmare but achievable.
So I'm currently in the process of deploying SIX recordings per song (original, demo for practice and learning the track version, duo with guitar, duo with keyboard, karaoke for solo, karaoke for 2 singers) and perhaps more will follow. Aarghh!
In order for this to work, the set of recordings has to be identically arranged for every song for any line-up to perform the song, so that the Default Recording number will work for their entire performance. I have deployed suitable '@Silence' recordings to occupy unused spots in various songs not required by a given line-up. This will become a problem when 2 duos are out at the same time and happen to update the BH site with the default Recording number; or when someone is practising at home; or other unimaginable scenario.
I realise that different projects and Recording permissions per-line-up could deal with it but that sounds fearfully complex and prone to mistakes. If someone were to move the 2-vocalist track to the solo vocalist project, or some such scenario, I don't think I could cope.
So can I please upgrade my previous request for different Default Recording numbers per-Project (or even per-user?) to a status of "really Quite Urgent" for my sanity? I'd suggest per-Event but I don't use them and, anyway, 2 concurrent events might get mind-boggling or worse.
Thanks Arlo. I'm sure your brain-the-size-of-a-planet can work something out.