Mainstage Sample Rate Conflict?

Firstly, please accept my apologies for making two posts about this, but I have a huge gig in about 24hrs that may self destruct if I don't solve this problem and I wanted to hear from anyone that might know more about how mainstage deals with audio files at different sample rates...


A detailed explanation of my issue is in this post:

Mainstage/Kontakt disaster in front of sold out venue)


In summary, I had a big gig last weekend and during the last song the samples being triggered in kontakt within Mainstage, started to warp and slow down.


After examing lots of possible causes my latest theory is that mainstage was not coping with the fact that most (not all) of my audio files were bounced at 48kHz (24bit) and Mainstage itself was set to 44.1kHz. I'll be changing all of my audio files to 44.1 regardless (as well as lots of other optimisations), but I'd really love to be able to isolate that as the problem.


If anybody can let me know of the likelyhood (or not) of this being the cause of this problem I'd really appreciate it!


Thanks!


OSX 10.8.5

Mainstage 3.0.1

Kontakt 5.2.0.6361

Akai MPK61 Midi keyboard

Native Instruments Audio4 DJ Interface

MacBook Pro, OS X Mountain Lion (10.8.5), 2.6 GHz Intel Core i7, 8GB

Posted on Nov 27, 2013 8:13 PM

Reply
3 replies

Nov 28, 2013 5:42 AM in response to CommanderCool

I've had issues with Mainstage while running it at 48k and running Logic 9 simultaneously. The default setting for Logic was 44.1k. The result was that all instruments in Mainstage played back a half step flat. To remedy the situation I had to match the sample rates. If you think your cpu is overheating, put a fan on it. The other thing I would do would be to max out the RAM to 16G.

Nov 28, 2013 6:07 AM in response to CommanderCool

I should have read your previous post before I responded. If you're maxing out the cpu, try adjusting your I/O buffer. I see you have it set to 128. A higher setting may cause too much latency, but maybe you can strike a balance.Try checking the I/O safety buffer box. Another option is to thin your patch. Remove anything that you can live without. If you're running several instances of Space Designer, try deleting one. Try deleting anything you can do without in Kontakt. Once you've made changes that seem to help, try quitting Mainstage and reopen it. It just seems to run better freshly loaded, as Landrix said.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mainstage Sample Rate Conflict?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.