1. when could update an other team talk 5’s other version with new improvements and a possibility to increase buffer, playlist etc? I think people with slow connections without interruptions audio or interferences! Because yesterday in the forum i understood a problem and is very rare! Is inpossible! In voip no interferences or interruptions please!

    • CELT is mainly for high quality audio whereas OPUS can be used for both voice and high quality audio. Internally OPUS uses the SILK codec for voice and CELT codec for high quality audio.

      — Bjoern

  2. Just a couple of questions about video sharing/broadcasting using TT 5 with the VP8 codec… is there any chance of utilizing more than a single core on a multi-core system for this process, perhaps by getting the SDK and compiling with a switch to use multiple cores, else if supported, GPU encoding using OpenCL to reduce/eliminate video stuttering?

  3. I was curious if you ever thought of changing the layout of your site?
    Its very well written; I love what youve got to say. But maybe you could a
    little more in the way of content so people could connect with it better.
    Youve got an awful lot of text for only having 1 or 2 pictures.
    Maybe you could space it out better?

  4. As a blind user I wonder whether or not this latest version will be accessible or will I have to continue using the Classic version? If so, are there any plans to update this version also?

    • Development of the Classic client will continue in TeamTalk 5, since the Qt Framework (which is used for the “normal” client) still doesn’t work very well with screen-readers.

      — Bjoern

  5. HI,

    will the problem of audio packet loss be addressed in TeamTalk 5?
    a room uses Celt with 44,1 KHz stereo and 128 KbPS.
    So, every 4 or 5 hours, a user starts to sound choppy and produces jitter errors.
    Or is there a way to fix this in TeamTalk 4 already that I do not know of?


  6. Hi Bjoern,

    usually, it may vary between 5 hours, even 8 to 9 hours.

    We are on a server where we tend to establish a streaming instance, playing stuff at night to sleep, or just listening to movies ocasionally.
    So sometimes, when someone streams constantly, this happens and results in the effect I described.
    Sound will become choppy and you have to reconnect the TT instance to fix it.
    It sounds like a CD with dust on it, or a badly ripped disk.

    Sometimes, when someone has been muted for a longer period of time, the effect isn’t observed within 9 hours or so, but it usually happens in less than 12 hours.
    We don’t really know why, but so far it does not seem to happen.
    All clients use the “Direct sound” setting.
    We do not use any echo cancellation feature.
    Oddly enough, a mac running for a longer period of time and with their beta enabled, does not exhibit this behaviour.

    I don’t really know how we could help you resolve that issue, other than describing the problem.

    Also, we’re all using the classic client with accessibility.

    Thanks and regards!

  7. Hi Bjoern,

    I tried both Windows Audio and Audio session, but both with the same negative result.

    The problem must be elsewhere, in the Codec, or on the server side, really no idea…

  8. Hello. As idea, the possibility of create User Groups could be nice; i.e. I want “unregistered users” join to that initial channel when connect to the server. So, we can manage lots of users which should have same permissions.

    Thanks for reading .)

  9. As for the audio causing jiddery effects after 5 hours of use, would it be possible to make the client detect it and reload the sound system? I stream music and movies sometimes and it seems to happen after 5 to 8 hours of use.

Leave a Reply