@Christoph-Hart I found the mistake - I had accidently reset the Server.HttpHeader() of the request when passing it into the makeHttpRequest function. Therefore only the the Auth Bearer Token was passed and the Content-Type was automatically set by HISE. Now I correctly appended the Bearer Token within the request and everything works perfectly fine :)

Thank you guys so much for your help, I really appreciate it!!

@Christoph-Hart this is how im passing the JSON data:

inline function requestDirectLicenseActivation(deviceName, deviceSignature, accessToken)
    {
        local requestData = {
            "deviceName": deviceName,
            "deviceSignature": deviceSignature
        };
        
        currentAccessToken = accessToken;
        
        makeHttpRequest("POST", "/client/licenses/" + PRODUCT_ID + "/request", trace(requestData), handleDirectLicenseResponse);
    }

Even when converting the JSON object using trace, I'm getting the 415 error due to an unsupported media type, as the endpoint will not receive the content as application/json, as its converted to x-www-form-urlencoded data.

@Christoph-Hart Another problem im still facing is the JSON encoding issue that was also mentioned in the linked thread.

Im struggling to send a POST with regular application/json Data, as HISE seems to package the data into x-www-form-urlencoded when using Server.callWithPOST. Everytime I'm trying to send out a POST request to receive a license token I'm getting a 415 error.

Do you have any idea how to change the format of the request in a way that the regular JSON dictionary will be transferred?

Checked the request and its format with Postman:

Using the x-www-form-urlencoded (same as HISE probably uses)

Using the JSON dictionary to receive a license token:

@Christoph-Hart That was the solution! Thank you so much!!!

@Christoph-Hart Okay great, this fix already allowed me to pass the plain string into the function.

Another problem, that also was mentioned in the referenced thread is that data is not being processed as text/plain or plain JSON as it looks like HISE is sending the data as URL-encoded form data (like a web form submission)

This leads to problems in calling the sign-in API endpoint of Moonbase - this is how Moonbase expects to receive sign-in data:

POST https://demo.moonbase.sh/api/customer/identity/sign-in?email=test@example.com
Content-Type: text/plain

Password1234!

I need to embed the mail into the URL endpoint and pass on the password as plain text. This is how I implemented it within HISE:

makeHttpRequest("POST", "/customer/identity/sign-in?email=" + email, password, function(success, response)

Due to the faulty URL encoding the data is being received in the format shown below:

I am not sure how to create a workaround for this..

Re: Server.callWithPost content type

Hello everyone,

I'm currently working on implementing a licensing system using Moonbase within HISE. One issue I recently faced regarding user sign-in was working with the callWithPOST function. As the Moonbase API requires me to pass text/plain instead of a json object, I can't get the sign-in to properly work. Is there any way to just pass a simple string via the callWithPOST function? anyone else, who faced a similar issue and found an workaround?

Moonbase Docs Sign-In: https://moonbase.sh/docs/licensing/api/#sign-in-a-customer

inline function makeHttpRequest(method, endpoint, data, callback)
    {        
        // Set base URL
        Server.setBaseURL(MOONBASE_API);
        Server.setHttpHeader("Content-Type: text/plain");
        
        currentHttpCallback = callback;
     
        if (method == "POST") {
            Server.callWithPOST(endpoint, data, function(status, response) {
                if (status == Server.StatusOK) {
                    Console.print("LicenseManager: Request successful");
                    currentHttpCallback(true, response);
                } else {
                    Console.print("LicenseManager: Request failed with status: " + status);
                    currentHttpCallback(false, {"error": "HTTP " + status});
                }
            });
        } else {
            Server.callWithGET(endpoint, data, function(status, response) {
                if (status == Server.StatusOK) {
                    Console.print("LicenseManager: Request successful");
                    currentHttpCallback(true, response);
                } else {
                    Console.print("LicenseManager: Request failed with status: " + status);
                    currentHttpCallback(false, {"error": "HTTP " + status});
                }
            });
        }
    }

/**
     * Sign in customer to get access token
     */
    inline function signInCustomer(email, password, callback)
    {        
        // Store callback in global variable for nested function access
        currentSignInCallback = callback;
        
        // Make sign-in request
        makeHttpRequest("POST", "/customer/identity/sign-in?email=" + email, password, function(success, response) {
            if (success) {
                Console.print("LicenseManager: Sign-in response received");
                // Parse JSON response directly without storing in variable
                if (isDefined(parseSimpleJSON(response).accessToken)) {
                    Console.print("LicenseManager: Access token received");
                    currentSignInCallback(true, parseSimpleJSON(response));
                } else {
                    Console.print("LicenseManager: No access token in response");
                    currentSignInCallback(false, "No access token received");
                }
            } else {
                Console.print("LicenseManager: Sign-in request failed");
                currentSignInCallback(false, "Sign-in request failed");
            }
        });
    }

@tobbentm any recommendation from your side on implementation? why cant we just pass json with the sign-in function? would have loved to use the JUCE module from you, but as you already pointed out, this is only compatible with JUCE 7.

Any help is greatly appreciated!

@Christoph-Hart haha, absolute madness from Apple, no one could have expected such an unnecessary change
thank you for the quick fix, that was indeed the solution - now the export runs just fine! you saved me from downgrading my OS again^^

Lets see when I will encounter my next bug with this new macOS update...

Re: ERROR: Cycle inside a single target

Hello everyone,

as I already upgraded to macOS Tahoe recently I was hoping to be able to go through the compilation process of my VSTi plugin as I have been before. Unfortunately I'm getting the same error as mentioned in the referenced thread..

️ Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
note: Target dependency graph (3 targets)
error: Cycle inside a single target; building could produce unreliable results.
** BUILD FAILED **

Standalone Export goes through just fine...

@Christoph-Hart One thing I noticed in the previous thread was a message from Christoph implementing a fix regarding the Copy Step - he then committed a fix, which should hold until macOS 20
Now we made the jump to macOS 26^^ so this is the reminder haha

I'm on the latest commit of the development branch and already tried downgrading to xcode 16.4, both unfortunately not working...

Any help is greatly appreciated!

@d-healey I also saw this old post from you, where you build some sort of factory preset system: https://forum.hise.audio/topic/324/factory-preset-creator

Do you feel that such an approach would still be suitable for the current state of HISE?

@d-healey Is an UI component like a sliderpack mandatory in order to save the state of an effect? My preference would be that I do not have to link the effect/modulations to UI as users will never be able to configure these on their own.

Hello guys,

I'm looking to create a sample-based VST which should include 20 factory presets. Therefore I would like to create lots of user presets with all kinds of effects, modulations and more. Currently my problem is, that changing settings within an effect doesn't get saved with the user preset when saving, as no UI component is linked to the corresponding effect/modulation. As the factory presets will go through lots of processing and different effect chains, I want to avoid creating a second interface with linked UI controls just to be able to save the effect chain in the user preset.

Is there any best practice in HISE for saving effects/modulations within an user preset?
I saw the Engine.addModuleStateToUserPreset(var moduleId) function in the Documentation, but actually hoped there would be an easier way such as the SaveInPreset Property of the UI components but for every FX/Modulation/MidiProcessor.

Would highly appreciate some help here! :)