![]() Has anyone found a workaround to get this to work correctly in MainStage 3? In any case I will be filing a bug report. The visual stuff is just there to indicate easily, in a live setting, what instrument patch you are plugged into (as far as I know. It's for playing live, with real (or MIDI) instruments. That way if you inadvertently trigger this problem you can quickly and reliably get it to stop.) MainStage is not for playing virtually, even if it looks like it to you. (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. Attributes in the Screen Control Inspector now update to reflect different selected mappings after Mainstage has been hidden and then show again. Assign and Map now remains active when mapping controls in a plug-in UI. Even so, MainStage 2.1.2 fixed the problem - it was specifically noted in the release notes. General Fractional tempo values can now be entered at all levels (Concert, Set, and Patch). 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. In a few steps, you can transform an individual sample into a fully playable instrument. Or record audio directly into Quick Sampler using a turntable, microphone, or musical instrument. This lets you access the Apple Store and download the app. It replicates the Apple environment on your Windows PC along with the Apple user interface. In this case, the emulator has to be an iOS one. The only way to download Mainstage 3 for PC is through an emulator. Drag and drop an audio file from the Finder, Voice Memos, or anywhere within MainStage. As already mentioned below, Mainstage is only available in the Apple Store. 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. Quick Sampler is a fast and easy way to work with a single sample. I don't think it has anything to do with how you switch patches (arrow keys, screen control mapped to a MIDI message, etc). If this is not checked, User Patches will not appear in the Inspector.I've also run into this problem with MainStage 3 and I'm unable to find a fix.If you click the little gear to the upper right of the Patch Library, is there a check mark next to “Show User Settings"? If so, you should see User Patches below the Workspace, and it should look exactly the same as your MainStage folder.Ģ.Is View > Show Inspectors selected inside MainStage? Expands the Sound Library with 120 Patches, 50 kits and 2800 loops from todays biggest hitmakers including Boys Noize, Mark Lettieri, Mark Ronson, Oak Felder, Soulection, Take A Daytrip, Tom Misch, and TRAKGIRL.I don't know what iPadian Setup is - apparently there's a piece of software called iPadian which seems to be an iPad simulation (not a fully-functional. If you see your patches inside your Finder MainStage folder, but not inside MainStage itself, there are a couple things to check: MainStage is a macOS application - it runs on Macs (usually some kind of macBook, for live work), and if you have macOS 10.12 or later you can buy/download/install it from the Mac App Store. If you don't see the product you downloaded in the MainStage folder, and are unable to locate it in Finder, you'll want to re-download and install again, checking that you put it in your MainStage folder. If you want to customize your folders, you'll want to do that in the MainStage folder as you develop your personal workflow. It's best to keep all patches inside the MainStage folder, and then you will see the exact same folders in User Patches inside MainStage. ![]() ![]() ![]() If your patches aren't here already, you should move them over: Users > Music > MainStage > You'll want to keep all your patches inside your Finder MainStage folder so MainStage can find them and they will appear under "User Patches".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |