I got around to finally adding some music on my site to test the streaming capabilities and I am running into the exact same problem I grabbed all the durations and put them in muscol so they show up correctly in the album page, but I am guessing muscol only uses that info to display text on the album page, and not actually in the playlist xspf. When I play the files via the play button so that it plays within the jw player plugin, it does not play the full song. The duration it shows in the player is shorter than the actual duration of the mp3 and so it cuts it off at that point. Typically around the last 10% or so of the song gets cut off.

You can see this issue at:

threechimps.com/index.php?option=com_mus...;view=album&id=3

temporary login:

username: temp
password: temp

well, you're right, the duration is not passed on the playlsit... but I think this should be a problem... anyway, let me a few time to add this info to the playlist, and see if it solves the problem.

I hope it resolves it. If it doesn't, not sure what else would cause this behavior. I will wait patiently for an update. Thanks for the help.

well I've been looking around on JW Player forums and still couldn't find nothing about this (maybe you can give it a try, too

to include the duration on the playlist XSPF file, open
/components/com_muscol/views/album/view.feed.php

and on line 43 you should actually find this commented:

$item->duration = $song->length;

just uncomment it.

but I don't think this will make a difference...

just a couple thoughts: have you tried it will all browsers? do you always get the problem?

also.. what is the BIT RATE of the problematic songs? I readed somewhere that jwplayer does not like much some "strange" bit rates...

also you can try this (still no clue if it will work.. this is a strange problem.)

on helpers/xspf.php on line 59 add this:

Thank you for the update. I will give it a try and report what I find.

The bug exists on the jw player after 4.3. They are aware of the bug. Unfortunately it affects mp3 playback more so than video, and they have been quick to point out that the jw player is designed to be a video player. Using it as an audio player is just a side feature. They have been far slower at fixing anything that is related to using it as an audio player, so who knows how long it will take. Basically it is a problem with the player not being able to correctly determine the songs length. This can be caused by a lot of things such as bad headers or mp3s sampled at anything other than 44.1kHz, such as 48kHz. The solutions they give were to include the song length in the xspf playlist, either hard coding the song length or using something to read the file to automatically get it like the getid3 library. This fixed the issue the majority of the time. The other option was to downgrade to the 4.3 player. Downgrading to the 4.3 player doesn't always fix the issue as well as one then loses quite a bit of features that were added since, like some bug fixes, additional api calls and some skin and mod support.

If you do a search for "duration" on their forums you will see all the problems people have been having with it. Here is one of the topics www.longtailvideo.com/support/forum/Setu...mp3-duration-problem You may have to go back a few pages in the search results as this bug has been there for more than a year now.

Also something I found interesting while reading up on this subject. In the 4.x player, if the length is included in the xspf file it will use the length. If the field is empty, then it will not set it to 0:00 but try to attempt to get the duration itself. Looks like it might be backwards compatible with allowing for both defined duration fields as well as undefined duration fields for those that don't want to enter a song duration. www.longtailvideo.com/support/forum/Bug-...-differently-than-v4


Yes it happens on all browsers. The durations are random though. Sometimes it guesses the right duration other times it will be off and the amount it can be off can change. Most songs are 44.1kHz. They are all ripped or tagged with jaikoz, picard, media monkey, or the godfather. Also this issue does not happen in other streaming programs I have used on the same files. Those other programs include the duration in the xspf though which is one of the few things different that could affect this.

EDITED to add additional notes and details.