The release for kernels comes in a folder with the release number appended and "atk-" prepended. E.g.,

atk-sounds-1.0.0

atk-sc3 expects the kernel folder to just be named

sounds

As a result, dropping the unzipped and un-renamed folder into Platform.userExtensionDir does not result in a working atk-sc3 installation. Here's my reply on the sc-users list to a new user attempting an installation.

The question, then, is what is the best way to resolve? Do we just give atk-sc3 users an instruction to rename the folder as I've done here (follow to my reply at the bottom)?

We'd like atk-sc3 and atk-reaper to both use the same assets to keep everything synchronized.

Related atk-kernels issue: Installation folder name conflict #5

From Paul Hodges:

I note that you list a number of sample soundfiles in your documentation, and that three of them have the address of a long-dead web site. Fear not! Those three files are still available at the following addresses:

http://ambisonic-files.s3.amazonaws.com/AMB/pwh-Purcell-Passacaglia(HowHappy).amb
http://ambisonic-files.s3.amazonaws.com/JL/orfeo.amb
https://ambisonic-files.s3.amazonaws.com/JL/jlc2.amb

In fact, all the files contributed to the old Sound of Space website by myself and John Leonard are available through my website:

https://ambisonic.info/audio.html

Update LICENSE

README.md includes a section discussing Git LFS:

Working with this repository

The sound files in this repository are versioned using Git Large File Storage (LFS). You will need to install LFS in order to clone and work on this repository. The repository is set up to use LFS with all WAV files.

Is this up to date? If not, I'd expect the Working with this repository section should be modified or removed.

@dmartinp given Workshop / Tutorial materials #7, supporting soundfiles will need to be added to atk-sounds.