Add Python Scientific Audio

[faroit]

awesome-python-scientific-audio

The aim of this repository is to create a comprehensive, curated list of python software/tools related and used for scientific research in audio/music applications.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

• I have read and understood the contribution guidelines and the instructions for creating a list.
• This pull request has a descriptive title.
  For example, Add Name of List, not Update readme.md or Add awesome list.
• The entry in the Awesome list should:
  • Include a short description about the list project/theme. It should not describe the list itself.
    Example: - [Fish](…) - User-friendly shell.
  • Be added at the bottom of the appropriate category.
• The list I'm submitting complies with these requirements:
  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • It's the result of hard work and the best I could possibly produce.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
  • Not a duplicate.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Includes a project logo/illustration whenever possible.
    • Placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Has the Awesome badge on the right side of the list heading,
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
  • Has an appropriate license.
    • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
    • If you use a license badge, it should be SVG, not PNG.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
  • Has consistent formatting and proper spelling/grammar.
    • Each link description starts with an uppercase character and ends with a period.
      Example: - [AVA](…) - JavaScript test runner.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't include a Travis badge.
    You can still use Travis for list linting, but the badge has no value in the readme.
• Go to the top and read it again.

[sindresorhus]

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

⬆️

[faroit]

sorry, I've read it again, changed a few minor things and marked all guideline items that I completed in my description above.

[sindresorhus]

The Awesome Criteria section should be in CONTRIBUTING.md

And the Related lists should be at the bottom, above Contributing.

License should be a top level section, not under Contributing.

---

Each link description starts with an uppercase character and ends with a period.
Example: - AVA - JavaScript test runner.

Not followed.

---

c++ => C++

c => C

python => Python

---

The Tutorials - Books section should be split in two. Each item should have a description.

Links like https://github.com/spatialaudio/selected-topics-in-audio-signal-processing-exercises are not good. It should have a title and description.

---

Highly recommended 👍, should say why it's highly recommended.

Excellent Book, look for the Tutorial notebooks, should say why it's excellent.

---

PyAU² ⚠️ Not maintained - Python Audio Unit Host

Don't include unmaintained stuff. Unmaintained is definitely not awesome.

---

I would like to see more non-library resources. YouTube videos/talks, blog posts, more books, etc.

---

I'd like to see some links to community resources: Stack Overflow tag, IRC, chat, forums, communities, Reddit, etc. Example: https://github.com/sindresorhus/awesome-electron#community

---

Generally, the list needs more work.

[faroit]

@sindresorhus thanks for the review. I will work this out.

[sindresorhus]

@faroit ping

[faroit]

The Awesome Criteria section should be in CONTRIBUTING.md

✔️

And the Related lists should be at the bottom, above Contributing.

✔️

License should be a top level section, not under Contributing.

✔️

Each link description starts with an uppercase character and ends with a period.

✔️ see commit.

c++ => C++
c => C
python => Python

✔️

Highly recommended 👍, should say why it's highly recommended.
Excellent Book, look for the Tutorial notebooks, should say why it's excellent.

I added brief descriptions

Don't include unmaintained stuff. Unmaintained is definitely not awesome.

all of these packages are removed now

I would like to see more non-library resources. YouTube videos/talks, blog posts, more books, etc.

I've added some additional resources, 2 books, 2 papers (one comes with youtube video) more tutorials and link to a slack channel

I'd like to see some links to community resources: Stack Overflow tag, IRC, chat, forums, communities, Reddit, etc. Example: https://github.com/sindresorhus/awesome-electron#community

unfortunately the community is not large enough currently. For this people might better off to look for unspecific Python communities.

Generally, the list needs more work.

I think it's more polished now. Tell me what you think. Thanks!

[faroit]

@sindresorhus ping

[sindresorhus]

Added :)

[faroit]

👍 thanks for your help and comments!