@d-healey I think this is a Linux compiler thing. On Linux int64_t is defined as long int - whereas Windows and Mac it is defined as long long int.

The compiler is throwing a wobbly because of that.

I think.

@Christoph-Hart - is this a bug, or is it intended???

Group Fade does support it. I'm just wondering why?

@Christoph-Hart said in CSS :nth-child() supported???:

I can add an attribute to my parameter dictionary for scale/unipolar/bipolar,

I've added a method requested by @DanH where you can setup default properties for each new connection (so you can eg. set the base intensity to 75% or whatever floats your boat.

https://docs.hise.dev/scripting/scripting-api/scriptmodulationmatrix/index.html#setmatrixmodulationproperties

siiiiiiicccckkkkk!! Nice one Christoph!

@Christoph-Hart said in CSS :nth-child() supported???:

Ah sorry, no you can't. The inspector shows all available selectors and the ID isn't one of them.

(The matrix columns can be addressed through the ID but I thought I've added it here to, but apparently that's not the case).

But yeah if you're almost there, just go with your own dragger. Note that there's a snippet in the example database that also gets you 80% there:

https://docs.hise.audio/tutorials/ui/index.html#drag-modulated-parameter

Yep, been referencing that :)

I've actually got quite a nice dragger right now. The UI is basically done. I just need to setup all the matrix connection stuff. Also I realised this probably gets me a cool benefit - I can add an attribute to my parameter dictionary for scale/unipolar/bipolar, and set the connection to that by default when the connection is created. I couldn't see a way to do that in the floating tile solution, but confess I didn't investigate very hard.

Thanks for the confirmation that I'm not a complete idiot

@Christoph-Hart said in CSS :nth-child() supported???:

@Orvillain you should be able to access them by the #id selector individually, no?

If I can, then I'm stupid. Coz I couldn't figure it out! Is okay.... I'm three quarters of the way there with my own matrix controller now!

@Felix-W Bah.... I'm just gonna write my own modulation controller then. TBH, I prefer that anyway, coz css still messes with my head.

Is :nth-child() supported in HISE's implementation of CSS?
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:nth-child

I'm looking to do different things to each of the draggers in the modulation controller. But it doesn't seem to work?

@Oli-Ullmann Yes I think you're correct. I checked the docs and there is a line about it not meant to be a dynamic state.

@Christoph-Hart

This is a bit complicated to explain. But basically.... I have a bunch of hardcoded effects. At initialisation, I create knobs in my UI.

I have a menu that loads an effect to the particular Hardcoded Master FX slot in question. When this happens, I assign the processorId and parameterId to the correct ones, and I update the matrixTargetId.

If I do this .... then my modulation for that parameter works audibly. But the UI animation, hover states, and modulation indicator completely break and stop working.

Now..... if I set the matrixTargetId when creating the parameter, and then NEVER update it...... it works fine.

I know this is a bit hard to get your head around, and maybe I'll try and make a minimal example. But as a fundamental question, do you support updating the matrix targetId parameter??

Not sure, but try putting it in a fix_block container???

@Lindon ohhhhhhhh

@HISEnberg said in Transient detection within a loaded sampler - SNEX ????:

@Orvillain Nice thanks for the tips! I'll have to look into spectral flux envelope it's a new concept for me. I'm about 40% of the way through this process myself.

Just curious how are you extracting the FFT information then broadcasting it to HISE, are you using Global Cables for this? I am trying to theorize how to make the jump from detecting the transients to updating the HISE side (transient markers, snap grid, etc.). I'm guessing just wrap all that info into some JSON and use GlobalCable.sendData to update my HISE interface and scripts!

Also agreed I'm almost exclusively doing the bulk of DSP and advanced analysis in C++ then using the HISE API and Interface builder to handle the rest, really efficient and powerful combination.

Thanks for the tips!

Yes exactly. I'm doing all the clever math stuff in c++. That gives me a bunch of transient time positions in samples. I then feed this list over to HISE across a data cable using the cable_manager in the c++ node.

Christophe had a good template for this somewhere. But in essence when you setup your node struct, you inherit:

using cable_manager_t = routing::global_cable_cpp_manager<SN_GLOBAL_CABLE(-389806413)>;

template <int NV>
struct data_node : public data::base, public cable_manager_t

{

The numbers there have to be the hashed ID of what the cable should be named. I don't really like this part of it tbh, but it is possible to setup.

Then in the constructor:

	data_node()
		: fft(//put whatever inputs you want to setup into the constructor here)
	{
                // this bit registers a datacallback function. As I understand it, any time data is sent, this function is triggered.
		this->registerDataCallback<GlobalCables::dataCable>([](const var&) {
			jassertfalse;
		});
	}

Later on you'd do something kinda like this:

// Create the JSON object
hise::JSONOBject nameOfTheObject;

// Fill it with data
nameOfTheObject[String("whatever you want the key to be called")] = sourceDataHere;

// Send the JSON down the cable
this->sendDataToGlobalCable<GlobalCables::dataCable>(nameOfTheObject;);

Use projucer to create an Xcode project.

Oh, and once I got my head around exactly how to interface c++ nodes with HISE, it has become one of my favourite ways of working. I pretty much just jump straight to a c++ node for any DSP or advanced analysis thing; whereas my very first transient detector was written in the HISE JS layer, and believe it or not it was quite good!! A little slow, but it did work.

@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.

Figured it out. It does support addModulator. This is how you do it:

Content.makeFrontInterface(600, 600);

const var builder = Synth.createBuilder();
builder.clear();

const var generator = builder.create(builder.Effects.SlotFX,
                                     "generator",
                                     0,
                                     builder.ChainIndexes.FX);


const var slotfx = Synth.getSlotFX("generator");
slotfx.setEffect("Hardcoded Master FX");

const hardcoded = Synth.getEffect("generator_Hardcoded Master FX");

const numP = 4;

for (i = 0; i < numP; i++)
{
    hardcoded.addModulator(i, "MatrixModulator", "P" + (i+1) + " Modulation");
}

builder.flush();

It doesn't seem like slotfx or hardcoded support the .addModulator() method.

I've got this far. What I want to do is create a matrix modulator for the first 8 hardcoded modulation slots.

And I assume these are the modulation colour references to use:

		HiseModulationColours::ColourId::ExtraMod
		HiseModulationColours::ColourId::Midi
		HiseModulationColours::ColourId::Gain
		HiseModulationColours::ColourId::Pitch
		HiseModulationColours::ColourId::FX
		HiseModulationColours::ColourId::Wavetable
		HiseModulationColours::ColourId::Samplestart
		HiseModulationColours::ColourId::GroupFade
		HiseModulationColours::ColourId::GroupDetune
		HiseModulationColours::ColourId::GroupSpread

Is there any limitations around which colour a particular parameter should use? Or is it really just down to how you want it to appear in the module tree??

And for the ParameterModes, would it be these ????

modulation::ParameterMode::ScaleAdd
modulation::ParameterMode::ScaleOnly
modulation::ParameterMode::AddOnly
modulation::ParameterMode::Pan
modulation::ParameterMode::Disabled

Woaaahhhh that's amazing!! I really dig it! And honestly, seems so much easier to my mind than messing around with scriptnode directly.

@Christoph-Hart Can I check with you... in the c++ code do we need to do anything special to support scale/unipolar/bipolar modes ... or does that just happen automatically when using the matrix modulator as a source, and an (for example) LFO in the global modulator container (set to bipolar itself)