Displaying 20 results from an estimated 900 matches similar to: "winamp >2.75 -answer on song titles // use_meta_data-"
2004 Aug 06
1
winamp >2.75 -answer on song titles // use_meta_data-
also, keep in mind that support for streaming song titles is also a
function of the source client you use....
I've been very successful with use_meta_data=1 and using either my DSP
source (oddcast) or the Shoutcast DSP source....
and you can always know for sure if song titles are supported on your
server by looking at the HTTP response headers from a request of the
stream, (your request
2004 Aug 06
0
winamp >2.75 -answer on song titles // use_meta_data-
All I can tell you is that I've been unable to ever get meta_data to
stream, and the question I sent about it a week or two ago has gone
unanswered.
I never actually checked that I was using WinAmp 2.75, but I do know that
whatever version of winamp I *was* using could stream metadata from other
sites.
On Fri, 13 Sep 2002, zeek wrote:
>
>
> I've searched the archives on xiph
2004 Aug 06
2
Lame, Bitrates, ReEncoding I
I'd like to use the Bitrate and Reencode features of ices and understand I
must recompile with lamelib.
However, it's Very Unclear where to begin here. This is noted in the
ices-0.2.3 INSTALL file:
I installed lame as a debian package so lame.h is in
/usr/include/lame/lame.h
and libmp3lame.a is in /usr/lib. configure finds everything automatically.
<p>I assume we
2004 Aug 06
1
Source Authentification
Hi,
I've just switched to icecast 2... I was using some shell script that
were re-encoding stream at differents bitrate but they aren't working
anymore with icecast 2 :-(
What is the new authentification protocol ?
Previously, I was sending :
SOURCE $PASSWORD $DESTMOUNTPOINT
x-audiocast-name: $NAME
x-audiocast-url: $URL
x-audiocast-genre: $GENRE
x-audiocast-bitrate: $BITRATE
2004 Aug 06
2
Icecast in Macromedia Flash
<?xml version="1.0" ?>
<head>
<title></title>
</head>
<body>
<div align="left"><font face="Arial" color="#7f0000"><span style="font-size:10pt">> you only have the header info in this, for protocol break up the actual</span></font></div>
<div
2004 Aug 06
5
Missing headers in Icecast2
Hi Karl,
Thanks for your help,
About the "Connection:" header, you are right, it's:
"Connection: close" and NOT "Connection: keep-alive". The protocol when the
SERVER sends the data is http 1.0. It's http 1.1 when the browser requests
the data.
I don't understand the "Content-Length: 54000000" header either. Also I
noticed the flash player on
2004 Aug 06
0
Lame, Bitrates, ReEncoding I
Ok, not bad -be sure to rm config.cache if ices has already been compiled.
Then
./configure --with-lame-libraries=/usr/local/lib --with-lame-includes=/usr/l
ocal/include/lame/ >configure.out
Check configure.out for:
updating cache ./config.cache
checking for lame/lame.h... yes
checking for lame_init_old in -lmp3lame... yes
checking for lame_encode_flush_nogap in -lmp3lame... yes
updating
2004 Aug 06
5
Getting Listed
At 23:25 3/15/2001 -0500, you wrote:
>Asym,
>
>What streaming program are you using? I'm using icecast 1.3.10 with meta
>data turned on and it doesn't want to list on yp.shoutcast.com. Can you
>e-mail me your icecast.conf and your streaming config file via e-mail?
>Thanks...
I'm running icecast 1.3.10 on FreeBSD 3.5-Stable, and my source is Winamp
2.72 w/
2001 Sep 03
3
source login schemes
Hi,
Could anyone tell me about the different login schemes sources can use
to connect to IceCast, ShoutCast, etc? From what I can tell:
ShoutCast uses something called icy login?
IceCast uses something called x-audiocast, but can also use icy?
IceCast2 uses what?
Also, where can I find details about these login schemes? I sort of
figured out a basic use of x-audiocast by looking at the JScream
2004 Aug 06
0
use_meta_data problem
Hi all,
I'm new to this list. I'm helping a friend set up Icecast on his
machine, but it seems the meta data isn't being used. I basically
copied over my config file (in which the titles work fine when
streamed), and made slight changes like the url, server_name, and
things like that.
I also set up his xmms and liveice 1.0 to mine (except for description
of server and passwords
2006 Aug 03
1
Strange file upload error
Hi There,
So we are having this really strange file upload error. We can upload a
file to rails, store it in the DB, and download it again all fine.
We also have things set up to allow us to edit the file, and upload a
new one to replace the existing file. This functionality works just fine
for text files, but fails for microsoft word and PDF files.
It''s really strange; we''re
2004 Aug 06
0
x-audiocast etc.
Hmm.. just switched back to icecast hoping that 1.3.9 would have fixed some
of the bugs I was running into, such as icecast gobbling up more and more
memory until it would tank around 200M or so (in a box with 256) if left
running a few days, and got some general questions for anyone in-the-know. ;)
1. Is there a definitive list of what players on what platforms support the
x-audiocast
2004 Sep 10
0
http streaming in the xmms plugin
Hi,
Here's a patch to add support for streaming HTTP transport to the xmms
plugin. Most of the code (in particular, http.c) is taken from the xmms
mpg123 input plugin.
You'll need to make a three-line change to the xmms mpg123 input plugin to
get streaming to work. The mpeg plugin currently handles all http urls
itself unless they end in an ogg or real audio extension (which means flac
2004 Aug 06
1
[SOLVED] Re: [icecast-dev] Why doesn't yp.icecast.org show my stream?
Just following up to myself here so this will be in the archive
for people.
The problem was in darkice 0.7. There is a patch required to make
it comply with the x-audiocast-public "standard". You can get the
latest CVS to fix the problem.
------
Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org
>>> The opinions expressed above are entirely my own <<<
2004 Aug 06
1
Streaming Supplier
Is there a UK streaming supplier anyone would recommend? If they use
icecast that would be a bonus. At the very least they need to support
x-audiocast login and hopefully vorbis.
Stephen
KUCS.net
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request@xiph.org'
2004 Oct 19
1
Some metadata missing, relaying icecast1 stream with icecast2
I'm relaying an icecast1 mp3 stream with icecast2. This works fine,
and the song title is displayed correctly no matter if I use
<relay-shoutcast-metadata>1</> or not on the relay.
But, the stream name and other metadata provided by ices0 on the
icecast1 server is not displayed in the listening client.
Icecast1 source:
[Id: 1] [Sock: 11] [Time of connect: 09/Aug/2004:10:01:24]
2004 Aug 06
1
Why doesn't yp.icecast.org show my stream?
Jack Moffitt <jack@xiph.org> writes:
> Now I see the problem. This will not cause anything to show up. You
> have no sources.
Eh?
-> sources
Listing sources
[Id: 509] [Sock: 14] [Time of connect: 18/Feb/2002:20:55:14] [IP:
205.147.43.110] [State: 1] [Type: pulling relay] [Proto: x-audiocast]
[Clients: 2] [Dumpfile/fd: (null)/-1] [Priority: 0] [Song Title: ] [Song URL:
2004 Aug 06
3
Icecast's YP bugs
Ok I've been discovering many bugs in Icecast's YP implementation..
The most serious of which is, if a YP server is rejecting a stream the
server has a memory leak which, as it continues to re-try to publish
it's rejected streams, grows until the server segfaults. On our server,
for instance, we're relaying shoutcast streams (which does not relay the
stream name and other
2000 Jul 06
2
GUI Samba?
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hello,
I'm new to Linux, I work on a PC, Mac, and now Linux network. I have
been looking for somthing like samba that will work on Xwindows. If you
could point me in the right direction I would be thankfull.
Hope to hear from you soon,
Zeek Bower.
2018 Sep 24
2
OpenStack output - server_id
Hi,
I've read the virt-v2v OpenStack output code to understand how it works and
I've seen this:
> (* The server name or UUID of the conversion appliance where
> * virt-v2v is currently running. In future we may be able
> * to make this optional and derive it from the OpenStack
> * metadata service instead.
> *)
> server_id : string;
Indeed, it can be