New client for Teensy Audio

VB-Audio Network Protocol and applications
palmerr23
Posts: 9
Joined: Thu May 21, 2020 5:24 am

Re: New client for Teensy Audio

Post by palmerr23 »

:-)
palmerr23
Posts: 9
Joined: Thu May 21, 2020 5:24 am

Re: New client for Teensy Audio

Post by palmerr23 »

An update.

So far, I have tested up to 8-channel audio and two streams of 2-channel audio running using a Teensy 4.1 running the Teensy Audio Library and Voicemeeter on a PC, on an isolated 100Mb Ethernet network. Several in and out streams subscribed and running concurrently for several hours without an issue.

The only limitation with audio is that it needs to be 44.1kHz PCM16 format, as that is the Teensy Audio standard.

Voicemeeter's chat function is working. I'm now tweaking subscriptions to enable multi-way chat.

After that, I'll implement Teensy-Teensy messaging for text and structured data. Not a big deal as the chat function implements almost all the features.

Thanks for your help so far.
Vincent Burel
Site Admin
Posts: 2085
Joined: Sun Jan 17, 2010 12:01 pm

Re: New client for Teensy Audio

Post by Vincent Burel »

thanks for reporting news on your development.
feel free to ask if you are missing something.
palmerr23
Posts: 9
Joined: Thu May 21, 2020 5:24 am

Re: New client for Teensy Audio

Post by palmerr23 »

The code is working well enough for an initial release.
  • Two-way, multi-stream, 1-8 channel audio is working with Voicemeeter (only at 44.1KHz PCM16 as that's the Teensy Audio standard).
  • VBAN Chat is also working, with one bug (my client eats the first few messages from Voicemeeter while it asks for a PING and then registers the response).
  • Text (e.g. JSON) and structured data is working between Teensy hosts, using the SERVICE sub protocol and format_nbc values other than the ones defined in the VBAN standard.
The new library is published at https://github.com/palmerr23/EtherAudio

While it runs fairly smoothly, beware that it is still ***alpha*** code .

A substantial quantity of diagnostic prints are embedded in the library code. They can (mostly) be disabled by commenting out the #define XX_debug lines in the header files.
Post Reply