Got it thanks....

This is probably a super easy question, but how do you extract .HR files using the Hise Standalone app?

Thanks so much for the detailed explanation and it is much appreciated.

And what's even more weirder is that when I have a mixture of 24-bit and 16-bit files and encode to CH1 I get 14GB as previously stated, but when I convert all of the files to 16-bit and encode, I get 18GB.

So it seems that the encoder compresses 24-bit better than 16, which is even weirder.

Part 1

Let me be more clear just to make sure I"m explaining it correctly. I have a bunch of .aif sounds in folders which represent a complete library that is 44GB. The library contains a mixture of 16 and 24 bit uncompressed audio files. I encode the library and convert to .ch1 compressed and the total library is about 14GB, which is great.

For this part, I just want to make sure I'm not loosing any quality of my 24-bit audio files given the dramatic compressions, which is awesome. Mind you most of the files have long decays, which your compression loves, so that may be where all the savings is.

---

Part 2

I go to create the .HR archives and choose 2 GB Split archive size and Yes to Support Full Dynamic Range of the 14 GB files

I'm ending up with about 10-2GB files, which ended up being 21 GB, which is more than the original 13GB .CH1 total library. So I'm just wondering if this makes sense

I don't want to loose quality, yet I still want to keep the archives low. So I need to know what I'm loosing or gaining.

So in Summary:

• Library Size: 44GB uncompressed AIF files
• HLAC Compression to .CH1: 14GB
• Archive with Full Dynamic Range Off - 6.78GB (4-Archives)
• Archives with Full Dynamic Range On - 21GB (10-Archives)

@Christoph-Hart The .ch1 files are compressed from uncompressed .aif files.

Bump...

Would really like help on this one

Still not sure I understand the Full Dynamic Range thing. As a practical example, what would happen if I export my 24-Bit library (.ch1) files and say NO to Support Full Dynamic range?

I don't have my engineers hat on right now, so I need a basic understanding of what would this do to the sample content when the user extracts? Is there any audible difference?

Still confused, because when I tried to turn on Full Dynamic Range with 24-Bit Ch1 files, it seem to increase the compression even more than the total size of the samples and I ended up with a ton of .ch1 files. For example, my library is 13GB, but ended up with about 8 2GB split archives, which is way more than the initial 13GB.

Trying to understand....Thanks in advanced.

I've been doing quite a few multi-mic position samples recently. I'm still old school as I still edit using Redmatica Keymap as nothing else on the planet can edit like it does. I merge all of the mic positions and can tune and edit all at once.

My question is how does Hise address the stereo field. I know there are options for Left, Right, and Center. Can this be done in post or does this have to be done during export?

My goal is to allow the user to dynamically assign the stereo field themselves, but not sure how all that works.

You may want to consider this tool as well: http://www.e--j.com/index.php/soundfilesmerger/. I have used it as of recently to merge different mic positions, so I only have to edit once. It merges all of the files into channels.

Does Hise have a way to encrypt the .ch1 files. I know we talked about this a long time ago and @Christoph-Hart I think mentioned that it would reduce the speed of the streaming.

I just wanted to follow-up to see if this may have been added in the past year.

So far so good. I think updating this in Amazon S3 Meta info to ```
application/x-www-form-urlencoded

I must say that the actual extraction portion is rock solid. Thanks @Christoph-Hart. As I said RAR is getting increasingly difficult, especially cross platform. Keka is finicky and UnRarX is discontinued, so this is a life saver. The main issues I get are:


* Users not downloading all files completely
* Users not having all of the files in one location

@d-healey said in .hr1 and .hr3 Files Opening:

@MIDIculous I use Amazon S3 too. The Content-Type for my HR files is set to application/x-www-form-urlencoded

I'm going to try Content-Type attachment

So I went to Amazon to check and it seems as if the Value for the content type is correct:

• Value = application/octet-stream which means it has to be opened with an application.

So my MIME Meta-Data types seem to be fine

@staiff said in .hr1 and .hr3 Files Opening:

compress (zip or rar) your hr-x files and you won't have weird issue with firefox ;)

I'm finding that Keka is no longer compatible with the Winrar format and yields tons of errors. Also UnrarX is discontinued. Having major issues with RAR extraction and Hr1 is so solid, except for this .hr1 .hr3 trying to open in the browser and can't download.

@d-healey My files are hosted on Amazon S3.

Just launched a sale and have tons of customers reporting this, so I know it's not just one person.

Just an FYI: In Firefox, it recognizes .hr1 and .hr3 files as audio files and is trying to open them, so users who purchase and try to download the .hr1 and .hr3 files has the browser trying to open it.

May want to consider a different extension for anyone having issues.

@Christoph-Hart said in More Error Logging with .hr1 Extraction Utility:

subclass from HlacArchiver::Listener and you'll get verbose logging info

Awesome!! Thanks!