TeamTalk v5.19 is now ready for download. Again the TeamTalk 5 project contributors have been busy adding new features and bug fixes. Corentin Bacqué-Cazenave has been busy adding new features to the desktop client and Amir Mahdi Fard has been busy with the Android client.
New Features and Bug Fixes
It is always possible to see then latest changes to the TeamTalk project in this ChangeLog. Give feedback in Discussions if you discover issues.
Here’s the list of new features and bug fixes:
- Default Qt Client
- Ctrl+Shift+C to copy only message content in chat list
- Ctrl+Alt+Shift+C to copy all chat list history
- Ctrl+Shift+R to generate tt:// URL for current channel
- Bitrate for OPUS is limited to 6-510 in Channel dialog
- Status message shown in “Preferences” dialog
- Ability to define status message for each server
- Option to ask confirmation on exit
- Fixed “Speak Client Statistics”, “Enable/Disable Text-To-Speech Events”, “Speak User/Channel Info” and “Speak Channel Statistics” availability if TTS events are only sent using push notification
- Fixed idle status message not being restored after network reconnection
- Fixed chat history name not retranslated on language change
- Fixed URL generation cancellation
- Fixed crash issue in “Connect to a Server” dialog on macOS 15.1
- Fixed file transfer speed display
- Windows and macOS updated to Qt 6.10.0 beta2
- Android Client
- Added “Online Users” activity to display users logged on to the server
- Added a new option to prevent talking users from moving to the top of users list
- Added the ability to leave channels
- Added the ability to set status messages
- Added the ability to control user’s transmissions
- Option to automatically join root channel in preferences
- Announce who is channel operator
- Announce who is selected for moving to other channel
- Ability to play sound when voice activation is toggled
- Ability to play sound for intercept subscription toggled
- Ability to use Text-To-Speech to announce transmission changes
- Ability to use Text-To-Speech to announce subscription changes
- Fixed bug where user’s status message is not announced when away
- Minimum supported is now Android v7.0 (Nougat)
- iOS Client
- Use VoiceOver to announce TTS events for screen reader users
- Server
- Fixed security vulnerability where users could accidentally become channel operators if a channel ID was reused
Hello, this is my first comment here. I want to mention a strange behavior I’ve been experiencing since version 5.19.0 beta, and now in the stable release. When I open the microphone, there’s a delay in the sound that indicates the mic has been activated. This wasn’t the case in previous versions. Now, when I press the voice activation shortcut, I need to wait about one second — or at worst, two seconds — before I hear the mic activation sound. I did a simple test to check whether this delay affects all events or just the microphone, and it seems everything else is working fine, except for the mic activation. I’m not sure if I’m the only one experiencing this, or if others have noticed it too. Also, I have another small issue — or maybe just a side note. Was the push-to-talk sound changed recently? From what I’ve noticed, it seems different. Personally, I prefer the old sound. I’ll double-check this later, and if it really has changed, I might try to replace it with the previous one. Thanks anyway. typed by AI
go to your settings, sound system tab, and make sure everything has been configgered properly there, and sound events tab. the playback mode should be set to default or one by one, sometimes it will have a little bit of delay in this case.
Dear [Developer’s Greetings.
I am Md.
Abul Kalam,
writing from Bangladesh,
and I’d like to share some important suggestions regarding the TeamTalk application,
which I deeply value for its commitment to accessibility—especially for blind and visually impaired users.
Currently,
TeamTalk provides excellent functionality through desktop systems,
including the ability to control servers via computer.
However,
one major challenge we face is the inability to control our desired servers using Android mobile devices.
For many users in our community,
mobile access is more frequent and convenient,
making this a crucial feature need.
Priority Feature Request:
– Android-Based Server Control: Enable full control over TeamTalk servers directly from Android devices.
This will significantly improve usability and independence for blind users who rely on mobile platforms.
Additional Android Functionality Suggestions:
– YouTube Video Streaming: Add support to stream videos from YouTube directly through the app.
– Local Media Streaming: Allow users to play or stream audio/video files from their device’s file manager,
supporting formats such as mp3,
mp4,
wav,
etc.
– Playback Controls: Introduce accessible buttons for:
– Play / Pause
– Next / Previous
– Seekbar slider
– Smooth transitions (segue) between media files
Accessibility & Usability Improvements:
– Gesture-Based Navigation: Make navigation easier for screen reader users using intuitive gestures.
– High-Contrast & Large Text Themes: Improve visibility for low-vision users.
– Interactive Help Assistant: Include a guided assistant or audio help for feature exploration and troubleshooting.
– Push Notifications: Add customizable,
accessible alerts for server activity, File Sharing: Easily and quickly share files among group members,
facilitating convenient information and document exchange.
– Integrated Help Assistant: Include a built-in audio guide or chatbot that assists blind users in navigating features. Screen Sharing: Share applications or your entire screen,
enabling participants to view and engage with important content together. I believe these enhancements will empower users and make TeamTalk even more inclusive and powerful.
I’d greatly appreciate your consideration and would be happy to offer further feedback or help test these features.
Warm regards,
Abul Kalam
Hello,
With version 5.17, I can still stream MP3 files on MacOS, for example, those created by Suno.com (COMMAND + S). This was no longer possible in version 5.18, but it would start playing but would mute the stream after 2 seconds. Installing version 5.17 fixes the problem. However, WAV files can be streamed without any problems in 5.18 and 5.19, but I find it cumbersome to always have to do “ffmpeg -i “file.mp3” “file.wav” first.
The tt5srv.log only lists status: 2048. The status msg contains no value. A 5.19 user on Windows 11 can stream MP3s, but the status is changed to 2048 and the status msg to “file.mp3”.
Even when transferring the WAV file to MacOS, the status msg remains empty.
Running on the server for Ubuntu24: 5.19.0.5170
Running on MacOS Tahoe: same version number. Created with Qt 6.10.0 on August 6, 2025, at 8:32 AM.
Below is (c) 2005 – 2021, Not 2025
Greetings
David Losse
I think we should have the ability to totally control user tarnsmissions as admins, even if we are not inside of the channel. For example, voice, video permissions, etc. I also wanted to report that if you are not a channel operator in a room, but you do have the ability to control channels, if you try to enable or disable someone’s tranmission, you have problems, when using the keybord commands. For example, sometimes it will disable all the transmission setting when we only want to disable video, or sometimes it will not do anything at all.
I think the server should be set to ware we as admins and users with the ability to control channels, modify all the channels, that the server should allow us to control transmissions from any channel, in any area.
It would also be useful if we want to control a classroom channel but we are in another room. Lets say that I want to enable voice and video in a public room, while I am in the private room. As of now this is impossible to do. The only way it will work is if you go to the channel itself. It should be possible to control that from anyware.
I should clarify that I am talking about classroom and channel transmissions that I believe that we should make them be able to be controled from anyware. It is useful for many different reasons.
Hello everyone. First of all, I want to thank the TeamTalk team for their great work. I am Damián, writing to you from Argentina.
I have many suggestions for the TeamTalk Android version, but let’s start with the first one:
1. Now that screen readers work with gestures, my suggestion is that, to join channels, you can either double-tap the channel or swipe up or down (depending on the screen reader). By default, double-tapping should join the channel, and swiping should show options like “move here,” “edit channel,” and so on. In summary, it should work like when they removed the delete button and now swiping up shows “edit server.” So, by default, “join” should appear or the channel can be expanded (if the default action is to join).
2. It should notify you when a user enters or leaves another channel that you are not in.
3. To send a broadcast message, it should be faster; the option should appear directly in the chat because sending a broadcast message is a slow process.
4. Just like on the computer, if possible, it should allow microphone switching on Android. To explain: most people know that on Android, when we connect headphones to avoid feedback or echo, even though the headphones have their own microphone, a slight echo is generated. For users without headphones, the experience is very poor during interactions. Noise reduction also lowers audio quality significantly, and TeamTalk is an application known for its high audio quality. Furthermore, some external apps that were used before no longer work on Android 12 or higher. So, I don’t know if there’s a way within the app itself to switch and use the device’s microphone directly.
5. It should allow hiding the voice activation level, just like on the PC.
Thank you. It would be great if some of these suggestions could be implemented.
Best regards to the TeamTalk team and the entire community.
Hello guys, I’m here again.
I would like to ask for the gender error to be fixed. When it defaults to masculine and it is a woman, it changes to feminine, but then it switches back to masculine, which is quite frustrating.
I hope this correction can be implemented in the Android client.
Regards and thank you.