Tag: Scripting

https://youtu.be/PPTwXLQy5vw As you work on HISE projects of any size, you’ll eventually reach a point where the no-code tools can only take you so far and you need features that go beyond the basic modules. You know scripting will get you there, but you might not feel ready to dive into it yet. HISE’s built-in hardcoded scripts are a great middle ground. They let you add useful behaviour with almost no effort, and they often solve the smaller problems before you need custom code. Why HISE Uses Lots of Small Scripts HISE encourages a modular approach. Instead of one large script that controls everything, most behaviour lives in small MIDI processors that each handle a clear task. You still have a main interface script, but most of the actual behaviour lives in small MIDI processors. Each one does a clear job, and you can place them at different levels in the project tree. A processor in the master chain affects everything. One inside a sampler only affects that sampler. It keeps things tidy and makes debugging much easier. Simple Example: Legato with Re-trigger A good starting point is the built-in legato script. Drop it into a sampler and it handles legato notes for you. There are no controls. It just works. The envelope’s release time shapes how smooth the transitions feel. It’s ideal when you want basic legato without writing your own script. Transposing MIDI Notes The Transposer is another handy one. It shifts incoming MIDI notes by a set number of semitones. You can link its parameter to a knob on your interface, set your own range, and that’s the job done. No scripting needed. Switching Between Sounds If you have more than one sound source, the MIDI Muter is a very useful tool. It can block note-ons, block all notes, or let note-offs through to prevent stuck notes. Put one muter on each articulation, link a pair of buttons on your UI, and you have a simple switching system that avoids artefacts and keeps playback smooth. The Main Limitation The built-in scripts aren’t designed to work together. For example, the Transposer won’t shift the output of the Arpeggiator. They run side by side but don’t talk to each other. When you hit this kind of wall, you have three options: hire a scripter, use a community script, or write your own. Custom scripts give you far more control, but the built-ins are a helpful way to get started. Final Thoughts HISE’s hardcoded scripts are quick to use, easy to drop in, and perfect for early stages of a project. They let you get results straight away without touching the scripting editor. As your needs grow, you’ll soon see when it’s time to bring in community scripts or start writing your own. In the next post, I’ll look at how to bring community scripts into your project and make them work for your own instruments.