Okay...
i re-recorded my instruments in (min) 44100 kHz. redone the monolith and all is fine.

NOTE: i first create an .sfz encapsulation in ESC, just because i feel it more fun to import my samples inside HISE than direct .wav (.sfz has root note, start end sample, start end loop, etc. .. that is automaticly set up in HISE when importing)

when creating monolith a line is added in the samplemap.xml:

"MonolithOffset="value" MonolithLength="value" SampleRate="44100"/>"

maybe something wrong beetween the 27.8 kHz data infos inside the wav, the .sfz info and this line created in the samplemap file ?

BTW, with brand new 44100 kHZ or above samplerate: all is good ;)

So far nothing has been done with this and still cannot consistently do a Batch convert without crashing. I have to do things one by one, which is extremely tedious with thousands of samples.

@d-healey hahahahaha 😁

Any help?

@christoph-hart So is this SSE 4.1 requirment also system requirment of HISE exported plugins? Because of that should we give this information to the user before they buy the plugin?

@christoph-hart That worked! :)

Yup VS2017 it is plus the C++ extensions that will install themselves when you need them.

Could you make a video demonstrating the issue?

@d-healey I mentioned this before as well. I think Christoph is aware.

@d-healey Weird, this has stopped happening now!

@d-healey said in Zipper noise with group XF:

HiseSnippet 672.3oc6V0saSCCE1tsAwDvzPZHwk4E.oUX.6t0tt1oIVGQMkA2MYbNq0BG6LGmA8cfGNdT1a.bbR2RpHpp8hMj.xU47c7I9yemebBLZNjlpMD5Fimk.D5i8BmorS6MkITjiOjP2zaHK0BF+BnClkvRSgHBk17HG.ciVj7mq2+.ljo3PIDgblVvgSDwBaIZPm2IjxArHXrHtxp2sywbspmVpyP9zzaGRBi+E1D3TlaYM7HzGzORX0lPKyBoDZqCzQyBmp+ppX8mIREeVBNi1jP7CU.OPKibL18No2TgLJ3lycJgP8BJUglEpv1dCEQhawKUisxc3WFQU8f1XYzqcU5sSszqcMziTgcsJXGRBcTljYWjYtzwbGB8hYpiUVPkJryplt9iR2m5EHr7o0y2F0vWLQcWy24I+m30+hK.tsjrs7F7o62L8lET4QdgBEj2QlSjmka6+Q1Uf+QfBLNQcI8j+XU6ISV4dx2ys3tO1vToI5zE9vgPrXrV4DjRvOjBCLvkibI4p38zLSsttd+A3Yr1XBY1LSd0R2XclxtP0QyUNkTc1vhMMUVeMCJZ8+AE4zs4pIs0nfzfe6BmsvR53DIzWcEH0HRwzgCgKXYR6snUI4PsRmLUqD7pE.i.qQLYBXpR8ZOOcsV7hkRjs6LBj.qRw7deuyIXQHyfxDb2KEKKc8buB556ZL8+6X9dy+MmuORmYEpICYXg52v+63zr3PbtJGPlnTfD2HOZC2rwB6cb1ECVUQ4F+Del6rsylN2Y6abdurGwLtQeNduf0nktZ4GlifmaU9epsA9KinseaxULY1bUJFGGdNm6D6WfpS8Q7x0NhWs1Qr6ZGwqW6HdyZGwaW6H1aIQ3t6oalUGWz5g.A8OjYYXsceECqbyqxI+h8e0w4

@Christoph-Hart

I've used this snippet

Here's the plugin https://drive.google.com/file/d/1ADrP-XFSwUvtttDE2xYvhBuCye-_orjo/view?usp=sharing

@d-healey YAY!!

Oh wait I didn‘t ;)

But here is the post with the link:

https://forum.hise.audio/topic/884/zipper-noise-with-group-xf/3

@roy-n Why are you manually assigning the groups, were they not assigned by the token parser?

@christoph-hart Oh I forgot. Just tried it and it seems to have worked :D

alt text

Ah, OK, then I'll take a look why it doesn't behave...

Yeah, it most likely has something to do with the new file pool system and shouldn't be too hard to fix.

Ooops, I was still using the old GZIP decompressor to extract the user presets which are now compressed with the new shiny zstd compression algorithm :)

Yes, I don't think that anyone that starts thinking about customizing it's UI in anyway is using the default knobs :)