Value Set Mode for Sliders

[d.healey]

@Christoph-Hart That's exactly the kind of thing I had in mind :)

[DanH]

@d-healey @Lindon ah yes this was floated back when I was asking about this - would solve the breaking change issue but might be confusing to newcomers...

[Lindon]

@DanH - as in: more confusing than the cluster_**** of scriptnode ideas we've all been thru?

[DanH]

@Lindon ha, no.

[DanH]

@Christoph-Hart actually is there any likelyhood of this changing? I only ask because I’m about to roll out a major update and any changes would potentially break all the presets going forward.

[Christoph Hart]

Tucking the longer values at the end of the list is not an option, this is super ugly.

These are the options:

• Add HISE_USE_EXTENDED_TEMPO_VALUES as preprocessor, which adds a few options at the start of the list. This will break existing projects because the tempo index will be offset by a few numbers.
• Use a scriptnode version of the LFO. It's not as hard as it looks - I would create a core ramp generator using SNEX that supports retrigger and one-shot cycles and then shape the ramp to the LFO signal you need. I'll check if I can crank out something later, but this is a good "teach a man how to fish" moment.
• add a global tempo multiplier that you can control using Engine.setTempoMultiplicator(). this might have implications on other modules, but it might be a viable option depending on the use case.

[DanH]

@Christoph-Hart Option 1 makes most sense to me. People can choose to break their projects in return for the extra tempos and being able to retain their existing lfos as well.

[Matt_SF]

@Christoph-Hart I for myself, prefer to learn how to fish

[DanH]

@Matt_SF yes it also occurs to me that @Christoph-Hart will inevitably have to do option 2 anyway no matter what

Option 1 still a no brainer tho

[Lindon]

@Christoph-Hart well I like 1 best, then 3, then 2...