@Yannrog It's always easier if you name your components consistently.
Think like this for panel names, pnlPage0, pnlPage1, pnlPage2, etc.
All developers participating in the HISE Betatest Program
@Yannrog It's always easier if you name your components consistently.
Think like this for panel names, pnlPage0, pnlPage1, pnlPage2, etc.
@Yannrog Each component needs to have a different name.
There are different ways to do this depending on how your project is set up and how you want things to behave.
The simplest is to have a single callback function applied to all the buttons. Then in the callback you can check the value of all the buttons, if any of them are 1 you show the panel.
@PabloCaparros To be honest, I think Hise is now suitable for any task, especially for a bachelor thesis where you need to do things quite fast, like UI mockup implementation and audio processing that might not be 100% efficient but working anyway.
As for the pitch detection goes, Hise does not really have one (except a very basic pitch detection of a pre-recorded buffer) so what you'll need is either to make yourself or use an existing library (if the license is compatible with your project). Hise allows you to implement/create/import algorithms like FAUST, RNBO, C++, all implemented around the DSP network (create a network -> implement anything inside)
The MIDI conversion capability will reside in your algorithm, so in the end, Hise is not the limit.
As I see it for your project, Hise can just be the container where you connect everything, audio/midi processing and UI. But the pitch detect -> MIDI will be your job using any external language and/or library
@Orvillain said in Embed non-audio files into the plugin?:
@Lindon Hmmm, no they are not. Not at the moment. I have embed audio files and embed image files enabled btw.
as Christoph says above, I found non-image and non wav files in the Audio Files folder didnt load well - so I had to abandon the embedding and they had to get copied in there by the installer...
@Orvillain are nam files binary or json?
There‘s currently a gap in all non image or audio file resources (.hwt wavetables too eg), so this would be a good feature addition
@Orvillain are they also in the AppData folder structure?
@Christoph-Hart said in Sampler: Preload Size question:
You probably might want to put that in a non-preset setting file somewhere.
exactly what im doing....
with the complication that the Preload size is actually being set in another executable, the "player", so now when the Full instrument Expansion gets loaded I say this in the init:
for(i = 0; i < NUM_SAMPLERS; i++)
{
if((instrumentMetadata.instrumentSettings.PreloadBuffer * 1024) != TheSamplers[i].getAttribute(TheSamplers[i].PreloadSize))
{
TheSamplers[i].setAttribute(TheSamplers[i].PreloadSize, instrumentMetadata.instrumentSettings.PreloadBuffer * 1024);
}
}
only question is -- do I need to wait for everything to load before checking this?
@duma as Dave says... and this is why most of us ran away from using comboBoxes for this, instead one alternative approach is:
Your Combo Box is then just there to populate this textBox and call changed() on it... the comboBox then should not be saveInPreset...
It is also possible to set the LAF for your comboBox to show nothing in its default state...and you can then place a LAFed textBox that looks exactly like a "closed" ComboBox underneath the ComboBox, thus from the end users point of view it looks and behaves just like a regular ComboBox
@Lindon just like any other attribute. If you save it in a preset it will be restored in a preset.
AFAIK the sample loading is deferred until the plugin is initialised, so if you load a DAW project, it will not load the default preload size, then reload them again, but wait until everything is setup and then load the samples with the one preload size you set it to.
You probably might want to put that in a non-preset setting file somewhere.