- MAINSTAGE 3.3 CPU FAN COMES ON INSTALL
- MAINSTAGE 3.3 CPU FAN COMES ON FULL
- MAINSTAGE 3.3 CPU FAN COMES ON DOWNLOAD
- MAINSTAGE 3.3 CPU FAN COMES ON FREE
Selecting presets in Chromaverb no longer sometimes causes Audio Engine overload messages. Playback no longer appears to use unexpectedly large amounts of memory. MainStage no longer quits unexpectedly when exiting the app after pasting an Alias. MainStage no longer sometimes becomes unresponsive when editing Articulation Sets. MainStage no longer quits unexpectedly in rare cases when loading a concert that was saved with the Assignments & Mappings tab selected. MainStage no longer sometimes hangs when loading a concert that contains a renamed plug-in preset. MainStage no longer shows an error "The file format is not correct" in certain rare cases when opening a concert. MainStage no longer quits unexpectedly sometimes when changing audio devices while in playback mode. So far, in my testing, everything they say they fixed they did fix.ĭespite some of the growing pains, Mainstage is still the best $39 I ever spent on music gear. The missing past is a fancy UI and a simple way to switch patches, but for my band the amount of patches is limited and solved by my system. I've been using bidule for a very long time and it was always stable over updates (going back is also easy), no crashes and super flexible. I'm thinking of making a video of my setup. In a bank I can make 7 patches that can contain one vst, or all kinds of splits with effects.
MAINSTAGE 3.3 CPU FAN COMES ON FULL
I use this to disable a full bank at once to limit the amount of active vst's. Bidule has an option to disable a vst via a midi-switcher. My top keyboard has 6 banks of 7 sounds, some splits. I have a few piano-sounds on channel 2 (switched by program changes) on my bottom keyboard, also layers with strings, pad and a DX-piano
MAINSTAGE 3.3 CPU FAN COMES ON FREE
Mainy samples in sforzando (my own soundfonts and free soundfonts converted to sfz by extreme sample convertor) and OBXd does the job for me. The way I use it is not that normal I assume. 15-20% CPU load again (no loud fan activity), very fast switching patches and super flexible. Mainstage was so slow and was unreliable for me that i switched to Plogue Bidule. I'll report back here when I hear anything.
MAINSTAGE 3.3 CPU FAN COMES ON INSTALL
Hopefully they can see where the differences are between the old file with CPU issues, and this new one where my clean install seemed to fix it. I have been in communication with Apple this morning, and sent them a new Mainstage report from my gig machine. I also did the same on my test machine (late 2013 13" Retina, 2.4ghz, 128GB SSD), with the same better results. It hits the 51% when I am playing hard with lots of sustain pedal with PianoTeq.Īnyway, just an idea for anyone to try while Apple looks at all this. No lag switching patches, and CPU never went above 51%, which is how it behaved under 3.3.2 I actually ran 3.4 at a gig Saturday night, and it was flawless. With everything loaded, my idle CPU was back to 3%. I don't know why doing this worked, but it did. Then I opened Mainstage 3.4 and created a concert, and imported from a backup, all my patches. (I don't use the new studio horns or strings).
MAINSTAGE 3.3 CPU FAN COMES ON DOWNLOAD
I made sure to to download the exact Apple sound libraries I had before. I then went back into the App Store, downloaded 3.4 again, and let it do a fresh install.
I completely removed any trace of Mainstage and my 3rd party libraries (Arturia, PianoTeq, Syntronik) On my gig machine: Mid 2012 13" MBP 2.5ghz 16GB, 2-500GB SSD totaling 1TB While Apple is currently scouring the latest Mainstage created performance report I sent them, I tried something. He also told me they have received the reports of performance decrease in 3.4 compared to 3.2.2 regardless of OS (Sierra, High Sierra, Mojave, etc.)Īnyway, they are fully aware of the issue and are working to identify it.Īs soon as I hear back from them on my latest report I sent I will let all know what they say. It worked! CPU back to my original good baseline.Īt that point my guy at Apple had me create another one of those Support Profiles so he could analyze it, compared to the original Support Profile.
They spent a couple days running my concert on different machines, and didn't see the same increased CPU that I was seeing (and they could verify I was seeing).Īs a test, they had me create another user account on my MBP, and open the offending Mainstage concert in that. I did get in contact with Apple, and the person I worked with had me send them the concert I had issues with, as well as one of the "reports" you create. I initially had some increased CPU, but nowhere near the experience the OP talks about.
0 kommentar(er)
