@David-Healey Can you do it from the UI script?

const var ScriptFX_RM = Synth.getRoutingMatrix("ScriptFX"); // or master chain... global NUM_CHANNELS = ScriptFX_RM.getNumSourceChannels();

@Lindon Nice! And you're doing all that with branching logic in the LAF's ??

I did make a start, and I got a mix control to turn into a slider versus a knob, depending on what effect I have loaded. Seems pretty flexible for sure!

@Christoph-Hart
Here is a demo gif.
It's about the blue animation above the magician, which changes based on the large knob.
Everything works perfectly in HISE. However, it's still unstable in the compiled plug-in.

webViewDemo.gif

PS. I also want to build a xy-pad with a web view...

I could reproduce the crash - unfortunately I couldn't solve it properly, so the only fix is to delay the initialization for Webviews on FL Studio if the plugin is opened. If I "double click" on the instrument track, it crashes in the FL code, not the destructor of the webview (which I hoped it would).

I'll push the fix tomorrow.

@David-Healey Thank you,

Its working really great 👍

@ustk Yeah I'd rather avoid the c++ route (I'd rather avoid scriptnode too) but my preferred method is broken in the latest version of HISE and the fix requires more than Claude so I'm looking for the simplest alternative. It has to work with expansions so it's a bit of an edge case too.

@JulesV I haven't heard back from Christoph so I assume not...

@Christoph-Hart that's superb news! I'm so looking forward to bringing my AMS RMX16 clone to dolby atmos to have that gated reverb in my next album. It was a stupid idea to start making an album in atmos anyways but hey... why not

@David-Healey Oh good spotting, this might come from the fact that there's some internal path normalization but the wildcards do not use this.

BTW, I've added another feature to the asset manager last week: you can define a SharedWildcard which allows you to define files that might be shared across multiple of your assets - the asset installer will then skip them at installation / deinstallation (and verifies that they don't conflict when installing two assets that share files).

@David-Healey Yep, we talked about it here https://forum.hise.audio/topic/12926/question-about-ms-encode-decode-order-in-stereo-widener-example/3?_=1779473723375

@emmanuelbuccheri Loading a sample map always stops the audio engine.

To cross fade load the sample maps into two samplers at the start and crossfade between them. Or load the samples into multiple groups in the same sampler and use the group xfade feature.

I have an old video that shows some techniques here: https://youtu.be/0cn1l8231n4

@ScreamingWaves said in Module tree navigation tips:

does that mean that one can have multiple master chains?

There can be only one. But you can use containers to separate different flows. There's also send effects which occupy a separate chain.

@voxuer1 Yes, I have only tried as FX plugins, both on Mac and Windows, au & vst3.
It's working as it should

@voxuer1 nice glad it worked!

@David-Healey Hah that's that then :D. By a hair.

Yes it would have been a bespoke little thing just for my needs.

I'm not very hopeful about finding plugins. The Mac market in the 2000s was infamously sparse, especially in the sampler realm.

Still, it's a thought that didn't occur to me, thanks. I'll try and do a bit of research.

Cheers :-)

@MicheleBonventre What's different between the test plugin and the original project?

Also you might try with PluginVal to see if it gives any hints about the issue.

@Lindon well there was a problem in one of my includes, that neither HISE player nor HISE expansion projects was prepared to report.... so moving on for a bit...

@HISEnberg So Moonbase JUCE module requires JUCE8 indeed. Hise isnt stable when being compiled, or when compiling plugins, on JUCE8. So yeah its not working atm. Christoph noted that this is because he did some funky stuff for the MCP integration.

BUT you can work around that by compiling hise on JUCE6, then exporting a plugin. It will fail but it will create a .jucer file and you can pick that up with JUCE8. At least thats my workflow. You could probably script the whole thing. It requires some other steps as well as modifying some Hise source.

TBH if you dont need it right now (as stated, for me it was a neccesary step) I would simply wait for Christoph to integrate it.

@Christoph-Hart 🎉 great! I feel like it could really benefit the eco system surrounding Hise.

It was caused by having different sample rates in 2 different samplers. I had to convert all to 41.1khz which is what I started my project at.

@David-Healey Hi,

I will simplify, make the chord analyzer separately