I guess those connections only happen behind the curtain.
Maybe there is a way to adress these parameters via midi cc and manipulate the messages via lfo? By the fact that my scripting skills are very low, I'm still not able to imagine such connections, let alone put em into action.
@gorangrooves sometimes you need different mute at any place, not particularly for muting a sampler, but when you want to interact with different routings.
@d-healey yes, but just cut the signal is enough, no need to set the gain knob to 0, it can stay where it is, but mute the audio path anyway
@thedrumdrive Yes of course you can use your GUI elements such as: image files and vectoral graphics. Just search this forum, you will find lot's of useful things... ;)
@Christoph-Hart Yea it has to learn which samples to keep which can often cause dropouts the first time you play. The only advantage I can think of would be that you don't have to unfreeze to make edits. So it allows you to work with live tracks a bit longer before running out of memory and start freezing tracks.
It is pretty much just a convenience thing until you run into CPU bottlenecks and are forced to freeze tracks anyway. 🤷
maybe just renaming the function by "CC" learn than "midi" learn.
Most of time this function is used to control via CC (keyboard controllers has CC buttons and/or knob - as my UMX-610) but it's controlled via MIDI out/IN.
Yeah - sort of.... but no nice favourites processing and only two columns - as I said I could build my own and it would likely use a viewport or two, but then... see my first post here..
