BWSFBTP

Sorry for the (possibly) stupid question... I haven't used MS in a while. I recently updated it and now I can no longer seem to get an expression pedal to control the volume of a channel. I used to map expression to volume on a particular channel strip and restrict the top/bottom values to maintain control over the total range. I'm certain that capability wasn't removed, but I cannot seem to figure it out now.

I completely forgot about this solution - it'll save me an instance of Truepianos! Thanks...

Maddcow is correct. The volume settings and midi settings (regions/transpose) are not global - they apply to a single instance of the patch only. I did, however, discover some odd behavior with muting stuff. I have about 20 instances of VB3 in one patch that have various drawbar/percussion settings and are used (via alias) by several songs in the project. I have to solo/mute the original VB3 instances to do tweaks on them and I've noticed that changing the solo/mute settings in the original patch where they live has caused some odd solo/mute behavior with the aliases. I'm still investigating a workaround.

I think I may have answered my own question here: https://brianli.com/using-aliases-to-reduce-ram-and-cpu-usage-in-mainstage-ce198bee2a4a#.wpcz3d5bt I knew about aliases for sample-based instruments, but it seems I can also create an alias for a particular sound in any plugin. For example, I could create one AM Pro Soloist instance of the Trumpet patch and use it in 10 different songs. I'll give that a try.

I have a question regarding Mainstage concerts for you MS experts. I am the keyboardist in a Genesis tribute band and I'm using the following plugins: AM ProSoloVST (32-bit AU version via 32-lives) Kontakt (for various sounds like ProSoloist, Pianet, RMI, sound effects, etc) M-Tron Pro VB3 (via 32-lives) Pianoteq I am wondering how many instances of these things I can put into a single concert. Each of the songs uses a lot of different sounds so I am switching through patches a lot. Cinema Show, for example, uses 6 or 7 patches, each of which has an instance of AM ProSoloVST and VB3 at a minimum. I'm figuring by the time I'm done programming our repertoire, I could have 100 instances each of ProSoloVST, VB3 and M-Tron pro in a single concert. Is Mainstage going to handle that? Should I be doing something differently or approaching this in another way? I'm running Mainstage on a 2015 15" MBP w/16GB of RAM, 500GB SSD and quad-core i7 with a Resident Audio T2 (Thunderbolt).

Great update. What's odd is that no matter how many times I install the update, the app store still shows it as a new update. It also shows that it has already been installed 3 times....hmmmm. Anybody else seeing that kind of behavior?

Sorry it took so long to answer...I tested the Wavestation with a few patches last night and it works. I only have the M1 demo installed, so I'll try the poly6 for you.

I just installed these...I'll try it out and see if it works for me since I'll be using them extensively.

So far, I've been using a Kurzweil PC3K7. It's a very capable controller, but it's expensive and heavy, so I'll probably use something lighter and cheaper at some point.

Hello! First time poster and new to Mac and Mainstage. I just built a Mac Mini system (i7, 16GB, 1TBHD) running Mavericks and Mainstage 3 for use in my Genesis tribute band. So far things are going extremely well. I have a question about the Tuning tab and creating a user scale. As long as I'm using one of the plugins that came with Mainstage, user scales seem to work fine. When I try the same thing with a different plugin (i.e., Omnisphere or SampleTank3), however, the user scale seems to have no effect. The manual doesn't say it won't work with other plugins (outside of Apple's). Any ideas? Bill