@Christoph-Hart
If I don't connect the “value” parameter of the Matrix Modulator via the ‘processorId’ and “parameterId” of the Property Editor, but instead control the value via the callback function of the slider, is the modulation still sample accurate and polyphonic, or do I have to establish the connection via the Property Editor?

@aaronventure said in Quick F5 tip for Mac users:

@d-healey Hold Shift while typing to amplify my anger.

Exactly this! Left pinky on the SHIFT and hammer those keys! 😂

Same on iOS. Instead of double-tapping the shift key to lock it, I shift uppercase every character, just so it makes me more angry! 😜

@d-healey said in MIDI player laggy:

Yeah that's what I meant by he might get invalid values, because he wants to check "if something exists" not if it's true or false - or at least that's what I got from the statement.

Yeah, true (no pun intended). To check if something is defined I'd always use isDefined() because it's more readable and explicit.

But I do use !! a lot in other places because it's so consistent in what it returns.

And !! does return false for undefined, for reference.

Console.print(isDefined(somethingUndefined)); // 0 Console.print(!!somethingUndefined); // 0

Cool just to confirm for anyone else who ends up here, it does indeed work with the file_player in scriptnode

HiseSnippet 1448.3ocuX8zSabDEeVCiSvoIsopsms5IRUDxFLjf5gXL1t0sAvB6PiTOfF1cLdj2cls6NKXmnHkC8P+Vzy8qP+1zC8d9Fz9dyt16t0FJXQqQB44OuY9898dueuA5Fnr4ggp.hUo9S74DqOh1ahTOb+gLgjzoIw5SnsGuWjiPcTjtOOTSZLwmEFxcHVVq7M3trVaUh4yGdQClKSZySmhPNQIr4uT3Izoy1s92Kbcayb38EdY1cs5crUx8UtpH.QqPqP7Y1iXmyOjgaq.k7srvgDquht8laYWy4YNat416tiMaG9tCXCFTcKmZ01446VcqcY0d9N7JaSrJ1xQnUA8zLMODNzFJmI8FptTFeAmHBEm4xwAUI8faNdZx9CEtNcmROgDh0pcSIqUhIqOidfvQLa9rjFtP4TKxRZVEtNHU8V.IqLPZ0XH8XZO6.guNcEDOOf1Qp4ACXPrIKTh2Kw5Oo6qfMH0a3wFwaG.ClYv5aVoxSKC+5IecoRsjmKj7MbULGSRQagKOD1ppqR4tNtiRChj1ZgRVVIOTo4GIW+Ikdao0J8tRk+mKMXvBWCwRfx0kGrvkwblfqyv0kQdmwCdZ4KXtQ7YaD3n7DewaFwaGSMY1nR1QJzG4ySF2V45fDJ984CSjDtEBXERPHb2ZS35ySBWFx7GXWvGnB7HBGLEJ2bUIFmIakkCSyHVeI8scO9nuq098Os8QurYqie2IBkKWW9PkHjuwkrKHAL44bvoCfHM0BM0LSKoCN9298hwPzfqUhw0iRvUiHsVIM.ZMZ7fEfDxq5zDACjRk3qf+6yCzBjlsZxu.z.hyOWi1jGNRq7MjgmuRhLiE8VSGiyBfIYG3Ok663XzyLmX41uFiMo2XwafidE2w6+w5W8c3yB.wJn1AW4QzFZog46gtLY95UPoP4D4xz4kOPg0jEfT6b0rXgoLTnmjU38VnoT4Z0TtoP7wztBs8vEiwBK.iX1++AXLQI9gzVCFvs0o.bUZ6WurxtUt4xtz36uTRJ.bm3kmKiHKHNLxKU2Dq9vxwopv+BMULyOfCYR79pttrIqGx77c4GC.+okOyUYOpm3M74U.SxJaf6Xc6gLoj6FtLBkEui5PQNVEoExyOfoCDP0DE7+dPyca99InC4fBnFY73JSUn5wkNlA+E7IYwpyHLXwpSWLUdkbHWeoJXjIFk7ch08w.xWDKefjIO3zjX0XxdttpKQQAQRRLDhLy0U4NwenRJrwoh2wTLummJxnYY.dZEPioAlo9.7Xk9LgKVPzKJD5V3bjrGbNlWHYsxI7fPycdOZkMfefBjCUNvR2qMyFX+IcY5gXkF1.BRq4AaXOK89Jbnb4ZlGMcEaDuooOzJFsfS5YTFgmYgw5tSExPI7BVqjQROtD.GAE3EhS36DdBtpMykbRb+AfdvaINZXbrh3VeHc.vAm5a.DImq9ofqFv2H65y6P4s+58i7n1H+6xGOsWUlJwri.siNRG93oGXKnFwA5uaLKIo6.gLwKi2yArwyFaZnlg8vmNNcDjNlZZpzXp4ylqdOM2ONaJUlu2H9kwLV1YQV8QTLBeF7b4CPptOertuxblP4wE.Cf28CnuBbrAPpjCYNLzjOfE4pmadRFvu1MC7.PuUfuHzuSeGB5O7h8hzJO3LMciHWO8Wq9bdP8ecAzOn6bkdvGSOVozsC3+TDTdO4V6Ju+s0Wnq.yStCRdp+Gu4muF9+ATD4GipX29fvGdwUEDxWDXk0OhSYy83n69TqVigKSxby7HEnQcSQHCZd4jO2Y9TKyaYkbSKyv7CSTpwW3kWMpa1G+kjUSZnTi7Xl1RK0Ck+eoIpGyNPcpc76BP289lY.EToQ0cM5A33xK30+dvep6o114Op4Lbyk0vsVVCqsrFt8xZ3NKqgOaYM74+6Fh+mHRjCwTWnnpaq3VYVsjwUBPuUxeCPIPoOE

@Christoph-Hart A bit of context.

Thanks to the new CB, we can now drag to a panel, which makes the knobs to appears. It's working nicely.

But since the knobs are now modulated, their respective CBs are called by the modulation, causing the panel to update... Is that normal/intended behaviour?

@resonant You the Best!! Thank you

@d-healey wont open, i'll try tonight though, but the code is the same

@Mighty23 Oh of course... that's probably because your snippet does not include the dll so the ranges are messed up on my side...

@ustk @griffinboy are right the scripting portion doesn’t work for realtime. I’ve recently worked on something similar to this, you can perform the FFT analysis in a C++ node then broadcast the values to HISE using global cables.

@Bicrome the issue is your air windows nodes. Whenever you update HISE you need to recompile any nodes you are using as well. If you have air windows inside of scriptnode networks it will fail initially. You need to compile the air windows nodes first, then do another round of compiling the scriptnode networks that contain them.

@modularsamples Nice, thanks for the details.

I think I’m going to get a decent Intel computer to compile for Windows and Linux x86—it’ll be easier, hehe.

@d-healey That did the trick! Thanks!

@d-healey oh wow, so simple thanks David!

@Bicrome I made an attempt long ago, had several "client plugins" listening to the main plugin, It worked using osc.
I stopped working on it but I don't remember why.

Here I wrote about it:
https://forum.hise.audio/topic/6612/possible-to-communicate-between-plugins/24?page=2

@d-healey

got it to compile and it's working now thank you

@d-healey

Thanks David, will try that.
Have a great evening.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey Is there a way to completely reset all settings and make Projucer 100% clean?
I suspect something might be hidden in Projucer—are there any folders I should delete to ensure a truly clean build?

There will be an app data folder on your system for Projucer, you can delete that.

@ILIAM said in Abeleton shows An error about a plugin I Compiled with the Latest Commit:

@d-healey For FX plugins, do we need to add or remove anything new in the build process?

Nope

@HISEnberg
Thanks for the suggestion! :-)
I had to open a panel anyway to display the ViewPort. I opened the panel using a button. In the button callback, I then always set the ViewPort to the correct position. That solved the problem for me.