MainStage 3.4 playback plugin jumps back to the start

I had to time machine back as 3.4 was unstable with any playback tracks. (also increased cpu usage, heat and fan kicking in - has never done that before with previous version.

3.4 should never have been released with this many issues!

I'm getting the issue in the edit window also. I also discovered that the problematic tracks had markers. Including a start marker at the beginning. I removed these and now it seems fine. Still obviously a bad bug.

Having these issues as well. I hope Apple realizes how this renders Mainstage completely unusable to this of us running backing tracks.

seems like finding and re-installing 3.3 is my only recourse.

it seems to occur, in my case anyway, with any kind of MIDI activity. In some cases, just ppressing keys on the keyboard causes playback to go back to the beginning, and in others, it's in switching patches while the track plays.

and of course, it's random.

Actually, my computer automatically updated 3.4.1 yesterday ( which I didn't realize until this minute) and I was having these issues this morning as I was rehearsing for several upcoming gigs

So it appears that this latest update hasn't fixed the issue

incidentally, this happens randomly. I can't recreate it doing what causes it each time. It's a moving target, but most definitely happening enough to be unuseable in situations where backing tracks are employed

one note. .. I haven't upgraded to Mojave yet, hoping to not cause any issues with 3rd part plugins. I wonder if this is related in anyway

.

Same problem. Sound starts a second after the plugin starts.

Strange thing is that it doesn't happen on all the backing (click) tracks?

Work around is re importing all the click tracks where this problem happens.

Very annoying.

Already reported it.

Rolf

In case anyone at Apple is reading this, I downgraded Mainstage back to 3.3.2, and this issue is gone. Track playback works as it is supposed to, and has worked reliably and consistently all week.

So this is most definitely a 3.4 and 3.4.1 problem

Hello, I have the exact same problem with playback since I updated to 3.4.1 and it freaks me out, because I have a show on Thursday and none of my playback tracks play ok, they all jump the first second or so! How can I downgrade to 3.3.2? I can't seem to find an installer anywhere! Or maybe there is another solution to this problem?

Edit: I found a half solution, when I turn off sync or reimport the sample, playback behaves normally. BUT, unfortunately, if I save the concert and reopen it, playback jumps again for the first second, which means I have to redo this procedure again for all my Playback plugins for all the songs (and they're a lot of Playback instances!). So, I have to do this in the few minutes that I have for setup time during Thursday's show (it's a multi band festival, so there is no time...).

HELP please! How to find the 3.3.2 installer and downgrade??

I also tried redoing the patches again from the start and the weirdest thing is that, when I first make them, Playback behaves normally, but when I save the project, close it and reopen it, Playback glitches!!...

Same Issue with 3.4.1 version. I use playback to send a loop click (instead of metronome). But it miss the first beat... I've tried redoing the patch (it works), but when I save, close, and re-open...same issue

But backing to 3.4.0. it works fine... Hope they fix soon!

I never was able to find a 3.3 installer, but I thankfully still had 3.3.2 om=n my studio computer

Apple... at least offer and allow a downgrade to 3.3 if you are going to release updates that don't function correctly, or reliably.

Same problem. Sync of then sync on fix the problem but when i save and restart the problem is still there. Downgrading solve the issue. Just upgraded to 3.4.2. There is a very big upgrade in the OS. Tomorrow i'll see if everything is ok. Very big problem.

3.4.2 and still getting the issue here. Very annoying. My main laptop is locked on 3.2 and it’s incredibly reliable. I can only get 3.4 on my new laptop. If anyone could send me last version of 3.3 I would be enternally grateful!

Wow, that's terribly disappointing to read, as I had planned on trying this latest update again this week.

I find it incredibly frustrating that Apple is staying so quiet on this. I suppose it's not enough of an issue in the big picture of iPhones and Apple music...

electro daddy, what OS are you running currently? And what year/model of computer are you using? Maybe we can trouble shoot some of this ourselves

Until yesterday I was on Mojave with MS 3.4.2 running on a decent spec mid 2017 Macbook Pro. A 3 day rehearsal resulted in the rest of the band wanting to kill me. Ended back on my 2013 Macbook locked on El Capitan / MS 3.2. Has been flawless for 6 years. Someone kindly sent me 3.3.2. Created a new partition running High Sierra. Not had a chance to test it in anger but will next week when we have more rehearsals. I'll be happy if it works but I've probably changed too many factors to be able to pinpoint what is causing the issue. However it's certainly something that has come about since 3.4 and none of the subsequent bug fixes have helped. I've used many Macs with various versions of MS over the years and never had this issue before.

OK, well, that throws out the High Sierra/Mojave factor. I'm still on High Sierra, and when I went back to using MS 3.3.2, I got the consistent, reliable results I needed with the playback plugin.

I'm using MS on an older 2012 Macbook pro (with SSD drive) and outside of occasionally hitting the wall with the maxed out 16 gig of RAM, it's an extremely solid running system.

I wish more folks would weigh in on this. It renders 3.4 completely unusable when using the playback plug-in.

So if you're a MS user, and use backing tracks, keep a copy of 3.3 on your system. You WILL need it.