Probably a dumb question, but...
-
@AudioHobbyist Check Maize Sampler to make simple rompler, but he has much less possibilities than Hise
-
@iamlamprey said in Probably a dumb question, but...:
HISE Player is basically pointless since we can recreate it within HISE
Not really. As I recall from research, the HISE presets/package/whatever system more or less lets you swap out small subprojects, sort of, but not to the extent I'd need to. I'd basically need to recompile the plugin every time I wanted a new feature anyway.
It would probably be easier for you to incentivize a HISE developer that already has their own proprietary player to either add your instruments/ideas to their working player
AKA 'not tinker with my instruments myself as I'd like to'
@Jerems134 said in Probably a dumb question, but...:
@AudioHobbyist Check Maize Sampler to make simple rompler, but he has much less possibilities than Hise
For my purposes this is far worse than most SFZ players and almost worse than soundfonts, last I checked, I see no reason to check it out over what I've already seen. It's also not open source.
-
@AudioHobbyist or Halion 6
I think here you can build your own player without a line of code. -
@MikeB I realize people here are trying to help, but as far as I can tell the subproject system doesn't work how people keep suggesting it works; again, it does not load ANY arbitrary patch that might use more (or less) samplers and effects and scripts. Or a completely different UI. Again, I'd have to recompile it every single time I wanted a new feature, and that kind of defeats the purpose...
Halion 6 is, also, not open source.
-
There is a (currently undocumented)
FullInstrumentexpansion mode which actually lets you switch entire instruments when you load an expansion, but it's not 100% finished.This will be the closest you'll get to a "HISE Player".
-
@Christoph-Hart I'm not exactly clear on what that entails. What can be swapped out, and what can't be? Different scripts? Different samplers? Effects? I don't know what constitutes an 'entire instrument' in the HISE structure. Is it a container?
Also expansion was the word I was thinking of, not 'subproject' or 'package'. It's been a while.
-
The expansion system in HISE in its default behaviour can be used to ship additional content (samples, images, audio files), but the instrument design cannot be altered.
However there is an additional mode that will load an entire instrument (in HISE speak a .hip file) when you load an expansion, so this makes an expansion basically the same as an .nki instrument in KONTAKT.
You can then write a basic "shell" instrument that just displays all available expansions and when you load an expansion (using
ExpansionHandler.setCurrentExpansion(), it will load the embedded .hip file of that expansion).It is not ready for production yet though, so I would recommend to wait a few more months before checking it out.
-
@Christoph-Hart Once again you solve one of my concerns about implementing future products :D
-
@Christoph-Hart That seems relatively close to the kind of thing I'd like to do, if I don't mind the headache of maintaining my own sort of 'HISE player'. It at least keeps me from having to compile every instrument by itself. I'll keep it in mind.
I assume a community project to resurrect the older HISE player idea would be pretty monumental, if you're saying that's as far as I'll get. Maybe a community 'Not Kontakt' HISE 'expansions = .nki' project... like LinuxSampler's 'Not KSP' scripting langauge...
-
@Christoph-Hart Aha - That's interesting - I can hardly wait for it.
-
Looking forward to this!
-
@Christoph-Hart Would this new feature allow for multiple expansions in a single instance? Similar to how Kontakt handles multiple .nkis. I've had some users request this.
