Value Set Mode for Sliders

[Lindon]

Okay --- waaaay back I the dark ages - when there was only 5 of us here.....I asked for this feature - and I still think its a good one, so here I am again;

Value Set Mode

• so Sliders have modes - (Frequency, Tempo Sync, Normalised Percentage, Linear etc.)

I suggest we add another mode: "Value Set"

When this is selected we get to apply a comma delimited set of values in the pop-up for the slider...

Knob man does this effectively, so lets say I want the slider to go from 1 to 10 - but I want to display something else like say this:

["A","B","C","D","E","F","G","H"."I"."J"]

I say:

mySlider.setValueSet(anArrayOfStrings);

and as the slider scrolls from 1 to 10 it takes each array element in turn and shows it in the pop up...

[d.healey]

I think this would be good to implement within look and feel. We already have Content.setValuePopupData() so maybe a kind of extension of this that allows us to modify the displayed values as well as the other properties.

[ulrik]

@Lindon Agree!

[orange]

@Lindon Agree

[Christoph Hart]

You can achieve this already with setValuePopupFunction().

HiseSnippet 1000.3ocsV8tZabDDeOYetUpsgjR9ZgE8I4hiPpIMoPITaKaUDw1QX4XJXBg02MmzFs2tG6tmsUK40oOJ84ouAsyt2IcR0FmDAUXr14++lYmYVMTqh.iQoIA0OaVFPB95vQyj1I8lv3RxfCHAOH7XlwBZZAq8mkwLFHlDDrwu5XDTeSh+ye+K6yDLYDTwhPNWwifi3obaE2g69JtPzmECmwSWR6ms6fHkrmRnxQ7rQXGRFKZJaLbByoVsPRvVGFysJ8HKyBFTm8UwyFMQcsrP+y4F9kBvQzkLBcTAaRuIbQ7v44pgPB1bXUluQQl+3vi4w7E7qp.OzKfVYwx0ffZ2Gj59Y.ofkfzlEP5Qgihz7LakDGd9pvAR7BIggk5kgRgtjZ+YsvdJTCoscJaJzWiDKrn0y6zYGJ9us+4FMvxswRuhoouRptrK8kz4FNFr8ToYJIRzpoWZyUs3blHGLnIMtf1rOWarM2g1bDfZD6NcFTvoetb5L+A7Z0+M+Jn4aQe48ZaCX8tZnJKOCUNxxUxVIyObkS11M9iF00fMWKKi6Ed9nW9vpnRvRVJKhz.dqbjJhINRoltmLtO.hVNSPEaqgwbWq8hn1LVyt9TkkomMRviAGdWfjw6PUW9dOTniamfsv6IDsJZWMnuhQ2Vmh+gZ0lgQ9hm9V52+RZ21cnOwyzi4ST5Tlf+6Pbo5ickfB2rvaWOgagsWnfKXmBQ1VyccgHetunJdqzDSQTg43mpjmnrvqks7oPiOzf9eEkjbmxbUSsRH.8cJ1MDquOCaIySuDz6PqtKcJhc4qN5r0m1nSTwk6RJpjCjb6qyfR59JQrajvc91CZjxtC2HWIBQUs9AtGTNvUb6S3nS9hPeEl3Ae0xpGuK4MCNfYYycC5QLJYf1xcISvAvU3puh435gG.loVUlW2xwJbW6GMn2PBBC9KLbybG9t.BwXm4JIa4U.ofrQXuDJMD6yHoKuPlPRY2rLhM4II7a7aRwNpTiEi5fTbAKI3aCeiAnwPBKWXoloneDb4TH9LkWeCVsqFSc.bePntFWleqkV35RUbtfYWcGp6whRAX2wJKtbKmjFtc1xOl7YrXsy8tX8SEhOJbH2FM4twXs6.i3M++GXr74nuI7vjDbluBfaF1+2V22d9Hg+TUtkKGeLCaIb8bmjmNBWDEAXzkRPXbse0byNEzcbztJvHPF6I9G7SovtN5fRgcmKDaFizp2EULw4dv6K8bPLI8uuWG+gFHMcwnVXXGeKcL+cQQtz+IcIj61leXMr4oqgMOaMr4GWCad9ZXyKVCa9o60F2O6YubqJsXb.YL7P+JuffCkLryx2ER9WndA0mC

[Lindon]

@Christoph-Hart okay great - so tell me again why we cant add the slower tempos at the end of the enums:

HiseSnippet 1126.3ocsVstaiTCE1SaGfDfUrR7.XkekVlllIIMsPYEsMoAUs8RTSoBopUqbmwIwTO1CdbZIf56FOB7nva.brmYRlvlsfhXihhiO27m+74br6qjAzjDoB4T55owTjym4NXpPOtyXBSfNsKx4EtmSRzTENUzwSiIIIzPjiy5euQfSoMP1O+42cLgSDAz4hPnajr.5YrHldtz9G9ZFm2iDRulEUv5VGdZfTzQxkS.7rtacTLI3dxH5EDiYq4hb9nSBYZoZflnoIHmMNVFNcvX4ihT6ugkvtiSMS7QCf.kJtmjGZPrQJpyXFOre99NAAQo+bVX8TV3KcOmExlIeNa7EVE34dTjObVaQ3s9BvyuH7pW.dKARNEfzFoP5ktCBTrX8bMF77otmJfCmgDf1KBkTaQq8sa31QBVHz0hH2S6ofIy7nZ6508vvOadP4x.0mnwOPT3WKj24ieEN2wQTcGYTrT.SpVwpsxhdbCgOgl.tT91JM2wuhGtRizA+7gFcyFyFtNcrUl3VYCYh2OS79YCYh8a2M+O4iYZZlG+lMxGyzzNeIZ2Je75Ju4fBn+ZJr4fr9fiRRXiDQv1zrWtsQcO+u1y2qgWSuVd6501aOu88.IfbeO+Fd9M87a44uqmeaO+8772GBqkdpkP0VNouLdRbuIh.MSJpNL+OOXzsY4eqbIEUOQIxHvasxgf7jgd2YqBXjSFV3DIPQgLryjAD9YR48GIB6Qo7pFu.CqoniXlR1YKbkPE4wqjZhZ5.NKjp.lXFXF4gk28SVzfGUaHTZdDmWMsLLAhUHD1RX3KXUMBrx217M3sdE1uVc71VgVXegTEQ3rekFlY9HCKjFlYQ6wwLMcyYFXVrqnA5p4gNUkc6OiHemsIrEAC1ZmxkKyDblfNaufkBqaFdRI4UCxSa8vyobPYhjSqEqXl7YXEv5wT7Y8tDaRB11lNf0xuoB9qVZtQ1wDfgmNn7yVjjx.Vrzgv42AsyptHDM6zBn+BoldonpEmkepL9epZ3vkpKKXbpZopMsYUOmiUEShtipJxRFCgdOK1Py882PqX+1fTNofgRwoBl9xXp380EFkQjlleYnBLUaa88hrVeo4tHFzg6icsrHxB3hW3f9gS6Rzj7v.QDVkXpRyLa.mtzGfKjR6nVxsKM4dsL1Za1YGD5+0E8Wlsf+93CmNaxe7yGBUcwCfZfh2JFQlaOp4gI.qLu2fInGS4xGgqEemV9vkMxvIbhdwafLW6lo.NEWnsuo0tHgomVD.+ucsz+UH9R29Lcv3kiw0VBFgSqODXL6x7O28jgCgtLyA3Ft89wOL2bitRNQyDiNmnUL3b28hIQCfVeATX0EBJ2TE4rlIeOcdcybCCLfJBsS9K3SlReybmLk94JQQj.k7sAoUIlmK7IVI.lD1WJUBdxFLGOq7v0sds5nH3kKuMHvr82FJAWtOMVAeZtB9zZE7Y2Uvm1qfO6sB9r+y5i4QiGMQKiRKG.A8Ow1lxw4DAAxrrYgn+FKyHKT.

[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...