Drag them to the desktop or a folder.Ĭlick Layout, press Command–A (or choose Edit > Select All) to select all elements in the Layout section, then press Delete to remove them. To export your sets and patches, click Edit in the toolbar, click in the Patch List, then press Command–A (or choose Edit > Select All) to select all sets and patches in the Patch List. Choose a location in which to save the layout, then click Export. Open the concert you're having issues with.Ĭlick Layout in the toolbar, click the Layout Action pop-up menu at the top of the Layout section, then choose Export Layout. When you rebuild a concert, you export the layout, sets and patches from your concert, then import them into a new concert. ![]() If the issue doesn’t occur in the new concert, then the concert you’re experiencing issues with may be damaged. ![]() Test if the issue occurs in the new concert. Create a new concert and then test MainStage to check if the original concert file is causing the issue.Ĭhoose the devices you want to use for audio input and output from the Audio Input and Audio Output pop-up menus in the dialogue.Ĭlick an instrument category on the left, then select the template you want to use. Sometimes concert files can become unusable, causing unexpected behaviour in MainStage. If you’re using Audio Units plug-ins not made by Apple, try bypassing or removing them.įind out more about troubleshooting Audio Units plug-ins Create a new concert If using built-in audio resolves your issue, you may need to update or service your audio interface. Test using a concert, set or patch you've had issues with. Open MainStage, then choose MainStage > Preferences > Audio.Ĭhoose your computer’s speakers from the Audio Output pop-up menu.Ĭhoose your computer’s microphone from the Audio Input pop-up menu. Unplug your external audio interface from your Mac. If you’re using an external audio interface, try using the built-in speakers and microphone on your Mac instead of the interface. Use your Mac’s built-in audio with MainStage If an update is available, follow the manufacturer's instructions to update the device or software. If you’re using an external audio interface, MIDI interface, storage system or plug-in not made by Apple, make sure it’s compatible with the version of macOS you’re using. If a MainStage update is available, click the Update button to download and install it. Update MainStageĬhoose Apple menu > App Store, then click Updates in the toolbar. Try these steps in orderĪfter trying each step below, test MainStage again to see if you’ve fixed your issue. Has anyone found a workaround to get this to work correctly in MainStage 3? In any case I will be filing a bug report.Before proceeding, make sure you back up the MainStage application. That way if you inadvertently trigger this problem you can quickly and reliably get it to stop.) (Aside: If you use MainStage in live performance one thing I would suggest is mapping a button or key to PANIC - I use the highest C on my keyboard. You don't always have enough fingers or hands available to hold the chord manually without dropping out notes, especially when there's also a page turn thrown in too! The situation is usually that you're holding a chord and you need to switch patches in the middle of holding it so you can be ready to play a new patch at the beginning of the next measure. ![]() I regularly play in musical theatre pits and it's pretty common for there to be at least a few spots where the keyboard book is written such that it's a necessity to do this. ![]() Even so, MainStage 2.1.2 fixed the problem - it was specifically noted in the release notes. At the time I posted this question to the MainStage forum and got a response explaining the workaround. Most of the default concerts were already set up this way so unless you started with a blank one (as I did) or removed it you probably never ran into this problem. In that instance it was only a problem if you didn't have a sustain pedal control in your layout mapped to sustain. this worked fine in MainStage 1.x but was partially broken in MainStage 2 prior to version 2.1.2. The notes that were sustained from the previous patch are now stuck until you switch back to it and tap the sustain pedal (resulting in a sustain off message to that patch) or until you use MIDI PANIC to stop it.Ī bit of history. The problem simply seems to be that if you switch patches with the sustain pedal down, once you release the pedal the sustain off message gets routed to the current patch instead of the previous one where the notes were sustained. I don't think it has anything to do with how you switch patches (arrow keys, screen control mapped to a MIDI message, etc). I've also run into this problem with MainStage 3 and I'm unable to find a fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |