@Christoph-Hart fantastic, thank you!

@Christoph-Hart thanks, that's great info!

What’s the proper way to do this? There is a Documents wildcard, which is great. How do I go to Music from there on each OS? It’s one folder back from the Documents.

Also - what’s the best non system-locked location for samples on the internal drive? I would assume the Documents folder to be fine but for some people, it’s permanently synced to the cloud, which isn’t optimal.

Also 2 - what if the username of the person using the samples contains dots or other bad characters?

Thank you!

@Christoph-Hart is ONNX more CPU-friendly than the older tensor flow method?

I definitely second that @Christoph-Hart !

I've been using Pulse since 2019, and I'm the guy who worked with them on native HISE support. Recently the ownership changed, and even though we - people who were using Pulse - were told that the terms of operation are going to stay unchanged, they informed me that they'll actually change the terms for me anyway. It was 10th of March or so, and they said something like "hey, we're changing the terms for you, and they'll affect your pricing from March 1st". Not a very respectful way to do business, in my opinion.

Also, keep in mind that all Pulse does is it gets the multi-zip archives from the server and unpacks them. There's no license management or anything like that.

Anyway - I'm using a custom installer now I built with HISE. You can pretty much replicate all Pulse does with this @d-healey (thank you!) tutorial: https://www.youtube.com/watch?v=mqGsqJoBxiQ

@aaronventure Perfect, thanks so much!

@aaronventure I already have a working shell script from the pkg installer I had earlier, so I could definitely reuse that. I'm totally new to background tasks, though. Could you please help me out to understand what I should pass into the docs example? Thank you!

@aaronventure @ustk @d-healey thank you!

@ustk could you please give me an example of the background task running a shell script so I can test this?

I'm getting some serious inconsistency with the File.move command when moving files to the user library folder on macOS. Whenever I test it - whether in HISE or in a built standalone app - the command works properly. I'm getting some reports from users about the files not being copied over. My script looks like this:

// Check if file exists and remove it if it does
if (componentFileMac.isFile() || componentFileMac.isDirectory())
{
    componentFileMac.deleteFileOrDirectory();
}

workingFolder.getChildFile(pluginname + ".component").move(componentFileMac);

All vars used are defined properly and again, it works on macOS 12.4 and above. I guess the issues is with some older macOS version, but I'm yet to confirm that. Anyway - is there something about using the .move command to get the files to the user library I should know about? Clearly, it's a permissions issue. Is the .copy method safer? What's the smart way about it?

As a walkaround I could start a .pkg from the main script just to get the files in place, but it's a custom installer and I think it would be great to keep the experience consistent without running yet another app from the main app.

@d-healey @Christoph-Hart I'm running into a similar problem where I need to include some headers in the download call. Have you found a solution to this issue?

Say I have a sampler that has 2 channels, and it's nested in a container that has 8 channels. I want to have the output of the sampler split to all 8 channels of the container, while adding some per-voice modulation (like an envelope) on each of the split channels. So:

• channels 1-2 get a simple gain with Envelope one
• channels 3-4 get a simple gain with Envelope two
• ... and so on

Or in other words - I want my 2-channel sampler to behave as though it had some multi-channel / multi-mic samples loaded, but without using multi-mic samples. I just need to have a single channel pair split to more channels before it gets to the container for furhter processing.

I could mult the 2 channels from the sampler on the container level, but then I can't apply per-voice modulations to each channel.

Is there a way to achieve this?

@Christoph-Hart ? :-)

Is there a way to programatically close the standalone app built with HISE?

Thanks so much, that's very helpful, I appreciate it!

I'm sure it's something simple, but I'm just figuring out the Server calls and stuff. I'd like to write a function that works like this:

1) Create a file name based on a var I defined in the script - let's say it's HISE_IS_AWESOME.txt
2) Make a call to the server to see if a file with such a filename exists - the path is mydomain.com/files/HISE_IS_AWESOME.txt
3) If the file exists, do something

How should I approach this?

Thank you!

Dear @Christoph-Hart would it also be possible to add the cursor type property to sliders as well?

Hence the feature request :-) fadeComponent has been working very well for me so far, it would just be great to have a quick and easy way to achieve fades to semi-transparent states like this.

@d-healey seems like CSS and LAF can't live together, can they?

@bendurso yeah, I know. fadeComponent is just much faster, doesn't require timers, and works with stuff other than paint routines like images etc.