Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document hrir filter installation #12

Closed
patrickdupuis opened this issue Jul 23, 2018 · 4 comments
Closed

Document hrir filter installation #12

patrickdupuis opened this issue Jul 23, 2018 · 4 comments

Comments

@patrickdupuis
Copy link
Contributor

Users require some hrir filters in order to make use of the HOADecLebedev* UGens. If I understand correctly, by default, these files need to be located in ~/.local/share/HOA/kernels/FIR/hrir/*lebedev50 (linux) or ~/Library/Application Support/HOA/kernels/FIR/hrir/*lebedev50 (macOS).

The SC-HOA documentation doesn't appear to instruct users how to obtain these files, or where they should be placed. The ambitools repository contains Lebedev audio files. Couldn't users be instructed to download those and place them somewhere on their system?

SATIE makes use of the files from the ambitools repo that we place in our own custom location. Ideally, we would like to access these files in the default SC-HOA location. Our installation instructions could simply echo yours in telling users they need some additional resources.

@florian-grond
Copy link
Owner

just added to the tutorial the info on where to get the FIR's from (ambitools)

@patrickdupuis
Copy link
Contributor Author

This information needs to be located in the Installation section of the README. Why bury this information in a tutorial?

Also, the addition is incorrect. The FIR folder needs to be copied to ~/.local/share/HOA/kernels/`.

I've also noticed an issue with the HOA.userSoundsDir, etc. I'll submit a PR.

@florian-grond
Copy link
Owner

florian-grond commented Jul 23, 2018 via email

@florian-grond
Copy link
Owner

florian-grond commented Jul 23, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants