@griffinboy
@Christoph-Hart

I'm starting to think there is something wrong with the latest Hise commit.
My nodes are not compiling anymore.

This can't be good

cannot open source file "hi_dsp_library/hi_dsp_library.h"
cannot open source file "hi_faust/hi_faust.h"
cannot open source file "hi_faust_types/hi_faust_types.h"
cannot open source file "hi_tools/hi_tools.h"
cannot open source file "juce_audio_basics/juce_audio_basics.h"

@Christoph-Hart I just recently wrapped my head around changing audio routing by script and this feels very familiar . Im excited to dive in! Thank You sir!

@Christoph-Hart I'm using markdown for my embedded documentation. Please don't kill it 😘

np figured out a workaround with setPlaybackPosition instead

@DabDab Probably need to put it in Extra Preprocessor Definitions.

4ed2d27b-fd98-4b8a-ab60-ff26b3d1a9c2-image.png

@griffinboy thank you!

@aaronventure yes lots, but I haven't done a huge amount of editing to existing code

@CatABC If you use a text editor that has the ability to search the text of all documents in a folder (and you can also do this on github) you can search the name of the function to find out how it works.

https://github.com/search?q=repo%3Achristophhart%2FHISE getSystemId&type=code

@Morphoice hmm, weird, anyways, I've added a safe check as well as the option to edit the flags set by the node_properties.json file in the DLL exporter. This should fix most issues related to this subject.

@Christoph-Hart don't know if this is helpful or how hard it would be to implement in HISE/C++ side, but, since you never got this running in linux: as an alternative to using websockets (and this would be my preferred way of communication if it were possible), you could potentially ust mqtt for communication. That's what I've done with a pretty large electron sound design app I made, and it works great for ipc and communication. (plus it's more reliable, faster, and cleaner because you have topic based message routing).

Basically main process just spins up an mqtt broker on launch, and then all my different webviews, and swift audio rendering processes, just connect to the main broker and use that for pub sub. Disadvantage would be people would have to include a lib like https://github.com/mqttjs in their webview, but it looks like you need to add a little code already anyways to get the comms working.

@T-B-Guang Having this same problem with no obvious reason. Trying this in a new tester project. only a few samples. sampler channels are the same as master channels. Have you found a solution?

global sends & receives will never be possible in a polyphonic context because the voice allocation system is not deterministic so you cannot expect that eg. voice number 13 is rendering the same note as voice number 13 of another sound generator - just add a script that adds an octave note on one of the sound generators (or even use an envelope with two different release times or sample lengths) and the voices will lose their index relation.

What might be possible at some point is to use the routing.send / routing.receive nodes WITHIN a polyphonic network to implement polyphonic feedback delay lines (for stuff like resonators etc).

@Allen Use a silent synth with a poly FX, there you have the ability of setting the channel amount.

Link Preview Image HISE | Docs

favicon

(docs.hise.audio)

@elemen8t Yessuh!

I'm back after ripping apart my project and putting it back together. The "Mother-Network" that was originally structured in the exported scriptnode has now been recreated in the Module Tree.

20bd4638-8a11-4e64-8deb-c5449c9db2cb-image.png

The minimal module tree from before will be missed. RIP

I have a few important notes. You need to use Synth.getSlotFX() not Synth.getEffect() when making a reference to the HMFX processor when using the setEffect command. This allows you to load in the exported scriptnode to the module.

Other notable functions are exportState() and restoreState(). These can be used to copy/paste control states of the processors after they move. Use the Synth.getEffect() for this one. The exported string even stores the loaded effect. This means you can simply use this command instead of having to load the effect and then the parameter settings. Both processes are accomplished by this single command.

I still need to set up a system for all the UI controls to adapt their connections depending the updated locations for each module. That should be fun.

@Christoph-Hart
If I might throw my humble 2 cents in....and my 2 cents are change left over from a whole career of working in guitar amp modeling software, having spent almost 20 years with the ReValver amp modeling software and another 4 years with the HeadRush pedals and software. The software market segment of simulating hardware has completely turned from component level modeling to leveraging NN modeling. Neural Network modeling allows us to do in a matter off days what took months or years to accomplish, with better results (most of the time). Beyond guitar products, NN modeling lends itself to preamp, channel strip, etc modeling, which is why it's such an opportunity for @orange. This has really nothing to do with simply downloading models from tonehunt.org, this is about implementing something that will be "how it's done" from this moment on. Here's a real-world scenario: I am currently working for a guitar amplifier manufacturer that has a 60+ year history in guitar amps. They would like to release plugin versions of every flagship amp they have ever made AND ship a plugin version with every new amp that they design and release. This is my project, NN modeling is how to do it, and I have to find the solution that lets me get it done.
Having said that, I have really fallen in love with HISE in a short time, but it might not be a realistic solution (at this point) for my project. I would hate to see all this not properly implemented in HISE. It would be such a missed opportunity.

Having said all that.....we are about to enter the 2nd wave of NN modeling market disruption, which will truly change everything...again:

Link Preview Image The first publicly-available parametric Neural Amp Model

Today, I'm releasing ParametricOD, a plugin that uses NAM's parametric modeling capabilities to give you a model of my overdrive pedal that is accurate across the full range of the pedal's knobs and switches.Get it here: Users | Neural Amp Modeler.GUI for the plugin.The plugin is available in VST3 and AU formats for macOS and VST3 for Windows with similar compatibility to the open-source snapshot plugin ("the NAM plugin"--or perhaps just "NAM"--to many users).This plugin is intended as a "concep

favicon

Neural Amp Modeler (www.neuralampmodeler.com)

Thanks for letting me get that out....

@d-healey not really, it's just an mailchimp replacement. You can segment users but you cannot automate

@fellhouseaudio said in C++ API: SliderBase cannot find Constant Modulator (SIGSEV):

reach a SIGSEV in RootObject.h:61

I opened a github issue

@ustk said in How to modify these title texts in CustomSettings:

so you can just make your own comboboxes

For those three settings actually I think this is a good idea. For the audio settings though it becomes complicated very quickly.