Mainstage 2.1.3 update

I have downloaded the 2.1.3 update but when I want to install it, well it says that they can't find my mainstage 2.0 in my application section..but IT IS there....whats going on ?
THanks

Hi
The Mainstage updater will probably be expecting to see an application called "Mainstage" with no numbers or spaces in the name, and it will be expecting to find it in the Applications folder, and not in a sub-folder
CCT

Similar Messages

  • TS4027 [HELP!!] where can i download mainstage 2.2.2 update?

    Hi, anybody knows where can i download mainstage 2.2.2 update? i still always experience unexpected quit which will greatly affect the stability of live performance!!! help please~~~
    thx very much in advance!!!!

    Wow... people need to learn to get back to you lol. You do not need to use 64-bit because it is really only useful for opening more than 4Gb RAM. you only have 4 so it would not benifit you. If you wanted to try to open it as 64-bit tho (Not Going To Help), just close the program, go to your Applications folder in finder, right click on Mainstage and go to "Get Info", under the General tab you will see a check box to open in 32-bit or not. uncheck the box to open in 64-bit mode. But like I said, it will not help you:/

  • 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 download

    I am on 10.8.4 and need to run MainStage 2.
    I have Logic 9.1.8 and Mainstage 2.1.3 updates installed.
    I understand 9.1.8 was the latest version before Logic X, but that 2.2.2 is in fact the latest version before MainStage 3.
    I understand that 2.2.2 was a paid upgrade from 2.1.3, but how do I get it now MainStage 3 is out?
    I cannot see MainStage 2 on the App Store.
    How can I fully upgrade MainStage 2 on OS 10.8.4 before going to MainStage 3?

    Hi
    James Drake wrote:
    ...that is a problem for my work...
    Why, if MS2.1.3 is working OK for you?
    MS2.2 has a new audio engine, which is further improved in MS3.
    MS3 has some new features like MIDI FX, support for Smart Controls, etc (and a load of bugfixes).
    MS2 and MS 3 will co-exist and run happily on the same Mac too.
    CCT

  • 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.1.1

    my software update says there is a mainstage 2.1.1 update. but i cant find it on the apple site.
    currently i have Mainstage 2.1 installed and i can find that on the apple site but not 2.1.1.
    could somebody post me the link.
    thanks

    Why, can't you download it with Software Update?
    All Logic updates, including the Mainstage 2.1.1 update, are available from the standard Logic download page:
    http://www.apple.com/logicstudio/download/

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

  • MainStage 2.0.1 released

    This update improves overall performance and provides numerous fixes and enhancements, including the Loopback and Playback plug-ins:
    Issues addressed include:
    • The Reverse option for Loopback now behaves consistently
    • Pitchbend data is transmitted properly to external instruments
    • A recording in Loopback can be used to define the tempo for MainStage
    • The I/O plug-in is now available in MainStage
    The update is recommended for all users of MainStage 2.

    MainStage 2.0.1 Update
    This update improves overall performance and provides numerous fixes and enhancements, especially to Loopback and Playback plug-ins. This update is recommended for all users of Mainstage 2.
    Issues addressed include (but are not limited to):
    * The memory usage display is now more accurate and shows MainStage and total system memory combined.
    * Feedback protection is now disabled if not in use resulting in a significant CPU performance improvement for audio channels.
    * The Reverse option for Loopback now behaves consistently.
    * Pitchbend is now transmitted properly to external instruments.
    * The I/O plug-in is now available in Mainstage.
    Enhancements include:
    * Loopback can now be started by a Play action.
    * Loopback now has an option to transfer its tempo information to the Concert when its Sync option is disabled, and it derives its tempo from the first recorded loop.
    * The Post-Pan option is now available for channel strip Sends.
    * MIDI out is improved to make it possible to send program changes via Mapping, and to allow MIDI Start/Stop/Continue messages to be sent on patch changes to external channel strips.

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

  • My mac won't let me open mainstage

    i installed logic x onto my mac through the app store and it came with mainstage. i installed an update that my mac was bugging me for. now it won't let me open mainstage as it seems to think it was installed off a cd and i need the CD key which i do not have as i bought it through the app store. how do i sort this?

    It is likely more something wrong with your kit. Try manually downloading and installing 10.7.1 over the top of your current installation of Lion. Hopefully it will fill in any missing pieces.
    http://support.apple.com/kb/DL1437

  • Mainstage no longer recognising caf files after update!?

    I just installed the update to Logic and Mainstage, and am really happy with the improvements in Loopback and Playback, but I just tried exporting a CAF file from Logic to use in Playback and it doesn't let me sync it up... which it should do with CAF files.... am I missing something here?

    I'm wondering what you mean by this. I have UB and a playback track in the same patch, and when I move around in the playback file, i.e. from marker to marker, UB doesn't seem to stay in time with the playback track. Granted, it could be because I have UB running in sequencer mode, but I don't know of any other way to run it in MainStage, other than triggered by external MIDI. How are YOU getting it to sync?

  • I just updated to 10.7.5.  I now cannot open Mainstage 2.2.2 in 64-bit mode.  It keeps telling me it quit unexpectedly.  It opens only in 32-bit mode

    After finally getting Mainstage to work with 10.7.4 for any extended period of time, I updated to 10.7.5.  Immediately after restarting, I tried to open mainstage and (after trying several more times and restarting again and again), I keep getting a message that it quit.  I tried to open the program in 32-bit mode and it does open.  However, in 64-bit mode, it continues to quit

    I have partially figured out the cause.  when I have both the apogee Gio plugged in and the Axiom keyboard plugged in (via USB), it quits.  However, if I only have one of them plugged, Mainstage starts up.  Anyone know a fix?

  • Mainstage 2 : The poeples who buy complete version of Logic with Mainstage 2 will not have free update of Mainstage ??? This is outragous !!!

    Mainstage 2 : The poeples who buy complete version of Logic with Mainstage 2 will not have free update of Mainstage ??? This is outragous !!!

    I also agree that the paid update is a sham to those who bought the full boxed set of Logic.  The ONLY reason I bought the boxed version of Logic was to get MainStage....I don't use anything else in that package.  So ultimately, I've paid hundreds of dollars for a product that's now selling for $30 and I don't even get a free update.....sheesh!
    As far as this logic goes: " MS 2.2 is a feature release" and that I "never bought that version of MainStage with the Logic Studio box": bollocks!  Many consider a feature release to be more than a .1 incremental update...OSX versions excluded.  With the exception of major OSX updates, I've never experienced being charged money for a .1 incremental update, and the vast majority of software developers have a policy that incremental updates are free until a new version is released i.e. v.2.5.6 to v3.0.  I'm sure that's not always the case, but it's definitely the case in an overwhelming majority of cases.
    Shame on Apple for this price gouge.

  • Mainstage 2.1.3 to 2.2 Update

    I have Mainstage 2.1.3 which is the most recent update that the Software Updates has shown.  My version of Mainstage 2 came with the Logic Pro 9 that I purchased back when it first came out.  I see the App Store has Mainstage 2.2.
    Is there a way to upgrade my version of Mainstage to the 2.2 version?

    CCT,
    Thanks I'll check it out and see what I think.  2.1.3 is working just fine for me right now and am having no problems with how I use it.
    Seems strange that the people who paid $500+ for Logic 9 that came with Mainstage 2 now have to buy it again if they want an update.  Oh well.
    Thanks again.
    Madtux

  • Cant update to Mainstage 2.1.1

    I cant get the software to update. it says that it is successfully installed after I download and do the install. When I go to mainstage it still says version 2.0.0
    Also, I cant create new projects. click "New" and nothing happens.
    I only have access to an existing concert that i created.

    I think that version of the updater left an older version of the app along with the updated version...so you might have a couple of copies of Mainstage. It's been fairly common for folks to be launching the older version. Go into your Applications folder, check how many copies of Mainstage are in there and make sure you're launching the updated version.
    Not sure if this is the problem you are having, but you wouldn't be the first so it's worth double checking.

Maybe you are looking for