shnaps52 Posted September 21, 2023 Share Posted September 21, 2023 First off - I am using Logic Pro X 10.4.2 - because I don't want to go thru process of buying/updating the 64-bit plug-ins. My issue may be present in the latest version of LPX. The sounds of one of the plugins is not mapped correctly - e.g. note D generates F tone. To overcome this, Initially, I isolated the MIDI track with just that note and inserted Apple's Pitch plug-in; shift the pitch by -300 cents in the plug-in interface. However, later discovered that I need to shift the pitch up by +200 cents. Rather than creating another track (with the new note) along with another instance of Pitch plug-in, I tried to automate the Pitch parameter. Usually, the automation parameter values are changed by dragging the value up/down - but the cannot set the value to the desired number. The value resulting from dragging operation jumps and could not set to exact value (e.g. -300 or +200). Is there a way to enter the exact parameter value on the automation line? Many thanks. Quote Link to comment Share on other sites More sharing options...
polanoid Posted September 21, 2023 Share Posted September 21, 2023 You'll get a finer resolution when you hold the Ctrl key while dragging 1 Quote Link to comment Share on other sites More sharing options...
Solution polanoid Posted September 21, 2023 Solution Share Posted September 21, 2023 (edited) I doubt that you can set it to 200 though as the value seems to change by steps of 24 cents, which would be a limitation of the plug-in, not of Logic Edit: Just tried with Ctrl key held and I can adjust the value in the automation line by tenth of a cent it seems. There's no way to enter the value of automation nodes by keyboard though. Edited September 21, 2023 by polanoid 1 Quote Link to comment Share on other sites More sharing options...
shnaps52 Posted September 21, 2023 Author Share Posted September 21, 2023 7 minutes ago, polanoid said: I doubt that you can set it to 200 though as the value seems to change by steps of 24 cents, which would be a limitation of the plug-in, not of Logic Edit: Just tried with Ctrl key held and I can adjust the value in the automation line by tenth of a cent it seems. There's no way to enter the value of automation nodes by keyboard though. Sounds very easy. But when I press the control key in the automation line, I get a context menu! Quote Link to comment Share on other sites More sharing options...
des99 Posted September 21, 2023 Share Posted September 21, 2023 (edited) 7 minutes ago, shnaps52 said: Sounds very easy. But when I press the control key in the automation line, I get a context menu! That sounds like you're pressing the control key *before* dragging or clicking on the node, not *during* dragging (ie after clicking on the node). Edited September 21, 2023 by des99 2 Quote Link to comment Share on other sites More sharing options...
shnaps52 Posted September 21, 2023 Author Share Posted September 21, 2023 4 minutes ago, des99 said: That sounds like you're pressing the control key *before* dragging or clicking on the node, not *during* dragging (ie after clicking on the node). Yup - that's the trick! Click, press Control and drag - worked perfectly!! THANKS - a very quick resolution. 1 Quote Link to comment Share on other sites More sharing options...
des99 Posted September 21, 2023 Share Posted September 21, 2023 You're welcome! Quote Link to comment Share on other sites More sharing options...
Richard Herczeg Posted September 22, 2023 Share Posted September 22, 2023 6 hours ago, des99 said: That sounds like you're pressing the control key *before* dragging or clicking on the node, not *during* dragging (ie after clicking on the node). Thanks des99. I've been making the same frustrating mistake too. 1 Quote Link to comment Share on other sites More sharing options...
envlpx Posted September 22, 2023 Share Posted September 22, 2023 Another option is to open the track automation event list (control-command-e) and type the value there. The problem is that while the automation lane will use appropriate types like dB, the track automation event list will always use midi values, from 0 to 127. Still, you can click on the value on the event list and drag it up or down. Maybe it'll be less annoying than doing it on the automation lane. Quote Link to comment Share on other sites More sharing options...
polanoid Posted September 22, 2023 Share Posted September 22, 2023 3 hours ago, envlpx said: Another option is to open the track automation event list (control-command-e) and type the value there. The problem is that while the automation lane will use appropriate types like dB, the track automation event list will always use midi values, from 0 to 127. Still, you can click on the value on the event list and drag it up or down. Maybe it'll be less annoying than doing it on the automation lane. The resolution is much more coarse then, and you will have no direct visual feedback of the value as it is displayed in the plug-in itself (instead it will always be an integer value between 0...127) so I doubt you will be able to set e.g. exactly 200 or 300 cents for the Pitch AU like that. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.