Can't seek through certain songs

Issue description:

EDIT: Are capable of seeing the files I uploaded? They include the screenshots below, and two screen recordings, with descriptions.

Hello, I couldn’t find any other posts regarding this issue.

I do not know why, but for certain songs, I’m not allowed to seek through them. By seeking through them, I mean that anytime I press on the bar (which progress through a song), the song does not play at the point I pressed, and instead restarts completely.

I also noticed that for songs with this problem, their time length is not displayed alongside their title in the app when viewing them in a list, like in albums, playlists, or queues. See “timelength” screenshot.

I also noticed, at least for now, that all the songs with which this problem occurs, they had the file type m4a. Conversely, for songs that don’t have problem this problem, I haven’t seen any wirh the m4a file type; they have flac or mp3 or something else.

I’ve attached a screen recording, “s1”, which shows what happens when I try to seek on a song with that problem. And there’s another screen recording, “s2”, for what’s expected when seeking through a song.

Logs:

Upload description: # Description of files; “Timelength” shows a behavior noticed in songs that don’t work versus those that do not: you seen the times alongside each song for which you can seek through. “S1” is a recording that shows what happens when you seek through a song that doesn’t work (problem). “S2” is a recording that shows what happens when you seek through a song that does work (expected behavior). “I can seek through this song” contains song details. “I cannot seek through this song” contains song details. # Description of forum post: Hello, I couldn’t find any other posts regarding this issue. I do not know why, but for certain songs, I’m not allowed to seek through them. By seeking through them, I mean that anytime I press on the bar (which progress through a song), the song does not play at the point I pressed, and instead restarts completely. I also noticed that for songs with this problem, their time length is not displayed alongside their title in the app when viewing them in a list, like in albums, playlists, or queues. See “timelength” screenshot. I also noticed, at least for now, that all the songs with which this problem occurs, they had the file type m4a. Conversely, for songs that don’t have problem this problem, I haven’t seen any wirh the m4a file type; they have flac or mp3 or something else. I’ve attached a screen recording, “s1”, which shows what happens when I try to seek on a song with that problem. And there’s another screen recording, “s2”, for what’s expected when seeking through a song.

Additional information:

I processed each song through Music Brainz Picard, using default settings.

Reproduction steps:

Idk. Try seeking through a m4a file. That’s my best guess.

Media provider:

Local device

Screenshots:

Your logs does not contains the start of the media provide proper logs and upload a couple of those songs too.

Hello, thanks for the quick response. How do I submit new files? The upload button only accepts images.

And also, to provide a better log, do I simply just turn on debug mode, play some of the songs that work and don’t work, then save the log?

In the meantime, here’s a link to the additional song files and log: SendGB | Send Large Files | Free file transfer . Idk if it asks you to login, hopefully not. This link should let you download a few songs that work and a few songs that don’t, along with a log that hopefully contains the necessary info. The link is available for 7 days.

Those are invalid flac files in an m4a container.

13 - Djo - Slither.flac: *** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC

The input file is either not a FLAC file or is corrupted.  If you are
convinced it is a FLAC file, you can rerun the same command and add the
-F parameter to try and recover as much as possible from the file.

Don’t know where you get those but the tool is broken.

Damn.

Ah ok. That’s unfortunate :(. Thanks for the troubleshooting.