only when plugin is visible?

[d.healey]

I'm investigating..

btw you should reduce the max voice count of each of your samplers, I doubt you need more than 16 per sampler in an instrument like this. It will reduce RAM/CPU usage.

[d.healey]

Ok it seems with samplers you have to set the UseSourceChannels property for the floating tiles to true otherwise it will use the master output - I don't know why this is necessary but should solve the issue for you.

[Morphoice]

@d-healey said in only when plugin is visible?:

you should reduce the max voice

true, actually only 1 voice per sampler is needed I guess

@d-healey said in only when plugin is visible?:

with samplers you have to set the UseSourceChannels property

wow thanks, Dave. another one I could never have figured out. I seem to have a lucky hand stumbling upon the hard ones ;)

[d.healey]

@Morphoice said in only when plugin is visible?:

I seem to have a lucky hand stumbling upon the hard ones

Everything's hard before it's easy ;)

[Morphoice]

@d-healey true :)

[Morphoice]

@d-healey you wouldn't happen to know why the balance/volume of the sampler doesnt affect the meter, would you? I#m having a hard time with them always peaking at 100% no matter how low I turn a voice to be

[d.healey]

@Morphoice said in only when plugin is visible?:

balance/volume

Try changing the SkewFactor or PaddingSize properties.

[Morphoice]

@d-healey nah the values must be taken from before the samplers balance control, which is funny, as the little indicator on the sampler module itself shows it correctly

[d.healey]

@Morphoice You should add a simple gain to each of your samplers and connect the peak meters and your volume sliders to those rather than connecting to the sampler's volume knob. The sampler's knob doesn't have any smoothing applied so you can get glitchy sounds when automating it, but with the simple gain this doesn't happen.

[Morphoice]

@d-healey Aye, I'll try that. Sounds like a better solution and will probably fix the 0-1 linear value to dB which I'm having

[Morphoice]

@d-healey the simple gains got everything sorted!

I did this to manage the eprom selection with the button colums

function onControl(control, value)
{
   if (snareProms.contains(control)) {
	   var index = snareProms.indexOf(control);
	   for(e in snareProms)
	  	 e.setValue( e == control);
	   Console.print(snareMaps[index]);
   }
}

there's the same problem with the controls all being triggered onInit unless I make them not a preset parameter. If I replace the console output with loading the samplemap the plugin get a bunch of commands to load maps at once, would that bother the sampler or be a performance problem? as I understand it the map is just parameters and the sampler lazy loads the samples anyways after it has read the map... however, setting an initial selection doesnt work that way again.

is there a workaround to have my selections saved in a preset that still works?

[d.healey]

@Morphoice control callbacks should be inline functions and there you can use local instead of var.

[Morphoice]

@d-healey stops working when I make it an inline function

this is the general onControl function if you go to Callbacks>onControl
not something I put in onInit script

[Morphoice]

@d-healey I'm just reading this https://docs.hise.audio/scripting/scripting-in-hise/javascript.html#variables so I guess I should declare my loop and index variables in onInit and get it out of the function

[Morphoice]

@d-healey or in that case maybe avoid them completely by doing

	if (bassProms.contains(control)) {
	   for(e in bassProms)
	  	 e.setValue( e == control);
	   Bass.asSampler().loadSampleMap(bassMaps[bassProms.indexOf(control)]);
	}   

that works too

[d.healey]

@Morphoice said in only when plugin is visible?:

you go to Callbacks>onControl

Don't use that, it's long deprecated. Assign individual callbacks to each control.

[Morphoice]

@d-healey ah damn. that would be a lot of controls given the number of buttons to pick the soudns

[d.healey]

@Morphoice you can apply the same callback to multiple controls in a loop

[Morphoice]

@d-healey funny enough I've been doing that from the start, then discovered the onControl function and though "great, that new feature saves me a lot of code" and moved it all there