Large file size in Mainstage 3.3 when using Native Instruments Session Horns plug in

Question

Level 1

5 points

Large file size in Mainstage 3.3 when using Native Instruments Session Horns plug in

Please help! I've got a concert for my band's gigs with about 14 different songs - all keyboard parts. I'm using the Native Instruments Session Horns plug in with the Kontackt 5 player on around half the songs - each one with a slightly different sound. But it's making the size of the concert file size huge and the 4GB memory of my MacBook is struggling, and makes any editing virtually impossible. As in the pics it seems that the first song using the plug in becomes up to 1.6 GB in size, even when the only instrument on that song is the brass (some songs have multiple instruments and effects). So when I removed the first song with brass in from the concert, the next one with brass in leaps in size. I suspect I'm not doing all of this in the best way, but I can't find any easy to follow help online. All advice appreciated, thanks. (MacBook Air 1.8 GHz Intel Core i5 4 GB 1600 MHz DDR3)

MacBook Air

Posted on Jun 9, 2017 6:22 AM

Reply

Answer 1

Madddcow

Level 2

463 points

Jun 9, 2017 5:55 PM in response to jmchugh100

I don't use Session Horns and can't help you out specifically, but a MacBook Air 1.8 GHz with only 4GB RAM running MainStage with big sample libraries is definitely not a great setup. It doesn't surprise me at all that you're having issues.

Are you running Kontakt in multi-timbral mode to try and reduce the number of instances you're using? And are you using MS aliases for patches that use the same sounds? If you're not doing either/both of these, that'd explain some of the issues you're having. Also, take a look at the FX you're using and get rid of anything that's not absolutely necessary...and use aux busses for FX instead of multiple instances. Have you turned off/disabled any OSX processes that you don't absolutely need? For example: Notification Center, iCloud processes, social media apps, WiFi, Time Machine etc all use resources. Disable Spotlight because its indexing process chews up resources. Disable everything you don't absolutely need because your machine is pretty much at the bottom end of the capability spectrum when it comes to running MainStage for live performance.

Finally, due to your setup, you'd be far better off trying to find synths and libraries that use considerably less resources....or invest those dollars instead to buy a MacBook Pro 15" with 16GB RAM. MainStage is an absolute resource hog and you're always going to have issues with your current machine, especially with big sample libraries and resource-intensive synths and FX. Kontakt can be fantastic in terms of being resource-efficient PROVIDED that your libraries are efficient, and so you're going to need to think smart about what synths and libraries you use.

You may even find that running something like Reaper or GigPerformer instead of MainStage is a better option if you can't afford to get a better machine or buy new synths/libraries. GigPerformer isn't cheap, but it's getting some great reviews about its low-resource usage. Download the fully-functioning 14-day demo and create a setup like your current MS concert to see if it works better for you.

Reply

Answer 2

jmchugh100 Author

Level 1

5 points

Jun 13, 2017 12:40 PM in response to Madddcow

Thanks for the detailed reply Madddcow. I understand at least some of it :-) Not sure what Kontackt in Multi Timbral mode means though! I will try and read up on it. We have a gig mid July so need to do something ! I intend to move the concert to my more powerful Imac and make changes there before moving it back to my puny macbook. What I'd really like is if I could find someone who could take the file and set it all up for me. Something for which I'd pay! John

Reply

Answer 3

Madddcow

Level 2

463 points

Jun 14, 2017 5:53 AM in response to jmchugh100

Hi John. Running Kontakt in multi-timbral mode means that you use one instance of Kontakt and load patches into a "rack", assigning a different MIDI channel to each until you reach the maximum of 16 MIDI channels. In MainStage, you then configure each channel strip for your MS patches to send MIDI on the MIDI channel corresponding to the Kontakt patch you want that MainStage patch to use. However, each of the MainStage channel strips will need to be an "alias" of the primary channel strip hosting your instance of Kontakt. By doing what I've described, you can often significantly decrease the system resources (primarily RAM, but also some CPU) being used by both MainStage and Kontakt. As each instance of Kontakt can host patches using up to 16 MIDI channels, you won't need to run many instances of Kontakt overall.

Reply