Hive free running LFO
-
- KVRian
- 814 posts since 18 May, 2007 from Berlin
Try switching the LFOs restart mode from "sync" to "single" and see if that does what you need it to do.
Cheers
Cheers
-
- KVRian
- 814 posts since 18 May, 2007 from Berlin
The OP specified "independantly of any gate input that would restart it", so I take it that's his main goal here, wether or not the LFO is actually always running in the background uninterruptedly, regardless of what happens around it.
It's not, of course, but the OP did specify one aspect of what they're looking for, and I focus on that.
Depending on the OP's use case, restart modes "sync" or "single" can feel like free-running LFOs. We don't have enough details to determine that yet.
To quote the user guide:
"Single - All voices share the same LFO, which is restarted at the next MIDI note after all previous notes have been released."
So there's a phase restart between "no notes being played" and "some notes being played", hm...
This might or might not suffice in the OP's use case. Overlapping notes don't restart the LFO phase, so that's a start. Perhaps even enough? The OP will let us know.
Hive is polyphonic, obviously. So are the LFOs. The OP can now choose to have all voices share the same LFO phase ("single" mode), this will feel like all voices use the same monophonic LFO, but he might want to need to add a Random->LFO Phase modulation to avoid having an obvious restart at the same phase position each time.
If the DAW playback is running, the option "sync" might be best, as it only listens to the DAW tempo (and to additional LFO modulations, should these exist in the patch). All LFOs start with the same phase (so the LFO again feels monophonic) but can be modulated apart if needed (LFOs then become polyphonic).
It's not, of course, but the OP did specify one aspect of what they're looking for, and I focus on that.
Depending on the OP's use case, restart modes "sync" or "single" can feel like free-running LFOs. We don't have enough details to determine that yet.
To quote the user guide:
"Single - All voices share the same LFO, which is restarted at the next MIDI note after all previous notes have been released."
So there's a phase restart between "no notes being played" and "some notes being played", hm...
This might or might not suffice in the OP's use case. Overlapping notes don't restart the LFO phase, so that's a start. Perhaps even enough? The OP will let us know.
Hive is polyphonic, obviously. So are the LFOs. The OP can now choose to have all voices share the same LFO phase ("single" mode), this will feel like all voices use the same monophonic LFO, but he might want to need to add a Random->LFO Phase modulation to avoid having an obvious restart at the same phase position each time.
If the DAW playback is running, the option "sync" might be best, as it only listens to the DAW tempo (and to additional LFO modulations, should these exist in the patch). All LFOs start with the same phase (so the LFO again feels monophonic) but can be modulated apart if needed (LFOs then become polyphonic).
-
- KVRer
- Topic Starter
- 2 posts since 22 Nov, 2021
Thanks for the interesting replies. "Single" actually does not cut it because it will restart at each new midi note. The Random->LFO Phase modulation trick is a nice one which I hadn't thought of, but it's not exactly what I'm after because the modulation isn't "smooth".
Say I have a sequence of short hits every 16th note, and I want one parameter to evolve smoothly while the sequence is playing. The Random->LFO Phase is a nice effect but it sounds random in this case rather than a smooth evolution
Say I have a sequence of short hits every 16th note, and I want one parameter to evolve smoothly while the sequence is playing. The Random->LFO Phase is a nice effect but it sounds random in this case rather than a smooth evolution
-
- KVRian
- 814 posts since 18 May, 2007 from Berlin
Yes, in that case, "single" wouldn't work.
See the last suggestion in my post, the "sync" option might work in your scenario.
Or, you automate that particular parameter in your DAW, might be the simpler approach.
See the last suggestion in my post, the "sync" option might work in your scenario.
Or, you automate that particular parameter in your DAW, might be the simpler approach.
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839 - KVRAF
- 1914 posts since 13 Sep, 2007
Unless your daw is ableton and cpu is on weak side.Viktor [TUC] wrote: Thu Apr 21, 2022 10:25 am Or, you automate that particular parameter in your DAW, might be the simpler approach.
Murderous duck!