@Christoph: sorry but i resampled it (so erased the old ones and replaced it). the new works. So the problem was the wav file for sure.

@Alexaudio : Maybe just use 4 layer and use the velocity modulator to control this 4 layer like it could have 9 layer. not sure it will be as good as real 9 layers. remember that old Roland MKS-20/RD 1000 piano had beetween 4 and 8 layers and a velocity layer to map the all 0 - 128 velocity steps. that was causing (in parts) his particular sound and velocity response for a 80's digital piano.
But maybe with your real piano it will sound as a "digital" piano. So not sure.... just an idea...

I might have stumbled across a bug but as yet I haven't been able to repeat it reliably. It occurs when I load some samples into a sampler, run trim start, then decide I'm not happy with the threshold I chose so I reset the start time of all the samples to 0 and run trim start again with a different threshold. What happens is some of the samples end up with their start time being set to the same as their end time.

I checked the latest version. Now the front panel has become active!
Thank you very much

I think your confusing AU with AAX.

AU is Apple's native plugin format for Logic, Garageband etc (although VST is also supported on OSX). AAX is the plugin standard for ProTools and is available on both OS (Windows and macOS).

And yes, you definitely need a Apple system to compile AU plugins (and AAX plugins for ProTools on macOS). A mac mini will be just fine as long as it has an Intel CPU (you can't compile Universal Binaries on PowerPC CPUs). I am myself using one as main system (I am running Bootcamp for Windows so I have both OS on the same machine).

In order to compile AAX plugins, you need to register at Avid, compile their SDK, get a iLok, register at PACE for a code-signing account, get a digital codesigning certificate for Windows from Comodo (or another company), build the AAX versions and sign them using their codesign utility which I can tell you is a very tedious and annoying procedure.

RE Commercial license, I am cooperating with a few companies that are building commercial plugins, where I offer my support during development and after release. If you want to discuss the specifics, drop me an PM.

I'll take a look, but it's possible that my loop-point importer is not as robust as it should be (it worked for my samples in the past, but there is no hard standardisation for loop point definition so there are many edge cases).

It is done! And by the way, I really believe in your program. Good continuation!

awesome. could i just replace the code in the vumeter.js with this code?

Make sure you don't install Xcode 9, it is buggy as hell according to everybody...

Well, you can simply select all samples and enter a new sample start value (or right click on the field to open a big slider). Loop points should not be affected by this.

If you want to change them dynamically, increase the sample start modulation range of all samples and add a constant modulator (take a look at the tutorial how to use the sample start modulation).

I found something better than Synth.noteOffByEventId() !
Just have to assign the button to Sine Wave Generator, and then connect to 'gain'.
0=no volume, 1= volume :)
Thx :D

Here is a link to the .jucer file: https://we.tl/wj7OFfq9BC

Thanks Christoph - didn't expect you to produce this tutorial so quickly :)
I'm a bit tied up for the next couple of days stacking firewood for the coming winter, but as soon as I get a chance I'll go through the tutorial and do some experimenting.....
Thanks again!

Can you check again with the most recent build and source code? I fixed a few things regarding sample detection last week.

now i got it so it doesnt freeze everything but i get "sample directory is not existing" i have tried so many different things but what is the correct practice to have all user presets and accompanying sample maps recalled

thats understandable

I may have found the answer!
Just tried again, starting from scratch as far as saving as a preset, but then this time instead of loading the project (step 2 in the reload as work in progress section) after restarting HISE, I simply opened the .hip file without doing anything else, and there was my project as I had left it, with working sound from mouse and midi keyboard.
It seems that the 'Load Project' option under Files is not necessary and indeed stuffs up the sound from the project - all that is required is to load the .hip preset file.....
It takes a while to get used to the terminology used - I had assumed that loading a project would re-load a previously closed project in the state that it was when closed, but obviously not so. So really the preset is a backup of the project at a certain state and if I want to go back to a selected point in the project development, as long as I have saved a preset at that point (with a suitable name) I just need to load that particular preset.
Now I'll continue with the tutorial, saving a preset at various stages and see what happens when I restore from each.....

Ah, the Panel is the ScriptPanel and has nothing to do with the FloatingTile widget.

The Panel can be customised using its callbacks (PaintRoutine, etc.). The floating tile is just a container for ready made widgets like the preset browser, the settings dialog etc. and can be populated and customised using JSON data.

OK - many thanks for the response. Appreciate you taking the time to help me out :)
Now I see how it works! Did as you suggested above and managed to create the factory function successfully - now onward and upwards with the remaining controls and the reast of the tutorial....

Also located the editorData.json file, deleted it and yes, 1.0.0 now starts OK

Now I'm wondering how best to pause a project overnight and reload it the next day to continue. I tried File -> Close Project, shutdown HISE, restarted and attempted to load the project(MusicBox), but there was nothing displayed - it was if it was an empty project.
Tried File -> Open File -> Presets folder and selected the latest autosave.hip and there was my tutorial stuff - except the keyboard now only plays the mallet sound, no musical notes. I may have stuffed something up by switching between versions 1.1.0 and 1.0.0 so I'll manually delete the MusicBox project folder and sub folders and start from the beginning again using version 1.0.0

What is the recommended way to save a project to enable a computer shutdown so that I can pick up again the next day?

Sorry for all the questions!