Global Modulator / LFO always retriggered ?
-
Actually, I guess this would be a custom script modulator, with the oscillator inside a no_midi container.... ??
yes, this. Also I highly encourage anyone to build their custom modulators with scriptnode unless you absolutely require some functionality that can't be achieved there (which is a very limited set of things by now).
-
@Christoph-Hart Yeah my thought was to built a custom LFO that could offer:
- Monophonic VS polyphonic (is this even possible?)
- Free-running VS sync via sub-divisions
- Retrigger on/off
That along with the usual suspects (shapes, frequency, gain, phase, etc) could be a powerful thing.
-
@Orvillain yup, should all be doable.
Monophonic VS polyphonic (is this even possible?)
Just make it an envelope then, that's polyphonic by definition. You can always switch envelopes to be monophonic (including defining its retrigger behaviour).
Free-running VS sync via sub-divisions
Also no problem, for the synced LFO this is your best friend:
HISE | ScriptNode | clock_ramp
A ramp signal generator that is synchronized to the HISE clock, producing a ramp waveform for modulation purposes.
(docs.hise.audio)
Retrigger on/off
There are multiple ways to go about this, you just need to make sure that you can somehow bypass the processing of the note on event. Of course in polyphonic mode this will always retrigger, but if you set a envelope to monophonic and ignore every note on message, it will just run.
-
@Christoph-Hart said in Global Modulator / LFO always retriggered ?:
Of course in polyphonic mode this will always retrigger
Some way to have polyphonic, free running modulators would be awesome. It's a really nice effect.
-
@modularsamples said in Global Modulator / LFO always retriggered ?:
Some way to have polyphonic, free running modulators would be awesome. It's a really nice effect.
what is a polyphonic, free running modulator? polyphony is tied to voices, so when no voices are rendered, nothing is there to be done...
-
@Christoph-Hart said in Global Modulator / LFO always retriggered ?:
@modularsamples said in Global Modulator / LFO always retriggered ?:
Some way to have polyphonic, free running modulators would be awesome. It's a really nice effect.
what is a polyphonic, free running modulator? polyphony is tied to voices, so when no voices are rendered, nothing is there to be done...
Only thing I can think of is, having the modulator continue to render in the background so that when the voice is re-triggered again, the modulator phase picks up the latest "newest" value, but still on a per voice basis.
But I would guess this is a pretty edge case thing.
-
@Christoph-Hart Orvillain describes it well. Think of a traditional, analogue oscillator. It is producing a continuous signal from the moment you turn it on, the only reason you don't hear it all the time on, say a minimoog, is because it's passed through a envelope controlled VCA.
It is pretty niche admittedly, but it would open up some interesting possibilities (modular, classic polysynth recreations).
-
@modularsamples you can replicate that with a monophonic script fx and an oscillator but when you do this polyphonically it just boils down to randomizing the start phase which isn‘t the most spectacular sound.
-
@modularsamples
@Christoph-HartI've done it in c++
I keep a global timer, and for each synth voice I remember the phase when the voice stops.
When the voice starts again, I look at the last phase, and the time that has passed, and I can make the voices start at the phase which it would be as if it had always been playing
It's the only solution I could think of. The reason being that hise voices inherently do no processing at all when they are not active.
This means that you have to resort to keeping track of phase yourself, and doing all the bookkeeping. -
@griffinboy forgive me if I'm ignorant, but why?
-
If you wanted vca to act like a gate.
Imagine that you have a saw wave polysynth.
Hold down a chord and keep it held.
Because each voice is a different note, you get the phasing effect, you can hear the held saw chord coming in and out of phase.Now, play the same chord in a rhythm.
The phasing effect stays continuous and doesn't get reset. The envelope sounds like a gate on the phasing chord. This is the effect you'll experience on an analog polysynth.Whereas, if it wasn't free running, the phasing pattern would change every time you re trigger the chord.
There is no reason to do this other than analog emulation. Admittedly, free running oscillators make bass sound loose and worse. But it does sound really nice on pads since you get this feeling of continuity.
-
@griffinboy yeah, but what's the additional benefit over just randomizing the start phase when you start a note? I get that you might want to have phase randomization between notes, but my gut feeling tells me that there is almost no perceivable difference between randomizing the phase and meticulously keeping track of the phase of each voice.
-
It's a big perceived difference in my opinion.
I can make some sound demos if you're not convinced. -
@griffinboy sure, please.
-
I thought the difference was significant enough for me to want to model it.
Then again, I am a perfectionist when it comes to audio things like this.
It might not be significant to others.But in some cases I do prefer the free running over random phase. The overtones in the highs have an evolving pattern which your brain can follow in free running, and I find that pleasing. Wheras random phase gives a chaotic and hard to follow pattern.
-
@griffinboy said in Global Modulator / LFO always retriggered ?:
I thought the difference was significant enough for me to want to model it.
Then again, I am a perfectionist when it comes to audio things like this.
It might not be significant to others.But in some cases I do prefer the free running over random phase. The phasing in the highs has a clear pattern which your brain can follow in free running, and I find that pleasing. Wheras random phase gives a chaotic and hard to follow pattern.
IMHO, it is extremely noticeable and having a way to support that behaviour would be excellent.
-
Do we have a way to prioritise these sorts of request? - not nesc. an order that Christoph might do a thing - that's up to him - but so we can see its relative importance to everyone. Im sure we had an approach I just cant seem to find it. Essentially so we(well me really) can say "Hey this sounds sorta esoteric and only applicable or even audible to a very few people - whereas MSEG envelopes might be considered more useful by a broader audience....."???
HISE Development for hire.
www.channelrobot.com -
Yeah, the feature request system is quite messy.
Not to mention there are bug fix type requests as well as feature requests. I'm not really sure what would make it easier though! -
I still would like a proper bug/feature tracker, the github + forum combo isn't the best
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey Could all be done on GitHub. There are Discussions that can be used for proposing and discussing ideas. It also has a voting system. Then the issue tracker can be used for formal feature requests.
Discussing things on the forum is great, of course, but a single source of truth for feature requests and bug reports would be really useful.
