#MAINSTAGE 3 TEMPLATES UPDATE#
#MAINSTAGE 3 TEMPLATES PATCH#
#MAINSTAGE 3 TEMPLATES PRO#

(Hopefully 3.0.5!!!)ДЄ template for live looping should have following features:ДЈ) Vocal processing channel strips (Reverb, auto tune, and Vocoder)Д¤) Output effects channel strips (EQ, Delay, Reverb) So I am campaigning Apple to include a live-looping template in the next release of MainStage. If Apple includes a template for live looping, it will make our life a whole lot easier. Any help MOST welcome.Apple MainStage 3 has an excellent library for unbelievable price and it is geared for live-performance, but most of the live loopers are not using MainStage at present. Now this happens and I'm back to reality with a crash. I followed all advice on cutting back memory and CPU usage ages ago as MainStage did sometimes crash on me, and have had it stable for a while now. In particular using Contact (something I only use only for special reasons as I know MainStage hates Kontakt!) the CPU rapidly climbed to 100% with any heavy piano usage (more notes I'm guessing) and having reached it started cutting off sustained tones and making the whole sensitive piano part I was playing a joke. The latency is not a problem and the keyboard graphics all look fine, but the CPU which normally flicks between 18% and 36% is MUCH higher for all patches. Sometimes held chords from previous patches were cut off when changing too - VERY destructive.

#MAINSTAGE 3 TEMPLATES PATCH#

Played my first gig with new Mojave OS and MainStage 3.4 last night (same performance patch I have been using all year) and patch changing was noticeable slower. I haven't had the system overload message but I'm getting this too. I'm have a gig coming in two weeks and I'm really frustrated and hopeless with the situation. Sadly, I can't say if this issue it's something related to MainStage 3.4, Mojave, or their combination as they got upgraded same time. Also, I donвЂ™t have any custom audio plug-ins, drivers, software etc. Also, the issue occurs without any external MIDI or audio devices. Keyboard Minimalist) bundled with MainStage. The reason is not that I would have something special in my concerts - this happens even with the simplest concert templates (e.g. The high CPU usage does not occur when I open just MainStage but when I open any concert the CPU goes up immediately and stays high as long as the concert is open.

#MAINSTAGE 3 TEMPLATES UPDATE#

After the update to 3.4, I didn't change any settings in MainStage, only updated the sound library. I have never experienced such behavior with any previous MainStage versions.

#MAINSTAGE 3 TEMPLATES PRO#

I'm running MainStage on MacBook Pro (Retina, 13-inch, Late 2013) with 2,6 GHz Intel Core i5, 16 GB 1600 MHz DDR3, and built-in 500 GB Apple SSD disk. Also, my MacBook is running super hot and fans are spinning top speed which is not nice. In practice, my MacBook becomes almost unusably slow to do anything and changing between patches is too laggy for doing any live performance. With 3.4, I'm experiencing continuous extremely high CPU usage (150-250 %CPU) by MainStage and also getting audio engine overload warnings. I installed macOS 10.14 Mojave and my MainStage 3.3.2 was updated to 3.4 automatically during the installation process (which is not what I wanted by the way).

Mainstage 3 templates