Jump to content

Xenophile

Member
  • Posts

    26
  • Joined

  • Last visited

Xenophile's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. It took them long enough! It seems they have fixed the issues with 3.6. Since I have not really used Mainstage for a few years, I have trashed by preferences file and started rebuilding concerts from scratch. So far it seems to be working well.
  2. Nobody? In case anyone is interested, I found a "settings" option (CTRL-Click on a blank area in the MidiQuest editor window) where I can select Send Edit Buffer on load. it works... sort of. Motif Rack ES switches to the desired program. Kronos switches to the desired program, but then switches to SEQ mode, which is not what I want. I have to manually switch it back to PROG mode. I don't see an option in the MidiQuest settings for selecting the HW synth mode.
  3. I recently bought Midi Quest 12 (64-bit), and have started trying it out controlling my Motif Rack ES and Korg Kronos hardware synths using the Midi Quest Editors as AU plug-ins in Logic Pro X. After a little initial confusion about how to assign the plug-in and midi/audio tracks (the Midi Quest plug-in goes on its own SW instrument track, and then a separate External Midi Track is used to play and record midi data sent to the synth, and finally the resulting audio can be bounced to yet another audio track when you want to "print" the part). But I haven't figured out how to get MidiQuest to automatically load the desired patch into my HW synths when I open the track in Logic. I still have to open the MidiQuest editor, select the desired patch from the bank, and send it to the synth. I'm sure there is a simple option that I need to set somewhere, but i haven't found it. I would like the hardware synths to get automatically loaded with the desired patches when I open the project in Logic. The next step would be how to record SysEx automation for MidiQuest to send to the HW synth during playback, for e.g. varying the synth's filter cutoff frequency while a part is playing. I'm having trouble finding a basic "How-To" tutorial or video that discusses this. Thanks! - X
  4. No file com.apple.mainstage3.plist there. MacOS High Sierra 10.13.4 MacBook Pro 13" mid 2014 I opened Terminal cd / find . -name com.apple.mainstage* didn't find it. Saw lots of "permission denied" messages when it tried to search system folders. I tried su It prompted me for my password, so I entered it... It said su:Sorry It is looking like I will have to uninstall/reinstall. Not sure if that is going to blow away the large plugins I've installed, Ivory Grand Pianos, Omnisphere, Keyscape, Kontakt 5...
  5. After one of the recent Mac OS updates moved everything around, I can’t find the Preferences file. Mainstage has become very sluggish on patch changes and I need to clean it up if I’m going to start using it again. A standard trouble shooting step was to delete the Preferences file, but I can’t find it any more. Has it been renamed? Hidden somewhere? I’m afraid I might have to uninstall/reinstall everything to get my performance back.
  6. According to the release notes, "MainStage no longer hangs in certain rare cases when dragging patches in large concerts." It still hangs for me, frequently. It doesn't have to be a large concert... Just a relatively complex patch with splits. I have a few serious plug-ins going... Omnisphere, Kontakt and Ivory along with some Mainstage sounds and an external synth module. I've learned the hard way... Instead of dragging patches around, I cut-and-paste them. Much safer.
  7. Anyone tried Nektar Panorama P6? Focusrite Scarlett 18i20? Kontakt 5? Omnisphere 2?
  8. Check this section of the manual on Controller Transforms. https://help.apple.com/mainstage/mac/3.2.3/#/mstg9086973c
  9. Thanks. I did the Kontakt part, but not the Mainstage part. So I'm getting all the Kontakt channels apparently summed to one channel strip in Mainstage. I'm sure you covered it already, I just haven't had time to soak it in. You said you never use the first slot in Kontakt? I'll get it figured out... Baby steps.
  10. Thanks, Michael. That "copy of an alias" trick does seem to work to create splits and layers with different instruments from a single instance of a Kontakt Multi. I had a little trouble getting the expression pedal to affect all the desired channels, but I think I got there by assigning it to "All Kontakt Destinations." Now I need to go back and understand how to add Aux(?) strips to get separate volume controls for each of the Kontakt instruments in my final patch. I have the original Kontakt strip set up with each instrument going to its own separate channel within Kontakt. But those "copies of aliases" in my final patch are apparently all pointing to the same audio track... If I move one strip's fader, they all move together.
  11. Thanks Michael. I'll try again when I get home this evening, but that sounds pretty much like what I've been trying already. Seems like that would be OK for layering sounds, but if you want a split, you'd have to create two channels strips that alias to the same multitimbral instance of Kontakt, and I found that Mainstage wouldn't let me paste more than one alias of the same strip in a single patch.
  12. I keep re-reading this thread, trying to understand Michael's process. I'm also trying to find the best way to build a single "rack" of sounds that can be used in different layer/split configurations on a per-patch basis. I am not able to go back farther than Mainstage 3.2.2. I currently use about 5 instances of Kontakt 5 in separate Patches, each running a different single instrument. Then I copy those instrument channels and paste them in as aliases in the Patches that I use during my shows. I haven't figured out how to make a Kontakt Multi work for me. I'm not doing any midi channel switching from my controllers... I have two keyboard controllers, and each stays on the same channel through the whole show. I wish that I could have Mainstage re-map these controllers' outputs to different channels and key ranges on a patch-by-patch basis. For example, on one patch I'd like the bottom half of one keyboard to map to Kontakt channel 1 (piano), and the top half of that same keyboard map to Kontakt channels 2, 3 and 4.(layered horn section). I can do this with separate instances of Kontakt instruments, but I haven't figured out how to do it with a single Kontakt Multi.
  13. I've been waiting for this release, and I'm really disappointed to read about all the problems. I'm a recent Mac convert, long time PC user. I've been a gigging keyboard player for 40+ years. About a year ago I started gigging with a Windows laptop running Forte with Kontakt, Ivory and Omnisphere along with my trusty Motif ES Rack. About 6 months back I bought a loaded 2014 model MacBook Pro and switched to Mainstage, thinking it would be more stable. Where can I learn more about creating separate boot partitions and tweaking for live performance? How difficult/risky would it be to try to add a Windows boot partition? Also Wondering how hard it would be to use Bidule to build a Forte-like environment on the Mac, with a "rack" for my soft synths and a flexible, programmable midi patch bay sort of thing where I could route a couple of keyboards to those soft synths in various split/layered/transposed configurations that I could call up with program change messages. I kinda liked using Lemur on my iPad for set lists with a few buttons to call up the patches I use for each song That's all so much work, though. I had really hoped that Mainstage would be the integrated application that would make it all happen. Still no "magic bullet," I guess.
  14. As I posted earlier, Nektar support also said the issue is on the Apple side. I would have expected a quick update if several controllers were affected... But still nothing. Meanwhile I'm still on 3.2.2. Searching for stable alternatives. Wondering what can be done with Bidule...
  15. I got an email reply from Nektar rep Justin Sullivan saying that the fix for Panorama is in Apple's court, as it affects other controllers too. But I haven't seen any mention of problems with other controllers here or in Apple's community forum. Maybe very few people are doing the update?
×
×
  • Create New...