Vst Instrument without having to install the samples

[AxiomCrux]

@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"

[d.healey]

Is the path correct in your sample map?

[AxiomCrux]

@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.

[d.healey]

@MacroMachines
What is the path?

[AxiomCrux]

@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.

[d.healey]

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

[AxiomCrux]

@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.

[AxiomCrux]

@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.

[Lindon]

@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...

[AxiomCrux]

@Lindon said in Vst Instrument without having to install the samples:

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.

that presumes users would read the manual before using or during setup, nobody I know does that, they assume the plugin they just installed will work immediately.

Ideally, this would be fixed or set up so that there is a dialogue that comes up after the sample installation that simply says "samples installed successfully reload the plugin to continue". there already is one that tells you the samples were installed, the text just needs to be amended.

Even more ideally, the package installer would do this before the plugin is even run, the samples would be installed and the plugin would know where they were installed so they don't have to do anything but run the plugin and it works.

I would love to learn enough JUCE to help in implementing these types of things if they are not priorities for the developer. I think of these things as very important, maybe others are ok with this. HISE is so close to being an ideal tool for plugin development, I just think with a few tweaks it would be so much better.

[Lindon]

@MacroMachines said in Vst Instrument without having to install the samples:

Ideally, this would be fixed or set up so that there is a dialogue that comes up after the sample installation that simply says "samples installed successfully reload the plugin to continue". there already is one that tells you the samples were installed, the text just needs to be amended.

So thats a simple fix in the C++ -- go for it.

I think it might be line 982 in BackgroundThreads.cpp

[ustk]

@Lindon I think it's worth to add permanently so I'll push a request to @d-healey's fork with the "fix" ;)

[Lindon]

@ustk said in Vst Instrument without having to install the samples:

@Lindon I think it's worth to add permanently so I'll push a request to @d-healey's fork with the "fix" ;)

er... its not even tested as the right spot....so David will need to do some work...I would do it if I wasn't in the middle of a big development build...

[d.healey]

I think it's a good idea. I'll take a look when I have a bit of spare time.

[ustk]

@Lindon Was nothing more than changing the line you kindly spotted :)
@d-healey pull request ;)

[Lindon]

@ustk cool well done.

[ustk]

@Lindon I tried to add \nbut it doesn't work. Although I've seen it in some other .cpp using the same message window...
So I let it on one line... any idea?

PresetHandler::showMessageWindow("Samples imported", "All samples were imported successfully.\nPlease relaunch the instrument.");

[d.healey]

Try \r\n

[ustk]

@d-healey It doesn't work, it's taken as a literal... Not a big deal though!

[AxiomCrux]

@ustk Do you maybe have to do it with another quote as in :

PresetHandler::showMessageWindow("Samples imported", "All samples were imported successfully."\n"Please relaunch the instrument.");

or maybe it just requires a space between the /n? as in :

PresetHandler::showMessageWindow("Samples imported", "All samples were imported successfully. \n Please relaunch the instrument.");