Got it working, thanks to yet another awesome @d-healey tutorial. Here it is, in case somebody else needs that too: https://www.youtube.com/watch?v=badkm6QVNIA&t=801s

I have a couple of buttons and would like to assign different paths to them. I hoped I could just create a LAF for all the buttons and then call:

g.drawPath(obj.text, ...and the rest of the parameters here)

to draw a path based on the obj.text property, but it doesn't work. If I enter the path name manually instead of using.obj text, it loads properly, even though the path name and obj.text are the same, so theoretically, it should work with obj.text too, right? Am I missing something?

@Gab you can use the transport handler to kill all notes when playback is stopped

@d-healey ok, but the files are automatically marked as completed on the queue. How can I get them to download again?

Here's how to reproduce the issue, at least on macOS:

• open the Server Controller
• start any download with Server.downloadFile()
• as the download progresses, disconnect from the internet
• the Status of all files in the queue will be marked as completed

Unless I'm not getting something right, this is a bug? The download is obviously not completed, it's just that the connection to the server has been lost. If it's not a bug - how to handle such a situation?

Thank you!

I totally second that!

@Christoph-Hart that would be super cool and flexible I think!

@Christoph-Hart will it also be possible to disable the crossfade after the transition and stay on the legato transition sample? I’m thinking about a scenario where the samples are edited so that the transition sample also contains the sustian portion to loop.

@d-healey maybe it works on some systems but not others, for whatever reason? Is there a way to get the final url of the call affected by the parameter property?

@d-healey none, but I suspect the problem is with the parameter part of the url called by HISE. The reason I suspect this is that the POST calls are made to a different server, and they work fine. The download callback works fine wherever I test it and - again, works for the vast majority of users - but I guess it's possible that the parameter part is not attached to the call properly, and the server rejects it because it doesn't pass the authorization.

HEADS UP: Server.downloadFile() issue on macOS Sequoia - and a solution

Is there any way to print the final url with the parameter part? The docs https://docs.hise.dev/scripting/scripting-api/server/index.html#callwithget say tha...

Forum (forum.hise.audio)

@d-healey of course not ;-) But I also have one guy on Windows experiencing this now.

Is there any way to print the final url with the parameter part? The docs https://docs.hise.dev/scripting/scripting-api/server/index.html#callwithget say that "The parameters have to be a non-nested JSON object and will automatically change the URL to embed these parameters". What does the final url look like after the change?

@d-healey no, I have three different macs here, one is on intel, the other two are on m1. One is running the latest version of Sequoia, the other is on Monterey. I can't reproduce the issue on any of these, and it's literally 3 people out of almost 500 having the same problem. But the problem is there, apparently. It's either that macOS blocks traffic on GET / download callbacks, or that the parameter part is not passed correctly on their system for some reason. Here's my thread: https://forum.hise.audio/topic/12537/heads-up-server-downloadfile-issue-on-macos-sequoia-and-a-solution/22 but I thought learning how to send debug versions might be valuable to other people, if they'll end up searching for it at some point

@d-healey thank you!

@d-healey yeah, and tha't the problem for me. The hise part is good, it's just that the traffic appears to be blocked on some random macOS systems, and I'm trying to figure out what's up with that

@d-healey but this won't fire system errors, right, only the issues in hise script?

@d-healey that's what I thought. The 2nd true will mean that subfolders are supposed to be affected, too, right?

@d-healey thank you, but this doesn't seem to work when I test it. Shoud it be (false, false) or (fase, true)?

The p part is the authorization that’s getting passed to the server. I was having an issue using that with GET - again, very inconsistent and on some systems only, and I can’t reproduce it on any fo the 3 macs I have around - as though the parameter was not being passed to the server properly. So maybe it’s about that, but then I have no clue on how to troubleshoot this further.

Ok, a quick update on the subject - the XCode transport solution only works for some users. For others, the download callback returns this.data.finished = true && this.data.sucess = false even before anything can be downloaded. This is happening both on Windows now, and macOS, for about 0.5-1% of users, for everyone else things are working fine.

Here's a very simplified overview of my download logic:

At the beginning of the scrip, I call:

Server.setBaseURL("https://");

which is used for POST calls, and then this download callback, with the url aprt being the rest of the url, after the https part.

inline function startDownload()
{
	// Download samples and content
	for (i = 0; i < plugincontent.length; i++)
	{
		local files = workingFolder.getChildFile(plugincontent[i]);
		downloads[i] = Server.downloadFile(url + plugincontent[i], p, files, downloadCallback);
	}	

	// There's just one zip file and it's always the first in the plugincontent array
	zips[0] = workingFolder.getChildFile(plugincontent[0].replace(subfoldernamefull).replace(subfoldernamedemo));
	
	// Show update progress panel
}


function downloadCallback(obj)
{
	if (this.data.finished != true)
	{
		// Show and update download progress
	}

	// Connection lost
	if (this.data.finished && this.data.success == false)
	{
		// Show error message
	}

	if (this.data.finished && this.data.success == true)
	{
		// Update downloaded files count and extract zips
	}
}

As said, this works 100% for POST calls for all users. The problem is for 1% of users with the download callback. I remember having a similar issue with GET when I started this project.

Save me, please!