There's also a
Writer class that allows you to inject your own metadata into a
data stream, which can then be displayed by another ICY client (like VLC).
But you'll probably be most interested in the
Client class that builds off of
http module, except this version works with servers that return
an ICY HTTP version, and automatically sends an "Icy-MetaData: 1" HTTP header
to notify the server that we want metadata, and finally it returns a
instance in the "response" event, therefore the "res" object also emits "metadata"
events. See the example below to see how it works.
A good use case for this module is for HTML5 web apps that host to radio streams;
<audio> tag doesn't know how to deal with the extra metadata and it is
impossible to extract (on the client-side). But a WebSocket connection could be
used in conjunction with this module to provide those
metadata events to a
web browser, for instance.
$ npm install icy
Here's a basic example of using the HTTP
Client to connect to a remote ICY
stream, pipe the clean audio data to stdout, and print the HTTP response headers
and metadata events to stderr:
var icy = ;var lame = ;var Speaker = ;// URL to a known ICY streamvar url = '';// connect to the remote streamicy;
Client class is a subclass of the
The other big difference is that it passes an
instead of a
http.ClientResponse instance to the "response" event callback,
so that the "metadata" events are automatically parsed and the raw audio stream
it output without the ICY bytes.
request() convenience function. Similar to node core's
except it returns an
get() convenience function. Similar to node core's
except it returns an
icy.Client instance with
.end() called on it and
no request body written to it (the most common scenario).
ICY stream reader. This is a duplex stream that emits "metadata" events in addition to stripping out the metadata itself from the output data. The result is clean (audio and/or video) data coming out of the stream.
Writer class is a duplex stream that accepts raw audio/video data and
passes it through untouched. It also has a
queue() function that will
queue the Writer to inject the metadata into the stream at the next "metaint"
Queues a piece of metadata to be sent along with the stream.
metadata may be a String and be any title (up to 4066 chars),
or may be an Object containing at least a "StreamTitle" key, with a String
value. The serialized metadata payload must be <= 4080 bytes.
Parses a Buffer (or String) containing ICY metadata into an Object.
Takes an Object and converts it into an ICY metadata string.