@Lindon I don't see a need to use a global to create the note off (unless you need to turn if off in another script) just a reg variable should be fine. If you want 1 ID per note then use a MIDIList instead.

function onInit() { reg noteId; } function onNoteOn() { Message.ignoreEvent(true); noteId = Synth.playNote(Globals.triggerNote, Message.getVelocity()); Console.print("playing trigger note:" + Globals.triggerNote); } function onNoteOff() { Synth.noteOffByEventId(noteId); }

Another option

@d-healey yeah because blog-posts = documentation☺

Yeah, I have to add a check that ensures a commonly used samplerate to prevent this. Noted.

@Christoph-Hart said in More Error Logging with .hr1 Extraction Utility:

subclass from HlacArchiver::Listener and you'll get verbose logging info

Awesome!! Thanks!

Download link for Wurly AU/Mac if anyone want to test it.

404 Not Found

favicon

(sampleson.com)

@Christoph-Hart said in A question to Christoph about plugins and Windows platform.:

Yeah, that's nonsense. It has literally no effect on CPU usage whether resources are embedded in the plugin binary or not.

Totally agree :)

No but you can open a url

Yes there is - if you recompile the target script without recompiling the caller script, the function will point to a invalid root object and it will crash badly as soon as you call any API method. The lifetime of a compiled function must never exceed the lifetime of its root and this would make it very easy to violate that rule.

Worst case in the current approach is calling setAttribute with an invalid ID.

@SampleScience

I guess that the developer behind the project is as important as the platform used to develop. Do you think that your background as a programmer helps when developing in Hise? Personally, my background is more in sound and graphic design. My coding skills are low (but I'm working on it).

If you can't write scripts then you will be limited in what you can achieve with HISE (or Kontakt).

Possible to have a stereo harmonic filter for containers?

No worries David!
Thanks, I'm going to have a look right now...

@ustk Thank you :) It works good ;)

@Christoph-Hart It's like to see a fusion between the fisherman and the mermaid in the Frederic Leighton's painting :P 493px-Leighton-The_Fisherman_and_the_Syren-c._1856-1858.jpg

@d-healey said in HISE shop with fees for Christoph:

@ossian1961 Just had a look at the Tracktion website. The licensing system they show is a bit misleading. Nowhere on that page does it mention that Tracktion can be used under the terms of the GPL license, you have to go to the github link to find it.

I see it now :)

@d-healey sounds gnarly - but I will give it a try - I'm really surprised no one has asked for this before...so it would be really really nice if we could use the JSON to do this....☺

If you don't defer a script, then the Engine.getUptime() is sample accurate down to +-8 samples because in its default setting which can be changed by the macro HISE_EVENT_RASTER, HISE rounds every sample position for events (notes and timers) to 8 samples to apply SSE optimizations and downsample the modulation control rate. This introduces a "jitter" of 90 nanoseconds at 44kHz, so it should be neglible.

If you defer a script, the Engine.getUptime() function will return the exact value that the audio thread is currently using, which can be any value in the future because you don't know exactly when the deferred callback is executed, and in the case of offline rendering this can have drastic effects.

So bottom line, whenever you need "musical" timing, don't defer the script. This function is rather for stuff like "update a button on the GUI if you press a note" type of applications.

@Christoph-Hart said in Persistence values - still cant get this to work:

But what exactly is the hiccup we‘re talking about here? As soon as you set properties with a script, you obviously can‘t change it on the interface designer anymore because it would get overwritten each time you recompile the script.

If you want to batch process widgets once via script but then keep on editing the properties, wrap the property changes into a function and call it once, then comment it out so you can access them in the interface designer again.

Christoph I don't saying you souldn't take off the old way, I'm agree with you about creating averything through code writing is better and powerful (I started in that way before the RAD Ides), but why we need, so, to get a widgets palete? I thought it's no useful (it's only my personal opinion, don't take it as a request or a criticism) ;)

@d-healey Thanks Dave.... in the meantime I will just have to get over myself... and try convince my customers that they wont really need authorisation (they already love the audio file protection in HISE)... I will create a post in the "Feature request" section...

So for those not needing the nice arrow buttons and happy enough with just getting a number field sorted this code works fine:

function onControl(myControl, myValue) { if (myControl == yourNumberLabel){ var myres = parseInt(myValue, 10); yourNumberLabel.set("text",myres); }; };