The sampler goes crazy with monolith

[bendurso]

I was trying to figure out why the sampler was behaving unpredictably in a project—it would sometimes play the wrong samples and occasionally play a slow arpeggiated melody after just one note.

At first, I thought it was caused by a module or script, but it turned out not to be the case. When I switched back from using monolith to WAV files, the issue was resolved. So, the problem was related to the conversion to monolith.

I'm currently using commit 6cdf5de7

[Lindon]

@bendurso did you rebuild the monolith(ch1 file?)

[bendurso]

@Lindon Yeap, I did rebuilt the monolith files with commit 6cdf5de7

[Christoph Hart]

Yeah, definitely a mismatch between samplemap and ch1 file. In the end the monolith file is just a big chunk of audio and the samplemap stores the offsets where the actual samples begin. If there is a mismatch between those two, you'll end up jumping all over the place.

Just reencode the monolith and you should be fine.

EDIT: Just saw your answer, if reencoding doesn't fix it, it might be possible that I broke something with the introduction of the release offset feature:

https://github.com/christophhart/HISE/commit/79019ea3399ac2300f94e95ea03a72493c88e2ed

Can you go back to a commit before that and check if it solves your problem?

[bendurso]

@Christoph-Hart I have a version built on September 12 (before release offset) and after recoding the samplemaps I have the same problem.

[bendurso]

This post is deleted!

[d.healey]

@bendurso Are you using the monolith reference feature?

[bendurso]

@d-healey Mm no, I don't know what that function does

[d.healey]

@bendurso It breaks monoliths for me, so don't use it :)

[bendurso]

Am I the only one with this problem?

I tested with 4.0.0, re-encoding monoliths and have the same problem, which is weird.

[d.healey]

@bendurso Can you make a mini example project for us to see the issue?

[bendurso]

@d-healey Yes, I've attached the project file. The error doesn't always occur, but if you start changing the sample map and play long notes (holding the keyboard note), at some point you'll hear an arpeggio of notes."

https://www.dropbox.com/scl/fi/1f0bdoa1d582oeuof1o82/Sapphire-Guitar-2-New-Test.zip?rlkey=1rz3lfd4x7j02p0xeqt0qzkxe&st=wb6e8qbh&dl=0

[d.healey]

@bendurso said in The sampler goes crazy with monolith:

but if you start changing the sample map and play long notes

Do you mean change the sample map while notes are playing?

[bendurso]

@d-healey Mm no, I mean playing normal notes until the sample ends. Sometimes it doesn't happen, but after changing the sample map several times, the error occurs while playing.

[d.healey]

@bendurso You say error, does that mean you get an error message? I'm not able to trigger any issues with the project and the steps you suggested. Might be helpful at this stage to make a screen recording of what you see.

[ulrik]

@bendurso I checked you project and yes, there is issues, for instance holding down B2 when having the sample map "Folk/Nomad Strings" selected, after 6 sec another sample will play.

So if this issue doesn't occur when playing that specific sample as wav or aiff, then it must be issues with conversion to monolith

[d.healey]

@ulrik Following your instruction I can trigger the issue too. It would be interesting to have the original audio files in order to test the conversion to monolith.

[bendurso]

@ulrik Thanks for checking :) Yeah, I just converted it to wav using the SaveMode=1 and the error was gone.

[bendurso]

@d-healey

Now I included the samples of the samplemap Nomad Strings. I re-enconde it again, and now the error it's on E3

https://www.dropbox.com/scl/fi/02f8y9qoguj2klhh1ms1z/Sapphire-Guitar-2-New-Test-2.zip?rlkey=r8fsa23im0yn9c97vakg06a95&st=r0t7038z&dl=0

[d.healey]

I just noticed in your sample map that all the files have absolute paths instead of relative paths (were your samples not in the project's Samples folder when you mapped them?). This could be the cause of the issue.