Vocoder Problems (Mainstage 2)

Hi everyone - I'm just getting into MIDI music cretion and purchased Mainstage to help accomplish this in a live setting. I'm having problems getting the Vocoder to work though. I've read through some of the posts in this forum and tried looking at articles online, but I'm afraid I'm too much of a noob to even understand that. I was wondering if anyone could walk me through how to get it working like in this video (http://www.youtube.com/watch?v=kmRSyVrimL0) that would super helpful. Thanks in advance!

Can you give me some idea where your understanding breaks down? I could repeat parts of the manual, but that may not be helpful.

Similar Messages

Mainstage 3 vocoder

Help,
I was using Vocoder on Mainstage 3 and now its not working. I have midi signal and side chain set to correct input.
I hear my voice when I click on interfase out put so signal is there. When I hit MIDI keyboard I hear noise coming out from speaker.
When I change to Synth on Signal I do hear synthe sound so Channel assintment is correct. It's just not getting Vocoder.
Thank you

masterbm,
Vocoder is not a technique I use, but you could try a couple of things to attenuate the feedback. The first is not to point you mic to you PA/Monitor system. The second is to use a pop shield. If you get feedback than you and your band are playing to loud for the volume of PA/Monitor mix where you could hear the vocoder.
The gate might help but the threshold and release should be adjust very high and your speak might not be ilegible.
But test with the helps I gave and should be better.
and its Bruno Filipe not Felipe
masterbm if this helped you please give me This helped me
good luck

Graphic problems/errors with Mainstage 3 and MBP (15'' 2011)

Hi,
I bought Mainstage 3 for my MBP (15'' 2011).
When i click con "perform" i get graphic errors.
I have the same issue with the old Mainstage version since Mountain Lion.
Also a fresh installation didn't help.
I think i'm not the only one with this issue!
I don't know how to report a bug?
Perhaps someone can help me.
(and I'm probably not the only one (see feedback in Apple Store) If you also have this problem, please add a comment with your configuration (Hardware, Software))
/forgotten ebi
So, here an example how it looks like when i click on "perform":

Same configuration,same problem. BUT I found a workaround.
Mainstage has this error with the AMD video card and/or a second monitor connected.
With a little app (http://gfx.io) it's possible to really force the MBPro to use the Intel Graphics card.
This will work only with the internal screen, not with a second screen connected.
And sometimes you need to restart, to really make the Intel video card free.
This works fine...In the meantime of a fix.

I have a serious (and bizarre!) issue with my novation impulse (Although i've tried it with two other keyboards and i still have the same problem) and its compatibility with mainstage 3

i have a serious (and bizarre!) issue with my novation impulse (Although i've tried it with two other keyboards and i still have the same problem) and its compatibility with mainstage 3.
the problem is best explained on the following one - page thread:
https://discussions.apple.com/thread/3951518?start=0&tstart=0
(Clearly i'm not alone in this problem, although i think i figured out what's going wrong a little more than he did...read on!)
his solution, to put mainstage in jump mode, is very unsatisfactory to me, as it bounces all of a sudden to drastically different settings.
basically, my analysis is that my controller is NOT receiving MIDI date from mainstage. in other words, mainstage knows what my controller is doing, but my controller doens't know what mainstage is doing.
let's say i turn the knob all the way to the right ... 127...and the virtual fader goes to the right like it's supposed to.
now...next...let's say i change to a different patch, where that same VIRTUAL fader is not at the max clockwise position..maybe it's only at 1pm. now when i turn the physical knob to the RIGHT, the midi data is still at 127 on the controller! it didn't "reset" to sync up with the new level (say 80 or so) setting on the new patch. so i can't increase that new setting of 80 by continuing to turn the knob to the right. i have to turn it all the way to zero,...and then continue PAST zero until the controller thinks that IT is at 0...at that point the controller and mainstage are in agreement, and things work fine....so bascially, the keyboard thinks the level is at max...but mainstage thinks the level is at 1pm.
i am using Logic 9, and i have a macbook pro 2.9 Ghz I7 with 8 gigs of memory and OS X 10.8.4

Hi Josh,
Thanks for taking the time to contact us here a Novation for technical support. Lets continue to correspond via email so we can get your issue resolved.
Thanks.
Mike Towns

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.

Has anyone had a problem using Mainstage 2 and Logic 9 with PreSonus fire studio Mobile?

I Still can't get Mainstage and Logic to play well with my setup. I'm using a Mac Pro 2 GHz Intel Core i7 with 4 GB ram and Logic 9.1.6 and Mainstage2. I have a PreSonus Firestudio Mobile and M-Audio Midisport midi interfaces. The only Midisport that works consistently is a MisiSport 2X2 sith a thru/merge switch set to merge. I am playing all of this with a Roland A-90 keyboard. Logic sometimes starts, but the audio interface doesn't work. Mainstage crashes on start-up. Can anyone help?
Thanks,
Bob

Hi
There have been several reported issues on this forum about problems a) with Roland controllers (Sending MIDI Clock and 'All Notes Off' ???), and b) MIDSport interfaces
https://discussions.apple.com/message/17138809#17138809
https://discussions.apple.com/message/17011191#17011191
I suggest that you try a 'scientific' process of elimination:
Disconnect all external hardware, and try MS
Connect the hardware singly, one at a time, to determine which is causing the problem
CCT

I'm having a problem with Ultrabeat's sequencer in Mainstage

In Mainstage, I've set up an Ultrabeat instance on the concert level so that I can use it as a metronome for the whole project. (I like to be able to customize the sounds, add subdivisions, make it louder than the default metronome sound, etc.)
However, I'm having a problem. Sometimes, when I try to use it, it doesn't work. Here's what I'm doing to recreate the problem:
In ultrabeat, I create the pattern in the step sequencer, and the sound I want. I have a very simple woodblock sound, and I set the sequence to be only 4 boxes long in Ultrabeat. The sequencer in UB is "on". I created a button on the workspace in Mainstage, and mapped it to UB's "sequencer Play/Stop".
1. When I start the squencer, it runs - i can see the curse in UB moving to the right and repeating - but no sound come through the channel strip
2. When I click the keys on the left side of UB, sound DOES come through the channel strip.
So in essence, UB doesn't want to send sound to Mainstage by using its sequencer.
Has anyone faced anything similar? any ideas on how to fix this? I've done it successfully before, but sometimes it just doesn't work.
thanks,
Keith

For the sake of clarity and to save people time, Todd is asking about the behaviour of the Patch tool when using it to repair the area next to the young lad's head. Todd gets a blurred dark tone pretty much regardless of the options he uses.
IMO that's what I would expect to happen because of the close proximity of the other image elements i.e. the lad's neck and the strong lines of his shirt. I would not choose to use the Patch tool in this situation. Content Aware Fill makes a better stab at it.

M-Audio M-Track problem with Mainstage 3.0.2

I recently purchased an M-Audio M-Track and wanted to use this to input guitar tracks into Mainstage 3. However, when I try, it does not recognize any inputs. The M-Track is working fine, because I can use it without any issue with Mainstage 2 and it also works fine with Ignite. I have seen other entries in the forum for with the same issue for the Fast Track. For the Fast Track, it appears that the problem was fixed with new drivers. However, there are no drivers for the M-Track. Has anyone been successful in getting 3.0.2 to recognize inputs for the M-Track?

Hello, crosbygs.
Thank you for visiting Apple Support Communities.
Here are a couple resources I would recommend going through for this issue.
MainStage 3: MIDI devices overview
http://support.apple.com/kb/PH13519
MainStage 3: Audio preferences
http://support.apple.com/kb/PH13675
Cheers,
Jason H.

Mainstage Cocoa View Problem

Hello,
I am just exploring mainstage and having the following problem:
When you load a third party plug-in, normaly a cocoa view opens where you can control the plug-in. This works fine for all my plug-ins, except for Omnisphere. When I open Omnisphere I get some kind of automatic generated view instead of the Omnisphere view. Of course this doesn't work at all. In other hosts Omnisphere loads normaly. Please, let me know if you know a solutioin, thanks.
Here a picture of the view I get and the view I want:
I get: instead of what I want:

I got finally the solution, thanks to the help of Spectrasonics. Their helpdesk is really good! They really digged into the problem and found the answer. Here is what they say:
"I've seen reports of Logic or Mainstage occasionally having problems displaying Cocoa-based plugin GUIs. Usually deleting the Logic/Mainstage preferences (the com.apple.logic and com.apple.mainstage files in the preferences folder) fixes it. "
And this worked. In my case I had to delete "com.apple.mainstage.plist" since I had only Mainstage installed. You can find it in the user/Library/Preferences folder.
Again special thinks to Spectrasonics (Especially Jonathan) and their terrific helpdesk!

Problem with midi input in Mainstage

Hi all,
I have a keyboard connected to my mac via USB midi interface.
When I'm trying to play midi instruments in Garage Band - it works very well, no significant latency and no other problems.
But in Mainstage the situation with the midi input is different. When I press a key on my keyboard, it plays the sound, then stops responding to other midi commands for about 2-3 seconds. And then after I press another key, it plays it, and stops responding again.
The "CPU" and "Memory" indicators at the top show a low load.
All in all, it's just impossible to play a midi instrument in Mainstage.
As the midi interface is working correctly in GarageBand and doesn't work well in Mainstage, I suspect that it's a Mainstage's software problem. But I haven't found anything like that on the Internet. Any ideas?
Devices: Macbook Pro 13" (2011), M-Audio MidiSport Uno...
Thanks!

I can input Chinese in Firefox, but there are
problems with the display of characters in input
fields for searches, etc.
Can you provide a specific example of a particular search box (url) and exactly what the "problem" is (TC or SC, characters involved, etc)? I would like to try and duplicate it. Perhaps the encoding in View > Text Encoding needs to be adjusted for that page for some reason (though normally that should affect all browsers).
Since Apple has nothing to do with FireFox, you might want to report the issue to the people responsible for that program (mozilla.org I think), since it may be a bug they can fix.

Problem playing with 2 axioms 49 2nd generation with MainStage

I play in a band. Me and another member are using the same controller attached to MainStage: Axiom 49 2nd generation.
At first we configured the layout mode with 2 keyboards and two gruop of percussion pads. Then we assign each keyboard to both axiom controlllers and we named them different. then we did the same with the percussion pads, but in layout mode we couldn't find a way to name them.
With the keyboard we found mainstage confused them a lot, and each time we started MainStage we had to reassing all the layout again. So we changed the midi channels each axiom was using: one of them to midi channel 1, the other to channel 2. No problem after that, the only thing is that we have to turn both on after starting the software.
But the pads.....one of them never worked. In editing mode, we created two channels to play the two group of pads simultaneously (as we do with the keyboards). In each "midi in" tab, we tried to asign one of the pads. The pop-up menu give us the chance to assign mine. It was shown as: "axiom USB In Axiom 49 (10)".
But as we went to the other channel to assign my mate's group of pads, we couldn't find it..in the pop-up menu these are the only options:
RAKEL (my keyboard)
axiom USB In Axiom 49 (1) 2 (my keyboard again)
axiom USB In Axiom 49 (10) (my pads)
JONAY (the other keyboard)
multitimbric
We tried with the multitimbric option but when I click the 11 midi channel in the pop-up menu, it shows again this four options.
RAKEL (my keyboard)
axiom USB In Axiom 49 (1) 2 (my keyboard again)
axiom USB In Axiom 49 (10) (my pads)
JONAY (the other keyboard)
We tried to change midi channels straight with the axiom (the same we did with the keyboards): for me the pads were still emiting to midi channel 10 and for him we changed the group of pads to midi channel 11 (didn't work), and we tried again changing the channel to 9. Nothing works, it just doesn't show in the pop-up menu, although they are assing perfectly in the layout mode and in the edit mode the notes we play with pads are shown in the input midi screen....
Could anyone help us?...is driving us mad and there's not too much information at the user manual or forums.
Thanks in advance! I really appreciate your attention

Open the Overdrive Help tab and search on "transfer" or "iTunes". You'll get selections that explain the WMA files work fine and will walk you through it. Among other things it will tell you:
"If you plan to transfer OverDrive WMA Audiobooks, OverDrive WMA Music, and/or OverDrive WMV Video to a portable device, you may want to verify that the portable device supports content delivered in the DRM-protected Windows Media format... many OverDrive WMA Audiobooks and OverDrive WMA Music titles can be transferred to Apple devices (where permitted by publisher)."
You must do a security update of Windows Media Player (even though you won't be using it) using Internet Explorer at http://drmlicense.one.microsoft.com/indivsite (the Windows Media Player Security Update is also in the Overdrive Tools menu, but I could not get it update). Once updated, with the iPod or other mobile device connected to your computer and iTunes open, go to the Summary pane for your iPod or other device in iTunes and click the "Manually manage music and videos" box.
Then go to Overdive, select the book, music or video and click the Transfer button. Select some or all the chapters you want to transfer. It will find the mobile device and begin.

Mainstage saving problems with nexus plugin

I just bought a new macbook pro, 3.06 Ghz 4GB ram, mostly to use it at live performances.
I'm using Mainstage 2 with the softwaresynths from logic and also Nexus (Refx)
The problem is that when I've added just a few nexus patches saving takes forever. On a set with about 20 patches (only a few of them are nexus patche) saving might take 3 minutes. Also moving patches up and down in the list takes a long time.
Also every now and then everything hangs for maybe 15 secs.
Need help, someone who has the same problem?
Thanks,
Arvid

Here are 2 screenshots illustrating the alignment issue in QTX. The first image is the movie with captions in QT 7 (everything looks perfect):
http://www.personal.psu.edu/pzb4/QT7.png
Here is the same movie opened in QT X. I've captured a bit more below and to the right so that you can see my Desktop to show that the movie is displaying off center up and to the left:
http://www.personal.psu.edu/pzb4/QTX.png
Notice that the video seems to overlap the dark gray bar at the top of the movie window on the right of the gray bar at the top.
Message was edited by: Patrick Besong

Problem with external MIDI routing has to be MainStage 2 bug

I posted a bug the other day where I was getting occasional bogus MIDI note events in one external synth while playing a keyboard that was (supposed to be only) sending MIDI data to a different external synth.
I have now performed two experiments that would seem to indicate that the problem must be caused by MainStage 2 and not by CoreMIDI or by MOTU drivers/external MIDI interfaces.
Experiment 1:
I created a new Digital Performer sequence, enabled multi-input mode and routed one keyboard controller to one external synth and another keyboard controller to another external synth, essentially reproducing the MainStage 2 patch. Played both keyboards together for some time with no problems whatsoever. (In MainStage 2, I'd get a glitch pretty quickly)
Experiment 2: (to eliminate the possibility that Digital Performer (a MOTU product itself) wasn't doing something special)
I used Max/MSP and created two midiin/midiout connections, one representing the first keyboard controller and external synth, the second representing the second keyboard controller and external synth respectively (duh). Again, I played both keyboards for a while and everything worked perfectly, no glitches.
I have reported this to Apple several times via their feedback but have heard NOTHING back from them.
Original bug posting
(http://discussions.apple.com/thread.jspa?threadID=2137282&tstart=0)

If I understand you correctly, I think I experienced a similar problem. However, in my case, I don't have two separate midi input devices, but rather one; and two separate external devices I am wanting to control with midi.
Brief background: I use an EWI to play various softsynths & now external synths via MS2. I also route the audio from my EWI into MS2 for additional processing and I use an external effects processor (Eventide Eclipse) for additional processing and sound manipulation. I send program changes with my EWI to change patches using MS2. My EWI transmits only on midi channel 1, which MS2 is set to receive on. Also, my Eclipse is set to receive midi data on channel 5 (a method I used to keep things separate in my all hardware rig when MOTU MTP AV was my switching device).
Initially, I thought I could just have my EWI send a program change message on channel 1, and then MS2 would send a program change message to the Eclipse on channel 5, all from the same MS2 keyboard object. It worked, but with one small glitch ... after the program change happened, and I started playing my EWI, the Eclipse began receiving my midi note information which in turn caused the Eclipse to be confused and start trying to change patches, etc. I checked the keyboard object which was not supposed to transmit on channel 1 to anything external, but I could not figure out how to set it up. Note: none of my devices are set to OMNI because I learned a long time ago, that I want to control routing and specific channels ensure their separation ... or supposed to anyway.
What I ended up doing was to create another midi object (this time the little spherical thing, not the keyboard), and assigned it to transmit on midi channel 5 and not receive on any channel. This turned out to be the solution / work around for this situation.
Another problem I am having with midi control when using MS2 as a go-between, is an issue with pitch bend information getting messed up as its sent to my external synth (Yamaha VL70m). For some reason, playing the VL70m by way of MS2, causes my EWI pitch-bend data to force the VL70m pitch-bend in the permanent down position making all notes flat. My solution in this case was to set up a direct link with MidiPipe, from my EWI to my VL70m and filter out any program changes so that I can use the MS2 to send a patch change to it, but use my EWI to play it directly. It seems to work well, and my pitch-bend is back to normal, but I am not certain (and don't know how to test) if the VL70m is now getting duplicate note on/off information with the potential of a minuscule delay from MS2 being in the path as opposed to playing direct from my EWI. It seems unnoticeable to my ears, but it's in the back of my mind.
Anyway, these are some of my midi episodes and I think it's pretty clear that Apple needs to quickly address some issues about midi handling and MS2.
Hope this helps ... and maybe we can come up with some more creative ways to deal with these "undocumented features" (to borrow a saying from the Windows world).

Problem with Amplitube Metal and Mainstage

Hi,
i'm trying to use Amplitube Metal on Mainstage. but when Mainstage checks at the start the audio units. He says that Amplitube Metal: validation failed. When ignore it, i'm able to use that, but without the ability to control it with the Mainstage-Controller, like Foot-Controller or something like that.
Do anyone have the same problem ?
Sorry für my bad englisch

I just tried pasting my crash report. It seems like it is too long to post?

Any problem between mainstage 2.2.2 an yosemite?

Some have had problems with mainstage 2.2.2 and yosemite ?.
I'm afraid to update

I have made an ssd upgrade on my macbook pro and new install of yosemite,
MainStage 2 opens but I couldn't download the additional content.
MainStage 2 is 32 bit, and I think they updated some loops and instruments.

Vocoder Problems (Mainstage 2)

Similar Messages

Maybe you are looking for