Mainstage volume patches

Hello,
Currently working with mainstage and not very expert, my problem consists in finding the way to have an indepent volume on each patch, so that I
can quickly adjust the volume of the entire patch without moving
all single channel strip's faders in the patch,and without altering the output level of the other patches.
The output 1-2 track in the patch is a "global" track, it changes for all
the patches.
Anyone can help me??
Thanks and happynewyear
Leandro

Hello, thanks for your answers!.
In fact , I've patches with up to 8 channel strips, and I need to change the patches very quickly in the same song. So my goal is to pre-adjust easily the level of all my patches
in order that when I change a patch (while playing), ther will be the same volume between a patch and the other.Of course I can "correct" it after the patch-change with a volume pedal, but, the first notes will be maybe too loud or not enough.
As sugested , I tried to send all channel strips into a bus, in each patch, so that I can "adjust" easily the level of the whole patch's multi-channel strip ensemble.
Leandro

Similar Messages

Is there a way to import Mainstage 2 patches into Mainstage 3?

Currently trying to upgrade from Mainstage 2 to Mainstage 3 on my new MBA. Haven't downloaded Omnisphere yet and have a gig coming up. Was wondering if it was possible to take built-in patches from Mainstage 2 and move them to Mainstage 3. (Most specifically Tranquil Horizon, an ambient pad)
Thanks for the help.

Drag and drop open via the gear menu, open existing concerts...

Mainstage Guitar Patches

Hi,
Very new to the world of Mac, but have converted to the new faith. The purpose for doing is Logic Pro / Mainstage and obviously seeing the light. Now having scanned 119 pages of Mainstage Q&A I am unable to find an answer to my question. Where can I find / download guitar patches to use on Mainstage. I'm looking ideally for a Metallica sound. Hope someone can help. Thanks
Also, I'm using a Focusrite 24DSp Audio interface, but the input levels displayed in Mainstage barely move off min, even when cranked up on the interface. Any ideas? Cheers

Welcome, brother.
You may be able to find patches easier by looking for Logic Pro settings for the specific plug-in you want to use (such as Amp Designer and Pedalboard; the two main plug-ins you will want to use to customize guitar sounds). Logic Pro and MainStage share plug-ins and settings for these plug-ins, and there are a lot more Logic Pro users out there. Also, I recommend learning to use these two plug-ins without relying on others for settings, because you will learn to customize sounds based on your own guitar, style, and amp. Start out using the settings bundled with the plug-ins and start customizing the ones that get you closest to where you want to be. It will be worth the effort.
Haven't used the Focusrite. Look to see if it provides level out controls, and make sure your level in gain is set properly. If so, it really should provide enough ample oomph for MS/Logic. If still a problem, add a Gain plug-in as your first plug-in and crank the beejeezus out of it.

Why aren't patch changes part of the AU spec?

I'm working with a Novation Remote25Sl and the new Automap 3 software with Logic. So far, it's kind of working. But kind of not... And it's brought up a question that's nagged me for a while now.
Why is something as simple as "+/- patch" not a fundamental part of the AU instrument spec? I mean, shouldn't it be dang simple to map a midi controller so that when you're playing MiniMonsta, or the impOSCAR or FM8, etc, you can just hit buttons to go back and forth through the patches without having to grab your mouse?
We're talking 1980's basic Midi functionality here folks... Anybody out there part of the AU developer community who'd care to comment? I swear, it would make software instruments so much more FUN if they could improve the "no mouse" experience.
Um, please?
Any workarounds Im missing? Yes, I know Logic's built in synths have key commands that be assigned to next/previous preset. I use'em all the time. But that's no good for 3rd party AU's. And as I say, wouldn't this be something you'd expect as part of the basic parameters for any instrument? Or do you think they deliberately left it out to discourage people from changing patches in the middle of a track, causing unpredictable CPU spikes, etc?
Hmmmmm

While I agree with you (the level of patch handling, although we have massive resources now, is in many other ways inferior to what we had when we were all using MIDI sequencers and hardware instruments) - speaking to instrument developers, realtime patch changing is generally regarded as a headache.
This is why the favoured approach is to have multiple instruments loaded (eg how Mainstage does patches) and switch between instruments, rather than having one instrument switch patches.
Now, for most of my instruments, I set them up with Logic settings, specifically so I can have keyboard/MIDI commands to switch patches - but there some instruments that can't be handled like this.
I wish some DAW developer really took this whole patch/instrument management area for plugins and developed a top-modern, elegant and comprehensive solution.
Ideally, in Logic please!

I made a MS patch-changer selecting ANY patch FROM MY KEYBOARD'S KEYS!

Love the Nord Electro 3, hate the sequential up-down button for patch changes, especially with up to 20 per song. Almost decided to sell it and go back to the Nord Stage I had before, sacrificing sound quality for rapid and flexible patch changing abilities, but I just made a MainStage-based patch changer for the Nord Electro 3 that can select any Nord patch from the Nord's keyboard. So Cool! Chances are I keep this beloved Nord now!!!
I've recieved so much help that I'm trying to be a giver here ....though maybe this is rookie stuff to the people here, it was a new level for me, so maybe it'll help someone....
It took a long time to figure out, but I decided finally not to worry about changing various (not sequential) MainStage patches from keyboard keys because I couldn't find a way, but just to make a way to choose NE patches WITH THE Nord's KEYS SENDING WHATEVER PROGRAM CHANGES needed to select a patch no matter where it is in the Nord -- this way I could choose any patch easily from the Nord keyboard keys instead of sequentially stepping through patches with two mapped up/down MS keys, or with the Mac's arrows, or hunting for a computer keyboard button.
I learned the bottom 8 keys of the Nord into 8 buttons in MS, then for each button mapped it to Send to All --> Nord Electro (destination) --> Program Change. Then I "mapped parameter" to whatever Program change number would select the patch where it's sitting in the Nord's patch banks. If it was PC 9 then the values would be 9 and 9. Pressing that keyboard key (F#0 in my case) while playing and having MS in Perform Mode would then switch my Nord to patch 5-B in the Electro, which is the Nord's PC9 location. It was a little tricky to figure out that I best go into the parameter graph and change the top and bottom numbers to 9, in this case. For some reason it defaults to 8 bottom and 9 top if choosing PC 9 outside the graph. It took some mousing sometime to get them the same.
Note: NO patch changer in layout, NO channel strips, JUST the keyboard and the 8 buttons. Also for some odd reason it does NOT work in Edit mode, MS has to be in Perform or Full Screen mode.
Granted, the number of patches you can choose is limited to the number of keyboard keys you want to reserve for this purpose. If I can give up more keys I might do 8 more to get 16 program-changing keys.
Anyway it's great to be able to choose whatever sound I want in the Electro 3 instantly without having to madly push an up/down button on the rig -- organ, Shodes, Mellotron, choir sample, no matter where it happens to reside in the Nord's banks. Cool!
What I couldn't figure out but might do next is to see if there's a way to use this tool, but also choose a MainStage synth patch or three from Program-changing keys without disrupting the works. I tried for a long time but couldn't find a mapping that would send something that would end up giving me a particular PC-mapoped Nord+MainStage layer -- that's probably to much. So I might default to also having a field with a patch changer window, a couple keyboard keys mapped to up/down, and just choosing up or down instead of a particular patch number or name. Dunno.
I can post or e-mail the concert if it helps anyone.
Neil

You may have to call back and tell the answering party you have an
existing open case involving a repair; tell them the 'case number' or
'incident number' assigned your initial repair by AppleCare, and say
if there is a problem, you've already paid; and 'please connect me to
the supervisor.'
A logic board issue could certainly be the cause of bizarre keyboard errors.

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).

Mainstage Mixing

I have searched but still no avail.
I want to start taking our electronic music on the road and play live, we use logic and use the plug ins a lot so mainstage is a good choice.
We cant play EVERYTHING live so ideally we will have to keyboards and a guitar.
What i want to know is is there an interface i need that means i can control mainstage, ideally like a mixer, so i can control the backing tracks as well as the keyboards externally.
For example, i would like a seperate track to control bass, drums, ambient noise etc. Almost like a Akai controller for live with those faders on the bottom.
Or how would anyone else play live for electronic music with mainstage with only 2 keyboards?
Glenn

I can speak for the Behringer, haven't tried the Evolution The bcf2000 is a bit klunky and challenging to learn, but there is plenty of online support, and the motorized faders sync up nicely with MainStage. So, yes you can control all the volumes with the faders, plus anything else you want with the rotary controls. I don't think the Evolution has motorized faders, so I would go with the Behringer so the faders move to adjust to your current MainStage volume settings. Less thrash!
If you keyboard is MIDI in/out only, you will need to be using a MIDI interface connected to your Mac, like a MIDISport or something. The Behringer will connect via USB. The MainStage doc explains how to set up a virtual instrument, played via your physical keyboard. To get your backing tracks synced up, there have been some other recent threads about this, so you may want to read those. You can also run your guitar through MainStage, but would need an audio interface. Some interfaces combine audio and MIDI, though, so one interface could do double duty.

How do I change Guitar rig patches when it is a plug in in main stage

I'm using Guitar Rig (v.3.2.1) inside Mainstage (v.1.0.2). I'm trying to use a midi foot controller (Yamaha MFC10) to change the patches. Pressing the Yamaha foot pedal sends program change information into main stage, but it changes the patches at the top level of main stage. Also, main stage responds to program change on all midi channels and I don't see a way to limit it to just one. What I'm hoping to do is have the MainStage patches respond to one midi channel, and the Guitar rig patches respond to another. Can this be done??

Hey Burr,
Okay, I was able to get Mainstage 1 and Guitar Rig 3 talking okay. I'll outline here how I got the two to talk but I probably need a bit more info to address your exact need(s). I've also re-read your posts and I'll take a stab at what I think you might need to do to get set up a little better. The caveat here is that I'm not 100% clear on what you want to do, so apologies if I make assumptions that are a little off
Since it sounds like you want to do MIDI patches and Guitar Rig patches and you're trying to separate the two, then let's look at that, we can always look at combined patches later.
So what it kinda sounds like, is that you're thinking about Guitar Rig at the concert level, the best thing is for you to think about Guitar Rig at the patch level. What that allows you to do is to create two different sets within the concert, one for your MIDI patches, and the other for Guitar Rig patches.
That way, you can navigate to whatever you want (MIDI patch or Guitar Rig patch) and not worry about the MIDI channel separation issue. When you were saying the Yamaha MFC10 was sending program changes for patches at the top level, instead, what you want to think about is using CC's (not PC's) for set and patch navigation and PC's only for direct access to a specific patch.
So, first program your MFC10 to send 4 different CC's for Mainstage navigation (Set Up, Set Down, Patch Up, Patch Down) e.g. you could use switches 7,8,9,0. Then go into Mainstage at the layout level and map the Set Up, Down and Patch Up, Down icon/switches using the MIDI Learn function. Go into Edit mode and test the navigation.
Next, create two different sets MIDI and Guitar Rig.
Then create your MIDI patches in the MIDI set as you normally would.
Create your Guitar Rig patches within the Guitar Rig set. Create separate Guitar Rig patches using the MFX stereo version of the AU plug in for GR. When the Guitar Rig plug-in window opens, select/edit the patch within Guitar Rig that you want to use. That specific Guitar Rig patch will now be saved in your Mainstage patch. Set up a separate Mainstage patch using a Guitar Rig patch for each of your different patches/songs.
Now you can go into perform/full screen mode to navigate to each set or patch using switches 7,8,9,0 (if that's what you used) of your MFC10 and that will call up you patch.
Additionally, if you want to call up a specific patch from MFC10, then program one of your MFC10 switches to send a specific Program Change. Then click on the patch in Mainstage, the Patch Inspector window will open up - now assign that same Program Change number there. Your MFC10 will now call up that specific patch when you press on the switch.
Now, the next thing is...if you then want to modify or express something WITHIN a Guitar Rig patch. Then you first have to program your MFC10 to set up/send let's say...5 different CC's so let's use 1-5 of your MFC10. We might want to turn on/off different effects for example, or boost a gain, or whatever. In this example, we'll choose turning an effect on/off.
So program your MFC10, then go into layout mode in Mainstage and assign the stompbox on/off switch by clicking on it, using MIDI Learn, and then pressing your footswitch to learn the CC.
Go into Edit mode, select your Mainstage Guitar Rig patch, then click the stomp button(s) you just programmed. The parameter mapping section then opens up at the bottom. Choose your Mainstage patch name (appears right under "Parameter Mapping".
Then the next column (to the right) populates, choose "Guitar Rig 3 MFX", the next column then populates with all the Guitar Rig 3 parameters, select whichever GR3 item you want to control and do the parameter mapping. In my test I chose Skreemer On/Off because I mapped my FCB1010 and Mainstage Stompbox to switch that effect.
Anyway, if everything was done ok then when you press switch 1 on your MFC10 it will turn the effect in Guitar Rig 3 on and off through Mainstage.
So now knowing all that, you should be able to map Mainstage and GR to do what you want by just using the same principles.
Sorry for the long explanation but it's the only way to give you the details...I hope I got what you wanted to do after all that...phew
Give it a go and let me know if you have any questions.
J.

Axium 61 + Behringer FCB1010 Midi Foot Controller

I'm thinking of using a Behringer FCB1010 Midi Foot Controller with my Axium 61 through Mainstage. I'm hoping to control volume, expression, and patch changes with the foot controller. Has anyone had any luck with a combination like this? Any suggestions? Also, is it better to run a keyboard through the PA or to buy a keyboard amp?
Thanks!

I'm using very similar setup with Oxygen 49 + FCB1010 and it works a treat. I can't recommend it highly enough. Also strongly recommend UNO firmware for FCB1010, adding "stompbox mode" amongst other things. I have control over volume, patch changes and mainstage fx pedalboard via FCB1010 and simultaneous parameter control via faders, knobs & buttons on Oxygen. Faders double as drawbars for my hammond sound.
I'm using a neat little edirol firewire card with 4 analog outs & 2 ins. Bass & mic go into inputs. Both are processed and amped in mainstage. Keys and bass both go to PA from outputs 1 + 2. Vocals go to PA from output 3. All go to my monitor (behringer powered speaker) from output 4.
Oxygen is hooked up to a bass sound, while all other voices are played with M Audio 88 note. I play all the time in several bands and am delighted with this set up

After reboot cluster node went into maintanance mode (CONTROL-D)

Hi there!
I have configured 2 node cluster on 2 x SUN Enterprise 220R and StoreEdge D1000.
Each time when rebooted any of the cluster nodes i get the following error during boot up:
The / file system (/dev/rdsk/c0t1d0s0) is being checked.
/dev/rdsk/c0t1d0s0: UNREF DIR I=35540 OWNER=root MODE=40755
/dev/rdsk/c0t1d0s0: SIZE=512 MTIME=Jun 5 15:02 2006 (CLEARED)
/dev/rdsk/c0t1d0s0: UNREF FILE I=1192311 OWNER=root MODE=100600
/dev/rdsk/c0t1d0s0: SIZE=96 MTIME=Jun 5 13:23 2006 (RECONNECTED)
/dev/rdsk/c0t1d0s0: LINK COUNT FILE I=1192311 OWNER=root MODE=100600
/dev/rdsk/c0t1d0s0: SIZE=96 MTIME=Jun 5 13:23 2006 COUNT 0 SHOULD BE 1
/dev/rdsk/c0t1d0s0: LINK COUNT INCREASING
/dev/rdsk/c0t1d0s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
In maintanance mode i do:
# fsck -y -F ufs /dev/rdsk/c0t1d0s0
and it managed to correct the problem ... but problem occured again after each reboot on each cluster node!
I have installed Sun CLuster 3.1 on Solaris 9 SPARC
How can i get rid of it?
Any ideas?
Brgds,
Sergej

Hi i get this:
112941-09 SunOS 5.9: sysidnet Utility Patch
116755-01 SunOS 5.9: usr/snadm/lib/libadmutil.so.2 Patch
113434-30 SunOS 5.9: /usr/snadm/lib Library and Differential Flash Patch
112951-13 SunOS 5.9: patchadd and patchrm Patch
114711-03 SunOS 5.9: usr/sadm/lib/diskmgr/VDiskMgr.jar Patch
118064-04 SunOS 5.9: Admin Install Project Manager Client Patch
113742-01 SunOS 5.9: smcpreconfig.sh Patch
113813-02 SunOS 5.9: Gnome Integration Patch
114501-01 SunOS 5.9: drmproviders.jar Patch
112943-09 SunOS 5.9: Volume Management Patch
113799-01 SunOS 5.9: solregis Patch
115697-02 SunOS 5.9: mtmalloc lib Patch
113029-06 SunOS 5.9: libaio.so.1 librt.so.1 and abi_libaio.so.1 Patch
113981-04 SunOS 5.9: devfsadm Patch
116478-01 SunOS 5.9: usr platform links Patch
112960-37 SunOS 5.9: patch libsldap ldap_cachemgr libldap
113332-07 SunOS 5.9: libc_psr.so.1 Patch
116500-01 SunOS 5.9: SVM auto-take disksets Patch
114349-04 SunOS 5.9: sbin/dhcpagent Patch
120441-03 SunOS 5.9: libsec patch
114344-19 SunOS 5.9: kernel/drv/arp Patch
114373-01 SunOS 5.9: UMEM - abi_libumem.so.1 patch
118558-27 SunOS 5.9: Kernel Patch
115675-01 SunOS 5.9: /usr/lib/liblgrp.so Patch
112958-04 SunOS 5.9: patch pci.so
113451-11 SunOS 5.9: IKE Patch
112920-02 SunOS 5.9: libipp Patch
114372-01 SunOS 5.9: UMEM - llib-lumem patch
116229-01 SunOS 5.9: libgen Patch
116178-01 SunOS 5.9: libcrypt Patch
117453-01 SunOS 5.9: libwrap Patch
114131-03 SunOS 5.9: multi-terabyte disk support - libadm.so.1 patch
118465-02 SunOS 5.9: rcm_daemon Patch
113490-04 SunOS 5.9: Audio Device Driver Patch
114926-02 SunOS 5.9: kernel/drv/audiocs Patch
113318-25 SunOS 5.9: patch /kernel/fs/nfs and /kernel/fs/sparcv9/nfs
113070-01 SunOS 5.9: ftp patch
114734-01 SunOS 5.9: /usr/ccs/bin/lorder Patch
114227-01 SunOS 5.9: yacc Patch
116546-07 SunOS 5.9: CDRW DVD-RW DVD+RW Patch
119494-01 SunOS 5.9: mkisofs patch
113471-09 SunOS 5.9: truss Patch
114718-05 SunOS 5.9: usr/kernel/fs/pcfs Patch
115545-01 SunOS 5.9: nss_files patch
115544-02 SunOS 5.9: nss_compat patch
118463-01 SunOS 5.9: du Patch
116016-03 SunOS 5.9: /usr/sbin/logadm patch
115542-02 SunOS 5.9: nss_user patch
116014-06 SunOS 5.9: /usr/sbin/usermod patch
116012-02 SunOS 5.9: ps utility patch
117433-02 SunOS 5.9: FSS FX RT Patch
117431-01 SunOS 5.9: nss_nis Patch
115537-01 SunOS 5.9: /kernel/strmod/ptem patch
115336-03 SunOS 5.9: /usr/bin/tar, /usr/sbin/static/tar Patch
117426-03 SunOS 5.9: ctsmc and sc_nct driver patch
121319-01 SunOS 5.9: devfsadmd_mod.so Patch
121316-01 SunOS 5.9: /kernel/sys/doorfs Patch
121314-01 SunOS 5.9: tl driver patch
116554-01 SunOS 5.9: semsys Patch
112968-01 SunOS 5.9: patch /usr/bin/renice
116552-01 SunOS 5.9: su Patch
120445-01 SunOS 5.9: Toshiba platform token links (TSBW,Ultra-3i)
112964-15 SunOS 5.9: /usr/bin/ksh Patch
112839-08 SunOS 5.9: patch libthread.so.1
115687-02 SunOS 5.9:/var/sadm/install/admin/default Patch
115685-01 SunOS 5.9: sbin/netstrategy Patch
115488-01 SunOS 5.9: patch /kernel/misc/busra
115681-01 SunOS 5.9: usr/lib/fm/libdiagcode.so.1 Patch
113032-03 SunOS 5.9: /usr/sbin/init Patch
113031-03 SunOS 5.9: /usr/bin/edit Patch
114259-02 SunOS 5.9: usr/sbin/psrinfo Patch
115878-01 SunOS 5.9: /usr/bin/logger Patch
116543-04 SunOS 5.9: vmstat Patch
113580-01 SunOS 5.9: mount Patch
115671-01 SunOS 5.9: mntinfo Patch
113977-01 SunOS 5.9: awk/sed pkgscripts Patch
122716-01 SunOS 5.9: kernel/fs/lofs patch
113973-01 SunOS 5.9: adb Patch
122713-01 SunOS 5.9: expr patch
117168-02 SunOS 5.9: mpstat Patch
116498-02 SunOS 5.9: bufmod Patch
113576-01 SunOS 5.9: /usr/bin/dd Patch
116495-03 SunOS 5.9: specfs Patch
117160-01 SunOS 5.9: /kernel/misc/krtld patch
118586-01 SunOS 5.9: cp/mv/ln Patch
120025-01 SunOS 5.9: ipsecconf Patch
116527-02 SunOS 5.9: timod Patch
117155-08 SunOS 5.9: pcipsy Patch
114235-01 SunOS 5.9: libsendfile.so.1 Patch
117152-01 SunOS 5.9: magic Patch
116486-03 SunOS 5.9: tsalarm Driver Patch
121998-01 SunOS 5.9: two-key mode fix for 3DES Patch
116484-01 SunOS 5.9: consconfig Patch
116482-02 SunOS 5.9: modload Utils Patch
117746-04 SunOS 5.9: patch platform/sun4u/kernel/drv/sparcv9/pic16f819
121992-01 SunOS 5.9: fgrep Patch
120768-01 SunOS 5.9: grpck patch
119438-01 SunOS 5.9: usr/bin/login Patch
114389-03 SunOS 5.9: devinfo Patch
116510-01 SunOS 5.9: wscons Patch
114224-05 SunOS 5.9: csh Patch
116670-04 SunOS 5.9: gld Patch
114383-03 SunOS 5.9: Enchilada/Stiletto - pca9556 driver
116506-02 SunOS 5.9: traceroute patch
112919-01 SunOS 5.9: netstat Patch
112918-01 SunOS 5.9: route Patch
112917-01 SunOS 5.9: ifrt Patch
117132-01 SunOS 5.9: cachefsstat Patch
114370-04 SunOS 5.9: libumem.so.1 patch
114010-02 SunOS 5.9: m4 Patch
117129-01 SunOS 5.9: adb Patch
117483-01 SunOS 5.9: ntwdt Patch
114369-01 SunOS 5.9: prtvtoc patch
117125-02 SunOS 5.9: procfs Patch
117480-01 SunOS 5.9: pkgadd Patch
112905-02 SunOS 5.9: ippctl Patch
117123-06 SunOS 5.9: wanboot Patch
115030-03 SunOS 5.9: Multiterabyte UFS - patch mount
114004-01 SunOS 5.9: sed Patch
113335-03 SunOS 5.9: devinfo Patch
113495-05 SunOS 5.9: cfgadm Library Patch
113494-01 SunOS 5.9: iostat Patch
113493-03 SunOS 5.9: libproc.so.1 Patch
113330-01 SunOS 5.9: rpcbind Patch
115028-02 SunOS 5.9: patch /usr/lib/fs/ufs/df
115024-01 SunOS 5.9: file system identification utilities
117471-02 SunOS 5.9: fifofs Patch
118897-01 SunOS 5.9: stc Patch
115022-03 SunOS 5.9: quota utilities
115020-01 SunOS 5.9: patch /usr/lib/adb/ml_odunit
113720-01 SunOS 5.9: rootnex Patch
114352-03 SunOS 5.9: /etc/inet/inetd.conf Patch
123056-01 SunOS 5.9: ldterm patch
116243-01 SunOS 5.9: umountall Patch
113323-01 SunOS 5.9: patch /usr/sbin/passmgmt
116049-01 SunOS 5.9: fdfs Patch
116241-01 SunOS 5.9: keysock Patch
113480-02 SunOS 5.9: usr/lib/security/pam_unix.so.1 Patch
115018-01 SunOS 5.9: patch /usr/lib/adb/dqblk
113277-44 SunOS 5.9: sd and ssd Patch
117457-01 SunOS 5.9: elfexec Patch
113110-01 SunOS 5.9: touch Patch
113077-17 SunOS 5.9: /platform/sun4u/kernal/drv/su Patch
115006-01 SunOS 5.9: kernel/strmod/kb patch
113072-07 SunOS 5.9: patch /usr/sbin/format
113071-01 SunOS 5.9: patch /usr/sbin/acctadm
116782-01 SunOS 5.9: tun Patch
114331-01 SunOS 5.9: power Patch
112835-01 SunOS 5.9: patch /usr/sbin/clinfo
114927-01 SunOS 5.9: usr/sbin/allocate Patch
119937-02 SunOS 5.9: inetboot patch
113467-01 SunOS 5.9: seg_drv & seg_mapdev Patch
114923-01 SunOS 5.9: /usr/kernel/drv/logindmux Patch
117443-01 SunOS 5.9: libkvm Patch
114329-01 SunOS 5.9: /usr/bin/pax Patch
119929-01 SunOS 5.9: /usr/bin/xargs patch
113459-04 SunOS 5.9: udp patch
113446-03 SunOS 5.9: dman Patch
116009-05 SunOS 5.9: sgcn & sgsbbc patch
116557-04 SunOS 5.9: sbd Patch
120241-01 SunOS 5.9: bge: Link & Speed LEDs flash constantly on V20z
113984-01 SunOS 5.9: iosram Patch
113220-01 SunOS 5.9: patch /platform/sun4u/kernel/drv/sparcv9/upa64s
113975-01 SunOS 5.9: ssm Patch
117165-01 SunOS 5.9: pmubus Patch
116530-01 SunOS 5.9: bge.conf Patch
116529-01 SunOS 5.9: smbus Patch
116488-03 SunOS 5.9: Lights Out Management (lom) patch
117131-01 SunOS 5.9: adm1031 Patch
117124-12 SunOS 5.9: platmod, drmach, dr, ngdr, & gptwocfg Patch
114003-01 SunOS 5.9: bbc driver Patch
118539-02 SunOS 5.9: schpc Patch
112837-10 SunOS 5.9: patch /usr/lib/inet/in.dhcpd
114975-01 SunOS 5.9: usr/lib/inet/dhcp/svcadm/dhcpcommon.jar Patch
117450-01 SunOS 5.9: ds_SUNWnisplus Patch
113076-02 SunOS 5.9: dhcpmgr.jar Patch
113572-01 SunOS 5.9: docbook-to-man.ts Patch
118472-01 SunOS 5.9: pargs Patch
122709-01 SunOS 5.9: /usr/bin/dc patch
113075-01 SunOS 5.9: pmap patch
113472-01 SunOS 5.9: madv & mpss lib Patch
115986-02 SunOS 5.9: ptree Patch
115693-01 SunOS 5.9: /usr/bin/last Patch
115259-03 SunOS 5.9: patch usr/lib/acct/acctcms
114564-09 SunOS 5.9: /usr/sbin/in.ftpd Patch
117441-01 SunOS 5.9: FSSdispadmin Patch
113046-01 SunOS 5.9: fcp Patch
118191-01 gtar patch
114818-06 GNOME 2.0.0: libpng Patch
117177-02 SunOS 5.9: lib/gss module Patch
116340-05 SunOS 5.9: gzip and Freeware info files patch
114339-01 SunOS 5.9: wrsm header files Patch
122673-01 SunOS 5.9: sockio.h header patch
116474-03 SunOS 5.9: libsmedia Patch
117138-01 SunOS 5.9: seg_spt.h
112838-11 SunOS 5.9: pcicfg Patch
117127-02 SunOS 5.9: header Patch
112929-01 SunOS 5.9: RIPv2 Header Patch
112927-01 SunOS 5.9: IPQos Header Patch
115992-01 SunOS 5.9: /usr/include/limits.h Patch
112924-01 SunOS 5.9: kdestroy kinit klist kpasswd Patch
116231-03 SunOS 5.9: llc2 Patch
116776-01 SunOS 5.9: mipagent patch
117420-02 SunOS 5.9: mdb Patch
117179-01 SunOS 5.9: nfs_dlboot Patch
121194-01 SunOS 5.9: usr/lib/nfs/statd Patch
116502-03 SunOS 5.9: mountd Patch
113331-01 SunOS 5.9: usr/lib/nfs/rquotad Patch
113281-01 SunOS 5.9: patch /usr/lib/netsvc/yp/ypbind
114736-01 SunOS 5.9: usr/sbin/nisrestore Patch
115695-01 SunOS 5.9: /usr/lib/netsvc/yp/yppush Patch
113321-06 SunOS 5.9: patch sf and socal
113049-01 SunOS 5.9: luxadm & liba5k.so.2 Patch
116663-01 SunOS 5.9: ntpdate Patch
117143-01 SunOS 5.9: xntpd Patch
113028-01 SunOS 5.9: patch /kernel/ipp/flowacct
113320-06 SunOS 5.9: patch se driver
114731-08 SunOS 5.9: kernel/drv/glm Patch
115667-03 SunOS 5.9: Chalupa platform support Patch
117428-01 SunOS 5.9: picl Patch
113327-03 SunOS 5.9: pppd Patch
114374-01 SunOS 5.9: Perl patch
115173-01 SunOS 5.9: /usr/bin/sparcv7/gcore /usr/bin/sparcv9/gcore Patch
114716-02 SunOS 5.9: usr/bin/rcp Patch
112915-04 SunOS 5.9: snoop Patch
116778-01 SunOS 5.9: in.ripngd patch
112916-01 SunOS 5.9: rtquery Patch
112928-03 SunOS 5.9: in.ndpd Patch
119447-01 SunOS 5.9: ses Patch
115354-01 SunOS 5.9: slpd Patch
116493-01 SunOS 5.9: ProtocolTO.java Patch
116780-02 SunOS 5.9: scmi2c Patch
112972-17 SunOS 5.9: patch /usr/lib/libssagent.so.1 /usr/lib/libssasnmp.so.1 mibiisa
116480-01 SunOS 5.9: IEEE 1394 Patch
122485-01 SunOS 5.9: 1394 mass storage driver patch
113716-02 SunOS 5.9: sar & sadc Patch
115651-02 SunOS 5.9: usr/lib/acct/runacct Patch
116490-01 SunOS 5.9: acctdusg Patch
117473-01 SunOS 5.9: fwtmp Patch
116180-01 SunOS 5.9: geniconvtbl Patch
114006-01 SunOS 5.9: tftp Patch
115646-01 SunOS 5.9: libtnfprobe shared library Patch
113334-03 SunOS 5.9: udfs Patch
115350-01 SunOS 5.9: ident_udfs.so.1 Patch
122484-01 SunOS 5.9: preen_md.so.1 patch
117134-01 SunOS 5.9: svm flasharchive patch
116472-02 SunOS 5.9: rmformat Patch
112966-05 SunOS 5.9: patch /usr/sbin/vold
114229-01 SunOS 5.9: action_filemgr.so.1 Patch
114335-02 SunOS 5.9: usr/sbin/rmmount Patch
120443-01 SunOS 5.9: sed core dumps on long lines
121588-01 SunOS 5.9: /usr/xpg4/bin/awk Patch
113470-02 SunOS 5.9: winlock Patch
119211-07 NSS_NSPR_JSS 3.11: NSPR 4.6.1 / NSS 3.11 / JSS 4.2
118666-05 J2SE 5.0: update 6 patch
118667-05 J2SE 5.0: update 6 patch, 64bit
114612-01 SunOS 5.9: ANSI-1251 encodings file errors
114276-02 SunOS 5.9: Extended Arabic support in UTF-8
117400-01 SunOS 5.9: ISO8859-6 and ISO8859-8 iconv symlinks
113584-16 SunOS 5.9: yesstr, nostr nl_langinfo() strings incorrect in S9
117256-01 SunOS 5.9: Remove old OW Xresources.ow files
112625-01 SunOS 5.9: Dcam1394 patch
114600-05 SunOS 5.9: vlan driver patch
117119-05 SunOS 5.9: Sun Gigabit Ethernet 3.0 driver patch
117593-04 SunOS 5.9: Manual Page updates for Solaris 9
112622-19 SunOS 5.9: M64 Graphics Patch
115953-06 Sun Cluster 3.1: Sun Cluster sccheck patch
117949-23 Sun Cluster 3.1: Core Patch for Solaris 9
115081-06 Sun Cluster 3.1: HA-Sun One Web Server Patch
118627-08 Sun Cluster 3.1: Manageability and Serviceability Agent
117985-03 SunOS 5.9: XIL 1.4.2 Loadable Pipeline Libraries
113896-06 SunOS 5.9: en_US.UTF-8 locale patch
114967-02 SunOS 5.9: FDL patch
114677-11 SunOS 5.9: International Components for Unicode Patch
112805-01 CDE 1.5: Help volume patch
113841-01 CDE 1.5: answerbook patch
113839-01 CDE 1.5: sdtwsinfo patch
115713-01 CDE 1.5: dtfile patch
112806-01 CDE 1.5: sdtaudiocontrol patch
112804-02 CDE 1.5: sdtname patch
113244-09 CDE 1.5: dtwm patch
114312-02 CDE1.5: GNOME/CDE Menu for Solaris 9
112809-02 CDE:1.5 Media Player (sdtjmplay) patch
113868-02 CDE 1.5: PDASync patch
119976-01 CDE 1.5: dtterm patch
112771-30 Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 9
114282-01 CDE 1.5: libDtWidget patch
113789-01 CDE 1.5: dtexec patch
117728-01 CDE1.5: dthello patch
113863-01 CDE 1.5: dtconfig patch
112812-01 CDE 1.5: dtlp patch
113861-04 CDE 1.5: dtksh patch
115972-03 CDE 1.5: dtterm libDtTerm patch
114654-02 CDE 1.5: SmartCard patch
117632-01 CDE1.5: sun_at patch for Solaris 9
113374-02 X11 6.6.1: xpr patch
118759-01 X11 6.6.1: Font Administration Tools patch
117577-03 X11 6.6.1: TrueType fonts patch
116084-01 X11 6.6.1: font patch
113098-04 X11 6.6.1: X RENDER extension patch
112787-01 X11 6.6.1: twm patch
117601-01 X11 6.6.1: libowconfig.so.0 patch
117663-02 X11 6.6.1: xwd patch
113764-04 X11 6.6.1: keyboard patch
113541-02 X11 6.6.1: XKB patch
114561-01 X11 6.6.1: X splash screen patch
113513-02 X11 6.6.1: platform support for new hardware
116121-01 X11 6.4.1: platform support for new hardware
114602-04 X11 6.6.1: libmpg_psr patch
Is there a bundle to install or i have to install each patch separatly_?

Listen to program change on single midi port?

Hi,
I am trying to control MainStage via program change messages. Is there a way to make MainStage listen to program change messages only on a single midi port? It seems like MainStage switches patches no matter on what port or midi channel program changes arrive.
Thanks
Jens

Yes, that would do the trick if I did not want to change MainStage patches remotely. I should have made clearer what my setup is and how I want to use MainStage:
I have two ot three keyboards attached to my Mac via USB. When I change programs on one of them, a small application that I made myself recieves it and sends program changes to the other keyboards. It also loads MidiPipe setups that I use to route midi data to and from the two keyboards and to another sequenzer. So all keyboards need to be connected and program change messages have to be sent. My goal is to have that application also switch MainStage patches. Because I need to rearrange the patches in my 'master' keyboard frequently, I need to have MainStage respond to the program changes from my app and not to the ones that are sent from the keyboard, so that the right sounds are loaded indepently of what the order of patches in the keyboard is.
But I think it just can't be done with MainStage that way. I think it should be a very basic thing for every midi application to choose where to recieve its data from. I thought maybe there is a hidden preference or something. But it seems like I have to wait for MainStage 2 because I need to have program change messages arrive at the computer. Maybe then it supports AppleScript to change patches this way.
Thanks anyway
Jens

Volume changing on patch change

Hi everyone
I'm fairly new to mainstage. There are a couple of patches I've created with multiple software instruments that are always being set to mute (not in the fader section but in the midi volume section at the top of the channel strip) whenever I change patches. I've discovered that if I change the Parameter Values > On Patch Change to "Keep Current Value" it doesn't do this. But I don't think I want that setting. Can someone explain it to me fully? When I have it set to "Reset to Saved Value" I am making sure that I save it with the voliume up before changing patches, but it's still reverting to no volume as soon as I switch back.

have you a midi controller connected to Mainstage ? Do you see Midi activity when you change patches ?

Anyone know when Apple will bring out a patch to fix the volume problem you get on mac mini after downloading OS 10.8.5

Anyone know when Apple will bring out a patch to fix the volume problem you get on mac mini after downloading OS 10.8.5?

Only Apple knows the answer to whether or not there is a verified problem and if so when will a fix be released. As is their custom, Apple does not talk about these things and the rules of these communities prohibit speculation about future udates or upgrades. It is probably safe to say if a fix is deemed necessary it will be called OS X 10.8.6.

How do I set up different hardware controls for different patches in mainstage?

I'm using Mainstage 3.0.4 and a Novation Impulse.
I created a concert, with the drawbar organ as my first and most important patch. I assigned the hardware controls on the Novation exactly how I wanted them, with the sliders controlling the drawbars, and the rotary controls changing the distortion, reverb, etc. It was perfect. I was happy.
Then I added a new instrument (a new patch, not a new channel or anything like that), a Wurlitzer. Once again I assigned my hardware controllers as I wanted them, and was happy with that.
When I saved the concert, and went back to my organ patch, my settings didn't stay the same, but they still work for the Wurli.
My question is this - do I have to have a new concert for each instrument patch I want to use, if I need to assign different controllers for each patch? This would be stupid! If not, what I am doing wrong, that I can only set up one set of hardware controls per concert, instead of per patch?
Thank you in advance for the help!!!

Hi
matthewabennett wrote:
CCTM, thank you! I have a small idea what you mean, but I still can't implement it :-)
You have some fundamental choices:
A) If you want to see Drawbar Controls for organ Patches, and then have other types ( knobs/sliders etc) for other Patches, you could simply make all the screen controls you need, then assign and map them as required.
B) you could simply use drawbar screen controls only and remap them to other parameters for non-organ patches
C) You could use Smart Controls ( which will update their appearance in a 'smart' way
D) You could make your own Drawbar type controls using standard faders
The basic process in a 2 part thing:
Assign incoming MIDI messages from your controller to Screen Controls in Layout mode. This is global for concert. Per patch ( or Set or globally for the Concert) you then map the Screen Controls to parameters for each patch as needed.
Smart Control MIDI assignment is done in the Assignments and Mappings pane
CCT

How to set-up Mainstage for 2 Keys, 2 patch lists in a single concert?

Am new to Mainstage and Logic. Need help ASAP for a show, please, and am too lazy to read the manual How do I set up Mainstage for 2 Keys with 2 performers each controlling a patch/set list of their own in a single concert file? First rehearsal is Monday (Memorial Day) with opening night a week from today, so time is of the essence, and your help is sincerely appreciated! Thanking you in advance. --Jon

koolzero wrote:
When I start TI after I pointed it to my repository I get a message that no packages applicable were found. I did not download all the updates just a few to test it, will it not work unless all updates are downloaded?
Did you change status from test to active in UR before downloading? If not you can change the downloaded items in the manage repository menu.
Assuming the items you did download were not already installed on your client with TI it should work.
Message Edited by zilla on 2009-05-06 10:23 PM
T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

Mainstage volume patches

Similar Messages

Maybe you are looking for