Don't know if this is the done thing really, but I wanted to show off:
https://youtu.be/1kMHloRQLcM

Again, wasn't sure where to put this. But I created my own node.

https://youtu.be/-siB1UJfrD0

Modelled analog bucket brigade delay. I'm starting to build up quite a nice collection of delay and reverb utilities now!

@Chazrox I might do a video or two on everything I've learned!

@d-healey I really like that UI. Very simple, accessible, and smooth looking - for lack of a better word!

@HISEnberg
Yes I wrote a custom transient detector in a c++ node, and made sure it utilised an audio file, which I can load in my UI using the audio waveform floating tile.

I implemented spectral flux extraction:

• Take your audio.
• Perform an FFT on it.
• Extract the spectral flux envelope from the FFT.
• Downsample the spectral flux envelope (optional but can help accuracy)
• Perform peak picking on the spectral flux envelope.

I used the stock JUCE FFT processor.

Free mankini with every commercial license???

@Chazrox said in I wrote a reverb:

@Orvillain Please. I've been waiting for some dsp videos! I've been watching ADC's everyday on baby topics just to familiarize myself with the lingo and what nots. I think im ready to start diving in! There are some pretty wicked dsp guys in here for sure and I'd love to get some tutuorials for writing c++ nodes.

There's two guys who got me started in this. One is a dude called Geraint Luff aka SignalSmith. This is probably his most accessible video:
https://youtu.be/6ZK2Goiyotk

Then the other guy of course is Sean Costello of ValhallaDSP fame:
https://valhalladsp.com/2021/09/22/getting-started-with-reverb-design-part-2-the-foundations/
https://valhalladsp.com/2021/09/23/getting-started-with-reverb-design-part-3-online-resources/

In essence, here's the journey; assuming you know at least a little bit of C++

1. Learn how to create a ring buffer (aka my Ring Delay thread)
2. Learn how to create an all-pass filter using a ring buffer.
3. Understand how fractional delays work, and the various types of interpolation.
4. Learn how to manage feedback loops.

Loads of resources out there for sure!

Lesson 5 - SNEX code in a bit more detail.

So I'm by no means an expert in C or C++ - in fact I only just recently started learning it. But here's what I've sussed out in regards to the HISE template.... and template is exactly the right word, because the first line is:

template <int NV> struct audio_loader

Somewhere under the hood, HISE must be setup to send in an integer into any SNEX node, that integer corresponding to a voice. NV = new voice perhaps, or number of voices ????

The line above declares a template that takes this NV integer in, and creates a struct called audio_loader for each instance of NV. Indeed we can prove this by running the following code:

template <int NV> struct audio_loader
{
	SNEX_NODE(audio_loader);
	
	ExternalData data;
	double note = 0.0;
	
	// Initialise the processing specs here
	void prepare(PrepareSpecs ps)
	{

	}
	
	// Reset the processing pipeline here
	void reset()
	{
		
	}
	
	// Process the signal here
	template <typename ProcessDataType> void process(ProcessDataType& data)
	{

	}
	
	// Process the signal as frame here
	template <int C> void processFrame(span<float, C>& data)
	{

	}
	
	// Process the MIDI events here
	void handleHiseEvent(HiseEvent& e)
	{
		double note = e.getNoteNumber();
		Console.print(note);

	}
	
	// Use this function to setup the external data
	void setExternalData(const ExternalData& d, int index)
	{
		data = d;
	}
	
	// Set the parameters here
	template <int P> void setParameter(double v)
	{
		
	}
};

There are only three things happening here:

1. We set the ExternalData as in a previous post.
2. We establish a variable with the datatype of double called 'note' and we initialise it as 0.0. But this value will never hold because....
3. In the handleHiseEvent() method, we use e.getNoteNumber() and we assign this to the note variable. We then print the note variable out inside of the handleHiseEvent() method.

Now when we run this script, any time we play a midi note, the console will show us the note number that we pressed. This is even true if you play chords, or in a scenario where no note off events occur.

That's a long winded way of saying that a SNEX node is run for each active voice; at least when it is within a ScriptNode Synthesiser dsp network.

The next line in the script after the template is established is:

SNEX_NODE(audio_loader);

This is pretty straight forward. The text you pass here has to match the name of the script loaded inside your SNEX node - not the name of the SNEX node itself.

Here you can see my SNEX node is just called: snex_node.

But the script loaded into it is called audio_loader, and so the reference to SNEX_NODE inside the script has to also reference audio_loader.

@d-healey said in scriptAudioWaveForm and updating contents:

@Orvillain Did you try, AudioWaveform.set("processorId", value); ?

Yeah I did, and it does update it based on a follow up AudioWaveform.get('processorId') call - but the UI component doesn't seem to update, and still shows data from the previous processorId. When I compile the script, then the UI updates one time... but not on subsequent calls to the set method.

I figured I needed to call some kind of update() function after setting the processorId, but no such luck so far.

Hmmmm I started using it for the modulation matrix controller, but there were things I wanted to do that I couldn't, so I wrote my own script panel matrix controller using LAF instead.

LAF is - I guess - a subset of the JUCE graphics API, so I'm more comfortable with LAF. CSS hasn't really fully clicked for me yet, if I'm honest. I've never needed it for anything else I've ever done, because none of it was web based and it was all Python, c++, JUCE, Lua, and C#.

@Christoph-Hart

I'm still getting a crash when loading files into the wavetable creator and resample mode. It doesn't seem to happen when I use one of the other resynthesis modes.

>	HISE Debug.exe!juce::MemoryBlock::MemoryBlock(const juce::MemoryBlock & other) Line 42	C++
 	HISE Debug.exe!hise::getMemoryBlockFromWavetableData(const juce::ValueTree & v, int channelIndex) Line 1324	C++
 	HISE Debug.exe!hise::WavetableSound::WavetableSound(const juce::ValueTree & wavetableData, hise::Processor * parent) Line 1357	C++
 	HISE Debug.exe!hise::SampleMapToWavetableConverter::rebuildPreviewBuffersInternal() Line 712	C++
 	HISE Debug.exe!hise::SampleMapToWavetableConverter::refreshCurrentWavetable(bool forceReanalysis) Line 1597	C++
 	HISE Debug.exe!hise::SampleMapToWavetableConverter::setCurrentIndex(int index, juce::NotificationType n) Line 1637	C++
 	HISE Debug.exe!hise::SampleMapToWavetableConverter::parseSampleMap(const juce::ValueTree & sampleMapTree) Line 854	C++
 	HISE Debug.exe!hise::WavetableConverterDialog::loadSampleMap::__l2::<lambda>() Line 787	C++
 	[External Code]	
 	HISE Debug.exe!hise::WavetableConverterDialog::run::__l2::<lambda>(std::function<void __cdecl(void)> & f) Line 942	C++
 	[External Code]	
 	HISE Debug.exe!hise::LockfreeQueue<std::function<void __cdecl(void)>>::callForEveryElementInQueue(const std::function<bool __cdecl(std::function<void __cdecl(void)> &)> & f) Line 1316	C++
 	HISE Debug.exe!hise::WavetableConverterDialog::run() Line 936	C++
 	HISE Debug.exe!hise::DialogWindowWithBackgroundThread::LoadingThread::run() Line 397	C++
 	HISE Debug.exe!juce::Thread::threadEntryPoint() Line 96	C++
 	HISE Debug.exe!juce::juce_threadEntryPoint(void * userData) Line 118	C++
 	HISE Debug.exe!juce::threadEntryProc(void * userData) Line 66	C++
 	HISE Debug.exe!thread_start<unsigned int (__cdecl*)(void *),1>(void * const parameter) Line 97	C++
 	[External Code]	

That's the debugger callstack in VS2022. The main error I get is Exception thrown: read access violation.
other was nullptr.

It makes no difference as to whether I use a SampleMap in a sampler, or I drag and drop the sample directly into the creator.

Is this anything you know about or could investigate??

@resonant

My project is setup for this:

HISE_NUM_SCRIPTNODE_FX_MODS=32
HISE_NUM_POLYPHONIC_SCRIPTNODE_FX_MODS=32
NUM_HARDCODED_FX_MODS=32
NUM_HARDCODED_POLY_FX_MODS=32
ENABLE_ALL_PEAK_METERS=1
 JUCE_LOG_ASSERTIONS=1

If you're going to be using hardcoded modulators, then you're definitely going to want to activate some of the mods. Saying that, I don't think having them set to zero would cause a crash. Would just cause modulation to not work.

If you're using a hardcoded module, are you initialising the SlotFX properly when your plugin loads? I'm not 100% certain, but if you're not ensuring the slot actually has the effect and then you're trying to map modulation to it at any point, that could cause a null pointer and a crash.

@Chazrox In the UI editor, the foldable panel on the left hand side that shows all of your added components. There's a search box at the top of it, but it is a bit ropey.

Component search seems a bit iffy to me. If I search for something like "Engine1SamplerTabArea" then depending on what the names of my other components are ... I might end up with a load of stuff in the results that just isn't anything remotely to do with my original search term.

How does it work?

No crashes in my plugin no. If you're getting a crash, the initial idea I'd suggest is to check for deferenced or null pointers. Are you trying to access any variables, functions, or namespaces that exist when you're in HISE standalone, that might not exist in the compiled plugin??

Using the Builder API can be a cause of plugin crashes too.

Hmmmm I started using it for the modulation matrix controller, but there were things I wanted to do that I couldn't, so I wrote my own script panel matrix controller using LAF instead.

LAF is - I guess - a subset of the JUCE graphics API, so I'm more comfortable with LAF. CSS hasn't really fully clicked for me yet, if I'm honest. I've never needed it for anything else I've ever done, because none of it was web based and it was all Python, c++, JUCE, Lua, and C#.

@David-Healey Oh weird. Must've deleted it somehow. Fixed.

HiseSnippet 1768.3oc2Xs0biaaEFz1LSrSSaRZlN4g7.FOcxnsxUQxV1RNYxDYKa4U6JsRwR6tYaeXGHRPIDSBv.BIaMc1o8w9yK+Fxuf7Tdc6AjTRfwZscT1la7AYdtA7gCN2n6JENznHgDYsU+ogTj0evt2TtZT8QDFG07Dj0aY6H7EREMRgNdZHIJh5hrrV+LsBVatAJ94697iI9DtCcAKD5IBlCsEKfoVvsasGx78aPbo8YAFZWtVSGAuNrUiAvrtcQTHw4BxP5iHZ0VyFceRzHj0eyduJGP71sREJ06fhGVoh2AUbH6Rok2qb4AtjA6VspS08qTEY8Fm5xTBYOEAPOxZiiEtS6MRbIOYCdBKhMvmpIJg5A6bB6FBeW8QTyEUeDy2s6LuTDBYY2cgOa8De16a2l4xlyegu6chEfWXgoCzZsrva8LvqjI7JZ.uk.o0LfzFytF6KI7nPQDUlBE7BN3R3LPYtjiBDi4F2VeTseDnrzMhRz0A46Z2yQxBUKjjDv0jqnROBDLYBxDcQq88qYWW.ZvUEBHWPaHAh4Vja+hE2AC+buOcKHdJRgmPjXehG9yvyrxQRgyRKgCwukPbwQb2FTpeNvhs.EKHoCYQvx0XL2QwD7ba6JIWdDm3OEbcGCQkCkfWxc6cvdyTY3NXwfu5da8u1BCOCK3Aw3G46mq3UMZTJ9AV8Wn2g6vVblj8JV7MgiPjvmVP6Tjp9xwzbdD+H5rU+1W7tD0naB4QTURRXtj+DU3xQLkdCzxi+4i+XrdEwpQTLIcYwgv5hIQXBNRIEWPcw9LNEyfq.JwEK7.IZuBHf.9+zcSuNZDkCvPA8RDilBZM1Auaghy8ZKtKa3KHJFeXelOsjws5PMvCBEbfH21YzZa8Rjgi9Xds..v4cuOcliAK3ORnnc34hc7a8hsv+PQddKUlFPRAbRkKUrtrm7lLLGebv.pbG3z5OlNWQHqIaln8cKSzIw+Xnnf2jyTcBo7WUQNTpSEd6wMOgnHPQFqTdfdgPrGSCAqSnSfR7IYyaZeBM5BkHLV2zaBnRjJsFYR9q40.hAI1+I6L2LnqL6fLcNw+4I0RAvrcqquPAg4nACm00Xy2XlcPDavBtu7ku7+lk6tlJGe.sFYqSA1dtano61eBd6VM5faKbG6S.Oeos2QqRStK8JP3euTL4wi87nxVT9PHy5SvkKFyE5h3Kt7oB4EQPiLJHHNQcqWftj4pFM+bU6eWaDkMbjQQ2mUSQuRc8C0RpfBMXlANytN5dyoBfPqLUQ0UJ4QL0Tyd2u9ZEYYfQ6DL9go275.+mPjLBWMGzw3Emp.VqANUECu9si+zVCVeq8h7oPIMDpizWz0mLMWDIHzmdNb71Am7dTWnXtuv4hqmJFlbFhklaP706qrHvq85C+HqBr58i+okieWCFeW6tLkynkGMt1RtM0yy7ZJZDc8Q0da6SgqSG0B.tgciu7+OykYt8+wjs+sr6AcEimvNdy+Kwz3mRlPwmQ4T40C3yNm82bWmyN7NOmcGGEr8yGAzbg6QCX8g53QlLebDLyE8qOWeaZxutfHWpnu6ya.GxkZSOhZrLNr3GN4IDFr9MM9doUb78M9U236+Vnrt4WXr4LL1ioqidJeB0GJWDiw2CpO3QF6qlwMarbaAWDNRvYNlWzmSUR1vgToI1W5A5HkBF+dAm2u14TeJwLn8uVqEDrQjfehth9hR28Vb2z80GXm.2j1Z+hbuYFZ8NIP01FFoIMdJ6vM2NtzoviobmLUq0kXZxM4nql4IjAosLladK5PXiL4zmBiIBUCcxzLOPHTihmGLHS0HXV8vS4D3j6Zpe2QP..zrEFoOSoEXY6KZSzeJTccmbSgMGxERZRC7L0vFGoDAyN.Hqu2tT0hEx9Loi7nm15P8qGVOltH8AEOzP9Tm6WO+jKuxau5Kn61lFseBcohEOM+8C7GWIgNre9l485JNtbBcmxrGkeh24mlJu6E62Iu2f+wgo1eYiAeQ75mRe0fyNOuAdJ8.uGmeuprAoxeF7juvdMdX55e34bm7dmc7fTZ3GOS6Q8Tzvjoh+m1GTtvfp7tKNulOdU4Sh5T+ocdPdPoIU5M7qOqXm1Sa06v6epxc+5J29S5.ucR9SfW2Ow9C9hgO7vBnWeojqcGSI+ywg7yis0A++BkMd6nbdx1uRQ4MNX25+9dvtyEi0evZaBz3B9dU6GMNnGLOkCE1cNm5q+5bq0z0SRnKpoSFnh6FS.eR5KSEVRSakJrzLg+rrGADGo34NIewgNQ5Mi4.mad7+00MsaqowkPweEh4cY.LYzycbxtTWyvcWUC2aUMr7pZ39qpgGrpFVYUMr5sandv0iFC8xRRMQn1cOMoht07VnVqi9eJuzmhC

This gives a plotter LAF like the following image:

As far as I know, based on conversations with Christophe, this stuff is unavoidable. If you want any of these seamless start/end/loop/direction changes, you need to write a custom sampler from scratch in c++ or SNEX, and use it in scriptnode.

@David-Healey Well I don't know what else to tell you: https://forum.juce.com/t/int64-t-vs-juce-int64/45358

As reported here - it is a typedef issue, specifically affecting Linux compiles.

Actually, I might have that wrong. That thread is about juce:int_64.