velanche Posted February 5 Share Posted February 5 Hey Folks: Once again, what sounded like a good idea is hampering me, and I'm not sure where the disconnect lies. I saw a video on YouTube earlier that demonstrated real-time automation, and it was demonstrated that once a feature called Automation Quick Access was enabled, with a hardware nap (in my case, the knob from the KORG NanoKONTROL Studio), I can confirm on a selected track with automation that it works with Volume, which is the default. Then I have "Autoslect Automation in Read Mode" also enabled, which allows me to select a parameter in a plugin or on one of the Smart Controls. While the parameter is selected, I am getting mixed results. Sometimes the parameters will move; other times, they grey out and I have to remap the knob in order to use it again. I am also aware that apparently, the KORG NanoKONTROL Studio can be glitchy. It's honestly my first time using it in Logic, but I'm very keen on using the large jog wheel for real-time automation when I'd like to use a knob. All of this is to say that I'm not sure if what I'm experiencing is a function of the controller, or of choosing a different parameter, where the same automated knob should still work despite the parameter change....or at least that's what I thought it should be. What say you? Thanks. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 5 Share Posted February 5 (edited) Not to sure to understand your issue. AQA used to work reliably with NanoKontrol (old model). And is also reliable with Mackie MCU Pro and/or C4 controllers. The selected parameter to automate will be the one to react to the AQA assigned controller (knob, fader, slider, etc). Otherwise it defaults to volume. Edited February 5 by Atlas007 Quote Link to comment Share on other sites More sharing options...
velanche Posted February 5 Author Share Posted February 5 @Atlas007 Yes, I do see Volume is selected for the NanoKONTROL and then I can control it wiht the jog wheel, but when I click on another parameter wiht "Autodetect Autiomation," it shows the parameter I cliick on, oddly looks as if it's greyed out, and more often than not, the jog wheel has no effect. I then have to go to AOA again to remap it, so I'm sure that something is not right. I'm just not sure why it consistently does this. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 5 Share Posted February 5 (edited) If you try with another controller (besides the jogwheel), how does it go? (I would suspect the problem being the use of the jogwheel, which sends some kind of data that Logic’s AQA doesn’t like). What does the Korg nano’s jogwheel sends as MIDI data? Edited February 5 by Atlas007 Quote Link to comment Share on other sites More sharing options...
velanche Posted February 5 Author Share Posted February 5 7 minutes ago, Atlas007 said: If you try with another controller (besides the jogwheel), how does it go? (I would suspect the problem being the use of the jogwheel, which sends some kind of data that Logic’s AQA doesn’t like). What does the Korg nano’s jogwheel sends as MIDI data? I opened up MIDI Monitor, and the cogwheel is outputting "Controller 86" as data. I quickly just moved a couple of the faders on the unit, and they. have different data results, and I think that could be how they are mapped by default because I have neither not mapped them or used MCU with it. Logic does recognize it in the Inputs tab of MIDI Preferences. I did it really quick here; juggling some things at home. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 5 Share Posted February 5 6 minutes ago, velanche said: Logic does recognize it in the Inputs tab of MIDI Preferences. I did it really quick here; juggling some things at home. Have tried deactivating it from in there? Or perhaps using a different Nano’s Scene? Or remapping it via the Korg Kontrol Editor app? Have you installed the Korg nano driver? Korg’s nanoKONTROL Studio‘s download support page. Quote Link to comment Share on other sites More sharing options...
velanche Posted February 5 Author Share Posted February 5 4 minutes ago, Atlas007 said: Have tried deactivating it from in there? Or perhaps using a different Nano’s Scene? Or remapping it via the Korg Kontrol Editor app? Have you installed the Korg nano driver? Korg’s nanoKONTROL Studio‘s download support page. Funny thing was...when I looked in the Input area yesterday after the lack of response from the cogwheel, and bear in mind that it's the first time I used it with Logic, it was initially grayed out and unchecked. I have since checked it, in hopes that things would improve. I have not installed the driver; I wasn't aware it was needed, if Logic had found it. I do note that the NanoKONTROL Studio is not on Logic's CS list, though a couple of other non-Studio versions are. I will give that a try. I have done a Google search yesterday, and apparently there has been issues with the use of the editor. But if it comes to it, I'll give it a try. Really, all I wish to use is the jog wheel; I have other controllers that I use for most everything else. Thanks much! Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 5 Share Posted February 5 (edited) 7 minutes ago, velanche said: I have done a Google search yesterday, and apparently there has been issues with the use of the editor It could happen that googling about something will reveal more of an aspect than the entire picture. I found out that often the problems are more prevalent to show up, especially when attending forums. Which I find foreseeable, since people will resort to same in search for a solution to an arising issue (rather than just posting their contentment about a gear or software)… Anyhow, please keep us posted… Edited February 5 by Atlas007 Quote Link to comment Share on other sites More sharing options...
velanche Posted February 5 Author Share Posted February 5 7 minutes ago, Atlas007 said: It could happen that googling about something will reveal more of an aspect than the entire picture. I found out that often the problems are more prevalent to show up, especially when attending forums. Which I find foreseeable, since people will resort to same in search for a solution to an arising issue (rather than just posting their contentment about a gear or software)… Anyhow, please keep us posted… I've actually gone down that "Googling" rabbit hole last night, checking and querying several places. Usually, I get an answer from somewhere, though it could take an hour, a day, a few days, or maybe longer. Most of the time I do get them that leads to a fix or workaround, but not always. So with that, KORG has posted as I was reading the system requirements that it recommends the use of Apple's standard drivers in place of its own, which seems to have halted with macOS Catalina. The editor apparently will work with Apple silicon, but I'll see if it'll be of any use. More later....maybe. 1 Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 5 Share Posted February 5 17 hours ago, velanche said: Sometimes the parameters will move; other times, they grey out and I have to remap the knob in order to use it again. Exactly what gets grayed out ? Could you post a screenshot ? Do you mean you have to go to Logic settings and "relearn" the knob to AQA ? Quote Link to comment Share on other sites More sharing options...
velanche Posted February 5 Author Share Posted February 5 6 minutes ago, JakobP said: Exactly what gets grayed out ? Could you post a screenshot ? Do you mean you have to go to Logic settings and "relearn" the knob to AQA ? I'll follow this up, either tomorrow or Tuesday, and you can see it. I mentioned "greyed out," but the color has changed and has gone lighter. It's like an opaque shade of blue than the solid yellow color. Quote Link to comment Share on other sites More sharing options...
velanche Posted February 7 Author Share Posted February 7 After giving it a rest for a day or two, I decided to return to this issue with a fresh perspective. I am now convinced that there's a disconnect, but I'm unsure what that is. The reason why I think this is because on three....THREE....different controllers, the same behavior happens. I would enable Quick Automation, move the parameter (usually Volume, which is the default), test it, works fine. But add "Autoselect...Read Mode," I click on a parameter on a Smart Control or a plugin, the name of the parameter changes. But when I move the mapped device, visually in Logic there is no movement. It's as if the "Autoselect" function breaks the quick mapping. I am planning to contact Apple in a bit, in hopes of getting some clarity. I'll share my results here. I do hope that it's not one of those "Did you delete your presence file" thingie, because doing that is last-resort and usually disruptive because then I'd have to rebuild what was lost. Also, I've read that others with similar issues have tried it, only for the issue to persist. All for now; more later. Quote Link to comment Share on other sites More sharing options...
Solution velanche Posted February 8 Author Solution Share Posted February 8 Okay, so I spent some quality time with Apple Support. One tech tried helping me and ran into similar issues, and bumped it to another tech. We found out that the second part, "Autoselect...Automatoin in Read Mode," works when an instrument or effect parameter is click ON ITS UI. Not only does the name of the parameter appears, but turning the knob/fader/whatever moves the automation. The bug is Smart Controls. Click on one of the parameters there, the parameter's name can be seen, but that seems to break the automation because turning that knob or fader has no effect at all. So in case anyone runs into a similar issue, know that you need to click directly on the instrument/effect button/knob/control, not a Smart Control. Hopefully, Apple with fix it. This is going to be potentially a great workflow enhancement, so glad to get that sorted. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 9 Share Posted February 9 @velanche: Thanx for keeping posted! Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 9 Share Posted February 9 I can confirm that AQA doesn't work at all with Smart Controls here either. Selecting a SC parameter on the track seems to assign "random" parameters to AQA. Take the audio patch "Bright Vocal" as an example; when trying to control the "Compression" SC with AQA, my AQA knob get assigned to "Channel Format", so when twisting the knob, the channel strip goes from mono to stereo to left input to right input 😄 Trying to use the next SC knob in that patch, learns the AQA knob to "Channel Input" etc... Very buggy 🙄 1 Quote Link to comment Share on other sites More sharing options...
velanche Posted February 9 Author Share Posted February 9 @JakobPI did see in the Controller Assignments “Channel Input” while stuck trying to troubleshoot, but I did not knew, and still don’t know, what it means, so glad you’ve given some clarity on its buggy behavior. I am also finding “Autoselect Automation Parameter in Read Mode” also buggy with Sampler. I have not gotten this nailed yet, but I tried some third-party instruments whose parameters did not work, and some first-party ones that did. I was really quick on that, so haven’t had time yet to dive deeper to see if there’s a pattern. The Apple tech I was working with noted that if the names were in orange, I noticed that it did work. When it was in a dim blue color, sometimes yes and sometimes no. I have not read, for instance, if there’s a color that represented a Smart Conrol parameter, even if I clicked directly on the instrument’s UI instead of the Smart Control UI. I need more time on that. I hope to eventually take some info from here, and maybe from you too, and send to Apple for feedback. Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 9 Share Posted February 9 I don't use the "Autoselect in Read mode", it's jumping around parameters makes it a bit annoying imo 😄 I just set the track in Touch or Latch instead, then wiggle the plugin knob I'm interested in... I tried it a bit in Sampler and it seems to work here... The "Channel Input", "Channel Format", "Select" (the Filter1 Cutoff in SC assigns AQA to it) are all control surface functions, i.e. they are normally not accessible unless you have a control surface installed, but this seems to happen also with a fresh cs preferences file, no control surfaces installed... It's weird... Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 10 Share Posted February 10 (edited) Just tried using AQA controlling the Sampler Smart Control "Env 1 (amp) Attack", but instead it gets assigned to "Automation Mode", so when you think you're recording automation it suddenly goes to off, or gives you the "Write Mode" popup. This is with a totally fresh cs preferences file... Edited February 10 by JakobP Quote Link to comment Share on other sites More sharing options...
velanche Posted February 10 Author Share Posted February 10 @JakobP Buggy buggy buggy! Way to potentially kill one's creativity. Thanks for trying it out; it'll help, when I do that feedback with Apple in the coming days. I hope eventually, this all will get cleaned up. Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 11 Share Posted February 11 21 hours ago, velanche said: I hope eventually, this all will get cleaned up. In next release perhaps, who knows... 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.