LAF + Sampler Functions

[d.healey]

@trillbilly You need to create a user preset handler first. const uph = Engine.createUserPresetHandler() then you can call the function on that object

uph.setPostCallback(function()
{
});

UserPresetHandler.setPostCallback(samplestart, presetPostCallback);

If you take a look at the documentation again you'll see the setPostCallback function only takes one parameter, you've tried passing in two which won't work.

[trillbilly]

@d-healey Ok, I get it to compile. But then when I use the function (in this case the sample start time) it then spits out the same "Uknown function 'setPostCallback" error.

const var samplestart = [Content.getComponent("SampleStart1"),
                         Content.getComponent("SampleStart2"),
		         Content.getComponent("SampleStart3"),
			 Content.getComponent("SampleStart4")];

const uph = Engine.createUserPresetHandler();
					    

uph.setPostCallback(function()
{
	UserPresetHandler.setPostCallback(samplestart);

});

[d.healey]

@trillbilly It's late here so I'll give you an answer in the morning, but reread your code and look up each function you're using in the documentation in the meantime.

[DanH]

@Lindon Thanks :) Can I ask what you did in the post callback? I'm simply grabbing the values of the loop start/end knobs and then loading those values back into those knobs. It works sometimes and not others, leading me to suspect timing issues (poss related to sample loading time?!)

[trillbilly]

@d-healey it was getting late here too. I will be back in studio in a few hours to continue going over documentation.

[Lindon]

@DanH - what I did was I waited.... 2 seconds works here... so on preset postcallback I did the following:

1. tried to set the sample start and ends...it probably wont have worked but hey - no loss to try..
2. Started a timer on the panel its in (clearly the UI is visible otherwise we cant have selected a preset to load..)....so essentially this:

Circle.sampleLoadTimer.startTimer(2000);

in the timer... I did the following:

1. stopped the timer...as we only need to do this timer activity once...
2. reset the sample start and end times...as with luck the samples will actually now be loaded..

You may be using bigger(or smaller) sample sets than me (its only 12 waves) so the timing might need to be different, and I checked my timing loading from an external USB 2 drive..(very slow)

I am using a whole truckload of AudioWaveforms (I have 16 samplers) and I found I would need to "reset" these to show the new start and end values.. so I simply
call:

theAudioWaveForms[<someindex>].set("sampleIndex",<the zone index you want>);

[DanH]

@Lindon thanks, timer seems to be the way. Although does this mean that the post callback is slightly flawed, in that it should probably wait until the samples have loaded before triggering @Christoph-Hart ?

[d.healey]

@trillbilly said in LAF + Sampler Functions:

const uph = Engine.createUserPresetHandler();
					    

uph.setPostCallback(function()
{
	UserPresetHandler.setPostCallback(samplestart);

});

Ok so UserPresetHandler is the name of a class - that's a collection of functions and variables in C++.

In HISE you create a variable that has the type UserPresetHandler, just like you can create a variable that has the type String or Number. Then through this variable you have access to that class's functions and variables.

Can you see in the code above you have called setUserPreset on the variable we created uph, that will work, because that variable is of the type UserPresetHandler. That function takes one parameter, and that parameter needs to be a callback function, exactly like you use for a paint routine or mouse callback - anytime you see a parameter with callback in the name you need to pass in a function.

But then you've tried to call that function again directly on the type UserPresetHandler instead of on the variable uph and this second time you've tried to pass in the samplestart array as a parameter. This of course makes no sense from a program logic point of view and won't work.

The callback function (which you've assigned correctly with uph.setPostCallback(function(){});) is triggered after a preset is loaded. So any action you want to perform after a preset is loaded should go in there.

So what do you want to do with your samplestart array after the preset is loaded?

[trillbilly]

@d-healey it's all starting to make much more sense.

As @Lindon pointed out, the samples/maps dont load instantly, which in turn, makes it so the samplestart/end times dont load properly either. The idea is to have the SampleStart/End load AFTER the samplemap/preset is loaded so the correct location is placed.

[d.healey]

@trillbilly I'd have thought the loading callback would be the solution for this.

https://docs.hise.audio/scripting/scripting-api/scriptpanel/index.html#setloadingcallback

[Lindon]

@d-healey said in LAF + Sampler Functions:

@trillbilly I'd have thought the loading callback would be the solution for this.

https://docs.hise.audio/scripting/scripting-api/scriptpanel/index.html#setloadingcallback

@trillbilly - yep thats exactly what I do....

CirclePanel.setLoadingCallback(function(isPreloading)
{
	var postLoadZones;
	var postLoadStartPos;
	var postLoadEndPos;
	if(!isPreloading)
	{
		//OK so if we have just added a sound using the viewports then

		if (loadingFromViewport)
		{
			loadingFromViewport = false;			
			postLoadZones = theSamplers[SamplerSelector.getValue() -1].createSelection(".*");
			for (k = 0; k<postLoadZones.length; k++)
			{
				postLoadZones[k].set(theSamplers[SamplerSelector.getValue() -1].SampleStart,0);
                               // etc. etc.
			}

			
		};

    }else{
	    Console.print("Starting to load something.....");
	};
          
        
});```

[DanH]

@Lindon @d-healey I thought there was a loading callback :)

So one unintended consequence of changing the sample map data with ui controls is that (in HISE at least, not tested in exported) my sample maps will be overwritten at some point with the new data. I'm not resaving anything in the sample editor, it somehow does it by itself...

I can't help but feel this approach is a bit hacky

[trillbilly]

@Lindon @d-healey man, I'm all over the place with this lol. Thanks for the script snippet. So this is what is needed in conjunction WITH the presethandler, correct?

[trillbilly]

@DanH Uh oh, let's hope the compiled plugins have a touch of magic and just maybe don't have the issue lol

[d.healey]

@trillbilly No, the preset handler shouldn't be required in this case.

The loading callback is triggered when sample loading starts, and triggered again when sample loading ends.

The preset callback is triggered when a preset is loaded. This no longer seems to be relevant for what you're trying to do because the sample map is the thing we're interested in rather than the preset.

[Lindon]

@trillbilly said in LAF + Sampler Functions:

@Lindon @d-healey man, I'm all over the place with this lol. Thanks for the script snippet. So this is what is needed in conjunction WITH the presethandler, correct?

it depends....

If you are loading a sample and once its loaded you want to do something then yeah - just the loading callback,

but if you want to save the sample positions and reapply them in each preset ... then you might need to look at the preset post callback, ....

[trillbilly]

@Lindon Man oh man, ok.

If I'm not back in a few hours, send a search party...

[trillbilly]

@d-healey Thanks! I've been trying to comprehend everything all at once. I think I need to step back and focus on one part of this issue at a time. Yesterday still has my brain fried...

[Lindon]

@trillbilly said in LAF + Sampler Functions:

@Lindon Man oh man, ok.

If I'm not back in a few hours, send a search party...

Well its conceptually quite simple (well ish)

HISE and every other "windowing" system is event based, we have callbacks, so named because they get called back when something happens....

When a user clicks on or moves a control then its onControlCallback gets called, and does something.

So we have events - things that happen - and we have callbacks for them - so as well as the mouse click/drag etc. events there are system based events too...

like for instance the onTimer callbacks, all we are talking about here is two other callbacks, one when all the samples are finished loading, and one when the preset is finished loading...

The BIG problem is that we have to realise that more than one event can happen at (nearly) the same.... so as programmers we have to think about what's happening(or might be happening) when... and that can get a bit complicated...

[trillbilly]

@Lindon I understand what you're saying but I can't quite put it into script just yet lol.

I'll get there. It's beginning to make more and more sense, its just a slow process for an ape like me.