We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@henk-spook questioned whether the binaural kernels can be used with Google's YouTube / Jump Inspector
https://storage.googleapis.com/jump-inspector/workflow/thrive.zip
Would be useful to find out what, if any, changes would be necessary to do so.
They are using AmbiX1 encoding (ACN-SN3D), and I recall seeing something that looked like a virtual speaker cube decoding strategy.
There are a few strategies I can think of:
The first of these would require generating new sets from the current ATK sets. Results would maintain all the desired qualities of ATK criteria.
The second is more efficient in terms of processing, and the current Jump Inspector developers may not be aware of this technique.
The text was updated successfully, but these errors were encountered:
Here's a link to their currently implemented binaural decoding.
Looks like their using "virtual speaker" decoding in a cube.
Sorry, something went wrong.
Also note the omnitone project.
No branches or pull requests
@henk-spook questioned whether the binaural kernels can be used with Google's YouTube / Jump Inspector
https://storage.googleapis.com/jump-inspector/workflow/thrive.zip
Would be useful to find out what, if any, changes would be necessary to do so.
They are using AmbiX1 encoding (ACN-SN3D), and I recall seeing something that looked like a virtual speaker cube decoding strategy.
There are a few strategies I can think of:
The first of these would require generating new sets from the current ATK sets. Results would maintain all the desired qualities of ATK criteria.
The second is more efficient in terms of processing, and the current Jump Inspector developers may not be aware of this technique.
The text was updated successfully, but these errors were encountered: