#18092 closed defect (fixed)
Streamripper bus error
| Reported by: | dershow | Owned by: | cssdev |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | Cc: | ||
| Port: | Streamripper |
Description
I installed streamripper 1.63.1 Rev 1. When I try to use it to record RadioParadise, actually the reason that I installed it, I get a bus error. I have tried it both on a PPC and an Intel machine with the same results after 5-10 seconds:
streamripper http://www.radioparadise.com/musiclinks/rp_128.m3u Connecting... stream: Radio Paradise - DJ-mixed modern & classic rock, world, electronica & more - info: radioparadise.com server name: SHOUTcast/Linux v2.6.0 bitrate: -1 meta interval: 16384 Bus error
Clearly the bitrate is not right, and probably the meta interval is not either. I have tried adding a few different command line flags, but I keep getting exactly the same results.
Any suggestions about this?
thanks,
--Adam
Attachments (1)
Change History (7)
comment:1 Changed 15 years ago by mf2k (Frank Schima)
| Cc: | css@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to css@… |
comment:2 Changed 15 years ago by cssdev
| Status: | new → assigned |
|---|
comment:3 Changed 15 years ago by dershow
I went to that link, and instead downloaded the current version which is 1.64.3 (and not a beta).
I decided to try it with the same flags that are in the current port so I did:
./configure --with-ogg=/opt/local --with-vorbis=/opt/local --with-libiconv-prefix=/opt/local --with-included-argv --with-included-libmad --with-included-tre make
and the new version builds and seems to work just fine.
The odd thing is that I still get: bitrate: -1 meta interval: 16384 but then it seems to work just fine. So I guess these didn't relate to the actual bus error.
So, I think all it would take to get it to upgrade to a newer, and working version, is changing the port to 1.64.3 and getting in the correct checksums.
comment:4 Changed 15 years ago by dershow
It seems that the bug is fixed with 1.64.3. I just updated the port, and tested it locally. I have attached the portfile. The only change is the version number and the checksums. Please upgrade to this version on Macports. If it is easier to use a diff, I can do that, but I figured with this minor change it didn't make a difference.
comment:5 Changed 15 years ago by cssdev
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I guess I could have looked a little more closely to notice the new version. ;) I used to get emails for each new release, but maybe sourceforge isn't doing that anymore. Anyhow, I updated the port in r45699. Thanks for the feedback!
I haven't installed it since I rebuilt my Mac, but it might be worth seeing whether the 1.64 beta has the same problem. It sounds like it might be more an upstream issue than something specific to the MacPorts build. Any chance you could inquire there?