-
All replies
-
Helpful answers
-
Jan 24, 2016 7:10 AM in response to CCTMby Procman,Hello all,
Is there someone who upgraded WITHOUT any bug or crash or no compatibility with previous Concerts or excess of processor charge or slow reactions ? (I know I'm demanding much but my experience -3.1.1 to 3.2.0, back to 3.1.1, then to 3.2.1, go back to 3.1.1, and 3.2.2, go back to 3.1.1 ...- I wouldn't like to loose much time ;-)
-
Jan 24, 2016 7:34 AM in response to Procmanby gmmccurdy,It messed up my markers. I THINK I found a solution and will be working on it this afternoon. Like always, I'd recommend running a Time Machine backup before upgrading.
-
Jan 24, 2016 7:39 AM in response to gmmccurdyby CCTM,Hi
gmmccurdy wrote:
Like always, I'd recommend running a Time Machine backup before upgrading.
Whilst I cannot argue with making regular backups (Time Machine or otherwise), when it comes to MS or Logic application updates it is much simpler to duplicate the old version and rename it, then zip it (deleting the original before updating).
That way you can keep different versions on the Mac.
-
Jan 24, 2016 8:22 AM in response to gmmccurdyby Procman,Thank you CCTM and gmmccurdyfor your advice. I will run TimeMachine. But I'm still afraid because after go back from 3.2.1 or 3.2.1 to 3.1.1 (the only one version that works for me) I had a lot of problem when open Concerts I had opened whithe the 3.2.1 or 3.2.2.
After the first update (from 3.1.1 to 3.2) my Mainstage worked not as "fine" that it was before.
And do you know if the problem of Core are solved ? (probelms of Processors charge )
-
Jan 24, 2016 9:16 AM in response to CCTMby DrSchmenge,CCTM... Are you saying that I can have more than one version of Mainstage installed and working at the same time? I updated to MS 3.2.3 and encountered some serious problems with my existing Concerts, which are working well with 3.2.2. So I used Time Machine to go back to 3.2.2. It would be great to be able to have both versions available so I can run the reliable version for gigs and work with the troublesome new version at home when I have time.
with 3.2.3, external instruments in my existing Concerts aren't working, and integration with my Panorama P6 controller seems to be completely broken.
-
Jan 24, 2016 10:39 AM in response to DrSchmengeby Procman,I'm interested too to know about multiples versions. Is there abny problem if you rename the application ? for example: Mainstage to Maintage 3.1.1. The preferences are maintained ? (because it seems that I have only one Prefs file for a "generic" Mainstage named application)
-
Jan 24, 2016 12:12 PM in response to Procmanby CCTM,Hi
DrSchmenge wrote:
CCTM... Are you saying that I can have more than one version of Mainstage installed and working at the same time? I updated to MS 3.2.3 and encountered some serious problems with my existing Concerts, which are working well with 3.2.2.
Procman wrote:
I'm interested too to know about multiples versions. Is there abny problem if you rename the application ? for example: Mainstage to Maintage 3.1.1. The preferences are maintained ? (because it seems that I have only one Prefs file for a "generic" Mainstage named application)
In short:
You can have all those versions available, though they will only run 1 at a time.
The Preferences file applies to all versions ( but are quick to nuke if you need to).
Note that it is much better to have a separate boot disc for each in order to keep everything in it's own "space", but it does work.
CCT
-
Jan 24, 2016 1:40 PM in response to Procmanby scoplunk,Hi Procman,
So, it appears you're having the same issues I am with 3.2.x. I haven't found a version yet, including 3.2.3, that doesn't choke when using a concert that plays without any trouble at all in version 3.1.1. Here's a detailed post I wrote about it:
http://www.logicprohelp.com/forum/viewtopic.php?f=17&t=122321
Something fundamental changed with 3.2. I'd love to be able to use Alchemy, but I've spent literally days trying to troubleshoot this and I can't locate anything in particular that sets off the problems I'm having. At a certain point, my CPU use jumps and I get crackling and pops. Changing the buffer size doesn't help. I've tried to isolate different plug ins, but haven't had any consistent success with any of the things I've tried. I'd just give up and think the concert was corrupted, but it plays perfectly in 3.1.1, so that can't be the case. Plus, in my testing, I'm getting the feeling that maybe the problem is additive. In other words, the more patches I add, the more likely I am to see these issues. So, I'm not in any hurry to begin rebuilding and then find out that I'm right back where I started about the time I get into the middle of the project.
There aren't enough people complaining about this stuff for me to think it's some global issue. Apparently, there's something in my set of plug ins and the way I've set up this concert in particular that doesn't work with 3.2.x. But, this concert is pretty sophisticated and represents a lot of work. I don't want to start over and I'm especially gun shy now because even if I could fix it for 3.2, would it all be broken again with 3.3?
If anyone has any suggestions, I'd love to hear them...
-
Jan 25, 2016 5:19 AM in response to scoplunkby Blueberry,Do your issues only occur with Kontakt? If so, did you try changing the multi-threading options _within_ Kontakt? Omnisphere also has multi-threading within the plugin itself. If you use that one, also try turning it off. Another option is to limit the number of cores used by MainStage to allow Kontakt to use more.
-
Jan 25, 2016 5:34 AM in response to Blueberryby Procman,
Thanks Scoplunk,I had a lot of bugs between 3.1.1 to 3.2, 3.2.1, 3.2.2. (Concerts not "openable", midi transmit interrupted, windows "playback" that didn't follow the song, Sustain pedal not recognized, midi devices not recognized ... I can't count the number of bugs and the number of hours to try to resolve it).
I'm using Mainstage ONLY as a midi platform with just maximum 1 stereo Playback + 1 mono click. (all in Logic format, with or without synchro... same problems). I don't use any plug-in (no Kontakt, no "Apple" synthe or effects ...). That's why I'm very angry. My concerts are very simple and it's not acceptable to be unstable with the 3.2, 3.2.1, 3.2.2 versions as then it works (98%) with the 3.1.1 version.
I know nobody who can accept to not be able to open a doc Word 2011 created on a 2010 version.
I wait to update after I will be sure (at 100%) that it work. Professional approach the Apple's Mainstage developers should have.
-
Jan 25, 2016 6:48 AM in response to CCTMby halcyonseven,So I made the mistake of updating without a backup. Ugh. I've been so used to not having issues with updates that I went for it.
Big mistake.
It completely screwed up my patches. Things that were assigned to faders and knobs got completely moved around. No idea why. A few of them actually changed MID-LIVE PERFORMANCE.
Thankfully it's an easy fix, I just have to go in and move about 10 things back to the correct fader/knob but seriously, ***?
Anyway, don't be like me, backup first. :/
-
Jan 25, 2016 12:13 PM in response to Blueberryby scoplunk,I've always left the multiprocessor option turned off in Kontakt because I read that it can interfere with the MS multiprocessor scheme. I've been thinking turning it on again just to see what happens. At this point, I don't have much to lose! I also usually set my number of cores devoted to MS to 6 or 7. I've tried various settings of this, but none of them seem to make any difference regarding the CPU spikes.
I'm sure that the problem isn't just Kontakt. I've made some test concerts that don't include it at all and I still run into crackling and CPU spikes. But, since I've been testing using patches that also include other plug ins, I'm now in the process of trying just the instruments and deleting all the other plug ins in the signal chain. It's a tedious process because the CPU spikes and crackling don't start for about 20 minutes or so anyway, so I have to try something, wait and see what happens and then try something else.
I can't figure out if this problem is a particular plug in or if it's something that's cumulative - like no matter what I subtract from my channel strips, just the sheer number of things in the concert at a certain point causes instability that wasn't there in 3.1.1.
Still testing. I'll report back if/when I figure this out.
Thanks for the reply!
-
Jan 25, 2016 12:22 PM in response to Procmanby scoplunk,Yes, it sounds like your problems are even worse than the ones I'm having. Sorry about that. Still, I'm trying to hunt down incompatible 3rd party plug ins and you're saying you don't even use those and are having these issues. That's interesting since it points to an issue other than 3rd party stuff.
But, I'm trying to be realistic here and the fact is, there aren't a ton of people experiencing the same issues we're having or we would see endless ******** all over the internet. So, there's something that's particular to our machines or setups that is triggering a problem. I actually don't think it's machine related, because I have two different machines doing it, so that makes me think the problem has to do with something in the concert I'm trying to use. Since I don't see the same issues with the Apple keyboard concert, I'm pretty sure I've got a 3rd party plug in incompatibility. But, that's just a guess. Maybe it's something more fundamental and we've both triggered it somehow.
I've actually made a little progress over here. I'm going to start adding more things and see where it breaks. I have a few suspicions, but I've said that before and been wrong!
-
Apr 11, 2016 11:47 PM in response to scoplunkby Procman,Do you think it's reasonable to install the 3.2.4 update or (like with 3.2, 3.2.1, 3.2.2, 3.2.3 ) continue to test Ableton LIVE to switch and let Apple unable to solve the previous bugs ? Oh, last thing, please, Apple, remove Mainstage frome the "Professional Apps" section, it becomes ridiculous.
