Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jamstash player thinks songs are longer than they are #223

Open
khogeland opened this issue Oct 23, 2015 · 6 comments
Open

Jamstash player thinks songs are longer than they are #223

khogeland opened this issue Oct 23, 2015 · 6 comments

Comments

@khogeland
Copy link

I've seen this happen a few times on different albums, so I don't think it's a problem with my files. The Subsonic web interface plays everything correctly, and Jamstash does display the times correct in track listing and in the playback queue, but in the player they are sometimes arbitrarily longer:

https://i.imgur.com/6Co2TWv.png

When the player hits the actual time where the songs ends, it will just hang until I manually click next.

@Hyzual
Copy link
Contributor

Hyzual commented Oct 26, 2015

Hi, thanks for reporting this issue.

I personally haven't experienced this issue so I'm not sure I can reproduce it easily. Do you have transcoding enabled on subsonic ? any special settings ?

I should tell you also that I don't have as much time to work on Jamstash as I used to, so this might take a while to be solved :-/

@khogeland
Copy link
Author

I'm transcoding to v0, no special settings to speak of. Are you somehow getting the time differently in the library interface than you are in the player? I don't see how the time could be correct everywhere except the player.

@Hyzual
Copy link
Contributor

Hyzual commented Oct 27, 2015

Actually yes, in the library interface we display the duration of the song as computed by Subsonic. In the player interface, I suspect the player we use (jPlayer) computes its own duration. Maybe there is a difference in the actual calculation somewhere. I was thinking that this might be due to transcoding...
Maybe this is a bug with jPlayer actually, I'll have to check that out

@khogeland
Copy link
Author

Looking at the jPlayer API, a possible workaround might be to register a listener on $.jPlayer.event.timeupdate, and load the next track when it hits the actual max duration. That shouldn't break anything when it's working properly, but prevents it from getting stuck when jPlayer gets the wrong duration.

@khogeland
Copy link
Author

It appears this is actually a bug that occurs when Subsonic transcodes FLAC or WAV files: http://sourceforge.net/p/subsonic/bugs/121/

But it still couldn't hurt to have a failsafe, since the bug has not yet been patched on their end :~)

@Etuldan
Copy link

Etuldan commented Nov 2, 2015

For FLAC files, maybe you could try this : #169 (comment) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants