search for: smackfu

...e=>:userplace)) then it works, but that''s an ugly hack since now it includes the userplace columns twice in the SQL. OTOH, it saves a lot of query time. Any ideas? It''s very possible I''m missing something fundamental here but I''m pretty frustrated. Thanks, Smackfu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send...

...I'm trying to write a PHP script that communicates with the Icecast2 server directly to retrieve current song information. Since the documentation for the ICE/SHOUT protocol is, frankly, pretty much non-existant, I did a search on Google and eventually came up with this site: http://www.smackfu.com/stuff/programming/shoutcast.html I did some experimenting with this information and my Icecast2 server and, after a few telnet sessions, determined that those instructions were incorrect (at least with Icecast servers). I assume that this is due to the fact that there is no constant bitrate fo...

...an listen for (of course Icecast has no admin.cgi) The info you've provided for Shoutcast is useful and you allude to some other icecast methods ... need documentation for this function of icecast and googling produces no joy, nor do the official or unofficial guides for icecast. The Smackfu link is OK as a cursory introduction to how to pull attributes from a stream but not so instructive in injecting them in and it lists one of the variables. What are the variables used in the shoutcast-metadata-protocol and how do they work? I'm guessing through some extensive googling a...

the metadata format is not documented officially anywhere, but really isn't terribly complicated... http://www.smackfu.com/stuff/programming/shoutcast.html hows a nice concise description of it, and was the first result returned from doing http://www.google.com/search?q=shoutcast+metadata oddsock At 04:06 PM 2/25/2003 -0500, you wrote: > > The mp3 metadata format is a nasty hack originated by the shoutcas...

Like any other major radio station we output our music from automation software via analog audio through a mix board in a studio, where we insert other stuff like live DeeJays, etc. only to have that stream re-encoded by hardware MP3 encoders for distribution to our network of IceCast servers. The chain of song information gets broken as soon as we output from the Automation software,

Hi, I am planning to guide Engineering Students, to build a MP3 Streaming Server as part of their academic project. I downloaded icecast 2.0.2 & ices 0.4 & went through the documentation & code. I am not able to find technical resources explaining the streaming protocol between Icecast Server & Client (winamp or xmms). We are in need of technical details of streaming protocol,

...s a sort of id3 packet interleaved >at specific byte offsets with the mp3 program stream. AFIAK, >there's no documentation on this. Just read the icecast code >for an example. Look for the 'icy-*' headers. Here is a good decription of the Shoutcast metadata protocol. http://www.smackfu.com/stuff/programming/shoutcast.html Keep in mind, this is only enabled in icecast when a client sends a Icy-Metadata:1 in the request headers and ONLY applies to mp3 streams. oddsock

...g to write a PHP script that communicates with the Icecast2 server > directly to retrieve current song information. Since the documentation for > the ICE/SHOUT protocol is, frankly, pretty much non-existant, I did a search > on Google and eventually came up with this site: > http://www.smackfu.com/stuff/programming/shoutcast.html > If you're streaming mp3, and your streaming client supports setting metadata on icecast2 servers (this requires, among other things, a version of icecast2 no more than two weeks old. I know of no source clients other than very recent versions of oddso...

i found that too. but, imho, doesnt have all the necessary details to write a system that can process metadata. deva On Tue, 25 Feb 2003, oddsock wrote: > the metadata format is not documented officially anywhere, but really isn't > terribly complicated... > > http://www.smackfu.com/stuff/programming/shoutcast.html > > shows a nice concise description of it, and was the first result returned > from doing > > http://www.google.com/search?q=shoutcast+metadata > > oddsock > At 04:06 PM 2/25/2003 -0500, you wrote: > > > The mp3 metadata format...

when I move libshout.so.2.2 up into /usr/lib, it magically works. sloppy but, it works... On Mon, May 20, 2002 at 02:34:08PM -0700, Mark Luntzel wrote: > oh sorry. forgot this: > > bash-2.05# perl Makefile.PL > Checking if your kit is complete... > Looks good > Note (probably harmless): No library found for -lshout > Writing Makefile for Shout > > Thsi turns out not

> ah, sorry. what do you mean by the source program? streamer? what is > external synchronization? The source program is whatever provides the data stream - ices, for instance. External syncronisation means performing whatever synchronisation you need to get the data you want in a seperate program - not within icecast (or ices). > > btw, where can i find the mp3 straming specs? that

...streams they all take in metadata via the various admin interfaces I described above. For delivering the metadata to listening clients, there is really only one supported mechanism, and that is the "shoutcast-metadata-protocol". A really great explanation of this is here http://www.smackfu.com/stuff/programming/shoutcast.html. Most mp3 clients support this protocol but not all do (Windows Media Player does NOT, and the various Flash players that you are using do NOT). Most other media players that people tend to use (Winamp, Foobar, XMMS) all do. So, enough background, to your...