This version primarily focus on accessibility improvements in the desktop clients. Many thanks goes to Oreonan for implementing these improvements.
Also new in this version is the ability to restore volume levels and subscriptions when a user logs out and back in again. This feature is only available for BearWare.dk Web Login since the settings are linked to a user account.
New Features
- Accessible Windows Client:
- Update window title at login with server name
- It’s now possible to use numpad keys for subscriptions shortcuts
- Status mode is now displayed for Away, Question, Streaming media file and Webcam
- Away is displayed when switching automatically to Away-mode due to inactivity, and also when manually switching to this mode
- Status mode is now displayed on receiving side (after status message)
- Status message is now displaying after a hyphen (same behavior with QT Client)
- Fixed accessible hints on channel list and files-tab
- Ctrl+G now return “Administrator” when it’s the case
- Ctrl+H/Y and Ctrl+Shift+H/Y to increase/decrease voice and media files volume of an user
- Ctrl+Shift+E to send a broadcast message
- Ctrl+Alt+B to kick and ban
- Ctrl+Shift+Alt+M to mute/unmute media files of an user
- Text messages’ timestamp now also include dates
- New TTS option to enable messages from menu actions (move users, change volume…)
- Fixed TTS message when join/left root channel
- Contributors area in About dialog
- User volume levels and subscriptions are restored on login when using BearWare.dk Web Login
- Default QT Client:
- Update window title at login with server name
- Status mode is now displayed for Away, Question, Streaming media file and Webcam
- Away is displayed when switching automatically to Away-mode due to inactivity, and also when manually switching to this mode
- Status mode is now displayed on receiving side (after status message)
- Ctrl+H/Y and Ctrl+Shift+H/Y to increase/decrease voice and media files volume of an user
- Ctrl+Shift+E to send a broadcast message
- Ctrl+Alt+B to kick and ban
- Ctrl+Shift+Alt+M to mute/unmute media files of an user
- New text message area hidden when client is not in a channel
- Shortcuts to switch tabs of main window
- Some new events (user logged in/out, user join/left a channel…)
- Contributors area in About dialog
- User volume levels and subscriptions are restored on login when using BearWare.dk Web Login
- Android client
- User volume levels and subscriptions are restored on login when using BearWare.dk Web Login
- Server
- Allow BearWare.dk Web Login without “bearware” user account (Pro-edition only)
I really enjoy the ability to save individual volumes and subscriptions, but not many people use the web login–I think because it’s pro-only and it breaks decentralization. Does it save these values to the web login system, or does it store them locally in the client? What do you think of the idea of a server update that optionally stores this information in each user account? Also, can you explain what this means?
>Allow BearWare.dk Web Login without “bearware” user account (Pro-edition only)
Also, the accessibility improvements are much appreciated; thanks, as always!
The volume/subscription settings are only stored in memory. We could store them to disk on the client but then we also need to implement a cleanup facility.
Oh, that makes sense. If my settings for other users are not saved between (my) sessions, that makes it easier to deal with data. I think the only complicating factor would be people who use the same username across multiple accounts. it’s probably bad practice to arbitrarily exclude usernames like guest, admin and user (especially since that doesn’t localize well), but there’s no way to figure out when an account is only intended to be used by one person. Maybe “save subscription and volume states” could be a checkbox when saving server info in future versions? You wouldn’t want to check this on a server with a shared guest account, but you could choose the option on an account-based server. I can see why this was only done for web logins though.
The server doesn’t know about volume settings. Volume settings are only modified on the client side.
Also the client doesn’t know what user-rights other users have. The client only know about its own user account. Therefore it has no way of knowing if someone else’s user account is shared.
Failed to initialize video capture device
Hi Team,
We are currently using TeamTalk v5.6. Recently, we are getting the following error message while using video chat/call
“Failed to initialize video capture device”
We didn’t face this issue in previous version v5.5. Can you please help us to resolve the issue?
Thanks in advance.
Respected,
There is echo/noise in the audio conversation done in a chat room consisting of 3 to 4 members. We have already tried to resolve by using the option “Set Sound device effects”. But no luck, issue still exists.
Thanks,
Please try the new echo canceller in TeamTalk v5.7 pre-release