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
Since switching to Android 14, I see inconsistency with "playtime tracking" (lacking a better word) in DSub2000, as well as the original upstream.
With many (if not most) audio files the audio will play fine but the playtime bar will jump back and forth between the last few seconds. So if I play an audio file, the playtime bar will jump between 0:01-0:02. I can still use the playtime bar to skip forward, but the same thing will happen then, e.g. jumping between 0:41-0:42.
This gets especially annoying with long audio files such as audio books or podcasts, since stopping and resuming playback will resume at the currently shown playtime. So I could be listening to a podcast for 48 minutes and on pause and resume the playback will start again at 0:01 (or at whatever time I previously skipped to).
The text was updated successfully, but these errors were encountered:
Could be, haven't touched the server in a while :D but I don't think that this is the case, since it worked flawless on my old android 11 phone before switching recently. Will check though, thanks @khers
I observed some time jumping when DSub switches from streaming to the cached copy. Can you check whether the issue is actually, that your files are downloaded again?
Since switching to Android 14, I see inconsistency with "playtime tracking" (lacking a better word) in DSub2000, as well as the original upstream.
With many (if not most) audio files the audio will play fine but the playtime bar will jump back and forth between the last few seconds. So if I play an audio file, the playtime bar will jump between 0:01-0:02. I can still use the playtime bar to skip forward, but the same thing will happen then, e.g. jumping between 0:41-0:42.
This gets especially annoying with long audio files such as audio books or podcasts, since stopping and resuming playback will resume at the currently shown playtime. So I could be listening to a podcast for 48 minutes and on pause and resume the playback will start again at 0:01 (or at whatever time I previously skipped to).
The text was updated successfully, but these errors were encountered: