![]() ![]() Some songs didn't get affected, on others only a few tracks got affected. caf steams on the affected tracks but they just wont play. Few minutes later backing tracks just dropped, I was still getting the click and cues on my in-ear but everything that went to the house just died. MainsStage eventually closed abruptly so I had to restart. At first, I was getting the system overload message frequently during practice but the sound was not skipping or stopping so I figured it was going to be ok as long as I didn't mess with the program at all. The band practiced Sat morning and we went thought the set 3 times. Last Friday I spent quite a few hours setting up my session for Saturday's concert. I've also tried every possible variations under the program's setting with no luck. Some songs do take all the tracks, some don't but regardless of the template or what interface I use, I get the same results. I created my own custom template based on the 8 Backing Tracks default template. When I perform I use the Perform window, I have Wi-Fi off, notifications off, but I keep getting that system overload message telling me that the audio engine w as not able to process all required data in time. I have a clean desktop, basically a clean machine with everything stored on an external hard drive just to have the SSD handling the programs. I have the latest version (MainStage 3.2.3) running on a mid 2010 Macbook Pro, 2.4 GHz Intel Core 2 Duo with 16 GB of RAM on a 240 SSD, OSX EL Capitan. I recently spent a lot of money upgrading my Mac just to able to run backing tracks with MainStage 3, but even with the new improvements I've had no success.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |