@VirtualVirgin I think both work, not sure

@hyperphonias np! 🙏 Have a great day!

@Christoph-Hart Oh I was Using the old commit. I just Compiled the updated one . it works perfect Thank you

@Yinxi lol I like this one

@ulrik this is perfect. Thank you so much.

@Christoph-Hart Thought this was fixed, but apparently not 🤷♂

Screenshot 2025-10-24 at 23.25.38.png

@Christoph-Hart Amaaaaazing! Thanks Chris 😎

No need to guess what it's doing:

https://github.com/christophhart/HISE/blob/be4e58b835b21c0a7aa276a9e71f1025dbec31d4/hi_dsp_library/dsp_nodes/CoreNodes.h#L533

@Yinxi you didn‘t have to pay for a VST3 license before and the immediate real world consequences for plugin developers are not very substantive unless you have a fringe use case that requires a super permissive license. It is rather interesting from a business perspective and will ensure that they cannot pull stunts like with the VST2 SDK.

@sophiejean Hello, welcome to the forum. Please post in English so it's easier for us to help. I did a quick Google translate.

Hello HISE community!
I'm brainstorming a creative concept I'm calling "Chicken Road Games," envisioned as an interactive and gamified sampling engine (or plugin) integrated into HISE.

The main idea: simulate the metaphor of a "chicken crossing the road" using layered samples and random path logic.

Imagine that each step of the "chicken" triggers a different set of samples (clucks, footsteps, ambient road noises), and that users guide the "chicken" through musical "paths" (keys/samples) in real time.

Desired features: user interface with a road pattern, sample banks mapped to paths, random or user-controlled movements, adaptive modulation (e.g., tempo/time stretching during rapid crossing), and possibly a "road hazard" effect (interruptions, glitch samples) for an unpredictable experience.

Has anyone tried a similar concept in HISE, using its scripting and sampling engine to simulate non-traditional interactive behaviors?

What HISE modules or techniques would you recommend for mapping "lanes" to sample groups and managing random path logic (e.g., ScriptNode, JS scripts, state machines)?

For the UI: What are some best practices in HISE for drawing a "roadmap"-like interface and animating movements?

Do you have any suggestions for managing CPU load when randomizing sample paths and applying real-time effects (such as a "hazard glitch" when the chicken crosses incorrectly)?

If anyone is interested in collaborating: I would love to co-develop a prototype Chicken Road Game in HISE and share the project files.

Thanks in advance for your ideas, comments, or suggestions!

@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

That's the right direction, but I would also try to stay within the HISE user preset system so you get the intended loading prodecure (kill voices, load the preset on a background thread, then unsuspend the audio processing).

With the custom data model you can define the layout of the user preset file as you wish. Note that it will be converted from JSON to XML at some point though (which is a bit weird).

They also want to be able to export a preset, and include any sample content with the preset - ie; bundle the custom loaded .wav file, or the samplemap, with the preset. For personal sharing purposes.

I would detach this from the user preset system. A preset with sample mapping data and samples should be

The preset file The JSON (or SFZ or whatever) mapping file The audio samples

all in one folder.

can you confirm this is a vaiable solution?

Sounds like a hack, but then using HISE to create an installer app is already a bit weird.

Speaking of hacks, the "cleanest" hack would be to just deactivate the entire audio processing:

https://github.com/christophhart/HISE/blob/3ff4bbd9eb5596b084c7653e2d09fae2b4799c1e/hi_frontend/frontend/FrontEndProcessor.cpp#L96

This is the main callback for a compiled plugin (or standalone app). So if you add this code

#if IS_STANDALONE_APP return; #endif

at the beginning of this function, it will never call into the HISE rendering. Note that there are a few things that might be glitchy, some things in HISE rely on the audio thread to be working and initialised correctly.

@ustk yes I won't be using it again 😆

@d-healey Thank you so much

Could be references to components that no longer exist. I.e you have a reference to Button1 but deleted button 1.

Check in script view to see if any components are undefined

@DabDab
you are looking for this ?
https://youtu.be/lIehhPHiPOY

New Updates:

Custom Prefix for serial generator Custom Product Links Developer/Reseller Invite System In Place Smoothed Custom Domain Process

I will have Free vs Paid tiers in place by this weekend so signups will no longer require a card.

I also have the Website Designer in the pipeline.

If anybody has requests for any specific types of features, just let me know. I'll do my best to get them all added.