Hello Forum,
i havn’t been around here for quite some time. i’ve just been migrating back to Renoise after a couple of years hardly using it and i absolutely fell in love with the new meta-devices. exactly the level of modularity i can deal with - lots of creative freedom but user-friendly so i can get stuff done instead of just noodeling around…
anyhow, i checked through some device chains people posted here making creative use of the meta-devices. impressive stuff, got my head ticking! i build a couple of chains myself (most of them involve vsts so i cant put them up here), but here’s one i’m working on atm that needs a workover i can’t get done:
its an LPC-synced LFO that reacts to note-input. depending on what note is triggered it swings at different beat-synced rates, e.g. LPC 1 on one note or LPC 4 on another. have a look at the xrns, you’ll get the picture…
i can see a lot of things this could be usefull for, like beat-sync modulating
- track volume for gate-like effects
- filter cutoff (like i did in the demo i posted) for wobbly basses
- treshold of a compressor for rhythmic pumping effects (did that in the demo as well)
- send levels for blending from one effect to another at different rates
- or (using a a square-wave) changing from one track routing to another
- …
this i just from the top of my head. i’m sure there are lots of other creative ways to use it.
now to my problem: i use a custom envelope LFO to trigger the several LPC-values of the other LFO(1). dblue’s note-tuned ring-mod got me to that idea (kudos man!). problem is i cant draw in the right values for most LPC-rates in the envelope editor - i mostly get broken values like 15.37 or something and that makes it rather useless for most things i mentioned.
dblue mentioned he wrote an xml(?) patch for his ringmod frequencies and copy/pasted the right values into the custom env LFO. and thats actually what i need to make this device proper i think. so if dblue or someone else equipped with coding magic could help out with the right envelope values for the custom LFO that would be great!! i think this device really has the potential to be very useful for everyone if its done right!
i thought about what values would be most usefull. i think its a good idea to keep the number of different values small to prevent it from getting messy - two octaves=24 values should be enough. for small values i’d like a higher resolution (like one value for every LPC-rate), for greater values only having prominent (aka beat-sync) rates like 64, 128, 1024, … should be enough.
heres a mockup i came up with:
C3 - 2048 LPC
C#3 - 1024
D3 - 512
D#3 - 256
E3 - 128
F3 - 96
F#3 - 64
G3 - 48
G#3 - 32
A3 - 24
A#3 - 20
B3 - 16
C4 - 14
C#4 - 12
D4 - 10
D#4 - 8
E4 - 7
F4 - 6
F#4 - 5
G4 - 4
G#4 - 3
A4 - 2
A#4 - 1,5
B4 - 1
this is of course personal taste and debatable.
so to make a long story short: if someone could make this happen that would make me a happy roach!
regards,
Jan