HISE seems to have butchered all of my loop points.
-
This is a bit frustrating, considering it looks like many hours of work must now be redone.
I have meticulously set loop points for over 400 individual samples. I set the loop points first in an audio editor, but HISE only really recognized embedded loop points about 20% of the time, thus I had to manually enter the loop points (a second time) into the samplemaps by hand. One sample per sample map. Every single one of them was rigorously tested for quality and accuracy.
I converted the samplemaps all to HLAC monolith, and every single one of the loop points has been offset by anywhere from 1, to 5000 samples. Now I'm seemingly forced to jump in and manually set all of these loop points again, but I'm not certain I trust that they'll remain.
This is a major setback. Is there anything I can do here? Are there any quirks of how HISE handles samples that I should be aware of so that I can avoid this happening again?
Thanks in advance for any guidance.
-
Maintain a dictionary of sample start/end and loop start/end points. You should be able to script this.
Are the loop points still embedded in the audio files?
-
@Elezeid HISE projects, including sample maps, are trackable in git. It's well worth using and has saved me repeating work several times.
-
@Elezeid said in HISE seems to have butchered all of my loop points.:
Are there any quirks of how HISE handles samples that I should be aware of so that I can avoid this happening again?
You should absolutely use version control like Git when working with HISE. I use Git via the interface (fork.dev) for navigating the HISE repo and managing my own, and use GitHub to back them up online.
In parallel universes where I'm not using version control while working with HISE, I've probably committed suicide at at least a dozen different points in the past 15 months precisely because of issues like the one you're describing.
