@aaronventure said in Message.delayEvent() - 100% reliable and sample accurate?:

Just remember, it needs to be in a child processor, not have it under the same processor.

Can you pls expand on this?

@Morphoice Have you tried maxing out the process block size?

@d-healey thanks for documenting that.

@Morphoice Excellent!

@Dan-Korneff Thanks, Dan - helps to know I'm not alone. (Also prob helps to have a stack of Gold Records.)

@d-healey I do. It's the first line of my OnInit().

Does anyone now what this means?

It's in a longterm plugin, and Im not aware of anything I might have changed which has to do with that. The only thing I can think of is that I made some changes to the effects in my module tree, and was dealing with the module reordering bug.

Now, when I open my plugin, it tries to compile as always, but just sits there, occasionally responding to keyboard/mouse input, but not compiling.

Any thoughts greatly appreciated!

@oskarsh @d-healey My keyword list only the HISE Script keywords—a list of API keywords would be fantastic. How are you handling that when using an external editor?

@d-healey I love that idea, too.

@oskarsh I love your idea.

@griffinboy Yes. First, pls take a look at my commercial spectral editor, Steinberg's SpectraLayers. If you want to do anything you see in that programme, obviously I can be pretty specific. If you'd like a license for it, let me know.

@oskarsh Be aware that there are issues with using an external text editor—namely, that HISE will sometimes overwrite your original file. Usually, this happens when HISE opens the same file in HISE, like if you click on an error report in the Console. But sometimes it just happens. My workaround its to use an external editor that tells me when a file that it has open was overwritten by HISE, and gives me the option to reject HISE's changes, or keep my own. (Though HISE hasn't actually made any changes; it's simply overwritten my last changes in the external editor, though it's more nuanced than that, which is another of saying I'm too lazy to be more specific.) There was a bug about this which was fixed a while back, which improved the situation a lot. But problems remain, so be careful so you don't lose any code. I know @Christoph-Hart has put a lot of work into HISE's built-in editor, and after two years, I'm still finding about cool stuff in it that I wasn't aware of. If do decide to go with an external editor, I can send you my list of HISE Script keywords for your editor. (If you're using BBEdit, I went so far as creating a HISE Script language module.)

@griffinboy I'm happy to help, hit me up over DM. It's super-easy to do what you'd like. Though my first suggestion, assuming that's what you want, is to adapt the tile @Christoph-Hart is using for HISE.

@David-Kissam I wrote a detailed tutorial on this topic - just search the forum.

@griffinboy Like this?

@d-healey Thank you, Dave. For #1, do know how to use it—like, what functions are called? (And does this require the Custom Preset Manager?) Thanks, man, as always.

@Morphoice There are tools that can help decompose audio into partial for, and indicate the envelopes, etc. However, you can be incredibly sloppy, without anyone knowing the difference—think about AAC files, where 90% of the data can be removed, and it sounds the same. Focus on the few variables that matter, cognitively.

There are many ways in HISE to continuously control the amplitude of channels, relatively efficiently.

Does anyone know…

1. What setEnableUserPresetPreprocessing is for?

2. Does Filesystem have a constant for finding the user Presets folder?

3. If it's possible within any of Preset callbacks to know the name of the Preset entered by the user?

4. Exactly what is tested with runTest?

5. what is the intended use for getSecondsSinceLastPresetLoad?

Thanks!

@VirtualVirgin If you search the forum, I wrote a detailed tutorial on using UI factories, along with example code.

@Morphoice Also, @Christoph-Hart kindly wrote a new Snippet specifically creating a drum synthesiser within HISE. Check it out, and thank you @Christoph-Hart.