HLAC Compression for CH1 files - not working out so well...

[Lindon]

@Lindon -interestingly - yet more sfz problems...

Loading an sfz now captures the lops but sets Duplicate ="1" in all cases...

<sample ID="1" LoVel="46" HiVel="50" FileName="{PROJECT_FOLDER}CT Boot Boo FIXED_01.WAV"
          LoKey="53" HiKey="53" SampleStart="0" SampleEnd="158448" LoopEnabled="1"
          LoopStart="23385" LoopEnd="140829" Pitch="0" Root="53" Volume="-6"
          Pan="0" RRGroup="1" Duplicate="1"/>

There are no duplicates in this sfz....

[Lindon]

@Lindon OK more feedback - I went through an laboriously hand-edited the sample map to make sure all the entries were all correct - took me 3 hours...there were all sorts of strange duplications and anomalies - I still say this whole sample map making needs a serious work over -- and ran the compression again - and now I get a (very nice) 1,732,780 Kb - or 1.6Gb - so massive improvement...now all I have to do is go back and do the same to the remaining sample maps--- possibly days of work...

[d.healey]

@Lindon Which part are you hand editing? The loop points?

[Lindon]

@d-healey - no they are coming over fine now - Duplicates="X" is often wrong, and there are silly amounts of duplicated entries - so exactly the same meta data for a single file

duplicated elsewhere (nowhere near it) in the sample map, but with its duplicate="1" set ...

[d.healey]

@Lindon Could you send me over one of the files so I can experiment to see if I can find a way to clean it up more quickly?

[Lindon]

@d-healey well I just wrote over them!!! Let me see if I can find an original "broken" one...

[Christoph Hart]

@Lindon said in HLAC Compression for CH1 files - not working out so well...:

possibly days of work...

Nah, we'll make a fix for that one. What if there is a simple function that runs over the samplemaps and fixes the duplicate ID flag? This flag is not being used super prominently, so there might be many occasions where it gets corrupted (eg. if you delete a duplicate sample making the other one non-duplicate, etc).

[Lindon]

@Christoph-Hart said in HLAC Compression for CH1 files - not working out so well...:

@Lindon said in HLAC Compression for CH1 files - not working out so well...:

possibly days of work...

Nah, we'll make a fix for that one. What if there is a simple function that runs over the samplemaps and fixes the duplicate ID flag? This flag is not being used super prominently, so there might be many occasions where it gets corrupted (eg. if you delete a duplicate sample making the other one non-duplicate, etc).

I'd trade this for the ability to select an rr group and HISE actually import dropped audio into it - not into group1..

[Christoph Hart]

Have you tried using the scripting API calls to actually do the mapping? If you have a ton of samples to map, this is usually the way to go as you can apply Regex rules to extract almost every property of a properly named sample file.

Haters might argue this is the reason why the GUI based mapping is so sloppy - I never did it again after writing the scripting API for setting sample properties...

[Lindon]

@Christoph-Hart never thought of doing it that way - which scripting API calls do you mean?

[d.healey]

Fun with Regex

Powerful stuff!

Forum (forum.hise.audio)

[Lindon]

yeah -- sorta -- I can see how this would be useful if (As Christoph says in the thread) all the audio had comprehensive and inclusive file names (that included low note, high note, lo velo, hi velo, rr group etc..) - but frankly I nearly never get audio in that sort of format... its all "hand-named" using some folder structure.. and oft times comes from some pre-existing Kontakt product - so via sfz at best ---- .so I'm stuck with the drag-and-drop interface --I can usually work a way around (again usually with some python scripting to build the xml ) but it'd be nice if I could drag a set of audio into a sampler in a given rr group and have it map there correctly - but it never ever does.

[Christoph Hart]

If it's of any help, the folder name is also part of the sample's FileName property.

Another helpful tool is a batch file rename utility - usually the samples that I work with have "some" sort of useable info in the filename which might be massaged into something that the regex processor can cope with. This is the way to go to clean up inconsistencies before the import process (and your samples might thank you anyways for getting more meaningful names along the process).

[d.healey]

@Christoph-Hart said in HLAC Compression for CH1 files - not working out so well...:

Another helpful tool is a batch file rename utility -

This is my solution to badly named samples too. I use PyRenamer

[Lindon]

@d-healey @Christoph-Hart -- oh trust me this is a life saver for me (well MASSIVE time saver at least):

Bulk Rename Utility - Free File Renaming Software

Bulk Rename Utility: Free File Rename Utility for Windows. Bulk Rename Utility allows you to easily batch rename files and folders based upon many flexible criteria. Free Download.

(www.bulkrenameutility.co.uk)

[Christoph Hart]

yup, that's exactly what I'm using :)