art_31

I may have found the source of my problem. When I enter the automation mode by clicking on A, it works. When I exit this mode, AQA does not work anymore and remains stuck on the last parameter clicked.

Thank you for your answers. David, "Autoselect automation parameter in read mode" is already selected. Des99, no it's not happening... I have the 10.6.3 version. What is strange is that if I click on edit, the label has the right name (automation quick access), but there is volume as a parameter. The midi controller then only interacts with the volume even if I click on another parameter.

Hello, When I click on yes in automation quick access and I move my controller (mod wheel), it only affects one parameter (the volume). When I click on another parameter afterwards it is always the volume that moves if I move my mod wheel. Does anyone have any idea how to solve the problem? Thank you.. Arthur

Hello to all, In the loop browser, I mainly use untagged loops. Is it possible that when I click on O, the window opens on the untagged loops and not the apple loops? This would save me many clicks per project. I didn't find it in the keyboard shortcuts. Thank you by advance, Arthur

OK thanks David !

Haha I can't help you for that problem !

Hello David and thank you for your return, Even selecting a parameter from the menu does not work. I can automate in READ mode or if I assign the button to a macro, but not in Latch, Touch or Write mode. A line appears, with a second dot where I start moving the parameter, but no automation is recorded. Just a straight line. This works very well for my other plugins though, so I'm sure I'm doing the right thing. Arthur

Hello to all, When I want to use latch or touch in logic pro, it doesn't work for some plugins (diva and serum). (It works for others.) A line appears with a dot but nothing happens afterwards. I tried the solution proposed on another post, to delete the files in library com.apple.logic... but it didn't change anything. If I assign a macro, it works on the other hand. But it is not practical. Has anyone ever had a similar problem and managed to solve it? Thank you all and have a nice day! Arthur

Ok I understand better, thank you for telling me the solution!

Thank you very much David for this quick return. The start of my project is at -7,1,1. I leave room for a pre-intro. I have just tried to remove the pre-intro and export the midi again, indeed it works well this time. Do you know why? So the start marker should always be at 1,1,1? (I specify that in spite of the pre-intro, my region with the midi started on 1,1,1) Have a nice day, Arthur

Hello, When I export a midi file from one Logic Pro project, and import the midi file into another project, only half is inserted. The other half appears as a heap of notes at the beginning of the region. Anyone have any idea how to solve the problem? Thank you for your help!! Arthur