Feature request discussion - Message.isNoteActive(id)

[d.healey]

@Lindon Currently I manage this by setting any events I've killed to -99. But I agree that having a dedicated function would be much nicer. Especially when dealing with events generated/killed by other scripts.

[Lindon]

@d-healey said in Feature request discussion - Message.isNoteActive(id):

@Lindon Currently I manage this by setting any events I've killed to -99. But I agree that having a dedicated function would be much nicer. Especially when dealing with events generated/killed by other scripts.

-yeah - thats all fine - execept there are several scenarios where downstream activities "kill" the note - and the upstream script isnt aware of it... so having this function would be super useful - which is sorta what you said I realise - now I've re-read your post.....

[Christoph Hart]

You just need that function for artificial events, yes? Because if you kill a note at some place they have to be made artificial anyways.

I'm asking because then it's a trivial operation but checking the state of a "real" note by the event ID would be much more costly because of the data structure difference of the containers I use.

[Lindon]

@Christoph-Hart - well I'm assuming(always a bad idea) that its just using the point where HISE issues the warning message about the note id not being found... so wherever that is, which I guess is artificial notes...

[d.healey]

@Lindon He implemented it already :p

- added Sampler.setRRGroupVolume() · christophhart/HISE@6806cb7

The open source framework for sample based instruments - - added Sampler.setRRGroupVolume() · christophhart/HISE@6806cb7

GitHub (github.com)

[Lindon]

@d-healey -typical me, always late to the party...:)