MainStage 2.2.1 released
Symptoms
MainStage 2.2.1 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.
Installation
Resolves several issues related to the download and installation of basic and additional content.
Performance
Addresses an issue in MainStage 2.2 that could decreased performance of the Playback plug-in on computers with one or two cores.
Resolves an issue in MainStage 2.2 that could decreased performance when using the 8-channel mixer & backing track template.
Resolves an issue that could increased latency when playing software instruments with MainStage 2.2.
Improves performance when running multiple instances of EXS24 in 32-bit mode on computers with multiple cores.
Addresses an issue in MainStage 2.2 where performance decreased compared to MainStage 2.1.3 on non-hyper-threaded 2-core computers.
Audio
Fixes an issue in MainStage 2.2 where only the left side of the stereo signal was sent to an Aux if the channel strip had any mono to stereo conversion.
Panning now works correctly on outputs other than output 1-2.
Sends set to Post Pan now pan properly on mono channel strips.
Fixes an issue that blocked sidechain input for plug-ins.
Resolves an issue in MainStage 2.2 where the left side of external stereo audio signals was duplicated and processed by both sides of a stereo channel strip.
Plugins and Patches
Fixes an issue with using keyboard arrow keys to scroll through the Patch Browser.
The Hide Ruler option for the Waveform object again works as expected.
The slide direction of drawbars in EVB3 is no longer affected by the Scroll direction setting in Mac OS X 10.7 Lion.
Resolves an issue where the bottom of some plug-in screens were not accessible on 11” MacBook Air when the plug-in was opened in Controls View.
General
Corrects various problems in MainStage 2.2 with non-English localizations.
CAN MAINSTAGE 2.2.1 DO THIS?
Take a look below at SONAR...
You'll notice on the left...
- The Song/Project List with infinite number of songs. Open up next song Automatically or user defined. Change Song/Projects around on the fly with the mouse. Yes you can have the next song open up automatically, or user defined such as any delay you wish before the next song starts, or start the next song by pressing the spacebar. Also closes current Project/Song when done & opens up next Project/Song.
You'll notice on the right...
- Opens up the Project you're going to play, with ALL AUDIO, VIDEO, MIDI IN/OUT PROGRAM/CONTROL CHANGES, AND ANYTHING ELSE YOU WOULD PUT INTO A SEQUENCER, & CONTROL EXTERNAL/INTERNAL DEVICES!
P.S. WE ONLY USE SONAR BECAUSE APPLE DOESN'T SEEM TO WANT TO INCLUDE THIS CAPABILITY IN LOGIC!
- SO DO WE HAVE TO TRANSFER PROJECTS INTO MAINSTAGE?
- DOES MAINSTAGE TO THE ABOVE?
click to see image full size...
Similar Messages
-
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?
-
via software update!
MainStage 1.0.1 contains several updates, including:
Improves stability
Addresses minor usability issues
Adds options for saving parameter values when switching patches
This software is recommended for all users of MainStage 1.0.
For more information about this release, go to: Late Breaking NewsOption for saving parameters is exactly what I need.
Bravo!
Still wondering why it's not possible to use buffer 32 with MotU although it's possible with Logic with the same channel strips.
Using the new safety buffer helps though. -
MainStage 3.1.1
MainStage 3.1.1 includes the following changes. For more information, see www.apple.com/logicpro/mainstage.
Allows you to disable Screen Saver when in Perform Mode
Fixes an issue where expression pedals could not control the input level of audio channel strips
Resolves an issue where the Download Manager could appear empty
When more than 10 Drum Machine Designer patches are loaded, all channels show their associated sub-channels
MainStage no longer shows an error that the Concert file is corrupted when loading certain concerts created in previous versions
Next/Previous screen control buttons for changing patches and sets not assigned to a MIDI channel reliably respond to mouse clicks again
MIDI output now works when a channel strip setting file that includes an External Instrument plug-in is loaded
MainStage no longer outputs an audio pop when switching between certain patches
Pan works properly again with mono audio channels
The Instantly Silence Previous Patch setting works when moving from a patch using External MIDI to one using a Software Instrument
There is now a link to the AutoSampler documentation in MainStage Helpcool !
-
MainStage 1.0.2 addresses specific customer issues and general performance issues and improves overall stability.
This update is recommended for all MainStage users.Ronald Johns Jr. wrote:
This makes 3 of us having the same issue. I hope they get this resolved soon.
i guess if there are only 3 of us having this problem, then Apple will most likely not give it the attention it deserves. I honestly can't envision any serious professional musician feeling confident enough to use MainStage in a big time act. Logic has not been entirely bug free and users have found work arounds to help get their work done. If Apple chooses not to fix certain bugs in Logic then the only downside is a loss of market share to a more serious pro studio app called Pro Tools. But having a bug or a glitch in Logic is not the same has having an issue in MainStage. If Apple wants users to consider MainStage as a true "live" app, they need to make it bullet proof because unlike Logic, if the app stops working on stage, in the middle of a song, you can't correct the problem.
Well what is the common thread that the 3 of us are having when we experience this error? I am running MainStage 1.02, I have updated Logic Studio to 8.01 and running under the latest version of Leopard. I use a Firewire audio interface on a 17" intel MacBook Pro. How is my current set up the same or different than the others experiencing this issue? Lets see if we can identify some commonalities to try and zero in on the problem since Apple is obviously not going to involve our comments in the bug fixing process and there is no telling when this issue will be fixed since they haven't even stated its a known issue and is being addressed. -
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. -
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. -
http://support.apple.com/en-us/HT200269
MainStage 3.1
MainStage 3.1 includes the following changes. For more information, see www.apple.com/logicpro/mainstage.
New Features and Enhancements
Redesigned Compressor plug-in with scalable, Retina-ready interface and a new compressor model.
Retro Synth can now create wavetables from imported audio and is able to stack up to 8 voices.
The Plug-in Manager now allows you to customize the organization of your menu.
Expanded sound library includes over 200 new synth patches and 10 Mellotron instruments.
New Auto Sampler plug-in converts hardware synthesizers into sampled instruments.
Custom shortcuts can be assigned and managed using the new Key Command editor.
It is now possible to copy and paste ranges in the layer editor.
Stability
MainStage no longer quits unexpectedly when selecting all patches.
General
MainStage no longer drops out of Full Screen Performance mode when you use a KVM switch to change the display to another computer.
When moving the MainStage window from a 4K display to another display, the window width now properly adjusts to the new display size.
Mouse clicks in a plug-in window are no longer passed through to the Patch Browser in Performance mode.
Window positions are now properly recalled when opening a saved concert.
Parameter text fields are now displayed correctly when the first patch or set is skipped.
Text in the Graph Editor now renders properly when the window is resized.cool !
-
MainStage 2.1 release (64-bit)
MainStage 2.1 Update
This update delivers improved compatibility and numerous fixes.
Issues addressed include:
Support for 64-bit native mode
Compatibility with 64-bit Audio Unit plug-ins
Improved compatibility with MainStage 1.x documents
Multiple Playback plug-ins in the same group now sync reliably
Improved recording when using the Loopback plug-in
Updated System Requirements
32-bit mode requires Mac OS X 10.5.7 or later
64-bit mode requires Mac OS X 10.6.2 or later
The update is recommended for all users of MainStage 2.
For detailed information on this update, including some restrictions when working in 64-bit mode, please visit this website: http://support.apple.com/kb/ts2566MainStage 2.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2.
* An issue where Pressing Command-N to create a new concert could lead to MainStage quitting unexpectedly while the Save dialog was open for a previously loaded concert is resolved.
* An issue that sometimes led to MainStage quitting unexpectedly when closing a concert or quitting MainStage is resolved.
* An issue in which the Invert checkbox for mapping ranges could be unexpectedly enabled in a concert where the minimum mapping range was set, but the maximum was not altered is resolved.
* An issue where CPU usage was initially higher than expected when loading some concerts created in MainStage 1 is resolved.
* Importing patches from a concert whose layout contains more keyboard screen controls than the current concert no longer sometimes leads to incomplete display of settings in the Channel Strip Inspector.
* An issue that lead the the name in the Mixer to fail to update when renaming an alias of a channel strip is resolved.
* An issue where changes made to MIDI Out parameters on an external channel strip were not immediately displayed in an alias is resolved.
* The screen display of an expression pedal in an alias patch now moves correctly in response to incoming data.
* The number of sends shown on channel strips now immediately updates as expected after cut, copy, or paste of channel strips.
* An issue that prevented mapping a screen control to the mute parameter on Bus 8 is resolved.
* An issue where it was not possible to return audio from an Aux higher than Aux 8 is resolved.
* Sends no longer sometimes lose settings when patches are imported, copied, cut, and pasted.
* Polyphonic aftertouch is now sent to external instruments as expected.
* Polyphonic aftertouch sent to software instruments no longer causes unexpected parameter changes.
* Dragging an audio file into an empty patch now creates a channel strip with a Playback plug-in instantiated, as expected.
* An issue that prevented EVB3 drawbars in the workspace from correctly updating when MIDI to Preset Key was enabled, and a new preset was triggered via MIDI, is resolved.
* An issue that prevented screen controls from updating properly in response to CC7 and CC10 messages is resolved.
* Mapping to Solo now works properly with hardware buttons that send single MIDI values.
* Changing a Send All mapping from a channel strip directly to a MIDI mapping now works correctly.
* Grouped buttons now update correctly with the send level parameter.
* Mappings are no longer sometimes lost when importing layouts and patches exported from MainStage 1.x.
* Reset to Saved Value now works reliably when changing patches.
* MainStage no longer intermittently stops responding when choosing Undo after deleting patches.
* An issue that prevented Keyboard objects from sending to all channels of a multitimbral external instrument is resolved.
* Inputting notes while auditioning patches no longer sometimes causes MainStage to sometimes unexpectedly quit.
* The I/O plug-in now works correctly on channel strips with "no input" selected.
* MIDI input now works reliably with grouped keyboard controls.
* The alert dialog "The document 'Untitled Concert' could not be saved as '2'" no longer appears when saving a concert with a long file name.
* An issue that prevented Apple Remote from working as expected in Full Screen mode with Mac OS X v10.6.2 is resolved.
* Setting preferences when there is no concert open now works as expected.
* Parameter tabs now maintain a consistent order for multimapped parameters in duplicated patches.
* Changes to "send Program change" and "send Bank change" in patches are now reliably saved.
* Recordings in Loopback are now reliably maintained when Play on patch change is used while the transport is running with "Snap to:" set to "Bar/Beat."
* Count-in now starts immediately on play in the Loopback and Playback plug-ins.
* Setting a Loopback and Playback plug-in the same group and then recording to the Loopback no longer causes MainStage to quit unexpectedly.
* Issues that sometimes caused the metronome to drift out of sync with the Playback and Loopback plug-ins are resolved.
* MainStage remains responsive when making tempo adjustments in concerts that contain multiple instances of the Loopback plug-in with sync enabled.
* The "Start with Play Action" command now reliably triggers all instances of Playback and Loopback in a group.
* An issue that sometimes caused a small section of unexpected audio to sound when switching to a patch with Playback that had previously been stopped with the "instantly silence previous patch" command is resolved.
* The "Begin Finding Patch in Performance" key command now works properly with patches whose names start with numbers.
* Using the Undo command after deleting an object that is a member of a group in the workspace now correctly maintains the object's group membership.
* Control labels are now correctly displayed when switching from full screen view to layout view.
* An issue that caused the workspace in layout view to be invisible when remote connecting to a computer running MainStage with no display connected is resolved.
* An issue that caused objects to become ungrouped when dragging them from the palette to the workspace is resolved. -
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.2: Sustain pedal triggering E3 note on MainStage and making notes get stuck
Hey guys! I've been having issues recently with my MS and can't find to know why. I want to start of with a detailed list of what I'm using to know if this helps.
- MacBook Pro OS X 10.9 (8gb RAM and intel 2.26 core 2 DUO)
- MainStage 2.2. (32 bit)
- Keyboard controller (I normally don't take a keyboard with me but instead use my Macbook Pro to trigger sounds through MS and use the KB just as a controller, but normally I use Yamaha Motif KB's - this actually varies!)
- MIDI-IN and OUT to USB cable
- Normal, regular sustain pedal (FYI, checked that polarity is on the correct possition already!)
- Korg NanoPAD 2
- Korg NanoKONTROL 2
- USB splitter to connect (NanoPAD 2, NanoKONTROL 2 and MID-IN and OUT TO USB cable)
- Apoogee Duet 2 (connected to the most powerful USB port)
So here's the issue and what I've done to try to fix it (Troubleshooting) and also, what I know that is not affecting MS as in connections, hardware and routing processes.
ISSUE:
Every time I press the sustain pedal it triggers E3 note and it toggles between Sustain and this E3 note.
Every time I try to ASSIGN the sustain pedal in LAYOUT mode, press the ASSIGN button, hold and release the sustain pedal, it toggles between "Sustain" and "E3" noted assigned to the sustain pedal
TROUBLESHOOTING:
- I've made sure that the sustain pedal is connected to the right input on the back side of the KB (controller)
- I've made sure that the polarity is correct (switched it just in case - not working still!)
- In LAYOUT mode I ASSIGNED the pedal correctly to my sustain pedal (when it is on "Sustain" it is still triggering this E3 note)
- I've tried going through "ASSIGNMENTS & MAPPINGS" down to "PORT 1 USB2.0-MIDI" wich is the MIDI port that is shown on my MacBook Pro, and verify that it is showing "64 (Sustain)" as the mapped assignment and "SEND TO ALL" parameter (so it is triggered through all of my sounds)
- I've tried going to WORKSPACE and manually MAP PARAMETER the sustain pedal, but when I do this, it still shows that E3 note is being triggered.
- I've tried a clean boot of MS (same thing)
- I've tried a OS X clean boot (same thing)
- I've tried changing the MIDI-IN and OUT USB cable (3 different ones)
- I've tried connecting ONLY (NO SOUND DEVICE or Korg Nano devices nor USB splitter device connected) the MIDI-IN and OUT USB directly to the computer and into different USB ports (still the same thing!)
- I've tried different sustain pedals
What are your thoughts guys? Do any of you guys know how to fix this or have exp. this before? This is really strange and I'm actually thinking that it might be my Macbook Pro USB ports that are going crazy! One thing that I noticed is that sometime ago the MIDI DEVICE that was shown on "MIDI STUDIO" in System preferences was named after "USB MIDI CABLE" and now it is not available to use. Instead, now it is showing as "USB2.0-MIDI" and that's the one that is being used by my Mac. An interesting thing is that when I try "TEST" in MIDI STUDIO and play my KB, it does nothing .... no sound is heard as a MIDI signal being fed to my Mac.
PLEASE HELP! Need to fix this URGENTLY!!!
Blessings!
HIf we can't figure out why it's sending a note on command, let's just find a way to make it stop. First, go to layout mode, select the sustain pedal, and make your settings manually(don't press the assign button). Set it as you described above.
In Layout mode: (when toggled to sustain pedal)
Screen Control Inspector
Hardware Input
Device: Port 1 USB2.0-MIDI
Channel: Channel 1
Type: Press/Release
Number: 64 (Sustain)
MIDI thru: Automatic
Send Value to: None
Next, copy the sustain pedal control(the easiest way is command>C then command>V). It will look like this:
Select the new pedal and manually set it to:
In Layout mode: (when toggled to sustain pedal)
Screen Control Inspector
Hardware Input
Device: Port 1 USB2.0-MIDI
Channel: Channel 1
Type: Note On/Off
Number: C-2
MIDI thru: Do not pass Through
Send Value to: None
The idea is to send that unwanted note the the lowest note(0) so it won't be in the way. I don't know if it will work for you, but it's worth a try. -
I bought MainStage2 on May 30 2013, Am I eligible for upgrade to MainStage 3
I see today the new MainStage3 was released. I was unaware this was coming. Now, what is my eligiblity for upgrade to MainStage3? I just bought MainStage2 on May 30th of this year.
Thanks,
AllenJust to let everyone know, I reached out to Apple through the online process and Apple resolved this!!! I should get a refund in 7 to 10 days. This will allow me to purchase MainStage 3.
Now the plus was that I was able to present Apple with all my details regarding the original purchase and that along with being a n00b with Apple may have helped.
Apple Customer Service was a pleasure to work with and I won't hesitate to engage again if needed.
Apple also supplied me with the following:
a link here with more information about the difference of a software upgrade vs software updates. This is for your future reference.
Software update, upgrade--what's the difference?
http://support.apple.com/kb/HT1444
Thanks Blueberry for the point in the right direction. :-) -
MainStage 2 crashing when I delete a patch
I have an old concert (from MS 1) that I loaded and saved as an MS 2 concert, hoping to save myself some work.
I then opened that concert and deleted one of the patches. The CPU meter immediately displayed red (seemed to be totally overloaded) and then MS 2 crashed, claiming there was a problem with Lounge Lizard (which wasn't even the patch I was trying to delete).
This is 100% reproducible....did not happen with MS 1.
SighSorry, but that is COMPLETELY wrong and DON'T listen to dhjdfj! V1 concerts open just fine in V2.
This explanation was in a different forum:
There is ONE issue with V1 concerts, which use an almost esoteric feature: in layout mode you can select a specific keyboard in the "MIDI thru" selection. Usually this selection is set to "Do not pass through". For Pitch Bend, Modulation, etc. it is "Automatic" (which means: they are automatically forwarded to a channel strip without any specific mapping). But there is a third option: if you have multiple keyboards in the layout, you can set "MIDI thru" to a specific keyboard, so that it is forward to a specific keyboard. And if you used that option, you can't open the MainStage 1 concert in MainStage 2.
To get around that, you (till Apple releases a fix) have to change the popup to one of the common options, save, open in MainStage 2. You can - if you really have to pick a specific keyboard - change it back. Problem solved. -
"clicking" sound when releasing a key via MIDI
Hi, I have just started using MainStage 3 and my problem is the "clicking" sound I get when I release a key on my MIDI keyboard with orchestral instruments. Is there a way to "silently release" a MIDI key? Thanks, Stefan
I solved my problem: in "Edit", "Assignment & Mapping" the setting "Unassigned" (Channel 1-16) was set to "All Channel Strips" and caused the clicking sound. After unselecting "Send unassigned MIDI to all Channel Strips" in "Screen Control Inspector" the clicking effect vanished.
Maybe you are looking for
-
The Firefox 4.0 on my laptop reverts back to 3.6.16. This has happened several times. Why does this happen and/or how do I prevent it from happening again?
-
Hi everybody, we have the customer requirement opening an outlook calender page from a Web Dynpro application. scenario: 1. User clicks on a button, 2. A new Outlook calendar page will be opened, 3. On the opened Outlook calendar page, there are some
-
Hi Im using a cfformgroup type - accordion. WHen the page loads, the 1st tab is opened. By default i want them to all be closed. selectedindex="0" doesnt work. it still keeps my 1st level opened when the page loads Please help me here. Its driving me
-
Is there a VI to turn a 1-D array of integers into Intel Hex Format string?
I have a 1-D array of 16-bit integers. I guess I can turn these numbers into 2x8 bit numbers. After that I would like to convert this arary of numbers into an Intel Hex format string. Is there a VI for this?
-
Why free apps for mac asking payment
Every time I try to download a free app on my iMac, it will ask for billing information which I have already filled out, but why is it asking me for payment if it is free?