![]() And that dictates the organization of the main library. We have to look closer to find the best system for the individual performances. With a controller, you would have to re-assign the patch changes. ![]() You can change the order of the remaining song by just dragging them in the patch list. For each gig, duplicate the whole thing, give it a meaningful name and delete what you don't need. This is your library and everything should work there. Maintain one big Mainstage concert with all your songs/patches, properly organized, with sets for categories, style, whatever your criteria are. Since the Logic approach was not good for you, let's try the Mainstage way. I hope that's clear!Īh yes, now I remember this discussion. ![]() Now I'm starting to build repetoire in MS patches but am still dithering about how to hold my growing library of patches. I've figured out how to start the next patch automatically with patch change and Graeme's tip completed the solution. I don't use a controller on stage yet, just a macbook on a stand. It actually works rather well now I can use the space bar and up down mac keys to control MS. I can then use the MS patch to rehearse the individuals in the band and ultimately deliver the set live with anyone who is actually there (hopefully most!) muted. I arrange a song (with markers) for the (10 piece) band in Logic, bounce down groups of tracks into AIF stems and load those into multiple synched playbacks in a mixer patch. A bit like Graeme wants to do (is doing?) - you and I had some discussion on this in another thread somewhere if you recall - you proposed using Logic with markers (which I have tried but swapping songs takes a little while and I'm still exploring MS).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |