weTalk / Blog: Recent posts

...oh, dear.

We've got a few problems to overcome with gstreamer.

Stuff that was: Chat (26/6/2014)

Discussions

• Circuit-switched trunking between matrices was deemed unnecessary

  • Goes against the grain of the project's ethos
  • Additional packet-switched bandwidth is a commodity that can be added in a homogeneous way

• Discussed/architected audio flow within weTalk - in a nutshell...

  • We use JACK as an interface to local audio devices
    • ALSA APIs are a little messy, and with JACK, we get latency prediction
  • weTalk appears as one, homogeneous JACK client, with as many (ports) as necessary to communicate with all local audio devices
  • The JACK network is managed dynamically by weTalk, dynamically creating and destroying ports to on the weTalk client as necessary
  • Need to investigate latency of creating these pads dynamically - do we predict the number we might need in advance and use that on configuration changes?
  • For networked audio compression/de-compression, and general "menial" DSP work (attenuation, summing etc.) do we use GStreamer?
    • It'd make life simple!... read more