Well, I have a feeling that they’re project-specific. So if that’s the case the only way to always get your configurations is to make sure you have a template project that you always open for a given category of jobs, and then it’ll recall. It’s actually a good question because I just started using configurations (lord knows why I haven’t before!!!). I set up key commands etc, and when last week’s episode came around I loaded from template again and the configurations were gone… which is to say they were still available in the old project, but not the new one (because never saved it to the template).
So since you just asked I just tried to save to template and it recalls fine that way. But as far as going cross projects, I have no idea. Come to think of it, I’m guessing it might be a difficult thing to implement if a configuration includes which tracks are shown and which aren’t, because if you Project1 includes tracks A, B, C, D, M, N, O, and Project2 includes A, B, E, H, N, O, then a) how is that handled and b) is it even “workable” as a solution?
You know what I mean? I suppose I don’t really have an answer to your question
So… no bone from me…