@Christoph-Hart said in The Sample Map of The Future: Escaping the 20th Century Sample Mapping Paradigm:

Can you send me a samplemap that crashes?

Link Preview Image BellAndBone/SampleMaps/trumpet_sustain.xml at main

BellAndBone - Trumpet and trombone sample library

favicon

Codeberg.org (codeberg.org)

It looks to me like the group += 1 is on the wrong side of the else. Because, from what I understand, it should happen when we're not using the complex group manager.

@Orvillain

That should be possible

@Christoph-Hart ?

@aaronventure It shouldn't be limited to 16, but there's still a bug with the number of sliders an ExternalSliderPack can handle.
This might be of interest to you: https://forum.hise.audio/topic/11411/externaldata-sliderpack-seems-to-be-limited-to-128/13?_=1743103883757

@aaronventure I requested a proper bug tracker a couple of times, something like Mantis. It would prevent bugs being lost in the ether of the forum, or being lonely on github.

@Christoph-Hart Nice, going to give this a try now.

@clevername27 said in [feature request] Stop specific broadcasters firing at on init:
It's also not always possible to tell if a broadcaster is being called at startup…which doesn't sound right, but there are edge-cases.

Can you make an example?

@d-healey

Proposes the feature. Documents the feature. Codes the feature.

Because that's how @d-healey rolls.

@Chazrox Did you try itemColour1? You can use Console.print(trace(obj)) to see what's available.

Krita is open source and C++, the answer might be there somewhere, surely the colour picker logic could be tinkered with. Not that I would know

@Phelan-Kane this issue still seem to exist. Often also the compiler log gets cut off in HISE so you actually cannot see the error output.

@ustk Wow seriously impressive work here! Excited to dig into this.

@d-healey This is the only mention of "linter" on the forum so far :D

I know nothing about how much effort implementing a linter would be, but even the low hanging fruit would save me a lot of development time. Yesterday I spent ages debugging a condition where I accidentally went if (var = 2) instead of if (var == 2).

I assume the ideal solution would be to adapt an existing linter, but maybe there's an easy way to do some basic checks until then?

Hence the feature request :-) fadeComponent has been working very well for me so far, it would just be great to have a quick and easy way to achieve fades to semi-transparent states like this.