On Monday 19 February 2007 16:09, Roman Haefeli wrote: > hello Richard > > On Mon, 2007-02-19 at 15:15 +0000, Richard Lewis wrote: > > Hey there, > > > > I'm trying to use mp3cast~ with Icecast 1. > > > > Initially I had a patch where the settings messages ('passwd', > > 'mountpoint', etc.) for the mp3cast~ were sent when the patch was loaded > > and the 'connect' and 'disconnect' messages were sent in response to > > other events. In this setup I got all the expected messages from PD but I > > couldn't connect to the mp3 streams, my clients just said that Icecast > > was returning a 404 error. > > [mp3cast~]'s output on the pd-window should give you a hint, whether it > could connect to the icecast-server or not. if nothing tells you, that > connection failed or something like that, i would assume that it could > connect correctly and that the problem might be with the connection > between client-app and server.
Yes, I can't see the patch window because its -nogui. But I can see pd's output and it now looks as though its connecting properly: mp3cast~: connecting to port 8080 mp3cast~: logging in to IceCast server... mp3cast~: logged in to localhost.localdomain mp3cast~ : using lame version : 3.97 mp3cast~ : lame initialization done. (1) mp3cast~: initialising buffers > > some random possible problems, that come to my mind: > > -did you try to connect the client on the right port (e.g. > http://yourhost.com:8080/yourstream.mp3 ) ? > Yes, I keep checking this. Another things I might try is playing with the hostname setting in Icecast. Maybe just localhost isn't good enough and it might have to be the same as the hostname that clients give... > -is the port not blocked by a firewall? > No, I've made sure that my computer can talk to port 8080 (and my test server doesn't have a firewall!!) > > I wondered whether perhaps it might help if I sent all the settings > > messages every time I sent 'connect' so I altered my patch. Now, it tells > > me that I'm sending a "Bad Password". > > the only thing i know, is that before the [connect(-messages all other > settings-messages should be sent. > > > > > $ echo apassword | makepasswd --verbose --crypt --clearfrom=- > > hm.... my icecast-server (v2.3.1) has a configuration-file called > icecast.xml, where the password is written in plain-text (the file is in > xml-format). so no makepasswd and stuff is needed. i don't know if > icecast.conf works differently. Debian icecast is compiled with encrypted passwords option. > > > which seemed to work. I copied the encrypted version into my icecast.conf > > file. I guess thats right? > > > > In PD, can you send send messages in any particular order? If so, would > > it matter what order I sent the 'connect' and 'passwd' messages to > > mp3cast~? > > yes, you can send the messages in a certain order in pd and yes, it DOES > matter when sending the settings-messages to [mp3cast~]. first set all > settings like passwd, mountpoint, bitrate etc and after this send the > [connect blabla.com 8080(-message. you could put all settings-messages > in one single message-box, separated by a ',' like for example: > OK, thanks. I don't think this is a password issue any more. Cheers, Richard -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Richard Lewis Sonic Arts Research Archive http://www.sara.uea.ac.uk/ JID: [EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list