@ffx: you’re referring to the tuned shortcuts, I guess?
There also is an “endless feedback” problem in Renoise’s current implementation of observing VST parameters. While writing automation, the automation values are sent back to the vst, so the vst parameter observer will trigger again, which writes again automation etc. etc. Stuck in an endless loop. This should be prevented internally. Also vst plugins may round the value, so the sent in value and sent back value will differ. It is not possible to filter this out by checking for same values. I would define the following problems/thoughts about it, that should be fixed (IMO):
Oh, I remember that we talked about this. The “xAutomation” approach I’m using now is simpler than it used to be - I ditched the “latch mode”, it now has only two modes: “punch in” and “interleave”.
But with plugins, indeed that particular thing (rounding) might still pose a problem, I dunno… I say, let’s investigate
coll, it might finally be time to get my head round this… prospective gear I have includes:
Novation Remote SL
Stanton SCS3 (WEIRD Ribbon thing!)
Launchpad is definitely plug and play. It has a lot of “configurations” ready to go.
And it would be awesome to (finally) get the PadKontrol into the family. I’ll revisit this thread from 2014:
As for the Stanton and Remote SL, they were missing from thelist of controllers. I’m sure we can get something running. But I own a Novation Remote myself, the SL-MKII model, and it’s great quality (hardware) but the LED feedback via Automap/MIDI is unfortunately not 100% working. I even contacted Novation to let them know of the issue.
So I’m pretty sure that the first model fares equally well. Which means, great because you’ll most likely be able to record precise automation, but anything beyond that (bi-directional communication) is a bit unknown.