Embedded loop points
-
I'm loading a couple of samples into HISE that have embedded loop points, these show up in Kontakt's wave editor but HISE doesn't seem to recognise them - is there something I need to do to get them to show up?
-
I added metadata extraction for aiff files exported with Keymap Pro but wav files aren't supported yet.
Can you upload one sample with loop points and I'll try to find them in its metadata.
-
Thanks - here's a file with an embedded loop: http://www.filedropper.com/ebowdrone
-
Alright. This was rather easy. I abandoned the useless "Automap velocity" button at the import popup and replaced it with a option to extract the metadata from samples.
Or you can use the context menu command in the mapping editor (Tools -> Automap using Metadata).
Currently it supports loop points for .WAV files and some more properties for .AIFF files (they have a better defined metadata set). If you spot anything missing, let me know.
-
Brilliant, thanks!
-
How do loops work with multi-channel samples? Do I just need to loop one sample of the channel and it will be used by all of the other channels?
-
Yes it should work like this. I haven't tested it tough so maybe its a bit fishy...
-
I have some multi-mic samples, I've added a loop (outside of HISE) to the close mics. When I import the close mic sample I can see the loop in HISE, however when I import the other mics and merge them I can't see the loop points.
-
I've just pushed a commit that fixes this (it actually ignored all loop properties). I think I've implemented it pretty robust, but please test if it works with a whole batch of samples.
-
Thanks, I'll test it tomorrow
-
I'm having some strange issues with looping now but I'm not sure if it's an issue with HISE or the samples. I've uploaded some samples here (2mb) - http://s000.tinyupload.com/index.php?file_id=16031816873555185712 - these all have loops that show up in EndlessWav, Reaper, and Kontakt, but they aren't showing for me in HISE.
-
I'll take a look, but it's possible that my loop-point importer is not as robust as it should be (it worked for my samples in the past, but there is no hard standardisation for loop point definition so there are many edge cases).
