BearWare
Qt: Delay of sound events when master volume has keyboard focus
Description
Using TeamTalk v5.19.0.5164 with screen-reader optimisations enabled. There is a strange bug in TeamTalk v5.18 and higher that delays the triggering of sound events and program actions under certain circumstances.
As a workaround you can set the playback mode for sound events to one-by-one or overlapping, then this problem no longer occurs. The problem also appears to occur in other situations, for example when other users switch between rooms while master volume has focus, but I have not been able to reproduce this on my system. If the keyboard focus is in the channel list, everything also works normally.
Application
- [x] qtTeamTalk
- [ ] TeamTalkAndroid
- [ ] iTeamTalk
- [ ] TeamTalkClassic
- [ ] TeamTalkServer
Platform
- [x] Windows
- [ ] macOS
- [ ] Android
- [ ] iOS
- [ ] Linux
Expected behavior
Sound and program events should play immediately upon request, no matter where the keyboard focus is.
Actual behavior
As described above, TeamTalk sometimes delays playing of sound events, mostly after some inactivity or when switching to another program window.
Steps to reproduce problem
- In the settings, the playback mode for sound events must be set to default.
- Set voice transmission mode to voice activation and the voice activation level to 0% (continuous transmission).
- During a TeamTalk connection, set the keyboard focus to the master volume slider in the main program window.
- Turn off voice activation with CTRL+Shift+A and remain inactive for a few minutes. It also can help to switch to another program window or just minimize TeamTalk while being inactive.
- When voice transmission is turned back on, the sound events are only played after a delay of several seconds.
Hey @schulle4u! This is a problem in Qt. As I see it, it can't be fixed from our end. We have to wait until they fix the problem in Qt itself. Regarding the focus on master volume, I don't know. But regarding another window or being AFK, that's likely a Qt problem.
@schulle4u The thing is, the default mode uses Qt for sound playback, while all the others use SDK functions.