Recording Automation from M-Audio Oxygen Pro Faders

Yep, I’m in preset mode and Automation is enabled for recording. I verified that the sliders work for native plugins and automation is recorded correctly.

In the time since I posted my question, I found this page, which helped me set up connections for SWAM using Current Project -> Generators -> [SWAM instrument here]:

https://www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/recording_automation.htm

However, Last Tweaked does not work for Kontakt 7, and the project parameter browser can be very unclear depending on the instrument involved. It looks like there is a list of a couple thousand parameters that always exist when looking at Kontakt 7 and simply get renamed depending on what instrument is loaded. For example, a violin instrument renames parameter #1 to “Expression”. If I set up a link between #1 and a slider, then change it to a guitar, parameter #1 is renamed to “On/Off” (which turns the guitar’s native distortion plugin on or off) and the connection persists, so I cannot set up global links for individual Kontakt instruments. I can set the Input Port in FL Studio’s options for the plugin window to the correct port and then use Kontakt’s internal “learn” function to automate any parameter, not just those that are listed in FL Studio’s browser, but if I do it that way, then FL Studio does not record automation for that slider or knob.

Any ideas? Or will I just have to set up the connections manually in each project for Kontakt 7 with the “Current project” browser?

To be fair, that particular issue isn’t unique to Kontakt – FL Studio won’t record automation for any third party plugin where I attempt to use the plugin’s “learn” function if I’m trying to link something to anything other than the mod or pitch wheel.

That said, setting up local project links for Kontakt will work. It’s a minor annoyance, but bearable.

Thanks for taking a look and for your hard work in general!

Yes, tweaking the slider inside Kontakt doesn’t work, but you can still find the parameters in the parameter browser and map it by clicking on the multilink button, manipulating the parameter in the browser, and then tweaking the slider or knob you want to bind to that parameter. For SWAM (which has a separate plugin for each instrument), global links work fine (as it’s okay for them to persist), but for Kontakt, project links will have to suffice.

The reason it’s important to me is that I like working with stringed and brass instruments, which can benefit from recorded play and automation to add a human touch. I find it’s usually faster to record automation for a section than going through and trying to manually add articulations that feel organic.

Oh, it’s a line of virtual instruments. Physical modeling instead of sampling. The acronym stands for “Synchronous Waves Acoustic Modeling”. I haven’t had them for too long but my experience so far is that they’re a lot more flexible than an average sample library, but it takes a little more effort to make them sound convincing. https://audiomodeling.com/swam-solo-instruments/ Demos: https://www.youtube.com/playlist?list=PLT7gu1yXoV4H-cq5oZQNpJG9HPLyFXP4-

There are other companies that do physical modeling – Sample Modeling does some kind of hybrid, I think, and Pianoteq is a modeled piano.

https://www.samplemodeling.com/technology/

https://www.modartt.com/pianoteq_overview

I own Pianoteq, but not Sample Modeling’s libraries; Pianoteq is amazingly flexible. You can modify the piano you’re (virtually) playing with all the tuning techniques you’d use on a regular piano, set up to five microphones of various kinds, orientations, and distance from the instrument, and modify lots of other parameters to get the exact sound you want.

One of the things I like about physical modeling is that if two people use the same sample library, their instrument will probably sound pretty similar, but with a modeled virtual instrument, you can really make it your own.