Connecting multiple MIDI Controllers into MainStage

Seeing as there is only 1 MIDI I/O, can I run 2 midi controllers through the MOTU mk3 Ultralite into Logic MS? If so, how?

You have 2 keyboards in the layout? And they both work with the right physical keyboard? If that is the case, the input for the channel strips are probably not set to the right workspace object.

Similar Messages

Multiple MIDI Controllers in MainStage Problem

Hey there, I just assigned two different MIDI controllers to two different instruments as was recommended in this discussion (https://discussions.apple.com/thread/2280561?start=0&tstart=0), but after I tweak the sounds a little bit one of the controllers always just goes back to playing the instrument from the other controller.
For instance, I assigned Keyboard A (Arturia 49 Laboratory) a piano sound and Keyboard B (Alesis Q49) an organ sound. It worked beautifully at first and but now Keyboard B is playing a piano sound as well. The instrument strip shows the organ sound still though. And if I try switching Keyboard B to another sound it just keeps playing piano (although it displays whatever sound it "should" be playing).
Any ideas on this?

You have 2 keyboards in the layout? And they both work with the right physical keyboard? If that is the case, the input for the channel strips are probably not set to the right workspace object.

Multiple Midi Keyboards in Mainstage 1

Hi all
I am currently running mainstage with a Novation Remote SL61.
I want to also connect an Novation Remote SL25 to the set up, so I am running 2 Midi Controllers within Mainstage.
Does anyone know if this is possible?
Many thanks,
Steve

Just to be more specific, yes, you can use two (or more) separate keyboards.
If you have two identical controllers you sometimes can run into issues -- one way to work around this is to set the "device" drop down to all" and then set the channels differently, and have each keyboard send out everything on different channels.

I'm having an intermittent problem with my midi controllers triggering Mainstage 3. I'm using a PreSonus Firebox audio interface. It's been working fine for months, but now when I first turn on the computer in the morning , I'm not able to trigger Ma

I’m having an intermittent problem with my midi controllers triggering Mainstage 3.
I’m using a PreSonus Firebox audio interface.
It’s been working fine for months, but now when I first turn on the computer in the morning , I’m not able to trigger MainStage from the keyboard. I tried different midi controllers, different keyboards, different midi cords, and check midi preferences. The audio interface is working fine and is recogonized, but the midi doesn’twork. I re-started the computer several times and then finally it miraculously starts working again.
I’ve been having to this every day now. Any help or ideas is very much appreciated.

I Had the same problem with a FireStudio. Try unplugging the FireWire plug and the power plug. Wait for a few seconds, then plug both back in. The light on my FireStudio was flashing blue/red which means "not connecting." I did what I just described, and everything works again. Hope it works for you.

How to use multiple midi controllers with Mac book pro (2 usb)?

I have a newer macbook pro that has 2 USB ports, and a lightning port and a firewireport.
On stage I will be using the firewire port connected to a Presonus Firestudio mobile to use as the interface to the house mixer.
I will use 1 USB for my M-audio Axiom 61
I will use the other for my Yamaha WX-5 Wind synth
I'd like to be able to get the apogee midi foot controller to control the playback audio. For example I'll be using it to stay in a solo section, then step on it to move it forward ot the next section when I am done soloing
I'd also like to use some sort of midi switch to turn on vocal effects of the mic.
Anyway since I only have 2 USB ports, how should I connect the 3rd, or 4th USB midi controller?
Will a USB hub work to do this? If so, will I always have to remember to use the same controler in the same exact hub input to make sure everything maps the same?
I guess I'll also have to learn how to setup multiple controllers in Mainstage as well.
Thanks
Dan

Hi there,
is a question which many of us have spent ...
I think the obvious answer is that yes you can use a hub and connect everything. however ....
sincerely advise you to buy a good hub that is well feasible, the last thing you want on stage / rehearsal is one of midi controllers stop responding, or stay with hanged notes... etc., do not buy just because it is cheap it has to be stable and viable, some bring cable for connecting wall power just to not drain power from the USB port.
Other things to try is to distribute as much equipment for USB / Midi.
For example one of midi controllers connect via USB but not by Midi outside the Presonus Firestudio. Connecting Presonus Firestudio to a single USB port as it is a main equipment.
but it really is an issue that greatly limits the use of USB devices.
Try it and tell me how it went. Good luck
(sorry for my english i´m Portuguese)

Using Multiple MIDI controllers at the same time

It seems that there is no way to record from 2 different midi controllers at the same time without the data getting summed together. I'm trying to record a midi keyboard playing a piano sound and my roland v-drums at the same time. The result i get when i record enable both tracks is that both the keyboard and the drums each play both sounds. I'm using a MOTU midi express xt usb and have each of the devices on seperate midi ports and the drums are on channel 10. Is there anyway to keep this info seperated on it's own port? I've read through the environment chapter about 1000 times and there is no mention of this senario at all. Should I have saved $700 and stuck with MOTU DP4.6 which works just fine? Is there anyway to get some REAL help from Apple?

Have you tried: file/song settings/recording/auto demix per channel if multi-track recording?
hope that helps.

Multiple MIDI controllers

Hey errbody, so I just got a second MIDI controller, but I can't figure out how to have the two controllers controlling two different channels. This is possible, right?
Thanks a bunch

Did you read the manual? It's fairly simple.
Engage learn mode. Touch the softsynth parameter you want to automate with the mouse to select it. Move the external MIDI control to assign it. Rinse and repeat.
Turn off learn mode when you are done.

Help needed using multiple midi controllers with logic as rewire master

Hi all, i've been using logic 8 for a while now and have finally settled down after learning lots of digital production theory, to sorting my studio setup and start producing for real.
My setup includes 1 24" iMac 2.56ghz with profire610 interface, 1 behringer bcf2000, 1 mpk61, 1 apc40 and I'm using logic 8 with reason 5 and live 8 rewired and have recently brought in the komplete 7, sylenth and max5 plug-ins. My aim is to assign the behringer to logic to control it's tracks in the mixer, the apc40 with ableton (obviously!) and the keyboard switching between all three daws but more importantly keeping the mpc pads for the kong drum designer in reason.
Am I right in thinking logics environment section can offer me a workable option to get complete routing control over the midi messaging between the controllers and the daws??
Have I explained myself right?
Any help is greatly appreciated and thanks in advance

and I forgot to mention I'd like to be able to send and recieve audio and midi between the 3 daws like using one to sequence another and say be able to export midi/audio to ableton and start it playing.
I also dj so I would ultimately prefer to be creating and compiling drum and synth loops and easily pass them to ableton whether in the studio or at a gig.

Disabeling MIDI-controllers in Mainstage

I´ve got a AKAI APC40 that I uses with Ableton Live, and it works great. However, when I use MainStage (not rewire) at the same time, every time I use one of the volume-faders on the APC40, EVERY volume fader on the current patch jumps to the value of this fader. Is there any way to disable the APC40 in mainstage? I only need it in Ableton Live, and would very much like it to leave Mainstage alone...
Message was edited by: pianoeirik

Yes there is. You will have to change the CC number of the volume-fader on the Akai from 7 to another CC number. Avoid 11 as that will change all your expression settings at the head of each channel strip.

Using MainStage with multiple MIDI inputs (two keyboards!)

Hi Guys,
I use two keyboards for my live gigs, and am thinking about moving all my sounds over to MainStage. Most of my recording uses Native Instruments and Logic's standard AU instruments, and then I have to find similar sounds on my Korg and Kurzweil for live...
My question is... can you use MainStage with two MIDI controllers? I'd obviously want to set up the presets in MainStage so that there are different instruments being controlled by each synth.
Would love any advice on whether this can be done, and a quick pointer as to how...
Thanks heaps in advance,
Mike

Easily done (I'm using two USB controllers on a gig now). Just set them up in Layout mode, then be sure to select the input of choice for your specific channel strip(s) in each patch. Or of course you can set things up at the set or concert level as well.

Using multiple MIDI-in sources - can you now select the incoming MIDI port?

Exciting to see that Logic Pro X has launched at last!
I'm hoping someone who has already had a chance to download it can report back on a specific feature.
In previous versions of Logic, the only way to record multiple MIDI sources (for example a V-Drums kit and a keyboard) at the same time has been to make sure they are on different MIDI channels, and then choose the "auto demix MIDI channels" option in preferences.
In this way, the MIDI data is separated by channel and recorded to separate tracks.
However, it only separates the channels when two or more tracks are armed for recording, and does not offer any option for selecting the specific MIDI port for incoming MIDI signals.
DAWs such as Cubase and ProTools have always had a drop-down menu for MIDI channels, where the MIDI port can be chosen. This way, you can easily separate your MIDI controllers for either jamming or recording, and they will only play virtual instruments on tracks which are selected to their specific channel. This applies for recording as well as just jamming or trying parts prior to recording.
I have several hardware synths in my studio and often record MIDI jams with multiple players, and on that basis moved back to Cubase last year. I have been hoping Logic would update this feature for a long, long time!
Can anyone who is using Logic Pro X already confirm whether MIDI tracks now have a port select option, or whether the old channel-based system and the clumsy "auto demix MIDI channels" method remains...?
Cheers,
Mike

Guys, this is really quite simple to accomplish in the midi environment, susprised you've been hunting for so long for the answers, here's a quick step by step:
1. Go into Midi Environment
2. Change the view in the Environment window to show Click & Ports
3. To make things easier, click the 'Input Notes' label, and delete the object. And also click the 'Input View' label, and delete that also, so you're left with a blank canvas. (These are handy tools when testing, just deleting them to make things clearer).
You should now be left with just the Sequencer Input (And midi click, but ignore that) - Basically anything that connects into this input goes through as an input into logic... So, all we have to do now is to split each device into seperate channels. This is simply done through the 'transform' objects.
4. Add 2x Transformer objects via the 'new' menu (Or however many external inputs you need).
5. Drag the connection from each device listed on the left, to it's own transformer as shown:
6. Then plug each transformer into the Sequencer input
7. Double click each Transformer object and simply FIX the midi channel to be whatever you desire, in this example i've picked channel 2 and channel 3
8. Now, just make sure the 'Auto demix by channel if multitrack record' option is selected in project settings, and you're good to go!
Now just simply select the channel number that corresponds to the devices you transformed, and when more than one track is armed for recording it will be split to how you would like. *Please take note, that the demix only kicks in when multitracking, i.e. more than one track is armed*
Now, this seems really long winded on a forum with screenshots etc. - But it's truly not, takes about 30 seconds, and once you've done it a few times makes sense. Plus going through an environment like this opens up possibilites such as splitting one midi keyboard into different zones which can transmit to different channels, so you can have bass on your left hand, and lead on the right for example. But the midi data will split to each track when recording.
Reply back if you get stuck, more than happy to help!

Piping dry audio into MainStage for mixing/auditioning fx

Hello, is there anyway to pipe multiple tracks of dry audio and midi (like the playback you would see in logic) into mainstage so I can mix and audition fx/plugins using playback instead of performing live stopping tweaking knobs and on and on? Should I just do this in Logic for each song, save the channel strips, and then load them up into mainstage when they are all finalized? Thanks ^^

I'm not familiar with the apogee duet but assuming that it has multiple audio outputs, you will be able to select the output channel for the metronome through its channel strip, just like any other channel. That will give you exactly what you want.
As for reliability, my experience is that MainStage 2 by itself has become quite reliable if you're just using internal synths and softsynths and you create your concerts from scratch rather than importing concerts from MainStage 1, this latter apparently being the cause of glitches for quite a few people.
However, if you want to use external MIDI devices, then I have found that MainStage2 causes eroneous notes to be generated from time to time. As long as you're not doing any MIDI output, you should be in great shape.

Multiple MIDI tracks to one instrument?

The plugin is Ultrabeat.
I like putting the kick onto one MIDI track
the snare into another MIDI track,
hats on another, etc....
Problem is, all of the MIDI tracks that route to the Ultrabeat
are the actual instrument track that has the plugin inserted onto it.
So MUTING one track mutes all the audio coming out of
the Ultrabeat Instrument track.
An attempt at a workaround is: create a Multi-instrument
in the Environment, and connect it to the Ultrabeat.
But then MUTING the MIDI tracks doesn't do anything.
The MIDI tracks play even when MUTED.
So I'm guessing Region Muting is the way we do it?
Selecting individual regions for muting and solo-ing
instead of muting and soloing the track ?
So..the MUTE button on a MIDI track is there for...NO REASON.
It's just a button that doesn't do anything.
Well.. this MIDI track has muted and non-muted regions on it.
I guess I'll need to remember which ones are muted and which
are not ?
This couldn't possibly have been something that was thought over
and planned.
Nobody in their right mind would design it this way on purpose.
A solution would be to allow MIDI tracks to be MUTED using the 'M' button

Are you talking about MIDI track on external MIDI?
your question seems to be related with Instrument tracks...
there many Muting possibilities in Logic...
I suggest to read the manual serch for "mute track"
As you can see in the manual there are tons of pages and paragraphs about MUTE function in Logic Pro... so I cannot explain all the way to MUTE a Midi or Audio
I can only say that Instruments tracks are not the same as External MIDI track device... *but Muting Instrument track is very similar as Audio and Midi mixed together functions*
'cause the Instruments channels strips are AUDIO CHANNELs STRIPs!
Maybe the following pictures can help
Try to change setting with the one shown below
CPU-savings is not the correct therm and maybe this is caused of misunderstanding...
this set allow you to individually mute the duplicate tracks...
_+The "M" button that you are metioned in your post will works as you need.+_
I'm trying to replay to the O.P question
multiple MIDI tracks to one instrument?
if you need to mute individually tracks of a single instrument the last pictures shows the best setting to achieve the result that you are looking for.
G

Logic Pro 9 and GarageBand '11 won't recognize MIDI controllers

Hi there,
I have two MIDI controllers that are not getting picked up by Logic or Garage Band and I'm unable to figure out why. I'm running Mac OS 10.9.4 (Mavericks) on a Mac Mini with a 250 GB SSD and 4 GB of RAM.
Setup 1 is a simple Acorn Masterkey 49 USB controller whose manufacturer claims needs no drivers, although it doesn't show up in my Audio/MIDI setup pane at all, no matter how many times I restart the computer and/or the controller in any combination. I can't use it with Logic or with Garage Band.
Setup 2 is a Digi002 Rack connected to the Mac Mini by Firewire and connected to an old-school Korg M1 as a MIDI controller. I can launch and hear the tracks I've made in the past with Logic, but now that Korg M1 is invisible even though the Core Audio Manager says my Digi002 Rack is connected and running. This setup has really never been able to speak with Garage Band, although I have been able to connect it successfully in the past.
I'm a newbie to this and don't know how to get under the hood to fine-tune MIDI set-ups within Logic or GarageBand. Is there something funky going on between Logic 9 and Mavericks, however? I'm beginning to wonder if that's the issue.
With thanks,
Dustin.

Hi Dustin,
Nice to see someone pose a complete question with all the details...
First thing to do would be to delete Logic's preferences and the control surface preferences. Although I don't think it's going to help. I'll post the method at the end of this post.
One of the problem with older MIDI devices is that Apple changed something in their MIDI spec and some older MIDI devices either don't work (not recognized) or if they are recognized don't work reliably. Another problem, depending on ho old your Mac Mini is, the newer machines have USB 3.0 ports and that poses another hurdle.
Here's two things to try for the Acorn.
Turn the computer off, unplug the Acorn's USB cable. Restart the MacMini and let it settle for a couple of minutes, open Audio-MIDI Setup... plug the Acorn in, see if there's and life.
Try a powered USB 2.0 USB Hub, a hub that has it's own power supply. If you don't have one maybe you can borrow one as it's only a -possible- solution.
The Problem with the M! and Digi002 may be related. Are you using the very latest drivers available for the 002? Again, this may be a MIDI compatibility problem, although I thought this was USB only, I suspect it's more of a Digi002 driver issue with Mavericks than anything else.
MIDI Out on the M1 to MIDI IN on the 002
Delete the Logic 9 preferences file and control surfaces file.
In the Finder, choose Go > Go to Folder from the menu.
Type ~/Library/Preferences in the "Go to the folder" field.
Press the Go button.
Remove the com.apple.logic.pro.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro User Manual for details on how to do this.
If you are having trouble with a control surface in Logic Pro. then delete the com.apple.logic.pro.cs file from the preferences folder.
Be sure to include the Tilde~ in the path name above, be sure and delete both files.

Multiple users logged into one server, each users printer has a different name, application needs ONE name to print to.

Multiple users logged into one server, each users printer has a different name, application needs ONE name to print to.
I'm NOT in any way a Terminal Services expert and I need help trying to get an application program working in a multi-user environment.
The issue is that the printer changes for every user that is logged in. The application needs to print NOT to the default printer, but to a "special" printer which is selected in the application... let's call it a label printer to simplify the explanation.
You have your default regular printer, easy for the application to find that one, and then you have a special printer that labels get printed onto. The application needs to know what printer is the label printer. So we allow the user to select that in the
application and the selection is stored in a config file in
C:\ProgramData\mfgr\prog\setting files
I don't have access to the application so I can't change how this works.
In the "regular" world, selecting the label printer driver to use should be per machine, NOT per user. When a new user logs into a machine, the physical printer doesn't go "poof" and a new printer suddenly appear. Same printer for all
users.
Yet in terminal services, the physical machine is "merged" with the virtual machine on the server. And there can be many users logged in at the same time. So each users real machine (and real printer) is injected into the "fake" terminal
services machine. The name of the printers is made unique for each user. So the printers DO go "poof" and change names depending on the user logged into terminal services.
So user "A" logs in and sets up the application to print to "LabelPrinterForUserA" (or whatever the name of the printer happens to be), that setting is stored in the ProgramData subfolder, and all is well. Later, user "B" logs
in, and when they print, the application tries to print to "LabelPrinterForUserA" which doesn't exist for user B or is only accessible by user A. If user B re-configures, that breaks it for user A.
SOLUTION 1: The way that /should/ work (in my mind) is that you define one "generic" printer in Terminal Services... call it "Virtual Label printer" and when the user wants to print to it, the print job gets re-directed back to whatever
physical printer is actually connected to their local workstation. There is a map of virtual printer to actual printer depending on the current user. The application is told once to print to "Virtual Label Printer" for all users.
SOLUTION 2: Or... there should be some way to make the ProgramData sub folders separate per user. E.g. when user "A" tries to access:
C:\ProgramData\mfgr\prog\setting files
they actually get
C:\UserData\UserA\AppData\mfgr\prog\setting files
and user "B" gets
C:\UserData\UserB\AppData\mfgr\prog\setting files
So the question I have is: Does either of those solutions exist hidden somewhere in the setup of terminal server? Or is there another way around this issue that I don't know?

I don't really have a "for sure" answer to this, but because people here can't seem to deal with a question that hasn't been answered I'll provide the best answer I did receive from ServerFault.com user Nathan:
I can feel your pain with using old software on terminal servers ...the solution I've come up with definitely won't scale as it requires some manual configuration, but I've gotten this method to work with our label printers (which require to be
printed to an LPT port...yep, that old).
Share your USB-connected printers to the network on each machine. Then, have the user log in on aunique session for each of them
(a TS account cannot be shared among computers for this to work) and install a network printer pointing to the USB one they shared. Try to use a DNS name to account for possible DHCP movements.
After, it should work. Each user can do this since display names can be identical as long as the ports are different (which they are).
This was clarified by the following series of comments:
I think you are on to something here, and I originally advised the admin to do this. The problem he ran into is that it setup the printer names in the TS as "printer on usersworkstation"
and he could not rename it except to change the "printer" to whatever. E.g. the "on userworkstation" remained. I believe there is another way of installing the printer which avoids this, but I can't find it. Ages ago, one used to do NET
USE LPT2 \\computer\printer password /USER:domain\user /PERSISTENT:YES and then tell the driver to print to LPT2 –  James
Newton Mar
17 at 16:21
@JamesNewton That's actually the exact method we used. The way around the "network printer" part is to install it as local printer and map it to a TCP/IP port that way. –  Nathan
C Mar
17 at 16:28
You mean in the case where the printers are TCP/IP connected and not local USB / LPT to the users workstation? That makes sense. Wonder if this will work for USB connected printers... –  James
NewtonMar
17 at 16:35
@JamesNewton You'd share the local printer on the client's PC then on the server connect via TCP/IP to it. You'd need static addresses or use DNS names if DHCP, though. –  Nathan
C Mar
17 at 16:51
Ah. Yes. I see. Looks like the LPT thing should work even with a USB connected printer:superuser.com/questions/182655/… –  James
Newton Mar
17 at 17:09

Connecting multiple MIDI Controllers into MainStage

Similar Messages

Maybe you are looking for