@d-healey Great Thank you sir :) :folded_hands:

@Christoph-Hart yeah for sure, i've already got the residue samples as a backup in case it doesn't work out 😋

let's just say in theory the synthesis route can sound close enough, it would then be really easy to build up things like randomization/infinite round robins, as well as expose some of the synth parameters to the end user to adjust the timbre in some arbitrary ways

i'll stick to simpler sounds at first like plucked/percussive versus something like a legato string library for obvious reasons

@d-healey
ahh ok, i'll try that. Thanks

@d-healey Sweet. You are very welcome. Even if you decide to make your own (to suit your plugins) at some point, this should help the process be quicker. 😁

@DanH Unfortunately that does not do the trick. I had wondered and tried that myself.

I stumbled upon this one after having reset my mac. Since I've installed ProTools beforehand, the folder @Lindon was talking about was already there, but I was still facing the unable to create directory error.

I used the

chmod 777 Macintosh\ HD/Library/Application\ Support/Avid/Audio/Plug-Ins

command to grant this folder writing permissions and it solved the issue.

I'm leaving this here in case someone stumbles upon this one too.

dont worry, I found the solution, just right click on the alias version and click on " show original:

@ustk Thanks. So, this would be something for @Christoph-Hart to implement at some point if he deems it worthwhile? :beaming_face_with_smiling_eyes:

im a person that like to try stuff even if it dosnt make sense, so went to HISE program and create a new project and did some tweaking after various attempts and it export , It opened perfect and worked on MY ABLETON DAW, so I dont know how, but it did, thanx,

@oskarsh said in Morph between tables:

I have the UI table where I cannot edit the points via script

e98bd092-a470-4adc-82cc-b884de85ca64-image.png

@d-healey Thanks David. 👍

@Dan-Korneff Understood, thanks for the info! :)

@d-healey

Thanks David, this is actually my solution to this problem, I will have two sets 8+8 of VSTs loaded, so the first 8 will play the active style while the other 8 will be in stand by mode waiting for the next style to play instantly.
The same with the real time tracks played with the right hand, there will be 4+4 VSTs, first 4 active and another 4 waiting for a patch to change, so you can still hold the key and hear the active patch, for example Saxophone, while calling up the next patch, so after you let go the key the first 4 VSTs go offline and the second group plays further without any interruption.
I hope this translates well enough in English.

@Christoph-Hart

Thanks Christoph, this is very useful.

@Lindon

I use RR in my presets to add realism , but I do not see how I could use it to load all GM library this way, every patch uses different set of filters, envelopes, and other settings. but it sounds very interesting as a workaround. Am I missing something?

@aaronventure said in Universal Sample Player....:

@Lindon said in Universal Sample Player....:

so this can be an in -plugin download or a download manager download, or an installer download, but basically it says on the Button:
Download all the files I need now

the user presses this and the downloads are attempted.

This would be great. So the files are hosted on a server, the plugin downloads these, sets them all up automatically. I think this requires disabling the internal check for samples, didn't you (or someone) ask about it the other day?

If so, there should be a definitive guide on something like this. I guess Amazon S3 and Backblaze are what most people use these days (with Backblaze being around 10x cheaper).

definative guide for HISE developers -? sure.

@Frankbeat yes

@Christoph-Hart This is sick! Building redundant processes is a breeze now.

// This class is a helper tool to programmatically build up the module tree const var b = Synth.createBuilder(); inline function createDrumSampler(samplerName, samplerNumber) { local sampler = b.create("StreamingSampler", samplerName + "_" + samplerNumber, 0, b.ChainIndexes.Direct); local directGain = b.create("SimpleGain", samplerName + "_" + samplerNumber + "_Direct", sampler, b.ChainIndexes.FX); local monoGain = b.create("SimpleGain", samplerName + "_" + samplerNumber + "_Mono", sampler, b.ChainIndexes.FX); local ohGain = b.create("SimpleGain", samplerName + "_" + samplerNumber + "_OH", sampler, b.ChainIndexes.FX); local roomGain = b.create("SimpleGain", samplerName + "_" + samplerNumber + "_Room", sampler, b.ChainIndexes.FX); return { sampler: sampler, directGain: directGain, monoGain: monoGain, ohGain: ohGain, roomGain: roomGain }; } // Usage example: const var kick1 = createDrumSampler("Kick", 1); const var kick2 = createDrumSampler("Kick", 2); const var snare = createDrumSampler("Snare", 1); const var tom1 = createDrumSampler("Tom", 1); const var tom2 = createDrumSampler("Tom", 2); const var tom3 = createDrumSampler("Tom", 3); const var floor1 = createDrumSampler("Floor", 1); const var floor2 = createDrumSampler("Floor", 2); // This needs to be called at the end so it sends a rebuild message to the UI b.flush();

@Sampletekk Add a velocity modulator to the sampler's gain.

@paper_lung Search the forum, you will find the subject has been brought up before. Generally the simpler the lottie the more likely it is to work.