@clevername27 well yeah.

This ain't a JetBrains IDE, references don't automatically change everywhere.

It should throw an error (because the property you're now referring to returns undefined), then you know you gotta change it there. But no, it's not automatic.

Same thing if you change the ID of a component in the property editor. Any script references to it are now invalid (because you're getting the reference by means of ID).

@Allen Oh I see

Ran in to this again. It works for the MidiMuter but doesn't seem to work for others like CCSwapper or LegatoWithRetrigger

Edit: So it does work but you need to know the secret spellings. CC Swapper and Legato with Retrigger - spacing and capitalisation are important.

@Christoph-Hart

It seems that the drag and drop is broken now though.

You used to be able to copy paste .h files for external nodes. Now that doesn't work. the nodes don't make any sound unless you create them via Hise. Particularly for scriptnode synth nodes. Effects seem to work when you import them that way, but not scriptnode synths.

@VirtualVirgin Another workaround could be this inline function.

// a more accuate rounding function for -2.1474836485e9<=value<=2.1474836465e9 inline function roundBetter(value){ local r = Math.round(value); return (r+.5==value)?r+1:r; } const testArray = [0.,128.,-128., 32767., -32767. , 65535., -65535., 16777215., -16777215., 2147483646., -2147483646.]; for(v in testArray){ for(i=-11;i<11;i++){ Console.print("round("+(v+i+.5) + ")=" +Math.round(v+i+.5)+" ?=" + roundBetter(v+i+.5)); } }

@Lindon That's odd…a web page shouldn't be able to bring down a browser. (Wait, did I write it?) Does the Vimeo embed in my post work for you?

@aaronventure According to the docs it returns the ID (string)

@sletz I mean Hardcoded Master FX that is compiled from FAUST node core.faust not being modulated via LFO

what is the problematic Faust DSP code?

I don't know which one is responsible but the C++ code and RNBO working fine in Hardcoded master FX.

@d-healey
Cool, I will have a look. Thank you! :-)

@Christoph-Hart you are probably the only one who can help me with this

Did some more digging and found that

The bug isn't present in Rosetta builds

There are a few mentions of floating point values on ARM builds in JUCE's GitHub issues, including this one with a related forum post. Possibly related?

@ulrik oops, I was too ambitious here. I wanted to erase the warning message, not the flag. Should be fixed now.

@Lindon I do feel you, the synthesizer group has a lot of advantages so I'm really voting for a fix here too

@Lindon I can confirm channel aftertouch works fine, if I send a poly pressure message though if sounds like just all notes instantly get 100% aftertouch all over the place

@Christoph-Hart can you get us more info on how to get polyphonic aftertouch to work properly? in theory it could work like normal after touch just check if the transmitted note number in the message matches the played note before outputting it on the midi_cc node and otherwise ignore it, please let me know if I can assist in figuring this out, apparently it's important to many of us and not working properly for some years

@Christoph-Hart I think the thing is, the mulitmics actually break it. It works fine without multimics.