Pushing RAM Limits

Locked New Topic
RELATED
PRODUCTS

Post

Good afternoon,

Enjoying playing with my new Receptor 2 Pro Max today and have a few questions, in case folks know the answer!

Obviously the Receptor has a CPU meter to track CPU usage - is there a way to tell whether you are pushing things too far with respect to RAM availability within a multi? For example, say you are using Elektrik piano and want many different presets. Could you open 10 channels of Elektrik and use snapshots to move between the 10 channels - the CPU could handle it, but how do you gauge RAM capability in this respect?

I've been trying to see how much I could load in a multi, just to understand the silly/absolute limits. Right now, I have a multi set-up with two channels of Akoustik (different piano), 7 channels of Elektrik, B4II, Pro53, and FM8. Bypassing each channel, say, down to Akoustik only, brings CPU use down to 10%, maybe spiking to 20%. But, as I've built up this multi, adding sources on channels, it has crashed (gone to the colorful Musebox picture, followed by a pretty fast reboot) - of course, I'm intentionally pushing things. But, is this a RAM limit? Once I "worked through" the crashes and established this multi it "seems" fine.

Anyway, curious if others have pushed the limits on a multi/bypass situation!

Post

Hello MRHudson,

If you switch to the "System Tab", and look in the bottom right corner for the "Info" pane, the 3rd item listed (Memory) should tell you the total RAM that the HW sees, and how much (percentage wise) is available. It's too bad this isn't a histogram on the mixer page, because it could be useful.

Given the items that you said you were adding in your multi, I'm doubting that you were running into RAM limits. More likely you were hitting a random UI crash - that seems to be happening frequently for me on my 2-Pro-Max.

Regards,
Kevin L

Post

Thanks! Yeah, as I've built up this multi, its crashed a few times as I added VSTs, particularly later in the "addition". But, once loaded/in place, things seemed to "take" and hang on okay. I can tolerate some little glitches in the "Setup" portion of the workflow so long as it doesn't carry over into the "live" performance portion of the workflow! I'm going to keep experimenting and see if an ambitious multi is stable once saved, reload, etc..

Random UI crashes.....hmmmm.......I'll try to see if anything seems to set it off, and open a ticket a plugorama to see what they say.

Locked

Return to “Muse Research and Development”