TeamTalk v5.8.3 is now available in the Download-section. iOS and Android clients are still awaiting final beta-testing and approval from App Stores.
If you missed out of the beta-testing then notice there’s a new feature in the TeamTalk client to be notified about new beta-releases. You can read more about it here.
Many thanks to Corentin Bacqué-Cazenave and Beqa Gozalishvili for helping out!
Please write feedback in Discussions on GitHub, so others can benefit as well.
New Features in TeamTalk v5.8.3
Again there’s a long list of new features. Especially for the TeamTalk Qt client which again has a strong focus on accessibility:
- Accessible Windows Client
- Fixed bug where lowering user-timeout in Server Properties would cause a disconnect
- Default Qt Client
- Dark mode enabled on Windows if selected Personalisation Colour is Dark
- Menu item to enable/disable all sound events
- “Enable Text-To-Speech events” has moved to a new submenu named “Notifications” in “Me” menu
- Text-to-speech event when a remote user is typing in private chat
- Status message is triggered if unable to transmit
- Navigating with arrow keys in channels tree now includes entire item text in Text-To-Speech message on macOS
- Alert when characters limit exceeded for channel and private chat
- Client-menu now has “Sound Configuration”-submenu to quickly change sound devices
- Setup keyboard shortcut in Preferences dialog to reinitialize sound devices
- Russian translation updated
- More specific error messages are displayed when issuing server commands
- Server name used in file name when recording root channel conversation to disk
- Using close button or Alt+F4 shortcut to close main window will now close all windows on Linux and Windows
- Default values for channel and private messages sent applied when switching sounds pack in preferences
- Fixed issue where user account’s initial channel was not joined if channel was hidden
- Fixed “Cancel” button not working in “New Client Instance” dialog
- Fixed AltGr being treated as Ctrl+Alt on Windows
- Fixed Cmd+Q not working in non-English translations on macOS
- Fixed “Disconnected from server” TTS event emitted repeatedly when connection to server is lost
- Fixed nickname change for servers using BearWare account
- Fixed bug when client asked for apply settings even if .tt file doesn’t contain settings
- Fixed bug where lowering user-timeout in Server Properties would cause a disconnect
- Android Client
- Accessible hint for gender
- Notification on text limit exceeded
- Ability to kick and ban from channel when operator
- Fixed media buttons for voice transmission on Android 12
- Fixed bug where lowering user-timeout in Server Properties would cause a disconnect
- iOS Client
- Sound shared with other apps so iTeamTalk can run in background
- Ability to select stereo inputs in Preferences
- Notification on text limit exceeded
- Fixed overlapped TX button on some devices
- Fixed overlapped send message fields on some devices
- Fixed bug where lowering user-timeout in Server Properties would cause a disconnect
- Server
- Fixed issue where text messages exceeding limit would become blank
Hello! In the latest version for Mac, when you press command 4 to listen to yourself, the client closes.
Hm, on my Mac (with Monterey) I don’t see this issue. Could it be related to the translation file? Do you use English?
— Bjoern
no, i use spanish.
Is it an Apple M1?
intel wid latest version MacOs 12.2.
Ah, I was running on macOS 12.1 and didn’t see the issue. Now I upgraded to 12.2 and also sees the crash issue.
I’ve fixed it for next release (v5.9).
https://github.com/BearWare/TeamTalk5/commit/36045d4adf04522e2b2caf22fb06ed5a9bc86c20
— Bjoern
Enable “beta software updates” to try out the latest client with the issue fixed.
yes! Working fine