Skipping songs takes about a second from cached files. A regression seems to have happened as this was not present in the previous version
Upload description: shark0151
Start a Playlist.
Skip song.
Jellyfin
2025-04-23 00:19:44.805 Verbose PlaybackController Next
2025-04-23 00:19:45.014 Verbose ExoPlayer/2 isPlaying [eventTime=206.73, mediaPos=0.00, window=0, period=0, true]
That’s 209 ms very far from a second.
It varies actually. I just counted 2-3 seconds now.
And do the logs say it actually started playing? Because, yeah the song changed, but I get the loading spinner for however long before it starts playing
I think isPlaying = true is quite indicative 
Please provide logs showing those 3 seconds.
Should be another one uploaded.
Between Blew and About a girl.
I pressed next at about:
2025-04-23 15:36:24.144 Verbose/PlaybackController: Next
I think it starts at:
2025-04-23 15:36:29.358 Verbose/ExoPlayer/5: isPlaying
(i think)
In between it looks like it’s trying to reach my server but failed. I’m not on my home network so that’s expected
Ok can you try to disable the transcoding engine in settings to confirm this fix this ?
I have tried a permutation of all transcoder/decoder settings with no clear improvement.
Cleared all caches.
Redownloaded all songs.
I think transcoding was actually disabled in the first place.
The moment I connect to the home network it works fine. But when it can’t connect, it looks like it still tries and waits for a response even though it correctly determines that it’s offline and the song is cached.
Also seems that it ignores the wifi only setting for jellyfin since it tries to connect anyway
I know. I just said that i tried every setting on that page on and off. But fine, i uploaded another - transcoding definitely off and freshly restarted.
It happened when switching to the song ‘Running in the night’
When you’ll have done support for millions users over 13 years you’ll know that between what users says and what they actually do there’s a dozens of galaxies 
Anyway seems that option is actually also ignored in current release. That would explain the other issue and the delay.
Should be fixed in next release then.
Haha, as a fellow dev, I understand your pain 
And thank you
