Nope, the note length is derived by the envelope signal, the intensity can be dynamically changed and it would be weird if notes are killed if the intensity is temporarily set to zero.
administrators
Posts
-
RE: Possible bug with Global Envelope Modulator and note length?posted in General Questions
-
RE: Latest version of HISE breaks existing presets....posted in General Questions
Hmm, it appears that there is a pretty big matrix of all combinations of macros / matrix modulation / plugin parameters to be tested manually.
The commit in question was perhaps the worst thing I did in 2025 but there's no way back now so we have to somehow find a method to fix all cases and add some regression checks going forward.
-
RE: Colours added/removed in UI XMLposted in General Questions
@Orvillain component positions are rounded to integers anyway in the entire JUCE UI system.
You get sub pixel drawing stuff (so you can draw a rectangle at a float position / size, but not position a component.
If you design your UI in 2x for retina, then all the positions of the knobs have to be at a even position, so that if you divide it by 2 to get the "HISE coordinates" they are still an integer number.
-
RE: Issue macro taking the priorityposted in Bug Reports
@ustk whats the complete list of preprocessors you are using? There‘s a flag to add macro controls as plugin parameters but that obviously interfers with macro modulation.
-
RE: Selecting different functions in Faustposted in Faust Development
@JulesV AFAIK branching isn't really supported in Faust, so the most practicable solution would be to use a branch container in scriptnode and use one faust node per effect you want to switch.
-
RE: HISE Store, Tell me More...posted in General Questions
@David-Healey it's not an end user facing feature, it basically combines two things for HISE developers:
- A package manager system that lets you copy & update external code into your HISE project. So if you have one HISE project where you developed a few DSP networks or general scripting stuff, you can easily use that as a source to be copied to other HISE projects for easier project management. It supports versioning, local changes & automatic updating (so basically a mini GIT within HISE).
- A store where third party developers can offer assets (code, samples, DSP networks) for HISE developers. We'll present this at the perpetuously delayed next HISE meetup.
-
RE: Multiple expansions with the same nameposted in Feature Requests
Hmm I need to look at the PR, I haven't really catered in the fact of expansion name collisions, there are quite a few calls in the codebase that just say "fetch me the expansion with the name XXX" and a simple company / expansion subfolder structure won't solve that.
But yeah for a general purpose Full Instrument Player like Rhapsody this should be addressed at some point.
Sometimes you want to send an update to users that only includes data.
Can't you then not just update the .hxi file?
-
RE: WebView Bugposted in Bug Reports
@Adam_G it's touchy because you're running a browser in a plugin and eg. a DAW might create and trash the interfaces at its will with consequences not foreseen by the developers of the webview frameworks.