Subsonic Forum

Hi. New user struggling with an installation on Ubuntu Server 10.04. My desktop is Ubuntu 10.04 w/ Gnome.
For the most part Subsonic is trouble free. But I noticed the other day that it cuts off the last second or so af a file. My music is stored on the server as flacs. I play on another PC using webplayer, jwplayer. I have seen no errors in the logs, It does this with all files, you just can't tell with some music because of fades. It does not do this if I use an external player. I use Subsonic v 4.6 build 2585 and have upgraded the jwplayer to the latest, 5.8.2011. Nothing seems to help. My server has 1.5 gig of ram and usually hass > 1 gig free.
Does anyone have any experience with this problem or troubleshooting tips?

Hi mister Zomby !

I've got the same problem with subsonic-4.6 (WAR version deployed with tomcat6) on Ubuntu 10.04 with all players like iSub (app fo iPhone) or JWplayer. All my songs stop a couple of seconds before the end. You are the first having this issue since i posted here : viewtopic.php?f=4&t=8443

The only solution for me is to rollback to V4.5 and all work fine, there is no answer to this problem...

Thanks for the info.
Rather than backtrack I'll give the developer a chance to fix this.

NOTE to Sindre: I will donate once this works.

This does appear to a OS related problem but to give the devs a chance can you confirm if it is only flacs that are a problem or do other audio files, specifically mp3s, cut off early.
It does seem to be connected with

4.6beta2 change log wrote:Bugfix: Don't estimate content-length for web players.

I wonder if that regression did not get updated in the 4.6 Final for your version

Does it with Mp3s as well.

It cuts off video as well, afaict.

The REST api only gives us time in whole seconds, which is generically Bad - - if we have to depend on knowing the duration of the media to be able to end it and move on to the next thing, then we're only getting a round number, that is not accurate.

eblade wrote:It cuts off video as well, afaict.

The REST api only gives us time in whole seconds, which is generically Bad - - if we have to depend on knowing the duration of the media to be able to end it and move on to the next thing, then we're only getting a round number, that is not accurate.

Seems like you might be on to something. I inserted a few millaseconds to the front of a few flac files to make them whole seconds.
Now they work fine.

Is this fixable?

It sounds like JWPlayer is probably doing the same thing that I do on my webOS player, since I don't get a function call telling me specifically when the thing is done playing, I check it's status regularly, and if it's within one-second of completion, i move on. I'm planning on making it start a 1-second timer before moving on, and having that trigger the moment it gets to the 1-second-left mark, but that's a really hacky workaround, if i could just get a more accurate duration, that'd make me happier.

No more comments?
I guess I need to find an alternative webplayer.