0
Since entering in song lengths is too tedious, most of the songs do not have this entered into the database. Until ID3 tag reading is added, most users will not spend the time to enter these in manually.
When on the album and artists pages, the JW player calculates each song name correctly. This allows users to scroll through the time on each song. However when playing songs on the playlist page, playlist popout, or song page... the JW player is not calculating the song length. It stays at 00:00. This make the player unable to search through the song. Can this be fixed?
Thanks Germi... just trying to help you make MC as solid as possible.
When on the album and artists pages, the JW player calculates each song name correctly. This allows users to scroll through the time on each song. However when playing songs on the playlist page, playlist popout, or song page... the JW player is not calculating the song length. It stays at 00:00. This make the player unable to search through the song. Can this be fixed?
Thanks Germi... just trying to help you make MC as solid as possible.
Responses (13)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
0damn.. once more I forgot about this post.
please try this (for the playlist)
open /components/com_muscol/views/playlist/view.feed.php
on line 77 you see this:
$item->duration = $song->length;
change it for:
if($song->length) $item->duration = $song->length;
does this solve the issue on the playlist page? -
Accepted Answer
-
Accepted Answer
0hello!
in this case is a different file. I tell you what to do, but this will be added on a jwplayer update that we will publish very soon:
on /plugins/muscolplayers/jwplayer.php
add this on line 228:
if(!$song->length) $duration_comment = "//";
and a few lines below, where you see this:
duration: '".$song->length."',
replace it for:
".$duration_comment."duration: '".$song->length."', -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
0Hi (Hola)Germi
yes, i think so.
plg_search_albums_2.2.0_1.6.zip 2.2.0
mod_muscol_recently_added_artists_1.1.0_1.6.zip 1.0.0
plg_showalbum_1.1.0_1.6.zip 1.1.0
com_muscol_upgrade_220_to_221_1.6_NOT_AUTOINSTALL.zip 2.2.1
mod_muscol_top_viewed_1.5.0_1.6.zip 1.5.0
plg_jwplayer_2.2.2_1.6.zip 2.2.2
mod_muscol_jwplayer_2.2.2_1.6.zip 2.2.2
com_muscol_2.2.1_community_pro_1.6.zip 2.2.1
mod_muscol_featured_albums_2.0.0_1.6.zip 2.0.0
plg_myalbums_cb_2.2.0_1.6.zip 1.0.0
mod_muscol_featured_artists_2.2.0_1.6.zip 2.2.0
mod_muscol_letterbar_2.1.0_1.6.zip 2.1.0
mod_muscol_recently_added_2.0.0_1.6.zip 2.0.0
mod_muscol_recently_added_songs_2.0.0_1.6.zip 2.0.0
mod_muscol_search_bars_2.2.0_1.6.zip 2.0.0
mod_muscol_statistics_2.2.0_1.6.zip 2.2.0
mod_muscol_statistics_individual_2.1.1_1.6.zip 2.1.1
mod_muscol_top_rated_albums_2.2.0_1.6.zip 2.2.0
The problem is that player files duration does not match server duration.
For ex : 01 01 35 on server become 01 01 43 on player. :unsure:
Did you receveid the acces logins ?
If yes would you have a lokk please ?? -
Accepted Answer
0ok I understand what you say, but actually that's not what we discussed before on this thread.
what you say is JWplayer behavior, is nothing I can do about it really. it's the way the player automatically calculates the lenght of the file based on the size of it. I guess it can be a bit difference if the bit rate is variable on file encoding...
but anyway taht should not affect the playback of the file. does it?
classic!!! 
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »