Matrix Modulation System - Last Call for bugs fixes & changes!!

[Christoph Hart]

@DanH just use the css inspector to get the CSS selectors (#delete for the column and .delete-button for the button itself.

Not much to add to the docs here…

I‘ve also added a property for disabling the unselecting of exclusive source draggers.

[DanH]

@Christoph-Hart thanks, I was just about to look for that.! So do we add that into the data? I can't see a property tab for it.

[ustk]

@DanH yeah just add this

"UnselectableExclusiveSource": false

or delete the floating tile and create a new one

[DanH]

@ustk ah yes the old create new component to see the changes You'd think I'd have learnt that by now!

[DanH]

@Christoph-Hart So since we have the new shiny delete button do we need the 'remove row after selecting "no connection"' behaviour?

Also I'm experiences a little weirdness with the delete button - the matrix components seem to cramp up to the left in my project if no source is selected and in the mod matrix example snippet the aux intensity and plotter combine too. Will test some more

EDIT - Oh I don't think the AUX combobox is being drawn in this case.

[DanH]

@ustk

"UnselectableExclusiveSource"

this working for you?

[DanH]

@Christoph-Hart just a heads up but weirdly I'm getting the exact same crash just trying to move panels around in my main project. Will test more tomorrow

[ustk]

@DanH said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

@ustk

"UnselectableExclusiveSource"

this working for you?

Haven't tried, my project still either crash or refuse to compile the DLLs with the new Hise... So I'm stuck & lost for now...

[DanH]

@ustk for the dll try removing the networks from compilation so you're only compiling the nodes. Once that is done restart hise and add the networks back into the compile process and compile again

[ustk]

@DanH thanks, that’s what I did but it’s the nodes that are not compiling.
Although they compile from XCode directly, but then in this case the project crashes when opening…

So it’s either:

• xcode compiling nodes but leading to a project crash
• opening the project but nodes not compiling from the wizard

[DanH]

@ustk what if you just open the project in Hise but don't load any xml? Can you compile that way?

[Christoph Hart]

@ustk said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

the project crashes when opening…

Can you open it under the debugger?

[ustk]

Opened a new thread to stop polluting this one
https://forum.hise.audio/topic/14252/nodes-compiled-project-crashes

[DanH]

@Christoph-Hart any idea what's going on here? I've selected the top params to have external modulation enabled but it's suggesting something also happening with the nested params in the child container.... ui glitch or bug?

[ustk]

@Christoph-Hart said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

@DanH just use the css inspector to get the CSS selectors (#delete for the column and .delete-button for the button itself.

Can't seem to style the new delete button nor the column... EDIT: just me being dumb...

[DanH]

@ustk I managed a it a bit but haven't gone back to sort it out. This uses the general button css before it in the script

/** ============================================================ DELETE ============================================================ */

.delete-button
{
  width: 20px;
  padding: 0;
}

.delete-button::before
{
  left: 0;
  top: 0;
  width: 100%;
  height: 100%;
}

.delete-button::after
{
  content: 'X';
  position: relative;
  color: #C4C3C3;
  font-size: 12px;
  pointer-events: none;
}

[ustk]

@DanH How sh...! I wasn't editing the right css file !

Thanks!

[DanH]

@ustk lols

[DanH]

@DanH said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

@Christoph-Hart So I'm not convinced that the accumulated range is helpful / necessary.

So I need to row back on this a little bit

Displaying the Accumulated Range and a range isn't important to me, but I definitely do need the accumulated range values in order to have my little white dot display how the modulation is behaving, accumulated or not.

So is it possible to get something like obj.accumulatedModMin / obj.accumulatedModMax as obj items in the drawRotarySlider function? Might also need a currently selected range too (although this is basically "modMinValue": 1.0,
"modMaxValue": 1.0, I think?).

[DanH]

@Christoph-Hart Would it be possible to have a value parameter inside the extra_mod nodes -this way we could change the values whilst editing the network. Currently we have to break all the connections and then reconnect them when we need to compile. Obviously the value param would be ignored in the compiled network.