Vst Instrument without having to install the samples
-
I found this in the help doc:
Export Pooled Files to Binary Resource
Will collect all pooled Audio-, Image-, MIDI files and SampleMaps and save them as .dat files in a newly created PooledResources folder in your project.is this somehow related? Could this kind of thing be used to create the sample data in a way that works?
Now that the VST doesn't work, I have tried deleting the compiled vst file and recompiling hoping it might ask for the sample data again and I could try again, but it seems to compile and load with the not functioning version and I have no way to reset the sample data and try again.
@LightandSound I wish I had the JUCE chops to do something like that. I've tried using JUCE directly a few times and even though I know C++ and have done some large and involved projects I am not currently capable of making much inside JUCE directly. I would love to learn JUCE more in the future, and things like HISE are a clear path to facilitating that since I can theoretically create the core of my idea in HISE and then extend it as needed in the DSP. Its an interesting thought though.. but also as an end user experience, I would want to fire up the plugin and be going as quickly as possible.. having to sit and wait for a download upon first plugin launch would bother me, I would ideally want them to fire up and play a note and it works.
-
You need to delete the config files in order to get the locate samples prompt again
-
@MacroMachines so as @d-healey says you need to remove the config file to get to reinstall your samples - unless you have included the "move samples facility" in your plug-in;
go to:
windows: C/Users/yourname/AppData/Roaming/your_company_name/
and remove the your_product_name folder
mac: Macintosh HD/Users/yourname/Library/Applications Support/your_company_name/
and remove the your_product_name folder
if its not there look in:
Macintosh HD/Library/Applications Support/your_company_name/
-
@Lindon Thank you, I appreciate your help greatly :D. I'd be a bit lost without this info and you have responded very quickly.
-
So I did the process again, and now after I select the source hr1 file and the destination folder for samples, I get a message:
https://www.dropbox.com/s/wvbpycm577izuyo/Screenshot 2020-06-09 16.48.17.png?dl=0
Heavy sigh.
-
That's ok. You have to restart the plugin and it should work.
-
@d-healey I tried that, still silent. Also tried making a brand new project with 1 sample and 1 knob, exporting to vst and using the option to select the samples folder with the file I had used, still silent, nothing coming out of HISE based VST exports so far.
-
@MacroMachines What about standalone builds?
-
@d-healey Tried building one, it shows up but didn't ask about the sample location and doesn't have a midi input setting panel or typing keyboard input.
-
@MacroMachines OK go to the location I identified above, and open the file called LinkWindows
it will have a location in it, go to that location and make sure that all the ch1 files are there.
-
Are your samples, the original Wav files, in your project's Samples folder?
-
@d-healey Yes, theres only one in the test and I made sure to put it in there.
@Lindon Im on osx so I tried LinkOSX and the directory is the path I chose in the last test, which is the path to my project samples folder which does in fact contain the relevant samples, and the GeneralSettings.xml has the value SAMPLES_FOUND="1"
-
Is the path correct in your sample map?
-
@d-healey yes, they are there.. well IT is there, since I am holding off on building a more complex sample map until I verify it works with one sample.
it is an aiff file, but it works in HISE so I figured it would work, but I could try with a .wav file and see if there might be some weird format issue.
I am now going through the tutorial projects on the documentation, the phase wizard synth one (doesn't use samples) works as a vst and stand alone, and I am about to do the next one which uses samples, and if that works I can assume theres some issue with my sample somehow.
-
@MacroMachines
What is the path? -
@d-healey /Users/nicholascraftisiii/Dropbox/Vibrator Synths/HISE/TEST/Samples
thats where my HISE project was developed, so I tried the option to select the sample folder upon launching the plugin, and used the samples folder that I used to build the sample map.Currently finishing the tutorial projects to see if I can get those working, and then will resume troubleshooting this.
-
That's the problem. It shouldn't use an absolute path, it should be a relative path from the project folder. https://docs.hise.audio/working-with-hise/project-management/index.html#project-folder-wildcard
-
@d-healey I do notice in the tutorial I loaded all of the samples from the Samples folder and in the table they show up as {PROJECT_FOLDER} before the name, I had thought I did this in my project but its possible I did something wrong somehow. I wonder what it was.. I will make sure my files show up that way though for the future. about to finish the tutorial and compile and we will see if I can get that working.
-
@d-healey Ok, I just finished the tutorial for Music Box, and the SAMPLES DONT WORK. I created the samples for installer, everything said it succeded, and then I launched logic and the AU works, and asked me for the sample resource file, and when I select it and select the destination folder, it says everything worked, and everything else in the instrument other than the samples
EDIT, I then reloaded the instrument and it works... I think this needs to be a message that pops up telling the user they need to reload the plugin or HISE needs to make it so they work the first time this is loaded, cause that makes it feel immediately like its broken on first launch.
Also the screen popup. where you supply the samples doesn't really fit in this tutorial instrument.. there must be some kind of solution to make it feel like its not cropped in the window.
-
@MacroMachines said in Vst Instrument without having to install the samples:
EDIT, I then reloaded the instrument and it works... I think this needs to be a message that pops up telling the user they need to reload the plugin or HISE needs to make it so they work the first time this is loaded, cause that makes it feel immediately like its broken on first launch.
This a well known pre-condition that isnt going to go away any time soon - what we all do is put a big red comment in the user manual that explains you have to restart the plug-in to get any sound.
Also the screen popup. where you supply the samples doesn't really fit in this tutorial instrument.. there must be some kind of solution to make it feel like its not cropped in the window.
You have to make your instrument big enough to hold these dialogs...