mpg321 gives http_open error when playing streams

vrillusions · 08-08-2005, 09:32 PM

This is on debian 3.1. I am trying to get mpg123 (actually mpg321) working so it plays streaming audio. I got it working fine on slackware and just upgrading to debian and it isn't working. Here's what I get when I try to run it:

Code:

todd@sonica:~$ mpg123 http://64.236.34.4:5190/stream/8022
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3.
Version 0.59q (2002/03/23). Written and copyrights by Joe Drew.
Uses code from various people. See 'README' for more!
THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK!
http_open: Connection reset by peer
http://64.236.34.4: No such file or directory

seems like that http_open error would be rather common, at least common enough that people would have asked about it before but hardly any results showed up anywhere, just a couple in google and neither really helped. Any ideas? This is very minimal install so I may just be missing a library or something?

btw, I have tried playing a regular mp3 on the hard drive and it works fine, just internet audio streams. I've also tried several urls with and without trailing /s and different ports, they'll work in itunes but won't on that machine. Thanks for any help.

kencaz · 08-08-2005, 09:48 PM

I Think its a bogus URL... Here is what I get using curl:

ICY 404 Resource Not Found
icy-notice1:SHOUTcast Distributed Network Audio Server/posix v1.8.1<BR>
icy-notice2:The resource requested was not found<BR>

Try some other streaming content... I don't think it's mpg123 causing the problem....

KC

vrillusions · 08-08-2005, 10:43 PM

hmm, interesting...

I got it working with this stream hosted at digitalgunfire:
http://129.16.159.166:8000

but it's not working with di.fm. I am listening to this exact stream right now in itunes:
http://205.188.234.65:8022

but if I try to play that in mpg123 it gives me that http_open error. Tried both with and without the trailing / since I've had issues with that before. So it must be some issue with di.fm I'll have to figure out. Maybe I can see if anyone has ideas over there, either. Thanks.