@d-healey thanx for your fast response as always
found the issue , akai daw have 2 ways to set / re scan your plug-ins, 1 is in preference and the other is in the plug-in manager, there was the confusion, so I went to the preference / plug-in folder/ and select my Mac hd/laudio/vst and also AU FOLDER, it seems akai route the search by default to its own plug in folder (VST3/au) in its own directory, you need to add other locations manually, PROBLEM SOLVED,thanx

@WepaAudio said in clicking 'drum pad" buttons OF MY PLUG-IN in my DAW dont record midi notes:

@VirtualVirgin so I get it working now, but I believe for costumers will be an issue doing that midi in both channels, I hope we can find solution in the same midi channel

Can you explain more what you are trying to do with the MIDI channels?
What channel(s) do you want for input?
What channel(s) do you want for output?

@d-healey thank you I will do that, post later the results,thank you SIR.

@ustk thanx, for what i read on the link you gave me seems to.be the solution

@d-healey thanx, im using mac M1, i decided to bing the sounds to my DAW and export them in one of these samplerates to avoid this issue at the moment, i will look for more info on what you told me,thank you

@d-healey thank you

@Lindon since I do backups of my project from early stages to the latest I found that 3 versions earlier something happened, not sure, but I could export an earlier version today, lots of work lost but at least I know I can still export, thanx for all the help and for this new tool to test the plug ins

@Mighty23 I did and it rewrite but nothing happened, i restarted the computer and try but no luck, I will export again and see

@WepaAudio If you want to develop Audio plugins always go to Github and download the latest Develop branch, the n compile it using VS Studio or XCode to make HISE executable.
If you are new to HISE and if you want to give it a try, then install the pre built installer

For installer version you will get a check for update option. Use it to upgrade from previous version.

@WepaAudio You can't open another window but you can show/hide any UI component.

You need to wrap everything in code tags, it's difficult to follow the code when it's unformatted.

In general I would say don't try and merge different snippets or bits of code you find on the forum, it tends to lead to a Frankencode mess.

You need to understand what each bit of code does, and how it works, then rewrite it into your own project in a way that makes sense. If you don't know what the code does and how it does it then you don't have control over your own project and you'll keep running into these issues.

@ulrik from now on restarting Hise will be in my to do list when i fix codes and don't got fixed , because I erased yesterday that same lines i compiled but not restart Hise,
Tha k you.

@WepaAudio thanx, im in Mac m1, it seems some of the mono sounds not readable in hise, I use them in other stuff, I did a round robin with just the mono sounds and almost all work, I will try to combine the working ones with stereo and see, I will post result later, thanx

@WepaAudio I would always recommend converting the samples to monolith before distribution. It's faster, takes less memory (both disk and RAM) and has almost no impacts on the sound quality unless you feed it with special test case waveforms that know how to point out the weaknesses of the HLAC codec.

Anyways, you can look at the sample map XMLs. If there are samples missing, then check if the references in there are correct.