I figure the memory effect of the values in impulse’s implementation of tremor could be discarded in favor of adding more functionality to the vst.
The effect should disable itself every beat unless it is receiving a value. Every row the effect is enabled, it keeps a count of the current “ticks” on or off it needs to apply. This makes for an interesting question in how renoise handles it’s data internally. If a value in a pattern command stays the same, does it send an update of the same value, or is the value ignored?
The effect would also need to have a setting which may be matched to the ticks-per-line if desired. This will be how the vst’s tempo sync will divide each beat / each division being a “tick”
There is still a lot of play in how it could best be implemented if anyone has any thoughts.
It may be interesting to expand on it as well. perhaps it could be a filter rather than an amp, and the slope of the cutoff could be adjustable.
My inspiration behind this was spending too much time trying to precisely emulate tremor with a series of LFOs and a single column of pattern effects.
I find it a bit odd that renoise requires reset commands to keep the LFO in sync with the tempo when using pattern effects to control it; also that built-in effects like the screamer and filter do not allow note specific frequencies to be sent to them via pattern commands or any method. It is issues like those that make me resort to VSTs which is the last thing I want in a tracker.
Lots of older effects were based on the old speed/bpm timing engine. The engine got bpm accurate yet for some effects it still remains cumbersome to get a good synced situation unfortunately. It will eventually all be polished up, but one step at a time as it is currently going…
Sorry, I didn’t checked it if the conversion went 100%. I exported the ODS as .CSV equivalent (using enclosing quotes though!).
Google Docs is far from perfect. It claims to support various file-type including .ods, but the only way i could upload a file to convert without errors was CSV format.
Inspecting the CSV file, it lacks enclosure quotes in the last two columns on a lot of rows, so there is probably also something fishy with the column value format of the last two columns.
I guess the google-doc converter ignores quote enclosures when reading a “comma” within a quoted value. This is a typical classic CSV conversion error and usually a common programming mistake made by all level-type of developers.
Anyway, the big pro of google docs is that everyone can view and edit it in a web-browser without having to open up any specific office environment.
The video you linked to in the original post seems to be gone. Care to re-enlighten us on what you’re trying to achieve here? (A quick Google search didn’t help me)
I imagine that this effect could be accomplished with some combination of LFOs and Gains (or filters as you mention above), but it would be quite unwieldy.
Yes easily and using points mode in the automation envelope frame on the LFO parameters you can change the ranges as well.
But if one wants to use pattern Fx commands, then simply changing the LFO parameters from within the Effect column is the closest thing to this effect.