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

check audio encoding and decoding #4

Open
markvdb opened this issue Apr 29, 2019 · 1 comment
Open

check audio encoding and decoding #4

markvdb opened this issue Apr 29, 2019 · 1 comment
Assignees
Labels
software Issues pertaining to the software side

Comments

@markvdb
Copy link
Member

markvdb commented Apr 29, 2019

We're currently using aac throughout the chain in voctomix.

According to Luc, opus might also be a good intermediary option for going to voctomix:

  • low bandwidth
  • low cpu requirements for encoding
  • optimised for speech applications

To be checked:

  • cpu usage on A20 Olinuxino Lime2.
  • optimal codec & parameters?

Start with an uncompressed 44.1 KHz 16bit stereo input wav file.

Throw an audio stream at the Lime2 using ffmpeg on a different machine. Encode it live with ffmpeg using the -re option to get an idea of the realtime encoding performance/cpu requirements?

@gerryd gerryd added the software Issues pertaining to the software side label May 4, 2019
@libv
Copy link
Collaborator

libv commented Oct 24, 2020

Opus definitely would be great for low latency transmission to the other box in the room, so that the other box can play the audio over the PA system. Example project: http://www.pogo.org.uk/~mark/trx.git

Then, when opus is done with a buffer of, iirc, 512 frames, we can hand that buffer and the timestamp over to the AAC encoder for muxing in with the h.264 stream.

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

No branches or pull requests

3 participants