@Christoph-Hart bumpy bump

@Christoph-Hart This bug has been first reported in 2021 and it's still there

Encountered nan as well in some occasion

@Christoph-Hart Alright so it did fix it!

@Christoph-Hart said in Nodes compiled, project crashes:

but that's some advanced debugging skill required there :)

That I do not have for sure lol
In fact I first looked at it without seeing, but tried again with eyes opened and I confirm it easier to find this way

@Christoph-Hart Ok cool at least you've got a lead!
I have many nodes so we never know which one is causing the issue... or can we?

@Christoph-Hart Yep here is the crash stack

Note that I can now compile the nodes from the wizard as well. In fact I had to open xcode at least once to make the .xcodeproj to be created and found by the wizard...

So I did compiled the nodes (not the networks) as debug and here's the result:

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

@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 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 yeah just add this

"UnselectableExclusiveSource": false

or delete the floating tile and create a new one

Updated with the new submodule version, selected JUCE 8 (because, yeah, why not...).

During compilation, XCode complains about the Projucer being outdated (v6.1.4)

"This project was last saved using an outdated version of the Projucer! Re-save this project with the latest version to fix this error."

@MysticForgeRider I'd add that you shouldn't have warnings on the top right of the parameters. Click on them to correct the range.

Except for some exceptions like bypass_node, unscaled_nodes, etc... (which for shouldn't be the case @Christoph-Hart. A warning means something's off, so they should be removed for those special cases...)

@Dan-Korneff Nice

@David-Healey said in user password containing ":

@Dan-Korneff Did you make a PR?

The 10 grand question

@daniloprates I don't think the dynamic component feature is ready yet.

One way you can do is have a common parent panel, then add child panels to it dynamically following the layout your expansion requires. A child panel can be turned to any component like slider, label, or any more complex widget

@David-Healey I just confirmed that \ also leads to issues, so you better add this rule to your current snippet

@David-Healey Oh nice

What about the backslash escape char \? I'm afraid it can too lead to issues...

I am testing a plugin called WP Password Policy. For now the special chars can't be specified but I just reached out the team and they said it's a nice addition so they'll push it along with the next update in about a week... Very reactive

@Christoph-Hart

Ideally the ring around the knob shows the accumulated mod value while the hover popup shows the range for the selected source.

Well it shouldn’t be a straight accumulation (aka addition) because a positive value can compensate a negative one perfectly, drawing no arc at all, while the modulation actually moves following the combined value

The range should instead cover from the lowest min to the highest max

@dannytaurus strange it's not forbidden by default...

I have a situation where a user has a " in his password.
While wordpress is allowing it, Hise doesn't, and adds the escape char \ so the password sent during the authentication is altered...

Is there a way to prevent this in Hise or should I just prevent from using " on the password creation page?
Any recommended WP plugin for this?