LFO slower than 0.5Hz?

[Morphoice]

Sorry for asking so many stupid questions, but here's another one I can't figure out by myself. How can I make the LFO go slower than 0.5Hz?

[d.healey]

@Morphoice Recompile HISE with HISE_USE_EXTENDED_TEMPO_VALUES=1 in the Extra Preprocessor Definitions section of the Juicer file.

[Morphoice]

@d-healey said in LFO slower than 0.5Hz?:

HISE_USE_EXTENDED_TEMPO_VALUES=1

Bam!! thanks man

[Lindon]

@Morphoice said in LFO slower than 0.5Hz?:

Sorry for asking so many stupid questions, but here's another one I can't figure out by myself. How can I make the LFO go slower than 0.5Hz?

as David says HISE_USE_EXTENDED_TEMPO_VALUES=1 is useful but you can actually set the LFO in HZ to below 0.5 in a call back....- it just wont show up in the back end UI for the LFO

[orange]

@Lindon said in LFO slower than 0.5Hz?:

@Morphoice said in LFO slower than 0.5Hz?:

Sorry for asking so many stupid questions, but here's another one I can't figure out by myself. How can I make the LFO go slower than 0.5Hz?

you can actually set the LFO in HZ to below 0.5 in a call back....- it just wont show up in the back end UI for the LFO

I can reduce it to 0.1 Hz in the callback, but I can't go lower than that. Is there a way?

[Morphoice]

@d-healey tried compiling with HISE_USE_EXTENDED_TEMPO_VALUES=1 which built fine but the LFO can still just go to 0.5Hz

[iamlamprey]

@d-healey are sub 0.5hz LFOs supported in Rhapsody? also should the default not just be 0.01hz? Is there any reason why we should need the preprocessor flag?

[d.healey]

@Morphoice Ah I guess that must just allow higher speeds then. But as Lindon pointed out, you can make it go slower it just won't show it in the module.

[d.healey]

@iamlamprey said in LFO slower than 0.5Hz?:

@d-healey are sub 0.5hz LFOs supported in Rhapsody? also should the default not just be 0.01hz? Is there any reason why we should need the preprocessor flag?

I'm compiling Rhapsody with that flag

[ulrik]

@Morphoice the "HISE_USE_EXTENDED_TEMPO_VALUES=1" will extend the synced values, it will extend with this values:
8/1, 6/1, 4/1, 3/1, 2/1

I don't think it will change anything in the unsynced "free" hz value setting

[ustk]

As @ulrik said, I'm not sure there a relation between HISE_USE_EXTENDED_TEMPO_VALUES and the manual limit one can set. Though there might be a min/max range in Hz in the end, I can't see it