Bug 85 - fix progress/current song/time display at song transitions - Live365
: fix progress/current song/time display at song transitions - Live365
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: unspecified
: All All
: P2 enhancement (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-19 21:59 UTC by Blackketter Dean
Modified: 2008-09-15 14:37 UTC (History)
0 users

See Also:
Category: ---


Attachments
get time from stream metadata (968 bytes, patch)
2005-01-20 02:11 UTC, KDF
Details | Diff
reset song counter and use client->songduration in Pages.pm (1.52 KB, patch)
2005-01-22 00:45 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2003-12-19 21:59:26 UTC
 
Comment 1 Vidur Apparao 2004-06-03 17:32:12 UTC
Live365 does Shoutcast Icy protocol streams, right? If so, we should be getting
song title in the metadata. Progress isn't possible because we don't get song
duration information. It does make sense to restart the song time counter when
we get a metadata block that's different from the last, but I consider that an
enhancement.

Re-classifying this bug as an enhancement.
Comment 2 KDF 2005-01-20 02:11:10 UTC
Created attachment 258 [details]
get time from stream metadata

live 365 returns a block of xml metadata that contains songtime.  we can use
this to provide song timing info for the display, within a bit of margin.
Comment 3 KDF 2005-01-22 00:45:54 UTC
Created attachment 260 [details]
reset song counter and use client->songduration in Pages.pm

In order to display proper time from the Live365 plugin, song after song, we
need to reset the startTime when we grab the new metadata. Also, use
$client->songduration from Pages.pm so that the status panes get proper time
for streams as well as songs.
Comment 4 KDF 2005-01-27 18:50:51 UTC
commited as change 1846 to trunk
Comment 5 Chris Owens 2006-06-16 14:42:11 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.