eelco

Yes, the stuck notes problem with my Clavinova CLP-170 has been solved again. Many thanks!

Do you see the letter "P" instead of "R" on the Record Enable button in the channel strip inspector? Then the reason is probably that you have punch on the fly turned on. I had the same question just a few weeks ago: http://www.logicprohelp.com/viewtopic.php?t=51848

Not so great news: The exact same problem seems to be back in Mainstage 2.1 (!) I will resubmit the bug to Apple. Update: Fixed again in 2.1.1!

Are any more details available on Ivory 2? I can not find any mention of it on the Synthogy website.

Yes, that should be possible with the Playback plug-in, if you set it up to sync with the concert tempo. You can control the concert tempo using a tap-tempo button, or using a slider or rotator control, and this tempo then changes Loopback's sample playback tempo. Make sure that the audio file that you load into Loopback contains tempo information, for example by bouncing it from Logic. Loopback can also be set to sync to the concert tempo, but in my experience this syncing works only before recording the first loop. Changing the concert tempo afterwards leaves the Loopback tempo unaltered, even though it is set to sync.

Yes, with a MIDI foot switch, such as the Apogee GiO or Behringer FCB1010 (search the forum for message threads on other options), you will be able to control Mainstage to advance from patch to patch, start/stop the playback plug-ins, enable/disable effects, etc. I think that is all that you would need and more. You do not need to know much about MIDI to set it up, you can just the Learn function in Mainstage to assign the foot switches to on-screen buttons. Using AppleScript is another possibility, but unless you have experience controlling applications from AppleScript, I think that will be more error-prone and require a steeper learning curve. A MIDI foot switch will keep you in control without getting in the way.

I do not think it is possible to set this up to run automatically in the way you are describing. But I think it would be quite useful to connect a MIDI foot controller to the laptop, and simply control the change of patches with a foot switch.

There is no need to unlearn mappings, new ones replace any old ones. Perhaps you should check whether you already have mappings in the set or concert level that override the mappings in the patches that you are trying to change. Have you also tried creating a new Mainstage concert from an empty template? You can put in 12 buttons in Layout mode, arrange them on the screen as they are on the GiO, and assign them to the 12 buttons on the GiO using the learn function. Then add your patches/channel strips in Edit mode, and map some parameters to the 12 buttons by selecting them from the column-mode list in the Screen Control Inspector, or by using the Map Parameter button to the right of that list. Then you should be set to go. You should be able to modify the existing templates to your liking in much the same way, but make sure that you first understand which parameters/buttons in the concert template are linked at the concert level, set level and patch level. Review the Mainstage manual if you are not sure about this.

Yes, I can see that that would be a useful way to assign the buttons, but I have not tried it that way yet, and I do not know if it is possible, since the GiO sends control change, not program change messages.

That's it, now it makes perfect sense. Many thanks.

Hi, I am relatively new at Logic (using version 9), and about halfway through studying David's excellent book. However, during the exercises, and my own fooling-around with the software, I am encountering some weird behaviour, which I have not been able to find an explanation for in the book or the Logic manuals. Both are related to the buttons underneath the channel strip fader in the inspector. 1) On audio tracks, I have on some occasions encountered the letter "P", instead of the usual letter "R" in the red record-enable button, when the button is enabled (red). In that state, I am unable to hear the sound of my microphone or guitar during playback. Only when I start recording do I hear the sound again. Changing the Audio settings in the preferences, and re-initializing the Core Audio drivers has on some occasions resolved this state. 2) Now, and this is new to me, on a software instrument track, I am seeing a blinking letter "M" in the disabled (grey) mute button. I am also not able to hear the instrument when I am triggering it from my MIDI keyboard. If I should guess, these are both indicators of a state of the software which I have inadvertently triggered. But I do not know why, or how to get out of it. Any help is appreciated.

I am quite happy with my new GiO. (Re)mapping the GiO buttons to Mainstage functions is as easy as with any other MIDI controller. I do not feel there is any issue there. Each of the 12 buttons can be assigned to control anything in Mainstage, including all Playback/Loopback functions, previous/next patch and prev/next set.

Perhaps you can configure your nanoPad to send program change instead of control change or note messages over MIDI? I don't know if that is possible with the nanoPad and its configuration software. Then in Edit mode in Mainstage, you should set the corresponding program change numbers for each patch in your concert. I have not tested this, but I would try it this way...

I do not think your CPU usage is anything to worry about. It is a good idea to not have any other software running when using Mainstage, so that it can make full use of the CPU, that means up to 100%. When it is at 100%, that means that your CPU power is not enough, and it can start to affect the sound. So I think your real problem is the latency. That depends largely on the audio interface and the instrument and effect plug-ins you are using. If these things are considered fixed, the main setting you can play with is the buffer size setting in the audio preferences. This is what the Mainstage manual says about this setting: So don't worry about using 20% or 60%, or even 80-100% CPU for short durations, as long as you do not hear any audio artifacts. Of course you should stress test your setup during practice, and leave some margin, because you don't want to go over the edge during a live gig and experience audio artifacts then.

I understand that the M-Audio drivers leave something to be desired. Although I am reasonably satisfied with my M-Audio interfaces as a hobbyist, if I would gig professionaly I would certainly invest in better gear. To use the standard line-out of the Mac in MainStage is an interesting recommendation. But in addition to that, there is also a reason that CPU and memory usage meters are featured prominently in the Logic and Mainstage interfaces. If there are audio problems and one or both of these meters is in the red, there is probably no other solution than to reduce the memory and/or CPU load of the computer. That can be done by limiting the number of channel strips and plug-ins in Mainstage, but it is also important to have a look whether any other processes are eating up CPU and RAM. The Mac OS X Spotlight and Time Machine components are sometimes the culprits. There is no way around CPU and RAM limitations, even when one is using the most high-end audio interface. I am very surprised by the costly solutions proposed in this thread, which might not even provide a real solution. Without more insight in the configuration of the topic starter, there is no way to say whether the problem is really in the M-Audio drivers, or whether there is something amiss with his OS X system configuration, or whether he has just overloaded his MainStage concert with channel strips and plug-ins, beyond the CPU and RAM capacity of his Mac. The Mainstage manual refers to the "Setting Up Your System" section of the Logic Pro User Manual, and has this to say about the topic in addition: