Playlist info for sc_trans

[idobi]

Is there a way to read what line in a playlist sc_trans is currently playing? Something similar to ices.cue file for ices?

[DrO]

not knowing quite what ices.cue returns, though if you use the ajax api then there is 'GetStatus' (in the current sc_trans install -> sc_trans_ajax_api.txt - section 2.2) which will return the current and next track in the xml response returned. other than that there isn't any simple way to get the current / next track from sc_trans.

in the current sc_serv2 you can use 'currentsong' / 'nextsong' via the admin interface to get just plain data or there is the 'viewxml' action which returns something similar to 'GetStatus' but based on the information sc_serv2 has pulled from the metadata sc_trans has sent to it. see sc_serv2.txt - section 5.1 for more details on those options.

-daz

[idobi]

ices.cue returns among other things, current file playing, song length, # seconds song has played, artist, title, PID, and (what i'm interested in) line number of the playlist file - ie. the current song playing is the 755th line of the playlist file.

Looks like I'll have to read the last playing songs and parse the playlist file to get the info.

After a week of running the new sc_serv and sc_trans, I gives a big thumbs up for sc_trans. As for Shoutcast 2, it is nowhere near ready for prime time. I've found several ways to crash it both from the streaming and client side, and that's just unacceptable. I currently have a shoutcast 1 server that's been up 182 days. I'd expect the transcoder to crash more than the server.

[xerano]

is it possible to refresh on the fly the content of the music directory?

so i add some tracks but dont turn off sc_trans to re-read the playlist



./home/shoutcast/sc_trans/music/*.mp3

[idobi]

is it possible to refresh on the fly the content of the music directory?

so i add some tracks but dont turn off sc_trans to re-read the playlist



./home/shoutcast/sc_trans/music/*.mp3

Yeah. It's in the docs. You can send a kill -SIGUSR1 <PID> in the terminal or issue "loadplaylist" from the web/browser.

[DrO]

ices.cue returns among other things, current file playing, song length, # seconds song has played, artist, title, PID, and (what i'm interested in) line number of the playlist file - ie. the current song playing is the 755th line of the playlist file.

i can log it to look into trying to add in some more information to the getstatus response about the currently playing file though cannot say when / if that will definitely happen at the moment as sc_serv is the main priority (as per following part of my post) though i've seen this request pop-up a few times so would make sense to add something i guess to GetStatus().

After a week of running the new sc_serv and sc_trans, I gives a big thumbs up for sc_trans. As for Shoutcast 2, it is nowhere near ready for prime time. I've found several ways to crash it both from the streaming and client side, and that's just unacceptable.

i'm all ears especially if you have reproduceable ways to crash the server (other than via the Winamp 5.5x connection crash - i probably should send you an interim build to see if it helps things out) as i'd like to get as many stability / compatibility issues resolved with the newer sc_serv2 for the next drop as i can.

-daz

[idobi]

i'm all ears especially if you have reproduceable ways to crash the server (other than via the Winamp 5.5x connection crash - i probably should send you an interim build to see if it helps things out) as i'd like to get as many stability / compatibility issues resolved with the newer sc_serv2 for the next drop as i can.

-daz

I'll do more testing this weekend and document my process better. I was concentrating more on sc_trans and moving the station to new servers for the new year.

I'll post info next week.

[DrO]

that's fine - which OS version of the server would you prefer for testing (will make more sense to test something current than the public drop with the fixes that are already in it) ? there's also a linux64 version if you're running on that.

-daz

[idobi]

I'm running both 32 and 64bit linux servers. Source machine is 64. Relays boxes are 32bit.

[DrO]

rightio, will send you a version of each tomorrow if that's ok (not in the mood to boot up the VM's and run off new builds as it's gone 10pm now ).

-daz

[DrO]

rightio, will send you a version of each tomorrow if that's ok (not in the mood to boot up the VM's and run off new builds as it's gone 10pm now ).

-daz

[idobi]

rightio, will send you a version of each tomorrow if that's ok (not in the mood to boot up the VM's and run off new builds as it's gone 10pm now ).

-daz

Sounds good. I just noticed that you're in the UK. Let me know and I will test it out.

[DrO]

just noticed that you're in the UK

yup for my sins
pm sent with link to the test builds for you.

-daz

[Armitage64]

I'm in the process of converting my ices1->sc_serv server over to the new sc_trans and ran into exactly the same question. I use ices.cue to display realtime information on my site in a PHP page. If you've got ices.cue functionality working with sc_trans I'd love to know what you did.

Thanks!

---
Matthew R. Demicco
ArmiTunes Radio