MainStage 3.4 playback plugin jumps back to the start

Yes. I'm no software tester expert but I'm pretty sure it's simply a very bad bug in 3.4. Difficult to test as its so random and can take ages to happen. But inevitably you can be sure it will be in front of a large crowd at some point.

I just started using the playback plugin with MS 3.4.2 and it is UNUSABLE. I have a new Macbook Pro 2017 running High Sierra. I've been programming Mainstage in my live duo. I have a double keyboard rig with splits and layers, but pretty simple. On this one song I have two playback instances, one for drums, one for bass. I imported CAF files created with Logic, no markers. for the Playback plugin, sync is currently off, but I have tried it both ways. Only one patch for the whole song, no program changes.

If I hit play and start playing along at random points (early in the playback) the backing tracks reset to the start, I cannot pinpoint it. I have filtered sustain/expression controllers from the tracks in case that was it, but no go.

This is probably a red herring, but I hit play and listened to just the backing tracks, not touching any pedals or keys, and they played all the way through. Then I restarted and played along, and I haven't gotten the random reset thing to happen for about a half hour of playing with this patch.

I do electronic music design for theater, so I am no stranger to Mainstage, but I think this puts the kaibosh on my ability to use it for my live gig. If it's not going to be rock solid every time, I can't take the risk.

Ok, since Apple removed my original post because “it contained feedback or a feature that was not constructive” let’s try this again

from what I have experienced, and what stansongman has inticatedin the above post, it appears that when the playback plugin, or multiple instances of the playback plugin, and a MIDI or controller event ( like playing your keyboard) occurs, the track from within the playback plugin will jump to the beginning

problem is, it’s random. It doesn’t occur every time, or in the same place, under the same circumstances, so it’s a moving target

Hi Carlo,

stansongman stated above that he’s having this issue with 3.4.2

is this the latest version you are saying that issue has been fixed on?

And how how much do you rely on the playback plugin for professional use?

Hi Jim,

i use 3.4.2 and Sierra and it's working fine.

I have MacBook Pro (Retina, 15-inch, Late 2013) 16GB SSD.

I decided to wait before upgrading. Of course I can't wait forever, but i had a lot of trouble in the past and i learned that it's better to be careful.

I don't know the level of professional use that you require, but I use it on stage and it works. I change in two hours up to 25 songs using Playback and loopers to start some pattern. It append that i stop and restart and I have no problem.

Hope they will fix quickly, but last time I had to wait a lot.

i use this in multiple professional settings, and there’s no way it’s useable currently

you said that you’re on Sierra. Is this a High Sierra/ Mohave issue?

so far, that seems to be the common denominator as it relates to those of us having this problem

Here's something I tried today that seems to be working for the backing tracks (I'm not yet confident this is solid). But, for my song with the two playback channels, I have set

sync - off

snap - off

play - relative

I'm recording the audio backing tracks at the desired tempo, so I'm not setting tempos in my concert.

I spoke to soon... it's back to the random reset thing again, so frustrating! Apple, what does it take to get the Mainstage team to pay attention to this? I've got to go find a total other solution because of this problem.

can you revert back to 3.3?

it would show a lot for Apple to acknowledge this bug, and at the very least, offer a download to the last version of 3.3 for those of us who have purchased their software, for professional use, but cannot use their latest version for professional applications

I still need MainStage for my theater programming gigs, but I have started working with Gig Performer for my live gig. It's a whole different paradigm so there's a learning curve, but it is much better suited for live performance, and so far in my testing it's been absolutely rock solid, including the backing track playback functionality. I don't have time to wait for a MainStage bug fix.

I have exactly the same issue. Everything was working fine in previous version but I have this problem with 3.4.

Same problem! Playback works terrible in Mainstage 3.4! I hope they will fix it soon!

Please try MainStage 3.4.1, which was released last week.

Has Mainstage 3.4.2 solved this issue of track playback randomly restarting? Has this been fixed?