# Sound files end early when playback speed \> 1.0. "Time elapsed" exceeds the shown length of the audio file

**URL:** <http://support.symfonium.app/t/sound-files-end-early-when-playback-speed-1-0-time-elapsed-exceeds-the-shown-length-of-the-audio-file/14886>\
**Category:** Support\
**Tags:** fixed\
**Created:** [August 31, 2026, 3:04am UTC](http://support.symfonium.app/t/sound-files-end-early-when-playback-speed-1-0-time-elapsed-exceeds-the-shown-length-of-the-audio-file/14886 "2026-08-31T03:04:47Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Celorien](http://support.symfonium.app/user_avatar/support.symfonium.app/celorien/32/9277_2.png) [@Celorien](http://support.symfonium.app/u/Celorien)\
**Post date:** [August 31, 2026, 7:49pm UTC](http://support.symfonium.app/t/sound-files-end-early-when-playback-speed-1-0-time-elapsed-exceeds-the-shown-length-of-the-audio-file/14886/3 "2026-08-31T19:49:24Z")

</div>

I had posted about this earlier on a [similar topic](https://support.symfonium.app/t/delay-when-changing-playback-speed-and-pitch/14615/2) but will follow-up here, since this topic is more directly related.

For me, on v15.1.0B1, the `player.position` now reports the correct value for the _ **current track** _ when changing playback speeds. But there is still an issue when transitioning _ **to the next track** _. Behavior is technically the same for playing fast vs slow, but _only playing slow_ causes an actual playback issue.

Actual audio playback begins and ends correctly for me in both cases. (Though I had no issue with it cutting off in the last version either.)

* * *

**Log:** `Celorien_Speed30`

1. When Playback Speed is _greater than one_ (i.e. playing fast), the `player.position` will briefly jump backwards based on the actual time elapsed. Playback then continues to the next track without issue.

![20260831_112714](http://support.symfonium.app/uploads/default/original/2X/2/2c08b76abbe73905fe0a1f77676b9fd505b76006.gif)

Seeked directly to 2:38 before starting playback. Thus 30s remaining at 3x speed means actual elapsed time is 10s. At end of track, `player.position` briefly jumped to 2:47, which is consistent with the +10s elapsed time.

Next track correctly begins at 0:00.

* * *

**Log:** `Celorien_Speed05`

1. When Playback Speed is _less than one_ (i.e. playing slow), the `player.position` _for the next track_ does not start at 0:00.

ISSUE: If the player does not reach the position of `player.position` within 20s (of real time elapsed), app will report “Unable to play media, make sure your device supports it” and skip to the next track.

(I can’t get the toast to show up for a screenshot but I know I’ve seen it.)

Initial `player.position` is based on actual elapsed time, just like above. Same track, seeked directly to 2:38 before starting playback. There are 30s remaining at 0.5x speed, so actual time elapsed is 45s.

Next track’s starting position was **displayed** as 0:15. (Actual audio correctly started from 0:00.) Playback is abruptly cut off and skips to the next track after an actual elapsed time of 20s.

NOTE: if the starting position is small enough to be reached (i.e. less than 0:10), playback will continue without issue.

![20260831_125557](http://support.symfonium.app/uploads/default/original/2X/c/c73bbd5fbe46f3104c577a45c63bfe98838a85ac.gif)

I started at 2:08 in this GIF so the numbers are different. Just showing the starting offset.

---

_[View the full topic](http://support.symfonium.app/t/sound-files-end-early-when-playback-speed-1-0-time-elapsed-exceeds-the-shown-length-of-the-audio-file/14886)._