Apple mainstage versions update#
Apple mainstage versions Patch#
Apple mainstage versions pro#
Apple mainstage versions software#

It works in much the same way and bears a similar user interface. I've spent many hours of my life debugging audio issues and have now learnt it's best to enjoy a few months off music and wait for the bugs to be fixed.MainStage might be thought of as a companion app to Logic Pro.

Apple mainstage versions pro#

The issue could also be Apple's USB stack as I use a RME Babyface Pro audio interface which connects via USB. Note also that only really OS code can block audio threads which generally have priority over everything else. I have the absolute best MacBook Pro money can buy (incl Vega 20, the only thing not maxed out is the SSD) so I'm sure this is an issue on Apple's side.

(Things also degraded performance-wise when I updated Mainstage before updating my HW). The spikes I'm hearing were not present in the same AUs a few months back with older (weaker) HW. These major issues with audio quality happen from time to time sadly. Looking at the RME forum (see link below which also references other forums), seems users worldwide with new Mac HW are having similar audio problems so I'll wait for Apple to sort this then come back to computer audio. 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.

Apple mainstage versions 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.

Apple mainstage versions software#

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.

Apple mainstage versions 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. 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).