jsbaker

1200 plugins x $50 average price = $60,000. Dang, brother!

This was the fix for me. It worked instantly! Give Tom a trophy!!

I've come back to Logic Pro after an extended time trying out Reaper. I liked Reaper but was loseing too much time trying to learn it, and I'm comfortable with Logic. I left off with Version 10.6.0, but have been saving a copy of all subsequent updates up through the current 10.7.9. Before I launch into new projects, I'd love to get opinions on what others feel is the "most stable" recent version (balancing stability with essential bug fixes or added features).

Thanks much. I'll stop trying a multitude of option command shift control combinations! I thought maybe I wasn't holding my mouth correctly.

I have several stereo tracks in a project, and I want to narrow the stereo field equally for each one while maintaining the "center" in degrees. With the Directional Mixer, I can easily set each track with the same settings. For example, 0.0º Direction with a Spread of 0.60. Easy and uniform. I would prefer to use Stereo Pan as it doesn't require a plug-in. However, I am finding it difficult and cumbersome to achieve equal settings between tracks. I've experimented with typing in values, and click-drag at various points in the pan control. Is there some magical way to quickly achieve equal settings as I can do with the Directional Mixer?

This is a vital feature, and its still missing?!!

@MikeShapiro --- thanks for the "save and replace audio" idea, I'm experimenting with it now. So far so good. I've given up on ARA for now.

That's not the problem though - Logic *should* detect new plugins when you run it, without requiring a reboot. But it seems an OS-related issue meant that the component that detects plugin changes fails to do this, so *any* application relying on the system to inform it of available system AU plugins should be affected the same (other, non-system plugin formats don't use the same mechanic, so those VST/VST2/AAX/etc plugins won't be affected the same way). And it's the restarting of this component that is sometimes required (depending on what the newly installed plugin does) - rebooting does it, but do does just killing the audiounit registrar process, which is then restarted and detects the new plugins as expected. So this is a MacOS thing, not specifically a Logic thing, and thus it can't be "fixed" by changing Logic. Hmmmmm. I don't agree. When I click the "Rescan this Plugin" for any selected plugin within the Plugin Manager, it invokes some sort of routine (auvaltool, perhaps) that does an AU scan. So why couldn't Logic simply invoke the same routine for any "unscanned" components while its running? Its a simple matter to check the components folder for new items that haven't been qualified.

No replies, huh? Still digging into this. It's seeming like Logic doesn't support what I want to do. Others have complained in the past. Read this thread: viewtopic.php?t=126288 I'm going to experiment with a different level plug-in to do my automation changes, then use Logic's volume control to adjust all recorded level changes when mixing. It seems like like a simple basic thing. If I can do it with my mouse in the little Trim box, why can't I do the same with a controller or Logic Remote? Bah humbug.

Yes, I find this to be true. But other DAWs don't require this. Why not a "Scan for New Plug-Ins" in the Plugin Manager? Jeepers!!

I still have to reboot to have Logic show newly installed new plug-ins. I'm running the newest version of Logic and Catalina. Why are some reporting they don't have to restart Logic? Is there a solution to this mystery?! Please provide a vaccine.

Have you rebooted your Mac? Sometimes I'm amazed what that fixes. Tried Safe Mode? I'm using OSX 10.15.7 with Logic 10.6.1 and not seeing the problems you are seeing. I suppose you could trash your plist, but I save that for a last resort.

Quote of the day!

Useful info in this thread! Thanks @JakobP