thalund

This has earlier been discussed concerning MainStage 3.0.2. If I open a Mainstage concert, do a few edits and press cmd-S, Mainstage copies all samples used in the concert into the concert file package. Has anybody else this problem? In my case, the concert file goes from 3.4 MB to 714 MB. In my workflow changes in concerts are frequent but only rarely include changes in my sampling library. So backing up to a memory stick is quick, with the concert file being small – the full sampling library of several GB is only rarely copied. In some cases it's ideal that samples are embedded, but it should be respect user's choice ,and the application should still default to save in same structure as the concert was originally? Right? If I choose 'Save as…' the option "Copy sampler data into concert" is defaulted on. If option is deselected a 'slim' concert is saved, but still any samples used in the new "Quick sampler" plug-in are embedded. File in my case goes from 3.4 to 12 MB However any regular save operation after that, still stuffs the full 714 MB into the file. Workaround is to never press cmd-S, always "save as…". Deselect "Copy sampler data into concert" (program will then stillsave some samples) Aggravating. Workaround 2 after closing concert: Right click "Show package content" on concert file and remove "Sampler instruments" and "Sampler files" folders. Only use if you're 100% certain the removed content is present elsewhere on the machine. It works for me, although I think Mainstage will then scan for the files when the concert is reopened as it probably has moved the concert's path pointer to the embedded…

I can reproduce this, so definately a bug, and I totally feel like "aguyfromsomewhere" posing about this FOUR years ago. When doing fine editing much zoomed the last thing you want on playback is catch, loose and then have to refind the edit point on every playback. There is NO alternative workflow unless you're content with not being able to listen do your edits while doing them, you simply can't make it do override the auto on. Just as OP I disabled all three "Auto Catch" options in prefs, and checked for conflicting hotkeys. No avail, still just re-engages catch on spacebar playback, or when pressing playback button on transport pane. I'm on Logic 10.7.9, Monterey It completely voids the purpose of there even being a button to switch catch off. Does apple even care about Logic anymore?

That is exactly right. I must say I still find it very weird that MS can't do simple midiclock sync. I'll look at the PlogueBidule solution, seems interesting Personally i've now taken all midiclock synced sounds out on hardware synths like the Artutia matrixbrute. Expensive solution…

I have a similar issue or more precisely Handling a changed audio interface is not handled gracefully. Audio strips does this: On an audio channel strip set to, say input 5-6, if I then open the concert without the interface connected - that input is not available but MS doesnt screw up the channel. Leaves it as 5-6 and will be available again next time you connect an interface with that many inputs. External intr. strips After reopen its nor INPUT R3-4 that i dont even knowwhat is (only 1-2 is available), save and re open with interface, now doc is screwed. Oh I wish apple would understand MS is used by professionals who expect reliable behavior. //REné

Feeling the same here. I'm generally annoyed by notifications, I find them intrusive – even a benine one like this. Why on heck doesn't it come with a "don't show again"-option? // René

I agree. I did the the same mistake as the OP setup playback modules according to stems and expected I could make MS load in a new set of stems pr patch (song) Copying the playback modules pr song is a solution, but you end up with a vast no of channels, and if you want to change some mapping for eg "backup vocals stem", you have to go through each and every song and do the same change.

If I disconnect my audio-interface with a concert open MS freezes. Didn't use to. I use a RME Fireface UC Ideally MS would just wait for a reconnect.

I know this is an old thread – but this is still one of my main issues with Mainstage. I use Mainstage for live keyboard sounds, but to sync a simple arpeggio to incoming midiclock I have to run other applications like ableton live in parallel. Even soft synths like N-I FM8 that will easily sync when running standalone, becomes a confused doggy when running within MS. Full syncing with timeline is not necessary. We're not talking song position or SMPTE sync. The "intention of the external device" is not relevant imo. My intention is to have midiclock supplied by my drummer control arpeggios, tremolo effects, etc on a bar by bar basis. My Nord Lead will do it, any old synth will do it. They don't have a clue on (long) timelines, but they know that the first incoming clock message is the downbeat, 96 midi-clock events is a bar, and then they do divisions accordingly. If anything MS should just gracefully pass on incoming midiclock to the plugins.

I've had this same issue twice, while trying to drag a new take into an existing comp track. Realised that it was because besides the region I tried to move, I clumsily had some region selected on a whole different track, outside the window area – and the move operation would attempt to put _that_ region on a locked track, so the dialog was right just concerning a different region… There could be a bug causing it in other cases, but worth checking before tearing you hairs out.

Hey, just back in this thread - never answered this. All my instruments / controllers are dublicated. With spare units ready to go with dublicate presets. I know it's an expensive solution that of course isn't for everyone, but safety in these types of setups really come down to thorough testing and as much dublicate redundancy as possible.

The main point is that you have important and ideally uninterrrupted sound from your machine. Backing track and/or live instruments. The Radial SW8 is rather expesive yes. It switches in analogue sound domain, so for using that you need not only two computers but also two soundcards (so the systems become independent) which is not helping the budget either. The beauty is seamless switching with no interruption. Moving the (usb?) connection of the Motu soundcard from one Mini to the other in case of failure will of course interrupt sound for a moment. A simple passive usb switch like this one could speed it up: http://plugable.com/products/usb2-switch2

"By default Mainstage will pass any unassigned Midi CC messages to ALL channelstrips (an unbelievably strange feature)." I utterly fiercely agree. Mind you this behavior was new in MS2. The point of MS' Layout section is specifying your control surface - which helps monitoring and assigning incoming midi meaningfully AND protecting your channel strips from any irrelevant incoming midi. The latter purpose is completely undermined. I connected a keyboard with a volume knob that for some reason put out cc7 on both ch1 and ch2, Took me an afternoon to realize why this already assigned knob turned down ALL channel strips. Thanks for the workarounds, guys. Hope that apple realizes this feature is no feature.

I have an issue with random faders suddenly going down in MS 2.2.2. The faders are unmapped, yet they spontanously go to a random level, sometimes all the way down, sometimes some of the way - always to a lower level, never to a higher. I've tried to monitor the midi, a can't see any pattern in this strange behavior. I've seen this post about the same issue, no solution though. http://www.macprovideo.com/forum/audio/mainstage/38629 Any thoughts appreciated René // denmark

@Rhodes54 Try this: 1. Even though you only use one controller go to the Layout pane (cmd-1) and create one more keyboard object (two in total) 2. Assign them both to your hardware input device. 3. For convenience you could name them "Set key" and "Patch Key" 4. Now for you "set" instruments use "set key" as midi input, for your patch overlays use "patch key" I tried this quickly with one set and two patches, it seems to behave as you required. If for a specific patch you want the to quiet the "set" sound, exploit the MS behaviour and use "set key" for this patch.

Hi I also have a motu 828mk3. Select it as audio output in Mainstage -> Preferences -> Audio. on each channel strip i now have all outputs as options 1-30. you're right that s/pdif individually is 13-14. The default out i think is what is presented to system audio. good luck rené