You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched searched open and closed issues for duplicates.
I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Overall summary
This is pretty much exactly #6908, except that this is a supported signal desktop build. The issue has been present since quite some time but I could never bothered to report this until now. This is a minor issue as the effect is purely cosmetic and does not actually affect how a voice message is played.
Steps to reproduce
Receive any voice message from a user.
Play the voice message.
Expected result
The timer and progress bar matches the length of the voice message exactly.
Actual result
The progress bar and timer reaches its end too soon. Any voice message is pretty much always a couple of seconds longer than the UI expects. I think this scales with length, the longer the voice message, the higher the inaccuracy.
With a 2 minutes and 18 seconds long voice message I got ~11 seconds of inaccuracy.
Voice message as displayed in signal desktop:
The very same voice message as displayed on my linked Android phone:
The sender of the voice message also uses Android.
Screenshots
No response
Signal version
7.26.0 production
Operating system
Arch Linux
Version of Signal on your phone
7.17.6 (Android)
Link to debug log
In app.log I see the following events spammed after the voice message exceeds the expected length:
Using a supported version?
Overall summary
This is pretty much exactly #6908, except that this is a supported signal desktop build. The issue has been present since quite some time but I could never bothered to report this until now. This is a minor issue as the effect is purely cosmetic and does not actually affect how a voice message is played.
Steps to reproduce
Expected result
The timer and progress bar matches the length of the voice message exactly.
Actual result
The progress bar and timer reaches its end too soon. Any voice message is pretty much always a couple of seconds longer than the UI expects. I think this scales with length, the longer the voice message, the higher the inaccuracy.
With a 2 minutes and 18 seconds long voice message I got ~11 seconds of inaccuracy.
Voice message as displayed in signal desktop:
The very same voice message as displayed on my linked Android phone:
The sender of the voice message also uses Android.
Screenshots
No response
Signal version
7.26.0 production
Operating system
Arch Linux
Version of Signal on your phone
7.17.6 (Android)
Link to debug log
In app.log I see the following events spammed after the voice message exceeds the expected length:
The text was updated successfully, but these errors were encountered: