![]() Now I noticed that my Access Virus TI will control the plugin but Logic will not record automation any more from knob moves on the desktop unit. I have to quantize the regions separately or go into note editor. Midi info is un-quantized when played into Logic even if the dialog box is set to a quantize value. Latest version of Logic 10.4.6 Serious Midi/Automation Flaws First I noticed that setting the quantize in the dialog box on the arrange page does not work. ![]() I've made a screen capture of this behaviour to try and demonstrate what I'm talking about. Working, as exoected when disconnecting the midi interface on the Knob on the software) while all the other knobs and faders stopped That the "rogue" knob still acts weird (affecting another unrelated Tried disconnecting the interface on Logic's environment, andĬonnecting it to a midi monitor, to see what happens. I contacted Arturia's support, and they kindly guided me through resetting the definitions on the Kelyab and on the plugins.Īt the end of the process, i.e following Arturia's suggestions, I still get one knob not working properly. In Logic however, some of the knobs stopped controlling the corresponding knobs on screen. Standalone, or either as an AU or a VST inside Ableton Live, everything Things further, it should be noted that when launching Analog Lab V as a (5) included, I started experiencing problems. Was working perfect for me with Analog Lab 4, but recently, afterĪrturia released the new version of the V Collection, with Analog Lab V Keylab Essential, and especially the meta-plugin, the Analog Lab. ![]() Very intuitive and a lot of fun to control the Arturia plugs with the I have Arturia's V Collection and also the Keylab 61 Essential. This one is a bit complicated to explain, but I'll try.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |