How to send metadata to a shoutcast server - Revision history

StefanG at 06:16, 21 May 2012

2012-05-21T06:16:14Z

← Older revision		Revision as of 06:16, 21 May 2012
Line 15:		Line 15:


	2) When the Instreamer is used for Shoutcast server mode(Shoutcast : 0.0.0.0 : port number) and your Shoutcast or Icecast server is configured as "relaying" server, then - and only then - you can feed metadata from the Instreamer through the Shoutcast/Icecast relay server to the clients/listeners. Here is an example how the Shoutcast or Icecast server must be configured as relaying server - of course, this is just an incomplete snippets of the configuration files:		2) When the Instreamer is used for Shoutcast server mode (Shoutcast : 0.0.0.0 : port number) and your Shoutcast or Icecast server is configured as "relaying" server, then - and only then - you can feed metadata from the Instreamer through the Shoutcast/Icecast relay server to the clients/listeners. Here is an example how the Shoutcast or Icecast server must be configured as relaying server - of course, this is just an incomplete snippets of the configuration files:

StefanG at 06:37, 18 May 2012

2012-05-18T06:37:19Z

← Older revision		Revision as of 06:37, 18 May 2012
Line 3:		Line 3:


	To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E=" you must supply standard ~~shoutcast~~ metadata format. Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).		To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E=" you must supply standard Shoutcast metadata format. Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).

	http://<ip-instreamer>/rc.cgi?'''E=StreamTitle='Title';'''		http://<ip-instreamer>/rc.cgi?'''E=StreamTitle='Title';'''
Line 12:		Line 12:
	The Instreamer can insert metadata in two modes:		The Instreamer can insert metadata in two modes:

	1) The metadata feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio : 0.0.0.0 : port number"). In this case no other ~~Streaming~~ server is involved, the clients/listeners will request/get the stream directly from the Instreamer.		1) The metadata feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio : 0.0.0.0 : port number"). In this case no other streaming server is involved, the clients/listeners will request/get the stream directly from the Instreamer.


	2) When the Instreamer is used for Shoutcast server (Shoutcast : 0.0.0.0 : port number) and your Shoutcast or Icecast server is configured as "relaying" server, then - and only then - you can feed metadata from the Instreamer through the ~~shoutcast~~/Icecast relay server to the clients/listeners. Here is an example how the Shoutcast or Icecast server must be configured as relaying server - of course, this is just an incomplete snippets of the configuration files:		2) When the Instreamer is used for Shoutcast server mode(Shoutcast : 0.0.0.0 : port number) and your Shoutcast or Icecast server is configured as "relaying" server, then - and only then - you can feed metadata from the Instreamer through the Shoutcast/Icecast relay server to the clients/listeners. Here is an example how the Shoutcast or Icecast server must be configured as relaying server - of course, this is just an incomplete snippets of the configuration files:


Line 49:		Line 49:

	When the Instreamer is connected as "Shoutcast source" (Shoutcast : <IP address of the SC server> : port number) then Barix Instreamer actively connects to and sends the live audio feed after authenication over a raw TCP connection to the server.		When the Instreamer is connected as "Shoutcast source" (Shoutcast : <IP address of the SC server> : port number) then Barix Instreamer actively connects to and sends the live audio feed after authenication over a raw TCP connection to the server.
	In this mode it´s not possible to add any metadata for the Instreamer, because there is no space in the header for it. ~~In this mode~~ metadata must be inserted on the Shoutcast server directly. The same is valid for Icecast servers.		In this mode it´s not possible to add any metadata for the Instreamer, because there is no space in the header for it. Then the metadata must be inserted on the Shoutcast server directly. The same is valid for Icecast servers.

	Back to [[FAQ]]		Back to [[FAQ]]

StefanG at 06:35, 18 May 2012

2012-05-18T06:35:04Z

← Older revision		Revision as of 06:35, 18 May 2012
Line 10:		Line 10:


	The Instreamer can insert ~~Metadata~~ in two modes:		The Instreamer can insert metadata in two modes:

	1) The ~~Metadata~~ feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio : 0.0.0.0 : port number"). In this case no other Streaming server is involved, the clients/listeners will request/get the stream directly from the Instreamer.		1) The metadata feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio : 0.0.0.0 : port number"). In this case no other Streaming server is involved, the clients/listeners will request/get the stream directly from the Instreamer.


Line 49:		Line 49:

	When the Instreamer is connected as "Shoutcast source" (Shoutcast : <IP address of the SC server> : port number) then Barix Instreamer actively connects to and sends the live audio feed after authenication over a raw TCP connection to the server.		When the Instreamer is connected as "Shoutcast source" (Shoutcast : <IP address of the SC server> : port number) then Barix Instreamer actively connects to and sends the live audio feed after authenication over a raw TCP connection to the server.
	In this mode it´s not possible to add any metadata for the Instreamer, because there is no space in the header for it. ~~Metadata~~ must be inserted on the Shoutcast server directly. The same is valid for Icecast servers.		In this mode it´s not possible to add any metadata for the Instreamer, because there is no space in the header for it. In this mode metadata must be inserted on the Shoutcast server directly. The same is valid for Icecast servers.

	Back to [[FAQ]]		Back to [[FAQ]]

StefanG at 06:32, 18 May 2012

2012-05-18T06:32:21Z

← Older revision		Revision as of 06:32, 18 May 2012
Line 3:		Line 3:


	To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E=" ~~parameter,~~ you ~~will need to~~ supply standard shoutcast metadata format. Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).		To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E=" you must supply standard shoutcast metadata format. Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).

	http://<ip-instreamer>/rc.cgi?E=StreamTitle='Title';		http://<ip-instreamer>/rc.cgi?'''E=StreamTitle='Title';'''

	~~Of course, the~~ metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.		The metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.

StefanG at 06:27, 18 May 2012

2012-05-18T06:27:35Z

← Older revision		Revision as of 06:27, 18 May 2012
Line 3:		Line 3:


	~~Well - this very much depends on how~~ you ~~operate your~~ shoutcast ~~server !~~		To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E=" parameter, you will need to supply standard shoutcast metadata format. Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).

	~~1) If the Instreamer is connected as "shoutcast source" (Shoutcast~~ : <~~IP address of the SC server~~> : port number) - the Barix Instreamer actively connects to and sends the live audio feed to the server, then there is NO WAY the Instreamer can send that information with the audio ! The Shoutcast source protocol uses a "raw" TCP connection (after authentication) to send the MP3 frames, there is no way the Instreamer could insert that information. If you use that mode, you must directly post the metadata information via HTTP to the Shoutcast/~~Icecast server (check the server documentation)~~.		http://<ip-instreamer>/rc.cgi?E=StreamTitle='Title';

			Of course, the metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.

	2) If the Instreamer is used as Shoutcast relay and your shoutcast server is configured as a "relay", then - and only then - you can feed metadata from the Instreamer through the shoutcast server to the clients/listeners.

	~~Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the~~ Instreamer ~~via the command interface, using raw TCP, UDP, serial port or the cgi interface.~~		The Instreamer can insert Metadata in two modes:

	~~To send metadata to~~ the Instreamer ~~for inclusion with the stream, please use the E= command~~. ~~After the~~ "~~E" parameter, you will need to supply standard shoutcast metadata format (documented somewhere else~~). ~~Here~~ is ~~an example to post~~ the ~~Stream Title - note~~ the ~~command is case sensitive and must be correctly terminated (;) and quoted (single quotes)~~.		1) The Metadata feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio : 0.0.0.0 : port number"). In this case no other Streaming server is involved, the clients/listeners will request/get the stream directly from the Instreamer.

	~~'''http://<ip-instreamer>/rc.cgi?E=StreamTitle='Title';'''~~

	Here is an example how the ~~shoutcast~~ server is configured as ~~a relay~~ - of course, this is just an incomplete ~~snippet~~ of the configuration ~~file~~:		2) When the Instreamer is used for Shoutcast server (Shoutcast : 0.0.0.0 : port number) and your Shoutcast or Icecast server is configured as "relaying" server, then - and only then - you can feed metadata from the Instreamer through the shoutcast/Icecast relay server to the clients/listeners. Here is an example how the Shoutcast or Icecast server must be configured as relaying server - of course, this is just an incomplete snippets of the configuration files:

	~~'''Shoutcast config:'''~~

	~~RelayPort=8000~~		Shoutcast config:

	~~RelayServer~~=~~192.168.10.175 (the Instreamer IP address)~~		'''RelayPort=8000'''

			'''RelayServer=192.168.10.175''' (the Instreamer IP address)

	~~On the Instreamer configure under "Streaming / Stream to " '''Shoutcast : 0.0.0.0 : 8000'''~~

	~~The Shoutcast server will pick up the stream from this socket.~~

			Icecast config:

			'''<relay>'''

	3) The ~~Metadata feature can be also used when~~ the Instreamer is ~~acting directly as streaming server (configured~~ as "~~Internet Radio~~"). In this ~~case~~ no ~~other Streaming server is involved,~~ the ~~clients/listeners will request/get~~ the ~~stream~~ directly ~~from the Instreamer~~.		'''<server>192.168.10.175</server>''' (the Instreamer IP address)

			'''<port>8000</port>'''

			'''<mount>/xstream</mount>'''

			'''<local-mount>/xstream1.mp3</local-mount>'''

			'''<relay-shoutcast-metadata>1</relay-shoutcast-metadata>'''

			'''</relay>'''


			On the Instreamer configure for both servers under '''"Streaming / Stream to" = Shoutcast : 0.0.0.0 : 8000'''

			The Shoutcast/Icecast server will pick up the stream from this socket.


			When the Instreamer is connected as "Shoutcast source" (Shoutcast : <IP address of the SC server> : port number) then Barix Instreamer actively connects to and sends the live audio feed after authenication over a raw TCP connection to the server.
			In this mode it´s not possible to add any metadata for the Instreamer, because there is no space in the header for it. Metadata must be inserted on the Shoutcast server directly. The same is valid for Icecast servers.

	Back to [[FAQ]]		Back to [[FAQ]]

StefanG at 08:00, 11 May 2012

2012-05-11T08:00:38Z

← Older revision		Revision as of 08:00, 11 May 2012
Line 8:		Line 8:


	2) If the Instreamer is used as Shoutcast relay and your shoutcast server is configured as a "relay", then - and only then - you can feed metadata from the Instreamer through the shoutcast server.		2) If the Instreamer is used as Shoutcast relay and your shoutcast server is configured as a "relay", then - and only then - you can feed metadata from the Instreamer through the shoutcast server to the clients/listeners.

	Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.		Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.

StefanG at 07:45, 11 May 2012

2012-05-11T07:45:55Z

← Older revision		Revision as of 07:45, 11 May 2012
Line 5:		Line 5:
	Well - this very much depends on how you operate your shoutcast server !		Well - this very much depends on how you operate your shoutcast server !

	1) If the Instreamer is connected ~~by the~~ "shoutcast source" ~~protocol~~ - the ~~instreamer~~ actively connects to and sends the live audio feed to the server, then there is NO WAY the Instreamer can send that information with the audio ! The Shoutcast source protocol uses a "raw" TCP connection (after authentication) to send the MP3 frames, there is no way the Instreamer could insert that information. If you use that mode, you must directly post the metadata information via HTTP to the ~~shoutcast~~/~~icecast~~ server (check the server documentation).		1) If the Instreamer is connected as "shoutcast source" (Shoutcast : <IP address of the SC server> : port number) - the Barix Instreamer actively connects to and sends the live audio feed to the server, then there is NO WAY the Instreamer can send that information with the audio ! The Shoutcast source protocol uses a "raw" TCP connection (after authentication) to send the MP3 frames, there is no way the Instreamer could insert that information. If you use that mode, you must directly post the metadata information via HTTP to the Shoutcast/Icecast server (check the server documentation).

	2) If the Instreamer is operated in shoutcast/icecast emulation mode ("internet radio"), and your shoutcast/icecast server is configured as a "relay", then - and only then - you can feed metadata through the Instreamer.

	Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.		2) If the Instreamer is used as Shoutcast relay and your shoutcast server is configured as a "relay", then - and only then - you can feed metadata from the Instreamer through the shoutcast server.

			Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.

	To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E" parameter, you will need to supply standard shoutcast metadata format (documented somewhere else). Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).		To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E" parameter, you will need to supply standard shoutcast metadata format (documented somewhere else). Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).
Line 21:		Line 22:
	RelayPort=8000		RelayPort=8000

	RelayServer=192.168.~~110~~.~~179~~ (Instreamer IP)		RelayServer=192.168.10.175 (the Instreamer IP address)


			On the Instreamer configure under "Streaming / Stream to " '''Shoutcast : 0.0.0.0 : 8000'''

			The Shoutcast server will pick up the stream from this socket.


	~~On the Instreamer, at least one "internet radio" server needs to be enabled.~~

			3) The Metadata feature can be also used when the Instreamer is acting directly as streaming server (configured as "Internet Radio"). In this case no other Streaming server is involved, the clients/listeners will request/get the stream directly from the Instreamer.

	Back to [[FAQ]]		Back to [[FAQ]]

Sandra at 13:04, 20 March 2009

2009-03-20T13:04:03Z

← Older revision		Revision as of 13:04, 20 March 2009
Line 26:		Line 26:

	On the Instreamer, at least one "internet radio" server needs to be enabled.		On the Instreamer, at least one "internet radio" server needs to be enabled.


			Back to [[FAQ]]

Jrietschel at 20:17, 27 January 2009

2009-01-27T20:17:47Z

← Older revision		Revision as of 20:17, 27 January 2009
Line 1:		Line 1:
	~~To send metadata please use the E= command. After~~ the "~~E" parameter~~, ~~you should see the song´s~~ title. ~~The command is extreamely key sensitive. The right syntax is:~~		A common question posted to the Barix support team is, "'''I am using an Instreamer to feed my shoutcast server, but how can i add metadata, genre, title information ?'''".

	~~http://<ip-instreamer>/rc.cgi?E=StreamTitle='Title';~~

	~~The Keyword: "StreamTitle" must be written as it is in the example. Please do not forget the " ' "signs and the " ; " at the end of the command.~~

	The E= command ~~work on Internet Radio mode~~. ~~It could also sucessfully transfer~~ the metadata ~~through~~ a ~~Shoutcast server~~, ~~when~~ the ~~Shoutcast Server works in the RELAY mode.~~		Well - this very much depends on how you operate your shoutcast server !

			1) If the Instreamer is connected by the "shoutcast source" protocol - the instreamer actively connects to and sends the live audio feed to the server, then there is NO WAY the Instreamer can send that information with the audio ! The Shoutcast source protocol uses a "raw" TCP connection (after authentication) to send the MP3 frames, there is no way the Instreamer could insert that information. If you use that mode, you must directly post the metadata information via HTTP to the shoutcast/icecast server (check the server documentation).

			2) If the Instreamer is operated in shoutcast/icecast emulation mode ("internet radio"), and your shoutcast/icecast server is configured as a "relay", then - and only then - you can feed metadata through the Instreamer.

			Of course, that metadata cannot be sent through the analog or S/PDIF audio ports .. it needs to be provided to the Instreamer via the command interface, using raw TCP, UDP, serial port or the cgi interface.

			To send metadata to the Instreamer for inclusion with the stream, please use the E= command. After the "E" parameter, you will need to supply standard shoutcast metadata format (documented somewhere else). Here is an example to post the Stream Title - note the command is case sensitive and must be correctly terminated (;) and quoted (single quotes).

			'''http://<ip-instreamer>/rc.cgi?E=StreamTitle='Title';'''

			Here is an example how the shoutcast server is configured as a relay - of course, this is just an incomplete snippet of the configuration file:

	'''Shoutcast config:'''		'''Shoutcast config:'''

	RelayPort=8000		RelayPort=8000

	RelayServer=192.168.110.179 (Instreamer IP)		RelayServer=192.168.110.179 (Instreamer IP)

	~~'''~~Instreamer ~~Config:'''~~
	~~Shoutcast Source : 0.0.0~~.~~0 : 8000~~
			On the Instreamer, at least one "internet radio" server needs to be enabled.

Jrietschel: How to send metadata moved to How to send metadata to a shoutcast server: too short title

2009-01-27T20:06:16Z

How to send metadata moved to How to send metadata to a shoutcast server: too short title

← Older revision	Revision as of 20:06, 27 January 2009
(No difference)