@Christoph-Hart Tested it, works perfectly here! :folded_hands_light_skin_tone:

@CyberGen New findings update: Even though changing the slices setting had initially yielded positive results, it was not solving the problem 100% of the time for me. After much trial and error I found a better fix by going into the sample editor window and moving the sample end just a few cycles short from the very end. This has been giving me consistent wavetable all the way to the end.

Hope this helps. Cheers.

@aaronventure Oh, I see now.

"CONFIRM_PRESET_OVERWRITE=0" no semicolon at the end.
:beaming_face_with_smiling_eyes:

It works now.
Thank You.

@aaronventure trace is more for like properties, I mean something like (see below) but instead of this customized code, the original or default look and feel code. It would be so useful as a starting point reference.

//	ALERT WINDOW
 	laf.registerFunction("drawAlertWindow", function(g, obj)
		{
			Console.print(trace(obj));

			var a = obj.area;
			var mA = [a[3]*0.01, a[3]*0.01, a[2]*0.99, a[3]*0.99];
			g.setColour(Colours.darkgrey);	
		 	g.drawRect(mA, 1);
		});

@d-healey Is pretty straight forward, below an example.

David, thank you again.

I will change all my paths to stings, its going to take me a minute. I'll let you how it goes.

Cheers!

//	GLARE 1
	g.beginLayer(0);
	g.gaussianBlur(a[3]*0.04);
	g.setColour(Colours.withAlpha(Colours.white, 0.9));	
	glarePath.loadFromData(glarePathData);
	g.fillPath(glarePath, glareArea);
	g.endLayer();	

Hello,

I'm moving this from a general question into a feature request.

Kindly requesting a way to change the base octave triggered by the QWERTY keyboard into HISE. This would be very useful for when you don't have a midi keyboard at hand and need to input notes directly from the computer-keyboard. "Z" and "X" are a very popular choice for + and - one octave. I've also seen apps that use the keyboard numbers for direct octave jump.

Below the original topic.
Re: Computer Keyboard Octave

Thank you.

I would like to propose the addition of a "Latch Mode" to the HISE Arpeggiator. This feature would provide users with a unique creative tool, distinct from the existing Hold Mode, to expand their musical possibilities.

Description:
Arpeggiator Latch Mode, although similar to the existing Hold Mode in some aspects, offers a distinct functionality that adds a layer of versatility to HISE's arpeggiator.

One unique aspect of Arpeggiator Latch Mode is that it automatically resets the arpeggio note pattern when the user presses a new set of keys after having released all keys. This behavior ensures that the arpeggio starts fresh with each new chord/note input, allowing for seamless transitions between chords and arpeggio patterns.

Some Benefits:
Enhanced creative possibilities with a unique approach to arpeggio sustain.
Clear differentiation between Hold Mode and Arpeggiator Latch Mode, catering to various musical needs.
A versatile tool for live performance and studio production across genres.

I kindly request the consideration of this feature addition, recognizing its potential to diversify the HISE experience for users across the musical spectrum.

Thank you.

@CyberGen

I leave this here cuz, nobody ELSE should spend a week of their lives figuring this out. :anxious_face_with_sweat:

The code below works for me doing the following.

User Authentication:
Set up credentials for JWT token generation and sent a POST request to the /wp-json/jwt-auth/v1/token endpoint to authenticate and receive a JWT.

Token Handling:
The received JWT is used for subsequent requests to ensure each request is authenticated.

Token Validation:
The token is validated by sending it back to the server, ensuring it's valid and active before proceeding with any sensitive operations.

License Activation:
Post-token validation, we proceed to activate the license using the license key and other necessary details, which are then verified by the server.

// Server Address
Server.setBaseURL("https://yourserver.com");

// Credentials for authentication
const var credentials = 
{
  "username": "you@yourserver.com",
  "password": "yourpassword"
}

// Relevant references
const var authUrl = "/wp-json/jwt-auth/v1/token";
const var validateUrl = "/wp-json/jwt-auth/v1/token/validate";
const var activateUrl = "/wp-json/wclm/v3/activate";

reg jwtToken = "";

// Some debug stuff
Console.clear();
if (Server.isOnline()) Console.print("Server is Online!" + "\n");
Console.print("Authorization URL: " + authUrl);
Console.print("Validate URL: " + validateUrl);
Console.print("Activate URL: " + activateUrl + "\n");

// Authenticate and retrieve token
inline function authenticateUser() 
{
    Console.print("Starting authentication process...");
        
    Server.callWithPOST(authUrl, credentials, printResponse);
};

inline function printResponse(status, response) 
{
    Console.print("Received response: " + JSON.stringify(response));
    
    if (response.token != "") 
    {
        jwtToken = response.token;
        
        validateToken();
    } 
    else 
    {
        Console.print("Authentication failed: " + response.message);
    }
};

// Validate the JWT token
inline function validateToken() 
{
	Console.print("atempting to validate");

    if (jwtToken != "") 
    {
        Server.setHttpHeader("Authorization: Bearer " + jwtToken);

        Server.callWithPOST(validateUrl, {}, function(status, response) 
        {
            Console.print("Validation response: " + JSON.stringify(response));

            if (response.code == "jwt_auth_valid_token") 
            {
                Console.print("Token is valid!");
                
                activateLicense();
            } 
            else 
            {
                Console.print("Token validation failed: " + response.message);
            }
        });
    } 
    else 
    {
        Console.print("No JWT token found.");
    }
}

// License activation details
const var licenseData = 
{
    "license_key": "your-prod-key-lic"
};

// Activate the license
inline function activateLicense() 
{
    Console.print("Starting license activation..." + licenseData.license_key);

    // Set the Authorization header with the JWT token
    Server.setHttpHeader("Authorization: Bearer " + jwtToken);

    // Send the POST request to activate the license
    Server.callWithPOST(activateUrl, licenseData, handleActivationResponse);

};

// Function to handle the response from license activation
inline function handleActivationResponse(status, response)
{
	Console.print(response.signature);
	
    if (response["response"]["result"] == "success") 
    {
        Console.print(response["response"]["message"] + "!");
    } 
    else 
    {
        Console.print(response["response"]["message"] + "!");
    }
};

// Example: Trigger authentication when a button is clicked
inline function onButton1Control(component, value) 
{
    if (value) authenticateUser();
}
Content.getComponent("Button1").setControlCallback(onButton1Control);

@d-healey Right. Thank you. That makes sense. Sorry for that one mate, I must have tried everything else.

I'm afraid to ask, but (in scriptnode) how do I delete a parameter knob after I've created it?

I honestly cannot find a delete button.

@d-healey yes. The project needs at least one expansion.

@d-healey in regards to the scripts-disconnected issue, I was able to trace it down to a Engine.setCurrentExpansion() call. It seems that when this is called, it moves all user scripts into a "user" submenu and then the scripts show as disconnected.

Can you please help me confirm this?

• Add the code below to an external script file like the on in the post above.

• Uncomment:

//Engine.setCurrentExpansion(expNames[0]);

• Hit F5.

• Your script menu should now have a "user" stack and the script should appear disconnected.

const expHandler = Engine.createExpansionHandler();
const expList = expHandler.getExpansionList();
const expNames = [];


//Set Default Expansion
inline function setDefaultExpansion()
{
	for (e = 0; e < expList.length; e++)
	{
		local p = expList[e].getProperties();
		local n = p.Name;
		expNames.push(n);
	}
	//Engine.setCurrentExpansion(expNames[0]); 
       // this can also be:
       // expHandler.setCurrentExpansion(expNames[0]);
     
};

setDefaultExpansion();

@d-healey will do. Thank you!

@d-healey @CyberGen said in Console.blink() not blinking?:

I haven't been able to reproduce it.

I take that back... I wasn't doing it correctly... I can reproduce it now.

simple test

Content.makeFrontInterface(600, 600);

Console.clear();
Console.blink();
Console.print("do you see me?");


//Move this to external file.
Console.clear();
Console.blink();
Console.print("do you see me?");

HiseSnippet 687.3ocsUssSaCDDc2PLpw8hJR8CvhmBRHHokBUpO.kboJpMPTCE02PKqmPVk06ZsdMknp9O2+f1YsCXmRDWhZ8CQYtb183YNy3AFMGRRzFBs1ISiAB8YdCmpriaMlITjdsIzW30mkXASPtqCmFyRRfPBktxGcNn0pRxd909GxjLEGJbQHmpEb3yhHgsv6fC9jPJ6xBgSDQkxdmC5w0pVZoNE4yJdMHwL9D1EvQLWZU7HzU6DJrZyPKyBIXNGpCmNbr96p77OUjHNWBNiljg3Ak6lzZrPFN3520DBgVcPwa9J4u4uxquHTbi+hJvKyBDTfnbMfV4tnTyGAknknT0bJsl2PtQDaKh33yS85ovFxHFVpKSk7bIUtf50RiYnraEwl.cMnwMHpuaiFaFf+rw688wzRzRXKtDXl5nmqcbtTnlT1QrQnr0WOTGLUmFj.PPDr+5tyve6s6quDBriEIAVc.bEdSJlLXj.w8O3JFkp3VgVEnUGosvwp5a3+C+Z9+zO3uCMZzBi4pFFsTBlEF1oBM2Ev5pznyAylAWxjovMIhso468q9v5877lSoD0pdJg83XXlcWsLz0Sc++1JExrtK9uu1qMyxbhmY9v7hAiU3nCsMbIN8kKkp40FRlX0w372szYnBWGlJY14k8t46YAv5wbZMmdRkHrSKO++HlEZbmyBOTJtl2.gkOdwbrxB3HVo9evwYaPdtWmQi.tsffU859skccw8b8eQmZEpK5yrFwUDp2QoQCwEmb.uckBj3g6Qq3TK41Mb1tJvPPElY7a7YVvlNa5rfMuNHIhwM5y34SAtcTOIyCxIU1J4Z32FP6fljrIix04Hbk4Yb97G0s.95kE3aVVf6rr.e6xBb2kE3dKKv2c+.ceQ6CoVcT9XCgzePmrUITZGECUfYpUxePQoUzR

@d-healey I haven't been able to reproduce it. I started from a clean project. But I can't get user files to stack in the way the are show in the gif.... Somehow this is al related to the user/docu/etc stack and this particular project.

@d-healey Check out the gif below. I start out in "onInit" with a blink and a print and it works. I switch to my arp.js page, and not only does it not blink or screen print, when I hit F5 it switches the combo box to show the script editor as disconnected. This happens with all other user scripts.

What could be causing this?

@d-healey no, it's not that. Things are working beyond the blinking point, and I moved it to the top for testing.
I just noticed that it works when I'm working on the onInit script but it does not work on any of the includes scripts. Weird.

@d-healey uh yeah, it does

what the?

@clevername27 great alternative when you need a debug hint and you don't need to print out something. But it stopped working for me. Along with the green mini printout that shows up next to the actual line of code.

Anyone one else missing these debug tools?

I'm using version 4.

Hi,

I fear I may have turned something off.

For some reason Console.blink is not doing it's thing. And Console.print() does not display the green mini print-out next to the code. Only prints inside the debug console.

Is there a setting to turn these things off that I might have inadvertently changed?