TeamTalk v5.1.3 released

TeamTalk v5.1.3 is now ready and has several new features and important bug fixes. Upgrading is highly recommended.

Default Qt client:

  • Option to enable/disable VU-meter updates
  • Show username instead of nickname in channel list
  • See which client application is being used
  • Fixed bug where video encoder was always set to 256 kbit/sec
  • Significant improvement in video encoder speed

Accessible Windows client:

  • Portuguese_BR, Chinese Simplified, Turkish, Czech, Korean updated
  • Fixed issue where away-status was not set after reconnect
  • Show username instead of nickname in channel list
  • TTS for private and channel text messages
  • See which client application is being used
  • Fixed bug where video encoder was always set to 256 kbit/sec
  • Significant improvement in video encoder speed

Android client:

  • Voice activation
  • Show username instead of nickname
  • Updated Turkish and Russian
  • Volume control more responsive
  • Green icon for “self” when talking

iOS client:

  • Fixed crash issue when creating channel and VoiceOver active
  • Fixed audio stream not resuming after phone call
  • Fixed disconnect issue after long phone call
  • Default to OPUS audio codec when creating new channel
  • iOS 7.0 support (iPhone 4)
  • tt:// URL and .tt file support

Server:

  • systemd configuration file thanks to Leonard de Ruijter

 

Download TeamTalk v5.1.3 for Windows, Mac OS X, Linux and Raspbian here.

TeamTalk v5.1.3 for iOS and Android are currently being reviewed by Apple and Google for submission to their app-stores. They should both be available within the next few days.

 

7 Comments

  1. Hello there. I hear the mac client still needs a lot of work on accessibility as it is coded in QT. I’m not always near my windows or iphone machines so having an accessible mac client would be a godsend. Is there a way this is beeing worked on? Loving the features I’m reading about.

    • Hi Sarah

      Unfortunately I currently don’t have the time or resources to look into the accessibility issues in the Mac OS X client.

      — Bjoern

Leave a Reply to ali Cancel reply