@Goodflow said in Midi Overlay Panels in Compiled Plugin Crashing DAWS?:

Line 40:

class MidiOverlayFactory: public DeletedAtShutdown

gets changed to

class MidiOverlayFactory

I was having the same crash and was fixed with this. Thanks!
Seems to work on mac, windows & linux. @Christoph-Hart maybe this could be included in the dev branch?

@David-Healey Haha that make sense too :)

@David-Healey @Dan-Korneff Great news! I was able to fix the issue with Amazon S3 pre-signed URLs and the HISE Server.downloadFile function.

Thanks to Dan's explanation of the source code (on the other post), the problem was identified:

HISE original logic sees the ? in the S3 URL and assumes it needs to separate and re-parse the query string into a separate parameter object. This process destroys the specific encoding required for the X-Amz-Signature, invalidating the S3 link.

So, I modified the ScriptingApi::Server::downloadFile function in the HISE source code to skip the parameter parsing if the URL contains the S3-specific parameter "X-Amz-Algorithm=".

I think this should be changed in the HISE source code because AWS S3 are pretty common.

@David-Healey I found a post where Dan was using the same amazon s3 links as me.
https://forum.hise.audio/topic/4635/question-about-queued-downloads-from-amazon-s3/26

I'm actually trying to use moonbase, but I got the same links for download.

@Dan-Korneff How did you solve this?

@David-Healey Thanks. It worked with cURL as a background process. I read that if the user has a Windows version prior to 2019 wont work. Should I use powershell for Windows for better compatibility right?

@d-healey yeap :)

@d-healey Thanks, yes it works with curl in terminal.

In HISE, I'm clearing the HttpHeader before starting the download, as I read in the forum, and I'm making sure not to repeat the base URL (just using https://).

It works with links from other servers, but it doesn’t seem to work with signed S3 URLs.

@bendurso The link contains 1359 characters. Maybe that could be the issue? Is there max limit for the link length?

@d-healey The link is the final one. But your comment led me to think the link was different, so I checked it and realized that the download link in Chrome transforms the " into %22 and the spaces into %20.

I can replace the spaces. But how do I transform the " into %22?
Because this doesnt work

String.replace(""", "%22");

update: ohh, like this:

String.replace("\"", "%22");

Now the link is identical.. but still doesnt work :(

I'm trying to download a signed Amazon S3 URL using Server.downloadFile(), but the request always fails. The same URL downloads correctly in the browser, so it seems an issue on HISE. The link is extremely long because it contains X-Amz-Security-Token, X-Amz-Date, X-Amz-SignedHeaders, X-Amz-Signature, etc.

@d-healey Thanks for your comments about my brand. You helped a lot for it, infinitely thank you :)

@tsempire Here's an example of how to make it with scriptnode https://forum.hise.audio/topic/11482/faust-aural-exciter/7

@tsempire Yeap.

@parabuh You can do it with WebView component. Here's an example of how to do it https://forum.hise.audio/topic/9121/remote-website-doesn-t-render-with-webview-in-executable/3

@d-healey Oh, I didn’t know I had to remove it from the plugin export as well. I’ve done that now, and my plugin works on an old cpu computer. So, removing AVX is better not only for older computers but also for ARM computers. And then.. what's the benefit of using AVX?

Definitely, having a checkbox in the project preferences—or maybe an extra definition—would be a good idea :)

@Yarost Mm maybe you could use the same knobs you have inside the amp. But I'm not sure

@Yarost It looks great. I like the everything inside the amp.

The only knobs I don't like are the input and output knobs. I don't know how to improve them, but maybe my feedback will help you.

I'm not a designer anyway, lol.

Plugins exported with Hise don't work on Windows ARM, as far as I know. Only on x64. Or am I wrong?

@d-healey It’s a bit old but.. I just wanted to say that I was able to get the internet connection working in the exported plugin using your fork of HISE (Linux). Thank you :) Not sure why it doesn’t work in the main dev HISE.

@d-healey said in Problem launching HISE build on Windows (Parallels Desktop):

unless Parallels can fake it.

It can but it's really (really) slow.

@lloyduss said in Problem launching HISE build on Windows (Parallels Desktop):

Or do I absolutely need to use a computer or virtual machine running a proper x64 Windows environment to get HISE working correctly?

Yeah, I spent a lot of time trying to run Windows x64 on an Apple Silicon Mac. It’s not worth it. The solution is buying a decent Intel computer. I got a $200 Lenovo ThinkCentre with an Intel i7 7th gen, and it works like a charm — it compiles HISE in just 4–5 minutes.

In the end, if you spend too much time trying to make that setup work, you’re probably losing more than $200.