6/13/2023 0 Comments Kirnu cream arpeggiator vst![]() ![]() Also note you have no need to mess with the clicks & ports layer! ![]() ![]() Note that you technically only NEED the arp track & final instrument track (to apply the arp to) but I prefer this for maintaining logical flow/structure of my projects. I usually do the first & second and skip the 3rd until I'm ready to 'commit the performance'. Secondly you can record your INITIAL performance (as played, not as heard) into the first track, record any AUTOMATION moves you do with the arp object (changing parameters etc on the fly) into the arp object track, and record the resulting midi data into the destination track. Why do this? Well first off when you select the arp object track you can easily adjust parameters in the inspector window on the left without having to return to the environment. You can also create an arrange track for the arp object itself, meaning you'll have THREE tracks related to the arp now: Create the arp object in the environment and cable the previous midi tracl object TO the arp (that way when you record arm the midi track the arp object gets your playing! And you record the notes BEFORE the arp is applied.), route the arp object to your instrument object (cmd/option click the output nipple and you get a menu that enables you to connect to any object on any other envrionment layer) and go. Never had a problem with the Logic arp here, the problem is that people think in terms of OTHER daws and linear workflows.Ĭreate a simple midi track, this is what you will record arm to get your live playing into the arp.
0 Comments
Leave a Reply. |