@aliabr_prod which version of Faust are you using?

@Christoph-Hart
Yes, you're quite right, that probably is the real cause.
Still a bit weird, since an older install worked as should.
Although it was the one with an .pkg, or was it .dmg, installer from the website,
so that might have to do with it as well.
And as the admin and the sole user of the machine, the writing rights should've been ok.

You just need to run a command to tell the system where xcode is.

Make sure your xcode app is in /Applications (not the user folder, the system one). Then run the command

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

I was not planning on making another one today as I am deep diving into glsl, but got an idea and had to flesh it out. 🥧

So this is "KOMPRESS"

Minimal with a central large knob, Figma design.

This one uses quite a lot of blur for the glow on the black knob which is a HISE problem but since its stationary on the knob , I could move only the line indicator on the knob and just either print the blur or if keeping as vector see if I can get away with one blurred component?

KOMPRESS UI

KOMPRESS Final.png

KOMPRESS DAW

KOMPRESS DAW.png

KOMPRESS D16:9

Wide AD.png

KOMPRESS 4:5

Long ad.png

@Christoph-Hart haha thanks man! i dont know what to say. im too new at this stuff, its all hieroglyphes for me.

@combamusic Thank you!

@Jeetender That is strange. Didn't you see the latency reported in the DAW?

Removing the module that causes latency is not a viable solution. Once you know the latency of your plugin, you should just be able to report it to the DAW with this method.

So it's not an "in plugin compensation" but telling the DAW "hey, I introduce this amount of latency, please compensate for me" (in which "this amount" is your job to determine)

@ospfeigrp You can draw that kind of thing using look and feel or paint routines, you'll need to get familiar with drawing arcs.

I figured it out.
In order for the matrix modulator to properly work I need to set my filter cutoff to 100%.
Then use the "Value" knob in the Matrix Modulator module as the main Filter Cutoff knob.
I was using a 2nd UI knob that I wired to the Cutoff, but the Matrix Mod module expects you to use "Value" as the main knob/slider and "Intensity" as the modulation depth.
Setting the filter to 100% ensure that both "Value" and "Intensity" have control over the full range of the filter.

@griffinboy sick isn't it? I wonder myself how I got there, but then again given Idid nothing else for the past months than spend every free hour on this... it's a bit pathetic ;))) I need to start having a life again lol

UPDATE: Native-Authoritative C++ Licensing Bridge

SoundSync HISE package is rebuilt so the UI stays in WebView/HiseScript, but the licensing authority is now native C++. The WebView only collects user actions and renders safe public state. C++ handles activation, validation, restore, protected storage, device identity, offline grace, deactivation, and the final mayOpenProduct access result. HISE copy protection then reads that native result.

It’s not a pure C++ UI replacement. It’s a hybrid: WebView for branded UX, C++ for licensing authority. That seems to fit HISE better because WebView is still the easiest way to keep product branding, storefront, My Products, and login flows flexible, while C++ owns the trusted licensing path.

@Lindon thanks for the suggestion.

@Orvillain said in Why I'm not making a Windows installer (nor code-signing):

Interesting, I wasn't aware of that. More details would be lovely! Private message if you need to :-)

https://forum.hise.audio/topic/14949/why-i-m-not-making-a-windows-installer-nor-code-signing/13?_=1785506496174

@David-Healey nope, I'll need to work on the details with Tobias when I'm back from vacation.

@lijas90 your installer needs to create/write to the Link file in the %APPDATA% folder with the path to your samples. so on Windows this is LinkWindows, on MacOS its LinkOSX.

As an aside putting samples in the %APPDATA% folder system, as you are doing, is generally a bad idea, esp. for Windows users who often have small C; drives (where the %APPDATA folder resides) as thus there is not enough room for the sample set. Better to ask the end user where they want to keep their samples during the install.

@lalalandsynth its all brand new to me. Just passing along the info. Im sure there's a fix.

@Chazrox yea similar to cosmos but cross platform at least win and linux it have a nice pixeldrain feature for sharing uploading user generated samples etc

@dannytaurus thank you so much my friend! 😁🙏🏻