zephtragic

When mapping a control, I seen in the inspector there is a folder called "Send To All." When I drill down into it I see it lists all of my possible Midi destinations and if you drill into one of those, it lists options for midi messages such as "Program Change" or 0-127. I've been fiddling with these options to see what I might be able to achieve with these settings and I just can't get it to do anything. I'm testing to see if I can get this to send out midi through IAC or anything really. But midi monitor is not detecting any midi traffic generated by these settings. Does anyone know how to use this and a use case for it?

Pumpkinzzz can you elaborate what it is you're trying to do? Its not clear exactly what you're trying to do (or the original poster, for that matter.) My brain keeps coming up with different ideas of what you two are trying to do, and there are a million ways to configure MainStage to do all of the things I'm thinking about.

I'm trying to configure my Smart Knobs Midi Thru attribute so that they're set to "Do not pass through" ( by default they're configured to "Automatic." ) I'm doing this by going into the Assignments and Mappings tab, selecting each Assignment for each Smart Knob one at a time, and changing the MIDI Thru to "Do not pass through" in the drop down menu. I've tried to do this on a concert level, as well as a patch level, being sure to hit CMD-S to save after each change. But no matter what I do, when I close the concert, the values always revert back to "Automatic" the next time I fire up the MainStage Concert. Is there something I'm missing? is this a bug? Does anyone have a solution to this? Thanks so much in advance.

Maybe I don't understand your question, but why can't you just put an EQ on the instrument strip and boost the bass for those patches?

Can you explain more what you are trying to do. I think from what you are describing, you want to look into setting up Markers for your clip. If you are bouncing your audio clip from Logic Pro X, it pretty easy to use the Marker functionality from there to define where you want the different "Positions" to be on the clip. When you pull the Audio clip into Mainstage, that Marker information is retained, and you can setup a button to "Play from Marker 3" or some such.

Nevermind, fixed it by deleting this file: ~/Library/Preferences/com.apple.mainstage3.plist and rebooting.

Not sure what happened, but suddenly I can not see the Workspace while in edit mode in my MainStage 3 projects. I can see objects if in Layout and Performance mode, but edit mode is something else. Just tried rebooting and even uninstalling and reinstalling the program. Anyone have any suggestions for me? http://wakingfae.com/images/temp/mainstage-missing.png

So I was playing around with adding my Traktor S2 controller to my Logic Pro Setup, along side my Nektar Panorama P6. I really love the feel, build and of the Traktor S2's encoders and pad buttons. You can set the S2 in Midi mode and by default it's Play Buttons are set to midi CC 10. I'm currently using MidiStroke to map CC 10 coming from the S2 to SPACEBAR, so that when I press it, it triggers my Logic Pro X session to play. The problem is, Logic Pro X is hearing the CC 10 message and hard panning my selected track to the left. Midi Monitor is identifying CC 10 as "Pan (coarse)" which seems clear enough to me what's going on here. What I don't understand is what/where is Logic Pro X applying this Pan (coarse) signal? Its not the track's pan controls that you see in the track info pane - that stays center, but the sound is still hard panning SOMEWHERE.

NM... Mission accomplished. Configured a column in the modulation router with the values: Dest: Art. ID Src: Ctr #1 Intensity: !00%

Once upon a time I had an M-Audio Axiom Pro and when I was using the String Ensemble patch in EXS24, the mod wheel just happened to be preconfigured to switch between articulations. From low to high CC value on the mod wheel it would move between articulations such as: Pizzicato Ponticello Staccato Tremolo Vibrato I no longer have that Axiom Pro and am currently using the Nektar P6 as my midi controller of choice. I'd like to get a similar behavior out of my mod wheel but don't know EXS24 enough to configure the mod wheel accordingly. Anyone know what the old Axiom Pro's mod wheel was actually controlling so that I can replicate this behavior?

I didn't fully follow what you were saying. I presume its because I'm not so familiar with the organ patches. I'm guessing what you are wanting to do is record some automation. Make sure your organ track is set to a write / latch / or touch mode and press play. While the track is playing, move the controls for rotor speed during the part of the song you need that movement. This will record the movement as an automation. When you are done, switch to read mode for automation and then next time you play the song, the controls will move on their own, the way you recorded it.

I don't get that behavior either. It works just fine. Furthermore, as of last night, I happen to have my logic libraries on my secondary internal SSD and is symlinked, and it works as intended in this instance.

OK, I've been able to replicate this issue on both a 2011 Macbook Pro and a 2011 iMac. The one exception is with the iMac, the Alchemy plug-in window settles on 125% and with the Macbook it settles on 75%. Even if I have an external monitor plugged into the macbook with 1920 X 1200 resolution, it still eventually settles back to 75% zoom view. I'm interpreting this as Apple automatically setting what it considers as optimal view based on the machine you are running Logic on, not based on the actually screen Realestate you have available. Sort of sad, because I'd like the plugin window to display larger by default, its sort of hard to read at such a small size.

It seems that if I open the Alchemy plug-in window it defaults to 75%. But if I set it to a higher percentage, for example the 200%, when I close the plug-in window (click the X on the top left) the next time I open the window it will open with the next smaller zoom value (175%) and if you repeat this over and over it works its way back down to the default 75%. 200% drops to 175% 175% drops to 150% 150% drops to 125% 125% drops to 100% 100% drops to 75% 75% stays 75% Anyone else getting this?

Oh... when I say "my other music libraries already live on hte secondary internal drive" I was referring to 3rd party libraries such as my Camel Audio Alchemy and Native Instruments Kontakt. This hasn't been the case with my Logic Pro / Mainstage instrument libraries. I had a memory that David N. was saying this isn't a good idea to relocate the Logic Pro stuff, but wasn't sure if he was referring to this method in particular.