Add Audio Over IP

[Mo-way]

https://github.com/Mo-way/awesome-aoip

Audio Over IP - Reliably transmit uncompressed, low-latency audio over an IP (layer 3) network.

Many people coming from Audio engineering aren't necessarily experienced with networking,
so this list should help them (and others) get started in the field.

PRs reviewed:

• Add Free Apps #3308
• Update link for "Drupal" CMS #3299
• Add Permacomputing #3293
• Add RT-Thread #3048

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. TODO

Requirements for your pull request

• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• 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.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
• TODO: check good example for my intro, e.g. no cureted list?
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or 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 a maximum of half the width of the original image.
  • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. The casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[Mo-way]

unicorn

[nicholasaleks]

I've checked the checklist and don't see anything obvious that is missing.

I'm not an expert in Audio Over IP, but the list seems a bit short. I did some light research and perhaps you can consider also including sections on Virtual Soundcards, Monitoring & Diagnostics Tools, Live/Archived Stream Tools and/or Developer SDKs might help expand on the content?

Also just a few minor NITs

• Typos: "plattforms", "ressources", "contianing" across the README
• A short glossary or link to terms like AES67, NMOS, PTP, and Ravenna would aid new readers

[Mo-way]

Hi @nicholasaleks, thanks for the feedback!

• Fixed typos, forgot to spell check final version, sorry!
• I'd love to add awesome Virtual soundcards. The only one I personally can truly recommend is the open source kernel module I added on the list. For Dante it's trivial to find the virtual soundcard as you did, because Audinate is the only vendor. For Ravenna I'm unsure: adding the ones I know are working vs. waiting for people to add the ones they prefer.
• For other sections it's a similar decision. Just add something that looks nice and seems to be fine vs. waiting for people who actually work with it a lot and can tell if it deserves the spot.

The list is short, because I pretty harshly went for quality instead of quantity for now.

I'm all for making it easier. Why did the links to AES67, Ravenna and Dante on the top not suffice?
I never saw a Glossary section in an awesome list, but adding one here makes probably sense.

[bloo-berries]

interesting repo! Seems like everything is passing - very thorough

[hstsethi]

The "Footnotes" heading is missing in the TOC.

I have sent a PR for it.

Edit: Oh I am really sorry then. Thank you for sharing this with me, I almost missed it.

[Mo-way]

The "Footnotes" heading is missing in the TOC.

I have sent a PR for it.

@hstsethi Well spotted, but it's according to guidelines:

grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.

[Mo-way]

@sindresorhus Getting no more feedback from others. Could you review please?

[twanamhmd430-lang]

Reply- ****

9.jpg …]() t_۲۰۲۵۰۸۲۴-۰۴۴۹۰۹.png …]()

creenshot_۲۰8-22T20_23_49.jpg …]()

3b79b3A07AeBng IMG_۲۰۲۵۰۸۲۱_۲۳۲۳۴۴۴۱۱.png …]()

---

[twanamhmd430-lang]

Repley> - ****

9.jpg …]() t_۲۰۲۵۰۸۲۴-۰۴۴۹۰۹.png …]()

creenshot_۲۰8-22T20_23_49.jpg …]()

3b79b3A07AeBng IMG_۲۰۲۵۰۸۲۱_۲۳۲۳۴۴۴۱۱.png …]()

---

[twanamhmd430-lang]

🤔

[Mo-way]

@twanamhmd430-lang I'm unable to decipher your text. Please elaborate. @everyone else: assuming they are a spammer, but you never know.

[Mo-way]

Hey @sindresorhus,

Would you mind reviewing awesome PRs here from time to time?
I fixed everything I could 3 months ago (the requested change was created by a spammer).

Judging from Mastodon, you're pretty busy with Supercharge, but checking in 4-5 times a year on a project this popular would be much appreciated <3

Thanks,
Mo

[sindresorhus]

The header image is almost not visible when using GitHub in dark mode.

---

You need to fix the merge conflict.

[Mo-way]

@sindresorhus Thanks! I think I fixed both.

Merge conflict resolved.

Using png image instead of svg, to get a white background. 300 dpi is considered "high" enough, I hope.

[sindresorhus]

Tweet: https://x.com/awesome__re/status/1983229070004629572