Jump to content

Does MainStage load ALL a concert's patches into RAM?


MonoPoly307

Recommended Posts

Hi guys,

 

I am in the process of making the move to MainStage for my upper synth layer for live gigs. It's (as you could imagine) a pretty massive process, but I am excited by the prospect of how customisable MainStage is - sonically and in terms of the way the interface can be set up.

 

I've run into a bit of an issue though - when I set up the concert on my Mac Pro in the studio, I could transition from one patch to another without the first patching being cut off (like older synths did, and some still do!).

 

I have now opened the concert on my MacBook for testing the live setup I will be using (the MacBook has exactly the same plug-ins set up, and is more or less a mirror of the Mac Pro in the studio). Everything is working perfectly as it should - except... when I move from one patch to the next, the previous patch is cut off immediately. (I have the "silence previous patch" setting configured to 5 seconds on both computers.)

 

I'm wondering whether this is occurring due to the limited RAM (8GB) I have in the MacBook, compared to the Mac Pro (16GB). Perhaps this is making it impossible for MainStage to load all the patches when the concert is opened up, hence it has to purge RAM between patches, causing the previous patch to cut off?

 

Keen to hear your thoughts on this - both on the cause, and on possible resolutions?

 

Thanks heaps!

 

Mike

Link to comment
Share on other sites

I'm wondering whether this is occurring due to the limited RAM (8GB) I have in the MacBook, compared to the Mac Pro (16GB). Perhaps this is making it impossible for MainStage to load all the patches when the concert is opened up, hence it has to purge RAM between patches, causing the previous patch to cut off?

 

That might be possible. You can check with Activity Monitor if your memory pressure is an issue. Typically it _should_ be OK, because while all patches and instruments are loaded on concert load, sample libraries are typically not fully loaded. Only the beginning (first second) of the all samples are loaded to be available, when you need them. But if you push the system to hard, the CPU load spike between patches might trigger an overload.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...