LinuxBBQ

Thanks mate,
will be added to the next release :)

Someone from outside Denmark should try if they can be played. Danmarks Radio is geo-locking their tv-streams, but I'm not sure about the radio channels..

^ works fine in France, using mplayer, I had to remove the .m3u.
here's a mad one we've been getting down with for the last month;

http://air.radiolla.com/mantra192k
perfect for tibetan prayer bowls back to back with indo gamelan music followed tribal islam music from morrocco.

in fact checking out the site http://en.radiolla.com/ ; reveals a bunch of cool stations

http://air.radiolla.com/radiolla192k
(pop newish easy listening)

http://air.radiolla.com/jiraffe192k
(jazz fusion)

http://air.radiolla.com/volta192k
(electronic/ambient)

http://air.radiolla.com/equalyza192k
(left field Hop)

http://air.radiolla.com/ilma192k
(classic)

all at a lovely 192k and NO adds or boring talking.

did the other stations make it to the bbqradio? noticed that the gui radio in XFCE only has a few stations.
bbqradio (cli) seems to need to be run as root?

Wux,
the latest bbqradio/bbqradio-gui have 24 channels, there's a bunch I stole from the soma.fm list (see also the "Recipe" section of the forums-> Scripts -> bbqradio)
The CLI version works as normal user, very sure. (There's nothing that requires root in the script, and it's basically the -gui version with dialog instead of yad)

Edit: I might make a 'button-only' interface, for the gui

Ok. i guess i could 'roast' the script (foresee borkage thread 8) )
hmm.
why do i get this on xfce64?
after typing bbqradio; prefixing sudo makes it work. weird huh?

edit: 'button only' as in 'no drop downs' sounds good, limits a bit the selection. but thats good encourages roasting

that's junk. wtf did I do there?
can you sudo rm /usr/bin/bbqradio ?
Then try again, it should grab it from /usr/local/bin/bbqradio

hmm

Edit ^

1) sudo rm /usr/bin/bbqradio
2) wget -c http://linuxbbq.org/shared/bbqradio
3) sudo mv bbqradio /usr/local/bin/bbqradio
4) sudo chmod +x /usr/local/bin/bbqradio && sudo chmod 777 /usr/local/bin/bbqradio

sorry wux

no need to apologise, you are amazing, i'm moaning about nothing.
if this is helping you i'm happy to grope about like the newbie i am to help you achieve Nirvana.
um bbqradio on it's own doesn't work, need to put /usr/local/bin/bbqradio to achieve fulfilment.
but don't worry really.

yes, it needs to be in either /usr/bin/ or the /usr/local/bin/ folder , chmodded into +x and for all users. I place the newer bbq things into latter folder, actually to prevent the shit I produced there :D Thanks for the heads-up!

glad i could help 8)

@Wux: Thanks for the nice stations.

Radio urls seem to be very unreliable - they get changed or just die, protocols alter...
Still, I'm finding my mpg123 (old - mpg123 1.12.1) failing to load quite a lot of these links, when radiotray works OK. The objection to gstreamer - size?

Other comparison between mpg123 & radiotray:
mpg123 uses much more CPU (10%~11% of Pentium4 playing 192K radiolla-mantra, while radiotray takes ~4%),
otoh radiotray takes 20MB of RAM out of 512, mpg123 takes about 4MB.

Found a nice option with mpg123 lets you send orders from anywhere like this:So you can change radio stations on the fly without restarting every time. Might be useful in a radio tuner.

thanks john, I thought you'd like mantra...
have you tried mplayer?

Thanks John, nice hint with fifo.
Have you tried mpg321 already? I wonder how it is different from mpg123. I've tested both and found them very very similar, both in CPU and RAM usage, but I don't have a Pentium4, so maybe it's more obvious on your box.

@wux thanks for mantra - it's nice! Yes, mplayer's my longtime favourite to be honest. It can play pretty much anything you give it, as long as you send it the -playlist option when needed.

@bacon haven't tried mpg321. Reading about it it sounds pretty much the same as mpg123. Is it supposed to be easier on old processors?

Actually, I'm inclined to suggest mplayer as the default - it can play a wider variety of formats than mpg*** (eg evil mms streams) and will use the mpg123 library to play mp3 streams anyway, if it's available. mplayer also has an equivalent to mpg's "remote" called "slave mode" which works the same way, letting you send commands over a fifo.

^ Well, mplayer2 is not the default media player for the 'main editions' (Tiny/Bass, no-X) because of heavy dependencies (there's another thread* in the Off Topic section, where we compared VLC and mplayer2 and were quite shocked). These editions are weighing less than 250MB for the ISO (and less than 1GB installed) and mplayer or vlc is purposedly not included. I had to follow the self-declared philosophy of "use the smallest available package for a certain task", and for the bbqradio stations that are included the mpg123 player does exactly what is wanted/needed.
For music playback there's mocp and mpg123 (for bbqradio), but mplayer2 is included in around 95% of the other editions. So, I'm inclined to keep mplayer2 out of the main editions (Tiny/Bass - these are basically the netinstall/minimal editions of BBQ), so the user can decide to install mplayer, mplayer2, vlc or the gstreamer-based players. I'll add a check for mplayer/vlc to the bbqradio script, so that it can fallback to mpg123 if the other players are not installed.


* http://linuxbbq.org/bbs/viewtopic.php?f=7&t=578

Fair enough. I never noticed mplayer pulling in a huge amount of stuff, but that was perhaps because I was installing it on a fairly full-featured/bloated system and most of those libraries were installed already. With media stuff I tend to install anything that's going, just in case it might be needed some day...

^ exactly. interesting experiment is to take one of the BBQ no-X bases, which are, as bacon points out, extremely bare, then do some dependency-checks before installing anything on top. gives you a very good idea of what stuff is being used. of course when your system is, for example, already filled with gnomes, you are not going to notice when an extra package uses those same libraries. this is why bloat is relative.

^true. Though mplayer, while it might call for a lot of libraries, is lighter than mpg123 on CPU use when it's running, at least for me.