Mainstage looses assignments?

Mainstage 2.1.3 on OS 10.6.8 / 2008 MBP
I have a Behrenger FCB1010 foot controller, and a CME UF 61 keyboard. Using a Tascam US-1800 audio interface.
This behavior is infuritating.
I'll spend *hours* getting everything set up in mainstage. And then randomly one of the two pedals will stop responding. Or one of the footswitches won't work, or one of the knobs on my keyboard will stop responding (it always seems to be CC's not notes). I can see the midi message is received by mainstage, but the objects in the edir or perform frame will not respond. If I flip to the "layout" mode, I can again see the objects responding, but the minute I go back into a patch, it acts like it's not receiving the midi message (even though I can see it in the midi monitor).
What's worse is that this appears to be consistent across even rebooting the computer and restarting mainstage (like something get's fouled in the concert definition or something). The *only* way to get rid of it is to start over and create an entirely new concert, new layout etc.
This just recently started. I don't know if a software update caused it or what. This is a serious problem for me. Mainstage *is* my performance rig, and I've used it this way for almost 5 years ... now I'm getting these disasters *on stage*.
Has anyone else started experiencing this? any work arounds?

i have exactly the same problem with my arturia analog factory. do you already have a solution?

Similar Messages

Having issues with profile manager on 10.9 loosing users/device assignments.

I'm having issues with profile manager on 10.9 loosing users/device assignments. Luckly I only have arround 70 devices added so far. The first time it happened I thought it was just a freak thing, but it has just happened again. What I find weird is nothing on the server was changed, no devices added. So when this happens my users phones lose access to email, because I'm using variables, which rely on the user being assigned to the device. Anyone know how to fix this, and if not. Does anyone know how to backup and restore just profile manager in 10.9. Thanks.

I enabled all users in my AD "Domain Users" group access to "Profile Manager". I had also initially enabled "Profile Manager" access for a few individual users. Those users did not loss the device assignments. I'm not absolutely sure why/if allowing access for a group is causing this issue. Enabling access for each person would be very time consuming.... Maybe adding access to the individual users is importing that user into OD?

Duet Sudden Disconnection From Mainstage

Hi There this is a really urgent post since i need to know an answer or some theories about this in the next two days since i am currently on tour at the moment and the next show is in two days. I'm using a macbook pro 2ghz intel core duo, 2gb gg7mhz ddr2 ram its first generation macbook pro i think and i'm running mainstage with an apogee duet. My problem i'm having is while onstage using mainstage to run keyboard sounds with my midi controller the apogee duet suddenly 'disconnects' from mainstage without warning and i lose all my sound and have to restart mainstage so it can reconnect to the duet, i'm a bit lost as to why this happens i have a few theories but i'm not too sure. My first theory is that i need to upgrade my processing power because mainstage is running at about 65-98% on some patches, however i'm not to sure about this as if cpu was running too hot i'd get latency or mainstage would crach. And my next theory is that vibrations from onstage are knocking about the firewire input and have dislodged or interrupted information travelling from the Duet to the Macbook however the cable has never fallen out.... i'm at a loss! please help!!

Sounds like a loose FW connection. Even if cable isn't falling out if it is just a little bit loose you'll lose the connection. Low-tech solution is to put a rubber band around the Duet and FW cable after plugging it in. Also be sure nothing is putting any sort of pressure on the cable itself causing it to wiggle.

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

Using Guitar Rig 5 in MainStage

Hello all!
I'm just getting started with MainStage, and so far quite liking the possibilities.
However, I've hit one thing which seems to be an issue for me, assuming I've understood it correctly. Each patch seems to have it's own channel strips, with it's own AU instruments etc... which to me seems a bad idea. Surely in this state, I will end up having hundreds of AUs running for the same software, which would slow things down?
On top of that, I'm running keyboard, guitar and vocal through Mainstage. All for me, as I switch what I'm doing depending on the song we're performing (and sometimes mid-song). However, this means I may sometimes want to change a guitar patch while keeping my keyboard the same, or vice versa.
So, to my question; is there a way to change AU presets without changing MainStage patch? I mainly need to do this with Guitar Rig 5 from NI, but I'd also quite like to do it with Massive and Reaktor too.
Not quite sure I've worded that very well, so an example:
I have a MainStage layout set up, which has my vocal going through clean with maybe some EQ etc. I've also got a guitar running through Guitar Rig 5, and my keyboard into Massive. During a song, I start off on keys playing Fat Bass 1 on my keys in Massive for the intro, switch to a distortion for the verse with my guitar, then Fat Bass 2 for the chorus in Massive. Maybe later I'll want a clean guitar in a bridge or something too, with some string hits thrown in from Massive again.
The way MainStage is set out currently, I'd need a patch for each combination, which would leave me with at least 3 "patches" for one song and three instances each of Massive and GR running. I'd much prefer to just send in a control message to change the presets in Massive and Guitar Rig.
Running on a 2014 15" MacBook Pro, 2.2GHz i7/16GB RAM/256GB SSD.
Thanks

I haven't been able to find a way to get it to work with Guitar Rig yet, but for Massive (and presumably Reaktor) I have found a solution. First, create an instance in MainStage, load it with Massive and load the presets you would like to use into Massive's preset bank. Turn it on so that it will respond to patch changes.
Navigate to the 'Assignments & Mappings' tab of the edit page. Find the device you want to use to send the MIDI CC messages. If it isn't in the list, click on 'New Assignment', which usually creates an Unmapped assignment in the 'All Devices' list. Click the area where it says No Assignment to bring up the Hardware Input popup menu. Choose your device, assign channel to 1-16, and change Type to absolute. From the number menu, choose the CC number you want to send the patch change. Set MIDI thru to Automatic. Name the input to something like CC to PG01.
Click on it to highlight the mapping info. In the far left side of the Control Inspector, you'll see a list of items such as Same as Input, Block, etc. You will also see the name of the instance containing Massive. Select it to bring up a list of control parameters, such as Volume, Mute, etc. From the list, choose MIDI Controller. The third item down in that menu is Program Change. Select it.
You'll see the Parameter values for Program Change. For saved value, select the Program Change number you want to send. Number scheme is 0-127. Now, here's the tricky part that nearly drove me mad before figuring it out. For NI instruments, one of the Range Max or Min numbers must be set to zero and the other to a non zero number. If you want to select PG 0, set saved value as 0, range max as 1 and range min at 0. For any other patch number, set saved value and range max to the same number and set range min to 0.
Also, make sure that the device thats sending your CC control message is configured as a toggle switch, not a momentary, or else it will send the range min program change number when you lift your foot or finger from the button. If you want to send multiple patch changes, add more mappings and assign different CC numbers to select the patch number you desire.
An additional benefit is that you can load up a single instance of Massive with as many presets as it can hold and use aliases of that instance for other songs. In this case you would create a new MainStage patch and populate it with an alias of your Massive instance. Set up a separate hardware input (I use logic remote) and rather than setting the number to a CC controller, set it to Any. By entering the same NI mapping parameters as above, it will send the correct PG info to Massive when you select the MainStage patch containing the alias. If you need to select multiple Massive patches from the new MainStage patch, simply assign the CC controllers to select new patch assignments. All that info is freely assignable and saved on a per MainStage patch basis, so your first instance could select the patch (say 0) and use three CC controllers to set patches 1-3. On the next MainStage patch containing the Massive alias, you could set the PG to select patch 4 and those same controllers can be set to select patches 5-7.

How do I filter only Volume (Controller 7) in Mainstage?

I want to filter only MIDI volume changes or controller 7 input in Mainstage.
I seem to move it from the Instruments output to the main output.
Auralwiz

I figured out how to do what I wanted by clicking on the Assignments and Mappings window above the workspace window. Then under the Channel 1-16 list there is a Assignment called Unassigned. When I click on that I get the option to send or not send MIDI to all Channel Strips. I un-checked that box and got the response I was looking for.

MainStage 2.2.2 released

MainStage 2.2.2: Release notes
Products Affected
MainStage 2.2
Symptoms
MainStage 2.2.2 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Resolution
About the MainStage 2.2.2 Update
Stability and Usability
Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
Resolves an issue related to the download and installation of basic and additional content.
The menu item for Release Notes now opens the correct URL.
Compatibility
Compatibility with the VAX-77 keyboard is improved.
Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
General
Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

Grabbed MS 2.2.2 last night, loaded, started and promptly crashed. Switched to 64 bit mode and it runs but my 32 bit plug ins (inc apple plug ins) dont work properly (causes crackles). Switched back to 32 bit mode and MS crashes after about 30 secs with no action on my part. I've looked for any special instructions concerning 2.2.2 but have not found any. Has anyone else out there used 2.2.2 yet in 32 bit mode?

Mainstage 2.2.1 and MAC OSX Lion update 10.7.4 CRASH!

hello there.
I'm dealing with an issue with mainstage and the last update from apple's OS, 10.7.4. The mainstage software (witch is intended for live - and steady - use) is crashing often after the OS update. I'm a professional musician and last night a had the third gig in a row with several problems with my setup. Mainstage starts behaving very strangely, a white intermitent bar appears in both sides of the section with the CPU usage and other infos in the top of the edit window. Then i suddenly can't change preset nor patches. the octaves are wrong and the sounds too. then comes the "rolling ball of mac" anouncing something really wrong. After the first time it happened and mainstage crash until closed, i managed to reopen it in the middle of the gigs... it was very stressing and frustrating.
before the last show, yesterday, I searched for answers in forums and here I found that maybe installing the update from appstore would end this issues. so I did, even being an owner of the logic bundle witch came with mainstage, and paid 29 dollars for the software again. the install was alright but the problems remain (actually it was the worst scenario in a gig for me ever...)
PLEASE HELP! i'm a recent user of the mac system, i have late 2009 macbook pro with mainstage 2.2.1 running mac OSX 10.7.4.
I cant afford having this kind of issues in the middle of my job! this become a real problem for me!
in case anyone would ask, NO, i haven't made a time machine backup in order to roll back the OS. my bad.
thanks,
piero

Its disconcerting to say the least to see that last post by SmithBurg was one year ago. Disconcerting because there didnt appear to be a clear cut solution to an issue that seems to be happening to many users in that for whatever user's MS setups were doing at the time, the end result is that the program quits "unexpectantly" during a show.
I had been using MS originally on a late 2009 MB pro, and as my patches evolved, I started having several issues which would quit MS.
I did find what seemed to be a solution by reinstalling the OS to 10.6.8, and and new "unclogged" system seemed to fix the issue. HOWEVER....a few months later and it "quit unexpectantly" in the middle of a show, or I couldnt get my focusrite scarlet 8i6 inteface to work in preferences...(had to use the MB pro minijack out!!   Which was very noisy with the power supply and I do NEED the power supply for a 4 hour show (that old banana)
I digress......
So, i think my laptop has had its day with all the issues id been having, and I go out 2 months ago and buy Apple's flagship macbook pro for $4200, with the idea that the ultra high specs of the laptop should do the trick.
MS reinstalled....I dont use 3rd party plugs as im content with MS sounds, (although i did install kontact to try out and it was far too memory intensive, so dont actually use it.
So for 1 month I play various shows with no issues. I have not changes the setup at all EXCEPT adding one patch that I made.
Then one gig last month it happens again. I'm flabbergasted now.      "MS quit unexpectantly" but I DONT have wi-fi connected at the random venue, and CANT send apple the error report.
My only choice is to reboot and attempt to get the flow of the show back up again.   Thus loosing the error report.
I NEED a solution, and I cant understand what the error report is even saying.
SPENDING $4200 on a new laptop, and if i had hair, I'd be pulliing it out.SHOULD I HAVE GONE HARDWARE INSTEAD? I know MS now, SO used to it, and i love MS far too much if only it worked for more than 5 seconds.
PLEASE APPLE HELPPPPPPPP!
or any kind users out there with some kinda fault finding knowledge

MainStage 2.1.1 released

This update delivers improved compatibility and numerous fixes.
Issues addressed in MainStage 2.1.1 include:
- Improved stability of the 32-Bit Audio Unit Bridge
- Fixed problems that caused audible artifacts when using the Playback or Loopback plug-ins[/list]

MainStage 2.1.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2. Issues addressed include but are not limited to:
64-bit Mode Issues
[*] It is now possible to run FXPansion's BFD2 plug-in in the 32-bit Audio Unit Bridge.
[*] Fixes several issues with the graphical user interface and controls of third party Audio Units running in the 32-bit Audio Unit Bridge.
Stability Issues
[*] In 64-bit mode, a 32-bit Audio Unit plug-in quitting unexpectedly no longer causes MainStage to also quit unexpectedly.
[*] Working with multiple concerts with open plug-in windows no longer causes MainStage to sometimes quit unexpectedly.
[*] MainStage no longer quits unexpectedly if a Patch increment button is assigned to a sustain pedal, and MainStage is switched from Layout mode to Edit mode while receiving continuous sustain messages.
[*] Resolves an issue that could cause MainStage to quit unexpectedly when removing or changing an audio device.
General Issues
[*] Resolves an issue that could cause loss of audio output when “Display audio engine overload” messages were enabled.
[*] Resolves an issue that could cause an unexpected sound when rapidly switching patches in a concert that contains more than one multi-output Ultrabeat instance.
[*] Duplicate MIDI events no longer sometimes lead to stuck notes.
[*] Resolves an issue that could cause MainStage to stop responding when simultaneously adjusting parameters for multiple controls.
[*] Resolves an issue where MainStage could stop responding when opening an auto-saved copy of an already open concert.
[*] Sustain pedal events with values between 1-126 no longer cause multiple triggering of mapped actions.
[*] Switching out of Layout mode while sending a note to a drum pad screen control no longer results in stuck notes.
[*] Drum pads now correctly display all parameter values.
[*] “Do not pass through” now works as expected with screen controls set to send to a specific MIDI destination.
[*] The Keyboard window now sends MIDI notes with velocity values of 100, as expected.
[*] The Layer Editor for external MIDI instruments is available again.
[*] Resolves an issue in which there could sometimes be audio "pops" when auditioning patches while notes are sustaining.
[*] Keyboard assignments are now reliably maintained for non-auto assigned keyboards when opening concerts created in MainStage 1.x.
[*] The right arrow for setting the high range in the Parameter Graph for mapped knobs now works as expected.
[*] The screen no longer flashes if a second concert is opened while a plug-in window is open, and Do Not Close is chosen for the original concert.
[*] Resolves an issue introduced in MainStage 2.1 that could lead to an accidental overlap of split points.
[*] Resolves an issue in which the left side key range of a split made no sound in some rare cases.
[*] MIDI note-off events are no longer handled as MIDI note-on events with a velocity of 0.
[*] Velocity scaling is now correctly performed with drum pads.
[*] The workspace aspect ratio now immediately updates to follow changes to the Layout mode aspect ratio.
[*] Using pitch bend on the Musical Typing Keyboard no longer causes a constant stream of erroneous pitch bend messages to be sent.
[*] The vertical scroll bar controls in the Template Chooser grid view now remain fully functional at all zoom levels.
[*] The items in the Help menu now remain available when the Template Chooser is open.
[*] If the preference for Silence Previous Patch is set to “Immediately,” MainStage no longer plays back unexpected segments of audio when switching away from and then back to a Software Instrument patch that has a plug-in with a long decay.
Screen Controls
[*] Pickup mode no longer behaves like Jump mode when assigning a hardware control that is at a higher initial value than selected screen control.
[*] Waveform screen control mappings are now reliably maintained when the sample rate is changed.
[*] The Screen Control Inspector now properly shows the status of the Mod Wheel control when reselecting it after it has been set to Block, and then another screen control has been selected.
[*] Meter screen controls now follow changes to channel strips that change between mono/stereo.
Parameter Mapping
[*] Number keys mapped to commands now reliably trigger the commands instead of patch changes in Edit mode and Performance mode.
[*] The Current Set action now reliably recalls a specific set when the min and max ranges are set to the same set name.
[*] The Current Patch action now works reliably when the Invert checkbox is selected.
[*] Range settings are reliably maintained for the Current Patch Number action.
[*] The Range pop-up for Current Patch Number mappings no longer show duplicate values.
[*] Undo after changing a mapping and then deleting a pedal from the Pedalboard now works as expected.
[*] Mappings of alias patches are now handled correctly when a plug-in on the parent patch is changed.
Playback Plug-in
[*] Resolves a rare issue where the Play button on the Loopback and Playback plug-in could remain lit with playback stopped.
[*] Resolves an issue that prevented a file that had been loaded and then removed in the Playback plug-in from being loaded again.
[*] If files containing tempo changes are imported into Playback, the following warning only appears once per session: “File contains tempo changes. One or more of the files you are importing contains tempo change markers. This version of MainStage does not support importing files with tempo changes.”
Loopback Plug-in
[*] The Position field in the Loopback GUI now reliably displays all positions at all loop lengths.
[*] After using Undo to remove previous recordings in the Loopback plug-in, recording a loop that crosses the cycle point no longer removes a portion of the loop.
[*] Using Undo to remove a take in the Loopback plug-in no longer removes crossfades at the cycle point.
[*] In the Loopback plug-in, Fade-out now works properly when applied to an overdub performed over reversed material.
[*] Resolves an issue in which enabling Reset to Saved could lead to recording in Loopback starting automatically when a concert was opened.
[*] Resolves an issue in the Loopback plug-in where immediately triggering a Software instrument after going into record could cause an unexpected sound.

How to save to .doc or .rtf without loosing formatting

Hi, I have to submit academic assignments with either .doc or .rtf file extensions. However, in the University there is a protocol for headers and footers so that the assignment is anonymous and when quoting from reference documents we have to indent paragraphs. When writing this is pages and exporting to .doc or .rtf all of the formatting gets lost. If I submit these without the right formatting, I will get marked down. They will not accept .pdf, which works OK - how can I save in .doc or .rtf without loosing the formatting?

Hi Peter Breis, you have suggested soemthing that works which is the first line and left paragraph indents but this still does not work with tabs. The .rtf is not a solution becaue of the need for headers and footers (with pages numbers). In the .rtf file they just appear at the end of the text rather than a header and footer.
Anyway, in summary, thank you Peter, you have given me a solution that works which is to indent using first line and left paragraph indents and to export into a .doc document. The headers and footers export without a problem using this method. I will nominate all the extra marks that I will get from following the University's protocol to you!, Thanks!

FlexConnect, EAP-TLS and dynamic VLAN assignments

I need to integrate Cisco ISE and WLC5508 with FlexConnect (local switching) using EAP-TLS security for wireless clients across multiple floors (dynamic VLAN assignments based on floor level). The AP model used is 3602.
I have some questions:
- What RADIUS Attribute can be used for dynamic VLAN assignments based on floor level? Is there an option where I can group all LWAPs in same floor for getting certain VLAN from ISE?
- I intend to use WLC software version 7.2 since 7.3 is latest version. Has someone use WLC software version 7.3 without any major bugs/issues pertaining to FlexConnect and EAP-TLS?
- I read some documents saying L3 roaminig is where the associated WLC has changed. However if user move to different subnet but still associated to the same WLC, would this be consider as L3 roaming too?
Can someone assist to clear my confusion here? any reference url for layer 2 and layer 3 roaming details is appreciated. Thanks

I'll give this a shot:)
For radius vlan attributes, bothe ACS and ISE in the policies have the ability to just enter the vlan id in the profile. You can either do that or use the IETF attributes.
The RADIUS attributes to configure for VLAN assignment are IETF RADIUS attributes 64, 65, and 81, which control VLAN assignment of users and groups. See RFC 2868 for more information.
64 (Tunnel-Type) should be set to VLAN (Integer = 13)
65 (Tunnel-Medium-Type) should be set to 802 (Integer = 6)
81 (Tunnel-Private-Group-ID) should be set to the VLAN number. This can also be set to VLAN name if using a Cisco IOS device (excludes Aironet and Wireless Controllers however).
You can find this by searching on Google.... A lot of examples out there
v7.2 and v7.3 I have had no issues with, with any type of encryption used. With 7.0 and 7.2, I would use the latest due to the Windows 8 fix.
Layer 3 roaming is what's going to happen if the AP's are in local mode. This means that the client will keep their IP address no matter what ap they are connected to and or WLC as long as the mobility group is the same. So a user who boots up in floor 1 will keep its IP address even if he or she roams to the 12th floor and as long as he or she didn't loose wireless connection.
FlexConnect you can do that. The AP's are trunked and need to have the vlans. So what your trying to do will be disruptive to clients. When the roam to another floor ap that is FlexConnect locally switched, they will drop and have to re-associate in order to get a new IP address.
Hope this helps.
Sent from Cisco Technical Support iPhone App

All STATIC DHCP Assignments wiped out

Out of the clear blue sky, my Verizon Fios Router (the new Gateway G1100) suddenly had none of my static DHCP Assignments. They all vanished! I have no idea how, but on January 3rd, I had a fully functioning router with everything set the way I want, and I had a backup of the settings.
Today, I'm trying to remote in to some PCs on my lan and their not responding. Well of course they're not, they have new IP addresses assigned dynamically because my entire address reservation entries were gone!
What the hell? Best guess I have is VERIZON pushed a firmware update that screwed me and never told me. The fact they can push updates at their whim kills me! I'm stable, don't push me jack S%$#. Don't fix what isn't broken. Notify me, let me opt in!!!!
I'm so hating my switch to verizon!
Has anyone else had this happen?

Verizon is pushing a firmware update to the Quantum routers. It adds useful functionality to the router. See this thread for the details:
http://forums.verizon.com/t5/FiOS-Internet/Fios-Quantum-Gateway-1-1-Enhancements/m-p/774233#M54060
My router was updated yesterday. Unfortunately, my router lost it's static DHCP assignments as well. I had even saved my router config prior to the upgrade as I was concerned about loosing my settings. A restore of the router config after the update did not recover my static DHCP settings. I'm not sure what else wasn't restored.
While I do like the improved features that the new firmware provides (Guest WiFi is a big deal for me), I too am disappointed in how this upgrade cleared out some settings and how we users have no control over the process. I've heard that we're supposed to receive an email about the upgrade, but I never got one.
Good Luck.
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

Mainstage Crash during live use after OS X 10.7.4 install.

I am a semi-pro musician and I have added Main-stage to my set-up, in line with my hardware synths, as I transition into the soft synth world in a live situation. Up until the latest OS X install, Main-stage has been stable, which is critical for live use, and my confidence moving forward is growing. However now, my Main-stage set-up hangs up and or crashes in performance mode after about 15-20 minutes. This is not acceptable, anyone here that is invested in Main-stage for live use, understands this. 30% of my show is dependent on this too,l but crashes cannot happen on stage.
I have read that the new OS X update 10.7.4 may be responsible, as this is the only thing that has recently changed. If so, what is the solution to resolve?, is it possible to back out a OS X update and if so, how?
This is my first post, which for me, means I am desperate for an answer quickly, thanks.

And there is your reply from Apple:
MainStage 2.2.2: Release notes
Products Affected
MainStage 2.2
Symptoms
MainStage 2.2.2 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Resolution
About the MainStage 2.2.2 Update
Stability and Usability
Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
Resolves an issue related to the download and installation of basic and additional content.
The menu item for Release Notes now opens the correct URL.
Compatibility
Compatibility with the VAX-77 keyboard is improved.
Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
General
Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

Project 2010 Server - Users loosing permissions to Projects

Hi all.
I am having an issue where some of our users are loosing permissions to certain projects. It is not always the same ones. It is even ones that they own.
I have done some searching through the forums but cannot seem to find the same issue.
Has anyone come across this or know what could be causing it?
We are running Project 2010 server on SharePoint 2010 platform.
Thanks for reading.

User are losing permission in project site or project ?? If it is project site then
May be users to whom access has been given manually and after every publish and change resource permission they were loose the permission to project site.
Choose only one approach described below then you will not face the issue
1.either Check to automatically synchronize Project Web App users" in PWA --> Server setting so that all the resource who are present in Project build team get the access.
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
When you have this enabled, it doesn't sync all of the Project Web App users from the top level site, it only syncs users to the project site that should have access based on the following rules:
Project managers who have published a project or who have Save Project
permissions on a project are added to the Project Managers (Microsoft Project
Server) site group.
Team members with assignments in a project are added to the Team members
(Microsoft Project Server) site group.
Other Project Server users who have View Project Site permission on a
project are added to the Readers (Microsoft Project Server) site group.
2. or If you disable Check to automatically synchronize Project Web App users" then either Administrator need to give access to project site to required resources. this one is manual work and hectic to administrator to mention the up to date permission
kirtesh

Changing Face Assignments

I've just switched to Aperture from iPhoto and I have to say overall the experience is better. I've assigned names to faces that have been found by the system. Overall, it's done a better job than iPhoto. However, by accident some of the faces assigned to an individual are incorrect. I've found that changing face assignments is a tedious task at best. First, one has to choose an individual's collection of faces. Find the faces that don't belong to an individual and then choose no more than 3 wrong images. The system then focuses on one picture and then one has to carefully choose "Faces" on the menu bar or press the shortcut key "N". It then highlights the faces it has detected for that picture. If Aperture hasn't already crashed, you then blank out the name of the mis-assigned face. Then choose the right name and then press "Done". This is just too many operations to re-assign a name to a face! If you choose to do more than one picture, the system proves to be very unstable and often just crashes.
Apple: Please provide a better way to re-assign a misidentified face.
Your next release must fix this problem.
Thanks, and if anyone else has had this problem, please share your experience or better way to do it.
Peter

if you normally use the master socket then I would buy a filtered faceplate which will replace the one that you have disconnected. it is a straight replacement just connect the wires on 2 & 5 there is no need for 3. hub will only then work in this socket and no other filters are required
you could also try replacing the front plate but disconnect the bellwire on terminal 3 first and tidy up loose wire this explains about bellwire
bellwire removal
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Mainstage looses assignments?

Similar Messages

Maybe you are looking for