Jump to content

jdoo

Member
  • Posts

    104
  • Joined

  • Last visited

jdoo's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

2

Reputation

  1. Cool. Thanks for that tip! In my case, I sort of appreciate having a visual cue that I've got aftertouch working (can watch a vertical slider move up/down based on aftertouch I am applying). But it's nice to know I don't need that, if I don't want it. Cheers--
  2. I had (patch specific / explicit) aftertouch issues a couple of months ago. Posted the settings that got me going in this thread: viewtopic.php?f=17&t=138774&p=712361 Posting this here, because it was settings on an extra control I had placed in the workspace that allowed setting the MIDI input (not a channelstrip). hth - Joe
  3. The ability to move the Sound Library to an external drive has a limitation, unfortunately. You can't share a Sound Library between Mac computers. If you have more than one Mac running Logic Pro or MainStage, each Mac needs its own Sound Library. Dangit. So - it's great that I can free up harddrive space on my systems... but a bummer that they can't share the same external SSD I have...
  4. Quick followup to my earlier post. The MainStage issues were not necessarily OS related, as the MS 3.4 release yesterday corrected the issue I mentioned. All good here now...
  5. I don't want to hijack this thread, but there is a bug in Mainstage 3.2 under High Sierra, and continued in Mojave that is a major pain in the butt... If you utilize the function in MainStage of selecting multiple patches, and choose "New Patch From Selected Patches" in the gear menu (next to patch list in the GUI), MainStage will combine the patches, but does not copy any text objects that exist outside of the first patch. Not a big deal unless you use this capability, and something that can be worked around by copying the text manually (from the original patches) and pasting it into the new combined patch. However --- depending on how you use templates, and MainStage ---- this can be a huge time loser. So ... MainStage is still whack-o'd by this bug in Mojave. (as it is in High Sierra). j
  6. Success. For the curious.. this is what worked for me. Not claiming this is the best way to map stuff to aftertouch for a concert… just saying this is the way I did it. In layout mode, I dropped a vertical fader onto my work area. The vertical fader allowed me to assign the Channel and MIDI signal (Channel Pressure) to it, at the concert level. In the Edit mode on the MIDI tab - I unchecked ‘Send unassigned MIDI to all Channel Strips’. It was checked before, as this was the only way I was able to get aftertouch working. What I am describing here, negates the need to be passing all MIDI everywhere (which I am guessing is inefficient) In my synth patches, where I had already mapped aftertouch.. they now work, with having the new fader receiving MIDI events. I think the magic here, is you need at least one on-screen control to be mapped to whatever you’re trying to capture (in my case aftertouch). So… it all works now.
  7. My primary keyboard is an Arturia ‘The Laboratory’, which generates channel aftertouch. The aftertouch MIDI messages are not making their way to MainStage. This all works if at the Concert level, I go to MIDI Concert Settings and check the ‘Send unassigned MIDI to all Channel Strips’. Wondering if there is a more explicit way to make this behavior work at the Patch level? I have several synth patches (primarily Leads), that I need to allow aftertouch to work on. I started using a template, that I've been told - one of it's functions gets honked up if I check the ‘Send unassigned MIDI to all Channel Strips’ option at the Concert level. thanks Joe
  8. Oh crap... I sure was! Must... read.... more....carefully - before replying. I thought I had used workstation for one or more plug-ins, and will try to dig up how I did it. Sounds like, I may have had to do manual generation though. Sorry for the diversion guys ... Joe
  9. Aloha Steven - Look at the presets I shared with you. In addition to other soft synths, I used those macros to generate presets for UVI Grand Piano Collection, Cameo, Falcon. Pretty certain I used the method that Des describes to save them. Check out the "Next Falcon and Next Falcon Lower" macros. Those position themselves within the UVI GUI, choosing to move to the next preset. Then - the macro issues a "SAVE AS" command, and from the pop up dialogue executes a Command-A (select all), and Command-C (Copy to buffer) from the area that has the preset name.. That copies the UVI preset name into the copy buffer. Finally - the macro finds and presses the [Cancel] button, closing that dialogue. This macros is embedded in the "2 SAVE a PRESET Many" macro.. which loops through xxx times within the GUI. So - you need to change this one, to call the UVI one (I believe it was set to "Next DIVA Preset" in the macros I sent you. Change that to Next Falcon Preset--- if you want to see it in action) I know it's a little convoluted... which is why sharing stuff like this is difficult. There are a lot of ways of making this all work. It's far easier, when you can stick to just the Logic PRO GUI... but it's definitely possible to screen scrape preset names off the instrument GUIs too. The high level process is: Loop xxx times -- Click within the GUI to select the next preset Select SAVE AS from the Menu Screen scrape the preset name (copy/paste the text) to the buffer Close the Save AS dialogue Save the preset next . . .
  10. This is in the big thread but.. is important. If you're going to generate Logic AU Presets presets for a commercial library and plan on sharing them, please work directly with the developers - and let them distribute the au instruments with their commercial libraries. These AU Instruments can bypass other restrictions on their libs. I learned this, early on from Urs Heckman. I am thankful I asked as he pointed out that the settings from their presets get baked into the au instruments.. negating the need for someone to actually purchase their commercial libraries. Since then, I have been sharing au presets that I generate - but only directly with the developers. I've done this with a few u-he lib developers, and a handful of others. I can probably share the macros I use.. but there is no documentation (short of Des' description of how to approach this). Anyway - I'll post up an export of what I have used, which might be a good starter for someone new to this. Joe
  11. Also... (as long as we're here). There was a recent thread on GearSluz, where a user (@vanhaze) posted up a list of the macros that he has created for Logic Pro. The list is at this location: https://imgur.com/Q9B1VJH . Some good ideas imo. Joe
  12. I'll start. A couple of years ago, user des99 posted up his method of utilizing Keyboard Maestro. I modeled what I created after his approach and consider it the gold standard of how to use KM for turning soft synth patches into AU Presets.. His post is at this location: viewtopic.php?f=8&t=15267&p=623825#p623825
  13. You need an iPad MIDI interface. Without that, youre only going to capture audio from the lightning connector. I use an iConnectMIDI4+ interface, which provides both the audio and MIDI interface to the Mac (which I can see in the Audio MIDI Setup window) from my iPad (as well as other MIDI devices). The connections goes iPad -> lightning connector -> iCM4+ -> Mac. There are other iPad/iOS MIDI interfaces like IKMultimedia's iRig.. but you need something that converts the MIDI coming off the iPAD.
×
×
  • Create New...