Hey everybody! Hope all is well, quick question and I know it’s been brought up before, but with all the progress. Is there any way to make advances in the headless Linux build for HISE. I believe this can be very useful for future endeavors. Thoughts?..
Thanks allot!
Corey
Does this fix the issue of the end user opening a saved project in the daw, and correct expansion presets will load that the user has saved? Been my issue the whole time
Meet Christmas’s everybody! Very grateful for the progress, hope everybody is safe
@d-healey I still have the c++ saveInPreset preset issue as before. It’s really important for users when loading the plugin on a saved project in the daw. The plugin should be able to load the used expansion preset onInit so the user doesn’t have to spend amounts of time finding out what preset they used for their project.
..unless their had been a fix for this I’m unaware of. Thank you lots
@Christoph-Hart im also assuming the percX expansion system when complete will resolve these minor issues?.. can’t wait
@Christoph-Hart the sample maps do actually restore but the expansion box doesn’t restore making the sample maps not pop up in the user preset browser. Therefore you cannot load your saved samplemap because the expansion selected isn’t being saved in preset That’s the issue I’ve been running into
@d-healey the main issue I’ve seen with moving forward with the expansion system is the same issue of the combo box not saving the Expansion chosen for the user preset box to load the correct preset. The combo box resets itself on load. I thought we’ve talked about this before. The user when using the plugin needs to choose their expansion and use the presets. Save the project. And when reloaded by the user, the plugin goes to the expansion that was previously loaded.
Currently the combo box used to choose expansion resets itself when save in preset is checks resulting in the loop error I’m guessing. This fix would enable me to actually use the expansion system instead of the workaround mess I have currently.
@d-healey yea I believe we’ve talked about that before. When I’m at a spot I’ll message you about that process as my whole end goal is to just run the vst3 through a web app or the elk hardware to users for free and have them purchase expansion sample packs. Would the open source method cover this?
I’m assuming we’re still a ways away from this happening..though the headless Linux build would be a good starting point if we could get that compiling correctly in the future
Thanks Dave
Ps I talked with the same guy at web audio modules a few months ago and was interested in the hise vst to web Project. I haven’t heard back but was curious if this was a thing that could be done..
@yall I chose to have a closed license due to sample licensing and our vst3 being mainly a sampler. So we pay the juce fee and hise closed license fee And totals somewhere around 85/mo I believe. which isn’t horrible for a closed license if you can make decent returns on your products.
As for the open source license, I would actually prefer that route if our samples weren’t made In house. I’m just iffy on the licensing coverage on open source samples.
I use a website called sendowl that distributes the serial numbers by email once purchased.
@ohtravioso there’s a hise build that doesn’t work at the moment but compiles your plugin without the GUI for other application use. I’m not terrific with c++ yet but I was wondering if what you were doing was similar
@ohtravioso so with this method your building if I understand, you will have your own GUI interface with the hise backend system? With this route would it be possible to bypass the headless system build for other application use? Just curious? Thanks
@d-healey I agree. This system is going to be a game changer when complete. Can’t wait
If it’s anything like the percx downloadable content, that would be fantastic
yea not workin correctly yet..Unless we all want to tackle the c++ side of things, we will have to be patient
@arminh gonna have to wait and see what @Christoph-Hart has planned. The new scriptnode build has new expansion features. But I’m not sure if they’re completely functional, as I’ve been trying to figure out the correct way to use it the last few days. Looks very promising
@arminh instead of manually moving the sample monoliths into the expansion folder. Have them created in the expansion folder so the link is correct. I believe if you move the samples from main folder to expansion folder, it gets buggy. Make sure to refresh your expansion afterwards