exs dropout

No, it's different, the MS2 problem sounds even worse.
In my case, some instruments with long samples are effected. If I once had a problem with an instrument, you never could say again if the exs plays the sample or suddenly stops the sound. Restart did not help anything, other exs instruments were not effected. To be more clearly: I could play other exs instrumnets.
I thought playing the sample from the RAM could solve the problem but its is not possible in MS1 (I dont know about MS 2)
To make that RAM disc is not possible with my concerts, too big and only 2 GIG RAM, and I cannot build in more (first generation of MacBookPro)
I hoped that MS2 will solve this problem, but it seems to be even worse...

Raino

Any fix on the horizon please apple??

We dont want to get this confused with other problems, but EXS does sometimes stop streaming from disc. It is at it's worst with Mainstage 2.1, although it sometimes does it in Logic as well.

It appears it is not related to a particular machine, nor disc speed.
Its a problem.

It appears like there might be light at the end of the tunnel.

As some people have mentioned before, this is a general problem of the EXS, so it not only affects MainStage but also Logic. (Of course it's much more of an issue in MS because in a live situation you can't just restart the application and act as if nothing has happened.)

Now here is where it gets interesting:

While we are still waiting for an update of MS2, LogicPro 9.1.2 has recently been released.
I have just been spending some time with it, pushing the EXS real hard to see how it behaves and so far it looks very good! Although I pushed the system to the point where the hard disk couldn't keep up and samples had to be dropped, it never persistently stopped streaming. So there where dropouts (obviously), but after the peak load was gone, the system recovered and continued to work normally -- just like it is supposed to.

As far as I can see, Apple's official release notes for the Logic 9.1.2 update don't mention this bug-fix explicitly, but still they might have finally addressed the issue.
If I am right about this, a corresponding update of MainStage may be imminent.



PS: I must note however, that I've had the update installed for just one day, so feel free to take this report with a grain of salt.
Maybe those of you who are like me struggling with this issue can do a little bit of experimenting with Logic 9.1.2 and post your findings.

How you getting on Cronbg?

Still no change for me. Once the dropouts start, they don't stop until I restart mainstage 2

Leo

Im trying to figure out a workaround (although I'm not there yet) maybe a button to restart the audio engine or something.... but its terribly frustrating.

frustrating? it's pretty much unusable....
I read that the last logic updated fixed it in Logic, why wouldn't it fix it in Mainstage

lrizzo2001 wrote:
I read that the last logic updated fixed it in Logic, why wouldn't it fix it in Mainstage

AFAIK the Logic-Plugins (exs24, evb3, evp88 … ) aren't plugins in the same sense that AUs are. They do not exist as separate binaries which are located in one specific place on the drive and then can be used by multiple hosts. Instead, they are integral parts of the application binaries of Logic and MainStage themselves.
Consequently, if just Logic's binary is updated, MS is not affected.

Hi Guys -

Please report if the new 2.12 update fixes this (or not...)

Fingers crossed......

I have no change, still doing the same thing for me, and this is with a fresh new preset, not loading in something that was previously created.....

No, it is not fixed.

It's still weird. I first installed it just on my secondary machine (this was on thursday I think) and at first it seemed OK. I was not able to reproduce the problem with MS 2.1.2. So I was almost convinced that this is finally solved.
However today I installed it also on my main machine and did some tests (heavily pushing the exs). After ten minutes it stopped streaming.

Furthermore: Meanwhile I have also been able to reproduce it in LogicPro 9.1.3!
So what I had written a few posts before about the issue being fixed in Logic is obviously not true either!

This is so very disappointing. To be honest, I'm starting to lose any faith in Apple's ability (or dedication) to fix this at all.



I can totally understand, that it's difficult to fix a bug which is occurring so randomly. But this thread shows:
A: it's definitely an issue for several users on several machines
B: it can be reproduced on purpose
C: it's serious enough to keep people from using MS2 on stage -- which makes the application utterly useless.


___
main machine:
MacBook Pro 15" (unibody, early 2009, Model Identifier: MacBookPro5,1) 2.4 GHz, 4GB, 128GB SSD, OSX 10.5.8

secondary machine:
MacBook Pro 15" (late 2006, Model Identifier: MacBookPro2,2) 2.33 GHz, 3GB, 160GB hard disk, OSX 10.5.8

I know that it's not ideal especially given that it costs money, but have you considered using a third party sampler like Kontakt?

I've been thinking about this possibility before. My main concern is that I've not been able to determine whether Kontakt (or any other alternative sampler for that matter) is in fact intelligent enough to manage memory in such a way that it loads redundant samples only once per concert.
I think this is crucial for any Sampler to work well with MainStage.

As a matter of fact, this question has been bothering me for quite some time -- enough to start a thread on this topic.

Hi Guys,

I'm not saying this has been fixed.... Its too early to tell but I seem to be having success with 8 gig of RAM running in 64bit mode, (still streaming) with the latest versions of everything.

If anyone else can help to help test this - I'd be grateful.

P

Ok so I spoke too soon.

Please apple, have someone look at this problem.