General questions about Hise Sampler
-
Hello,
I'm relatively new to using Hise Sampler, and most of my experience in plugin development has been with SynthEdit, Flowstone, and Maize Sampler. Before fully committing to Hise, I have a few questions:
-
Can I create a UI that is compliant with 4K displays and can be scaled? This has been a challenge with the development software I've used previously, as I couldn't create 4K-compatible UIs for my plugins. If this is possible with Hise, does it consume a significant amount of CPU resources?
-
Can I develop plugins with Hise that are compatible with Apple Silicon? Native compatibility is essential for me.
-
Is there a way to embed the sound content directly within a plugin? I'd like to create a synthesizer with my own wavetable, but I prefer not to require my customers to locate a separate content folder on their computers, especially when the sound content is relatively small (20 MB or less).
-
When it comes to romplers, how does code signing work on macOS? Is it a straightforward or complex process? Do I need to code sign the sound content files as well?
I hope these questions clarify my concerns.
-
-
- yes
- yes
- maybe, but usually you put this stuff into the app data folder during installation and don't ask the user (you only ask him to put the big sample library files).
- It's a not straightforward and supper complex process. The sounds don't need to be signed if they are external files but if you keep them in the binary, you'll have to sign the entire package.
