Questions about HISE Sample Archive tool



    1. What is the average ratio of compression for HLAC monoliths
    2. Can I adjust the script to break up the archive as per user defined size, i.e. each .hr1 = 1.5GB?
    3. It would be good to add the compression script to the Hise app


  • @midiculous

    1: I think it depends on the samples. I just compressed some harp samples with the full dynamics option (24 bit). The original samples are 1.5GB, the HLAC is 786MB.

    2: No. Well not without editing the HISE source code.

    3: What do you mean by add it to the HISE app? You create the HLAC monoliths from within HISE currently.



  • @d-healey said in Questions about HISE Sample Archive tool:

    @midiculous

    1: I think it depends on the samples. I just compressed some harp samples with the full dynamics option (24 bit). The original samples are 1.5GB, the HLAC is 786MB.

    2: No. Well not without editing the HISE source code.

    3: What do you mean by add it to the HISE app? You create the HLAC monoliths from within HISE currently.

    Yep...I see it in the export. I'm going to give it a try!

    Thanks!



  • @midiculous The option in the export menu doesn't create HLAC monoliths, that needs to be done from the sample mapping window. The export option combines all the monoliths into HR files for delivery to the end user.



  • @d-healey said in Questions about HISE Sample Archive tool:

    @midiculous The option in the export menu doesn't create HLAC monoliths, that needs to be done from the sample mapping window. The export option combines all the monoliths into HR files for delivery to the end user.

    Yep that is what I'm referring to. I want to create the HR files and I see it in the export. I'm already able to create the .ch1.



  • I'm assuming I can rename the Hise Project name.hr1 to what I want to call it as long as the names are all the same?



  • @midiculous No idea, I've never tried. Let me know if it works.



    1. .hr1 just uses FLAC compression internally, which has a slightly better ratio than HLAC. FLAC is as low as you can get for compressing lossless audio.

    2. There is a setting to break up the archive into .hr1 to .hrx using file sizes of 500MB, 1GB or 1.5GB in the export dialog

    You can of course rename the files, just leave the extension, since it will be used for determining the next archive part.



  • This post is deleted!


  • @christoph-hart said in Questions about HISE Sample Archive tool:

    1. .hr1 just uses FLAC compression internally, which has a slightly better ratio than HLAC. FLAC is as low as you can get for compressing lossless audio.

    2. There is a setting to break up the archive into .hr1 to .hrx using file sizes of 500MB, 1GB or 1.5GB in the export dialog

    You can of course rename the files, just leave the extension, since it will be used for determining the next archive part.

    Awesome! Thanks!

    If find the Hise Sample Archive does actually better than RAR.



  • When archiving the .hr1 files using the Tools--->Import Archive Samples, How do you point to the first .hr1 from this dialogue? There is no popup or dialogue to point to the .hr1 file, unlike the extraction tool that lets you point to any directory.

    0_1543344847310_Screen Shot 2018-11-27 at 1.53.15 PM.png

    0_1543344760844_Screen Shot 2018-11-27 at 1.48.34 PM.png



  • @midiculous It will automatically export all of the HLAC monolith files associated with the sample maps in the project. So there is no need to select any input files.

    This takes HLAC monolith and outputs HR archive files.

    Edit: On second thoughts is there some confusion here, you mention the import archive samples option in the tools menu but the image you show is the export samples for installer from the export menu.



  • @d-healey said in Questions about HISE Sample Archive tool:

    @midiculous It will automatically export all of the HLAC monolith files associated with the sample maps in the project. So there is no need to select any input files.

    This takes HLAC monolith and outputs HR archive files.

    Edit: On second thoughts is there some confusion here, you mention the import archive samples option in the tools menu but the image you show is the export samples for installer from the export menu.

    I did the two screenshots to show that there is an option to create the archive .hr1 to any location, yet I cannot extract from any location. The archives have to be in the project. It would be good to have the same Target Directory or Target File to extract from anywhere.

    Nevertheless, I compressed them outside of the project. What folder, within the project does the archives have to be in order for Hise to see it?



  • @midiculous This option is available in the Import archived samples tool within HISE. What version of HISE are you using?

    0_1543353741274_Screenshot from 2018-11-27 21-21-20.png



  • Ok I got it. I was in an older version. Works great and fast. One more question?

    What the difference between the Standard and Full Dynamic? I'm assuming one is 16-bit and one is 24?

    0_1543365880747_Screen Shot 2018-11-27 at 7.41.56 PM.png



  • @midiculous said in Questions about HISE Sample Archive tool:

    What the difference between the Standard and Full Dynamic? I'm assuming one is 16-bit and one is 24?

    Yes. And from what I understand the user will get the choice to extract the samples as either 16bit or 24bit if you saved them as "full dynamics".

    @Christoph-Hart is that correct?



  • Kind of. Full Dynamics is still 16bit, but it normalises the samples internally in chunks of 1024 samples so that decaying samples still use the full available bit depth.

    This way you still get the advantages of a 16bit signal path (half memory usage for all the streaming buffers) but the quantisation noise at the end of a sample is not audible anymore (which can happen if you heavily compress or distort the sound).

    The user can decide for himself if he favors disk usage or sound quality during the extraction of the samples. But with full dynamics enabled, the .hr1 archive files use 24 bit FLAC encoding, otherwise the normalisation would be pointless.



  • Ok...Still a bit confused. I normally create 16-Bit HLAC .ch1 Monoliths. I'm trying to keep things as simple as possible, so whatever the sound quality is when I created the 16-Bit HLAC monolith .ch1 files from a 16-bit sample, I just want to keep that quality. IMHO, I don't want my compression and extraction algorithms to be messing with the quality of the sample. The purpose of compressing samples is delivery, not messing with the sound.

    I did notice that the initial folder of 16-bit HLAC samples was 19.9GB. When I use Standard, I get 19.9 GB, but when I use Full Dynamic, I get a slightly bigger 23.5 GB.



  • Yes if your material is 16bit from the start, you won‘t get any benefits from using Full dynamics. Just disable it at exporting and the end user will not have this option.

    Oh and the .hrx compression / decompression is 100% bit equal, the Full Dynamics is something baked into HLAC directly.


 

1
Online

353
Users

1.1k
Topics

7.6k
Posts