read through this a bit and am not sure if it's relevant to what i'm seeing/hoping for or not.
I'm hoping to send one velocity tracker to a hydra and then the output of the hydra to multiple different LFO resets.
i'm not dead in the water because i can just make multiple velocity trackers and use them 1:1 on the the different LFOs, but i was hoping to do tracker->hydra->lfo1, lfo2, etc.. to keep things a little cleaner.
so... that doesn't work.
Why doesn't this work? I don't understand as there is no problem doing what you explain here., you may very well control resets of different LFO's through a hydra with any tracker device.
in a way it seems like the hydra only sends an output to downstream DSPs when there is a change in the value of the hydra input.
No, the hydra can send to any DSP, but the signal follower can't send to DSPs that is processed earlier in the chain or tracks to the left. You may however use a hydra in between and then it suddenly works for some reason, don't ask me why.
if i send key tracker output to the hydra, and then hydra to lfo reset, it *will* reset the LFO loop position according to the notes i play, as you'd expect, however it only does that if a note is *different* than the previous one.
No, the key tracker resets at any input, if the note is the same as the previous one it should still reset to that same position as the last note input. I suggest you take a look at this: http://forum.renoise...lope-generator/
It's set to reset every note to point 0, every note input will reset the LFO to it's start point and is set to play the envelope once and then stop at point 64. It works excellent for ducking and also the opposite
in other words, if i do key tracker -> lfo reset, and hit the same note over and over, i see it reset the LFO loop each time.
if i put a hydra in the middle, i only see the lfo reset when i play a note that is different than the last one.
You do it the wrong way around, you need to make it Key tracker -> LFO Reset -> Hydra -> LFO/LFO/LFO/LFO
this would seem to imply that velocity tracker would work in the same way, sending the reset downstream only if the velocity of a note changed.
Only the signal follower has this limitation, it actually makes sense because how can you follow a signal that is constantly changed by that same signal follower?
is this known / expected / working as designed / not a bug / EWONTFIX kind of thing?
This is actually a non existing problem as far as i can see, i don't really know how you came to all your conclusions.
If you tell me what exactly you want it to do i can probably make a chain for you.
Edited by TheBellows, 24 May 2017 - 16:37.