Yeah, regex is your friend here. The HISE regex seems to be missing a lot of features but you can still condense it down a bit like this:

const kickPattern = "kick|kck|kk|bd|bassdrum|bass\sdrum|bassd"; const snarePattern = "snare|snar|snr|sn"; const hatPattern = "hat|hh|clh|cl|oph|op"; inline function stringMatchesPattern(str, pattern) { return Engine.matchesRegex(str.toLowerCase(), pattern); } Console.print(stringMatchesPattern("Kick".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Kck".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Kk".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("kick".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("kk".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("BD".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Bd".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("bd".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("BassDrum".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Kick".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Kick".toLowerCase(), kickPattern)); Console.print(stringMatchesPattern("Snare".toLowerCase(), snarePattern)); Console.print(stringMatchesPattern("Snr".toLowerCase(), snarePattern)); Console.print(stringMatchesPattern("Hat".toLowerCase(), hatPattern)); Console.print(stringMatchesPattern("Clh".toLowerCase(), hatPattern));

If some of the usual regex tools worked, we could have shorter patterns like this:

const kickPattern = "ki?c?k|b(ass)?\s?d(rum)?"

Although the longer one might be easier to read and understand I guess.

@d-healey No there's a duplicate of the chain purely for the FFT display (otherwise the output would be playing the dirac-delta sample)

@Oli-Ullmann 🙏

@clevername27 Do you have the most up-to date version of this code? Just trying it out from the snippet browser but it crashes HISE instantly.

Edit @Christoph-Hart even if you just have the code for the Audio Render Example without fixing this issue I would appreciate the opportunity to have a look and study it 😁 If I can fix it I can push the fix to the snippet browser Github repo.

@d-healey Oh Math.pow won't be enough then... I haven't paid attention it's for an sp...

@d-healey Nice, in the meantime I'll modify it locally.

@Christoph-Hart merge request initiated 🤖

@ustk Turns out you're a genius and have already solved my problem 🥳:

https://forum.hise.audio/post/91573

Can replace the Sound Generator with a ScriptFX and use a midi container to get the gate information, tested and working in the compiled plugin.

Thank you very much ustk circa 2024 😂

@VirtualVirgin I think both work, not sure

@hyperphonias np! 🙏 Have a great day!

@treynterrio Did you already have a LAF going for column background? If you didnt, you will have to draw it again yourself because now you're taking over the look and feel of that section.

start with :

g.drawRect(obj.area); // or g.drawRoundedRectangle( obj.area, 6, 1.0); //etc.

@HISEnberg ok but i think there a way to make viewport and display both seq and track in order to select difference seq and difference tracks in midiplayer

@d-healey Thank you so much

@VirtualVirgin I looked at the js manual, of course there are more functions, but only the ones you mentioned work in Hise, maybe undefined match to context

@ILIAM Then you should first learn to get a list of your midi files, load them in a combobox, then use the combobox to load the sequences in the player.
Here's a good place to start https://docs.hise.dev/hise-modules/midi-processors/list/midiplayer.html

@Chazrox But the process for the user for adding tags is weird, I don't like it anyway :p

1000050915.jpg

@d-healey thats the best kind come on. 🤣

@d-healey
That's right. Because with SlotFX.getCurrentEffect(), you always get the effect loaded in the slot. So you could also implement it in the effect class and still have access to the functionality from a slot.

So I believe... :-)