@d-healey I've experienced this in earlier versions too

I'm building a few instrument with rather many samples. One sampler can be mapped with +1000 samples.
When mapping them, (I have notename in filename), it seems like when you have mapped around 800 samples, Hise crashes when using "Filename token parse" and clicking ok to map the samples.
I then maybe try to map around 70 samples.
After restarting Hise, it works if I import/map around 5-6 samples at a time.
If I restart the computer, (Mac), I can map again without crashing.
So, it seems that there are some kind of cashe that is cleared when restarting the Mac, but not when restarting Hise.
Any thought on this?

The ch-files that got stuck, came from a sampler that had +1600 samples. It works great and plays great, bot the process och packing the monolith files didn't. I ended up splitting it up into two samplers, and then everything worked. But it seems to be some kind of limit on the numbers of samples that can be in a samples in order for packing into .hr-files to work

@d-healey said in Limitation on monolith files size when packaging:

@Christoph-Hart

I'll contact him!

@Sampletekk said in Limitation on monolith files size when packaging:

@d-healey Yep, developers branch. I'll send you dropbox links in PM

Isn't there a PM function in this forum...???

@d-healey Yep, developers branch. I'll send you dropbox links in PM

@d-healey said in Limitation on monolith files size when packaging:

@Sampletekk How long are you waiting?

About one hour

@d-healey Same thing I'm afraid....

@d-healey I'll give it a try!

I have a large sample instrument, where one of the monolith ends up in three ch-files, two that has the size of 1Gb, and one 329mB.
When making .hr files, "Package sample monolith files", the export freezes after 100% compressing the first ch-file, .ch1. Total progress is then at 22%., (I also have some other samples beside this big one).
Anyone else experienced this?

Per Larsson, Sweden. Owner of SampleTekk, sampleproducer

@d-healey Thanks! Edited the samplemap! Good idea to report it at github!

Using the latest build from developer branch.
Do the following:

1. Add a sampler
2. Set RR Groups in Sampler setting to 4
3. Stack 4 samples on top of each other
4. Try to change RR Group for any of the samples

If I try to change the RRGroup, it changes to 0 and after that it can't be changed to anything else
Am I doing something wrong, or is it a bug?

@Chazrox That only sets loop points for the whole sample. Thing is, that all samples has loop points already set in another program. When importing to Hise, some of the samples still has loop points, others not.

I'm importing wav-files that has loop point set, and some, but not all, get's the loop points imported.
Here's one that Hise seems to miss:
https://www.dropbox.com/scl/fi/emni852izgkxmx3zfdg7a/1_-8.40_ClPu_E4.wav?rlkey=3wfpt45zbk9qsu6jyqlj0ev4y&st=4lboslq0&dl=0
Here's what it looks like in Wavwlab:

and here's the same file, imported into Hise:

I've checked the "Extract metadata for mapping" option, and also get the popup "Loop points found" window, but no loop points in the imported sample in Hise.

Any ideas?

Found the problem!

Logic Pro crashed when playing a MIDI file and starting/stopping the playback

After stripping down the instrument part by part, I could isolate the problem.
I have a sampler that plays hammerback sound, that is, the sound of the piano hammers, falling back after releasing a key.
It turned out that the Release Trigger MIDI processor for that sampler had the Time Attenuate activated, for some obscure reason, or mistake... When I deactivated that, Logic worked as it should.
I also have regular release samples that has the Time Attenuator activated, as it should, but the the curve is reversed, sinve I wan't those samples to trigger at a lower volume the longer a key has been pressed prior to release.

If the thing that caused Logic to crash was the combination of these two release samples, or only the Hammerback, I don't know, but when I, or anyone else, have more time and want to do a test, it might be a good idea. This was the AU version, and only on Logic Pro

I might be stupid, but I can't figure this out. Yes, I understand that things that should be in the Audio-thread, should not be in the UI-scipts, so I need to place that code in another script, that is not defered.
Should I make a new Script Processor and put the Audio stuff i there? Like this, (Script Processor1)

If so, should the code that was in the "On Note" callback in the Interface script, go into the "On Note" callback in the new "Script Processor1"?
And, how will I know that the code in the two "On Note" callbacks in the different script processors are executed in the correct order.
I realize that this probably is stupid, but bare with me, my first language was Cobol....

@d-healey What would be the best practice to pass data between UI scripts and non-UI scripts? Write functions or by using variables?

Is there a tutorial, or text, that explains what would go in a MIDI-thread, and what goes in a audio-thread.
For instance, in this code, what should not be in the UI-script?

function onNoteOn()
{
	var inVel = Message.getVelocity();
	var newVel;
	var noteNumber = Message.getNoteNumber();
    var Id = Message.getEventId();
    var velo = Message.getVelocity();
    if (velo == 1)
    {
    	Message.ignoreEvent(true);
    }
    
    noteNumber = noteNumber - 21;	
	//Console.print(noteNumber);
	//Console.print(Id);
	
	for (i = 0; i < keys.length; i++)
	{
		//Console.print(keys[i]);
	}
	
	//Console.print(keys[noteNumber]);

    Synth.addPitchFade(Id, 0, 0, keys[noteNumber]);

    if (transValue == 1)
    {
    	switch (noteNumber)
    	{
    		case 4:
    		{
    			//Synth.playNote(24, 1); 
    			Message.ignoreEvent(true);
    			break;
    		}
    		case 3:
    		{
    			//Synth.playNote(25, 1); 
    			Message.ignoreEvent(true);
    			break;
    		}
    	}
    }	
}
 

@d-healey So, by putting Synth.deferCallbacks(true); in the onInit interface script you don't need to ad it to other callbacks in interface scripts, that's the only place you should put it?