niquekayz

For whatever reason symlinks don't work for plug-ins (though they work for literally everything else in Logic...) It seems they are just hell bent on price gouging people on storage prices and building machines without any kind of upgradeable internal storage, and that's the way it will be going forward ::shrug::

That's unfortunate and seems like an oversight by the LPX developers. I feel like there should be a hack...thanks for your reply, David. It's a huge oversight especially if you've got multiple people working at the same location, all using Logic, and they ALL need their own individual sound libraries -- what a colossal waste of storage space. Honestly, they should just move the whole thing to iCloud. I don't see any downsides to that unless you're air gapped. It would probably save Apple bandwidth in the long run, people wouldn't need to download stuff over and over again and they would only download what they actually need to use at any given time.

I just figured this out thanks to a video tutorial that was posted on YouTube -- I'm using GGD but it's the same for Superior Drummer -- give this a try. Start with a new fresh project, to make sure you've got the procedure down and everything works properly. Then go ahead and try on an existing project. Keep in mind in the video he recommends making an additional "control" track, where the actual MIDI region goes -- which does kind of make sense, this way you can use one track to control multiple drum kit plug-ins...So if you want to use the Cymbals from one plug-in, the toms from another, etc...all that can be done within a single region, from a single track, with labels showing which MIDI notes correspond to which kits. But you don't need to do it this way. You can just ignore that and drag and drop on the main track with the plug-in loaded on it, if you want. It is actually a bit annoying seeing this "control" track in the mixing window. I haven't found a way to hide it. I've gotta say tho -- this is the most convoluted thing lol. Should just be an easy thing to do...just click on the damned label area itself in the Piano Roll and start typing, go up to "Functions" and then save note label template, or something like that. And then just load / save everything from there. Doing it that way would allow customization on each region. Should be no need to go into the MIDI Environment window at all. Very un-Apple like, but that's just my 0.02. And you know what they say about opinions

You're absolutely right -- I just tried it again. I have no idea why -- but the last time I tried this, it didn't do that -- when I dragged the loop onto the timeline it showed a waveform, not the MIDI data! This time, it's now MIDI data I'm going to have to research this a bit more to see what I did wrong originally. It's still bouncing it (for what reason IDK?), but yeah like I said when I drag it back it's MIDI! Maybe it bounces it so it can be played back (previewed) quickly from the loop browser... Sounds like I've got some RTFM time coming up either way tho

I'm a new Logic user, so this might be a dumb question, but I'm looking for a way to be able to recall commonly used MIDI patterns, on the fly. Example -- I want a specific chord, a specific drum pattern, a specific whatever... I'm aware that I can create MIDI patterns (or download other peoples'), export them as MIDI files, and then organize them myself with Finder and then just drag and drop into Logic, or use Logic's import sidebar. But I was hoping there was a more eloquent way to do this...I tried saving some of my patterns as Loops with Logic's built in Loop manager, but that's absolutely _not_ what I want -- it bounces them and saves them as WAVs...I just want the MIDI note data, possibly automation data as well. So I guess my question is, is there any way to use Logic's Loop manager with MIDI files? Or easily save my MIDI regions from my projects that I've already created to Logic's Loop manager without it bouncing them. That would be awesome.

Snap to Relative value is not supposed to be on the grid, it's supposed to keep the same offset as what you're dragging. For example if your region is on 1 3 2 76 and your Snap value is the bar, you can drag that region to N 3 2 76 (where N is the bar number, for example 5 3 2 76). IMO that's not what people are expecting when trying to "Snap" something. Especially when the key command is labeled "Snap to Grid" for a function that does NOT snap to grid when using the default "relative" setting. Apologies for resurrecting an old thread, but as a new logic user, this default behavior was very infuriating. I just figured out how to turn on the absolute value thing about two seconds ago, and it's much better! I agree with David here, snapping is supposed to mean it snaps to the grid points. Not to any other values. That's what the grid is there for in the first place, to keep everything lined up.

Okay, I see now -- I re-read your post. You don't hold down option when you're pasting it, you hold down option while selecting the "proper" automation parameter from the pop-up menu (even though you're already in the right lane!), after you paste it and it creates a mess. Selecting the proper parameter fixes the mess and changes the pasted automation data to what it should've been in the first place. This is still pretty infuriating that it just can't figure this out on its own, but at least there's a workaround! Thank you!! <3

Hi! Thanks for responding, I appreciate it. Even if I am on the same parameter (let's say we're dealing with plug-in automation, the "time" parameter for the "Echo" plug-in), it doesn't work. Holding down the option key doesn't seem to do anything either. When I do that, nothing happens period. Here's what I think the problem is (tell me if I'm wrong)... In the example project I made below I have two tracks, one is an Audio track, and one is a MIDI track, and they both have the same exact "Echo" plug-in loaded on them, with no other plug-ins I see that on the source track (the top one) the "Echo" is in slot 1 On the bottom destination track, the "Echo" is in slot 2 Is that why it's having a fit about this? Please tell me there's a way around this

I'm having a hard time with this! Whenever I copy automation points from one lane to another lane, be it on the same track to a different automation parameter (ie. one plug-in parameter to another plug-in parameter), or to a different destination track, it always wants to copy both the automation points AND the parameter assigned to those points. How can I copy the points just as unstructured data, with no parameter tied to them, other than their node values, so I can make a shape on one lane, select all the nodes, and then easily copy it to other lanes? Looking for some workflow guidance on this one, thanks in advance.

If I had to take a guess, probably something from long ago (where there -was- a valid reason) that was never updated. What I meant was no reason _today_

Two posts above your somewhat late "complaint" I clearly wrote: "The problem with two open projects is that coreaudio is restarted each time when switching projects - this gets annoying pretty soon, especially if one of the projects has loading time of a few seconds or more." That is why. That doesn't make sense though. I've used Reaper for years with multiple project tabs open, and coreaudiod absolutely does not restart every time you switch a project window. There's no "logical" reason for Logic to be doing that (tee hee) In fact with Reaper, you can even have one track (or multiple tracks) playing from one project window, while you record another track in another project window Just seems like a pointless limitation

How is this not just a simple cmd+c on one track from one project and then a cmd+v in the destination project? Why do they have to make even the simplest tasks so complicated haha...

I can't get this to work I did make sure both plug-ins are at the same FX slot in each track (although I don't understand why that should matter...I view that as a bug!) Also the dummy point thing doesn't work either Help?

I just purchased Logic Pro X today and I'm in awe that this isn't the default behavior, let alone something that can at least be enabled... Just checking, since this thread (and others asking the same question) are years old. Is this REALLY still a thing? Coming from Reaper this is like shell shock to me, but AFAIK pretty much every other DAW has this basic feature as well... How exactly are you supposed to line up your comps to your guide tracks...? Honestly I bought Logic for the sound library, I got a MIDI controller keyboard for Xmas, and that part of the app is great, but you can't even load the virtual instruments in other DAWs either, apparently... I'm seriously considering asking for a refund already lol