TeamTalk v5.6 released

BearWare.dk logo

TeamTalk v5.6 has now been released for all platforms and can be found on the Download page. Apple, Google and Microsoft app stores are currently processing the new release so it should be available in the next few days.

New Features

This new release comes with many new features, especially a lot of accessibility features for the desktop clients thanks to Corentin Bacqué-Cazenave. The Android client also got a thorough remake thanks to Igor B. Poretsky and Beqa Gozalishvili.

Here’s a summary of the new features:

  • Accessible Windows client
    • Removed duplex mode for sound devices
    • Removed Windows Sound system
    • Removed Advanced page from Preferences
    • Default sound system, Windows Audio Session, now uses Windows’ own echo cancellor, AGC and noise suppression
    • User accounts are now sorted alphabetically
    • Text message log files are stored with .clog and .ulog extension for channel and user log respectively
    • Blank nicknames are set to NoName followed by user ID
    • More items are now translatable.
    • French, Turkish, German and Chinese languages updated.
    • All areas of main window are now labelled
    • Slider controls now use down arrow to decrease volume and up arrow to increase volume
    • TTS announces volume changes when using shortcut keys Ctrl+Alt+Left/Right and Ctrl+Shift+Left/Right
    • When in main channel the application title is now server name
    • Blank characters are automatically removed from username and channel name
  • Default Qt client
    • Removed duplex mode for sound devices
    • Sound system Windows Audio Session now uses Windows’ own echo cancellor, AGC and noise suppression
    • Text message log files are stored with .clog and .ulog extension for channel and user log respectively
    • Press tab changes focus in text message dialog
    • More items are translatable
    • More controls are labelled with accessibility hints
    • When switching to Away mode due to inactivity the status message is now updated
    • Blank nicknames are set to NoName followed by user ID
    • When in main channel the application title is now server name
    • Blank characters are automatically removed from username and channel name
  • Android client
    • Empty channels with max users set to zero are listed first (sticky channels)
    • French language is now supported
    • Buttons for changing between tabs Channels, Chat, Media Streams and Files
    • Preferences are grouped into General, Sound Events, Text to Speech, Connection and Sound System
    • Users are now displayed before channels
    • Support for dark mode and day/night shift
    • Blank nicknames are set to NoName followed by user ID
    • More elements are now labelled with accessibility hints
    • Bluetooth headset microphone usage facility
    • Use back button on the action bar to navigate to the parent channel
  • iOS client
    • Channels are now sorted correctly in TeamTalk on iOS 13 and newer
    • French translation has been updated
    • Blank nicknames are set to NoName followed by user ID
    • Blank characters are automatically removed from username and channel name

11 Comments

  1. Hello, congrats for the new update!
    Me and a friend are now working hard on the new Romanian translation and will be sent to your email soon.
    Good day!

  2. hello.
    I have some suggestions for future team talk versions for android regarding to its accessibility, It would be great if you consider adding them.
    when we select a person to store for move, the talkback or any other screen reader, does not announce the selection status, so it would be great if you add a selected lable for those selected people for move, because when many people use the push to talk feature on a channel, the screen and the transmition status for people is refreshing automatically, during this process if you try to move someone you may move any other person by accident, so if you specify selected people this inconvenience will not happen.
    my second suggestion is also regarding to move: in addition to my first suggestion it would be great if we have select for move on user properties for each user so we can check the button and store each user one by one.
    Thanks for your attention.
    have a good day.

  3. Hello!
    I immediately apologize for my English.
    I am very happy with TeamTalkClassic and glad that you are improving it!
    I will divide this message into 3 sections.

    1.the problem is only in TeamTalkClassic_v5.6.0. and higher.
    I faced the following problem:
    when connecting to any of the servers, the program may hang for a certain time.
    It was explained to me that the program processes the channel list.
    try to improve it!
    otherwise the program freezes.

    2. another little nuisance, but already in the version for ios.
    in ios version of TeamTalk
    in the volume settings for streaming media files, there is a minimum value of 0.
    and in the computer you can set from 1 to 100.
    Please make it possible for TeamTalk for ios to set the volume of media files from 1 to 10.

    3.proposal for TeamTalk
    I also want to return to TeamTalk in general and suggest improving some of the functions for protecting accounts.

    I heard that the new version of TeamTalk has a function that allows, if the password is entered incorrectly 3 times, to block the ip address who picked the password!
    I suggest you do it differently.
    the system will not only block the ip address, but also the account in order to prevent access to it by illegal means.
    but then you can specifically find out the logins of administrators, because this information is publicly available, and specially select passwords so that their accounts are blocked and ip change through vpn.
    Yes, you can, but then try to implement one more parameter!
    Show account login:
    for everyone, the login can be seen by everyone who clicks on the account information.
    only administrators.
    only administrators will be able to see the login, and for other users the login field will be hidden.
    what I want to say!
    In the first case, when implementing the updated function, you can deliberately block accounts by brute-force password, knowing the login.
    when approaching the function, hiding the login, it will be very difficult to do.
    and the server, when entering non-existing username and password, will reject a successful login. also if, the password is correct, but the login is not.
    Thank you in advance for reading and answering!

Leave a Reply