Chipp Tate

Thanks for your help oscwilde!

Thanks for the quick reply. You've answered all my questions clearly and concisely, and I believe you verified that nothing shown in Smart Controls is above and beyond anything that's been done in the plug-ins that would affect the sound of the track - correct?

I know Smart Controls are a popular feature, which is fine, but I prefer to use plug-ins because they have everything I want in one place. I've been working that way in a long-form project when I accidentally opened that window and noticed a switch turned on, which was surprising since I've done nothing with those on this project. So to start with I have a few questions: 1) It's my understanding that Smart Controls can be mapped and customized for specific effects. Is it possible that I'm seeing the result of default mapping that reflects something I've done in a plug-in I've been using? 2) I use the space bar for start/stop and accidentally open the Smart Controls window with some regularity when I miss and hit B. Could opening that cause an active plug-in to be mapped? 3) Is there a way to keep Smart Controls off, or defeat their mapping so they're only on when and how I want them to be on? Thanks, Chipp

YES!!! That does work! Thanks, David, sorry about missing it the last time around. And now I know why there are so few complaints about this elsewhere.

I've known about and tried Command/Hold/Drag to improve vertical resolution, and it sometimes seems to help. I'm not familiar with Option/Hold/Drag for that and when I tried it yesterday it didn't seem to change anything. But... I'm still in need of a way to make accurate vertical edits easily and quickly. It may not be a fair comparison but I used AutoCAD for work and never had any problem getting those values to go where I wanted quickly and easily. So, David... If Logic can't do that, and I'm entirely pleased with it other than that, I'd like to ask if it might be possible to add a feature that could set the 0.1db resolution to increments (maybe even specified), like +/- 1.5db starting at 0. That would actually reduce the resolution and seem to make it easier to use. That would also make it like some of the Compressor adjustments that are in larger fixed steps. Thanks, Chipp

Hi oscwilde - I forgot to mention in my post that I'm aware of Hold Command (not Option - which does not work at all) when making these edits. And Hold Command does help - sometimes - but not consistently enough to make it worth the extra effort - or distraction - it takes to use that. I appreciate you reaching out and trying to help, but I'm looking for a permanent reliable solution to this, and think a modification to the mouse pointer interface may be required.

I've been dealing with this since I got Logic Pro, but a new Logitech MX Master 3S mouse (with DPI control) seems to have eliminated hardware as the cause of it. I'm writing to ask if my understanding of this problem is correct, and what, if anything, may be done about it. When I try to set and adjust an automation point for Gain, Volume. etc., I cannot get a continuous series of values in 0.1db increments, and I can (almost never) go straight to the value I want. It's not that it can't/doesn't happen, but it typically takes at least 3 attempts, and oftentimes more, from each direction, to get a series of numbers that includes the value I need. And that's taking far more time than it would if it worked as needed the first time. The number series that's provided varies each time I release the point and start again, and looks exactly like I've been dealt a poker hand with a random/variable sequence of values. Past experience suggests the resolution of that sequence depends on the zoom setting of the track, where larger provides more choices, but fully zooming the track will not solve the problem. I'm working on a project that requires a lot of adjustments to individual tracks to correct problems in the gain structure due to the way it was recorded live. Doing that works well in 1.5db increments, and those make it easy to accurately adjust tracks that need to be edited later. Please let me know if I'm missing something here that could provide the resolution I need.

Thank You, David!

Is there a way to monitor memory levels in use or see if there's been a recent shortage of memory?

I can't say I found a fix, but when I had time to come back to it later, I did find that I was not having that problem in other regions in the same track, and wondered if the difference were extensive cut/paste edits in the song I was working on where I had that problem, which is part of a continuous show recording that's over an hour long. I should also say I'm not the most experienced LP user on this Forum.

After catching up on other work I came back to compare the vocal track I was trying to correct with another. The 1st hangs up repeatedly with the least amount of mouse or keyboard input, making it impossible to use Flex Pitch. The 2nd does not hang up at all. In both cases I turn on Flex Pitch within the editor, thinking that may help. The 1st track's had a lot of cut and paste editing done to it, if that may have anything to do with this.

I reboot at least daily overnight, but I've been doing that a lot more often recently to see if it would fix this. And everything is on the same drive.

I've been using Flex Pitch more often recently where Logic becomes unresponsive per the spinning pinwheel and the Activity Monitor, which shows no Memory Pressure issues. On some tracks it happens occasionally and clears, but a lead vocal track is impossible to edit that way. And this is only in Flex Pitch. Everything else works fine. I have a MacBook Pro M1 Max w/64 GB of memory running Ventura 13.5.1 and Logic 10.7.9 Thanks, Chipp

OK - I'm impressed. X-Gate, Native Channel Strip 2 and Native Bus Compressor 2 all appear in Plug-In Manager and open as expected. When I first opened X-Gate after getting ChanStrip2 validated the image was a bit unsteady (kind of flashing?). But after rebooting it's all rock solid now. I won't take the time to explain everywhere I've been on this adventure other than to say I did reinstall Monterey to fix unusual behavior after the ~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache surgery. And nearly all of this trip was due to my ignorance of things Apple until I got Logic and my new MacBook Pro last fall. So Thank You des99. Logic Pro Help is a great resource and you have proven again to be a great Moderator! Chipp

Yes, that is what what I'm saying and I will try the Rosetta trick soon.