-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans (1) .- Knowledge Base  . 

RecordRadio

   0.2.3  

Amarok Script

Score 80%
Link:  http://
Downloads:  18832
Submitted:  Dec 23 2005
Updated:  Dec 29 2008

Description:

RecordRadio is a simple bash script that plugs into amarok and uses streamripper to record radio stations you listen to.
Now as of version 0.2 it can also save podcasts to your music collection!

Simply enable it as a plugin, and when you connect to any http stream it plugin will spawn a instance of streamripper that will record the songs and place them in subdirectories within a directory called "Music" in your home. Five seconds later amarok will start listening to a relay server on port 8017 so as not to use unnecessary bandwidth.
To save a podcast or remote mp3 or ogg file to your music collection, right click on it in your playlist, select "RecordRadio" and "Save Podcast". They will be saved in a directory called Music/SavedPodcasts within your home directory.

If you wish to change the streamripper options (proxy settings etc.) or the directory where things are stored right-click on RecordRadio in your script manager and click edit. These are simply variables that are set in the first few lines of the file.

Requirements:
You need to have streamripper installed. It comes as part of Debian and several other distributions. You can also download it from http://streamripper.sourceforge.net/ .
If you are using Mandriva 2006 you can get streamripper from "contrib". However for RecordRadio to work you will need to update to the latest version of Amarok due to a bug in 1.3.1
For RecordRadio to run need to have a few standard GNU commands available: (awk, egrep, ps, wget)
RecordRadio has been tested on and works with
Amarok == 1.3.7 (with xine and arts engines),
1.3.1 will NOT work!
Streamripper == 1.67.17

Note: This script will not work with Amarok 2.0. Please see: https://bugs.kde.org/show_bug.cgi?id=179015

Known Bugs:
When you start an internet radio station your playlist will be cleared. (This can be fixed as soon as the amarok developers fix the playMedia dcop call)
Because streamripper for whatever reason cannot produce metadata on demand for some stations, there may be a delay of up to 15 secounds before you can switch to the replay server. However you can continue to listen to the station live until then, and it will still get recorded. These stations may also cause amarok to be unable to report the length of recorded songs. However these can be fixed by using a plugin called MP3Fixer, and restarting amarok.
Sometimes the server is full and cannot support an additional connection for streamripper so you can't record that station, so it simply will not be recorded and you will continue to listen to it live. If this happens you will receive an error to the effect that localhost refused your connection.


If you like this plugin, please consider making a donation to the Electronic Frontier foundation: www.eff.org




Changelog:

0.2.3 - Separate "always record" and "Record on demand" modes and several bug fixes.
0.2.2 - Adds menu to listen without recording.
0.2.1 - Fixed bugs mentioned by pfeifle and prevented from going out of control if amarok crashes.
0.2 - Added ability to save podcasts.
0.1.1 - Removed bug requiring output file.
0.1 - First release




LicenseGPL
Send to a friend
Subscribe
Other  Apps  from tkaitchuck
Report inappropriate content



goto page:  1  2  3 

-

 nice

 
 by qurk on: Dec 23 2005
 
Score 50%

Your script works exactly as advertised. I like how it handles incomplete songs.


Reply to this

-

 Doesnt work for me

 
 by pfeifle on: Dec 28 2005
 
Score 50%
pfeiflepfeifle
Infotec Deutschland GmbH
editor
Home
-
Kurt Pfeifle 0

Infotec Deutschland GmbH
Germany, stuttgart
Last visit Jan 24 2011
0 Friends
0 Groups

More info
Send a message
Add as friend
Other contents
--

The script doesnt work for me. I am on SUSE-10.0. I compiled streamripper successfully and can run it from the commandline just fine, even traversing the proxy I need to go through. I'm using amarok 1.3.7 with the Xine engine (no other engine works for me...) However, RecordRadio.sh doesn't work as an amarok script. The major problem is described at the end. First a few minor quirks:

  1. First, the script tries to create $PodcastDir inside $MusicDir.
  2. Next, it changes directory into $MusicDir.
  3. Then it checks if $MusicDir exists and creates it if missing.

The order should rather be "3)"-"1)"-"2)", no?

Also, it would be nice if you could add "-p $http_proxy" to the calling arguments of streamripper (and maybe the line 'http_proxy="$http_proxy"' to the variable definitions).

The major problem is this error message:

The connection was refused for the URL: http://localhost:8017/

xine parameters: http status not 2xx.

Did you test the script with the Xine engine? What could be the reason for the "http status" error message?


------

In any case: thanks for the nice script -- I'm sure it is a very useful one for many people. Even if it doesn't work for me right now, it showed me just how much and how well DCOP support is already implemented in amarok, and what kind of amzing things one can do with DCOP scripting KDE applications! Thanks a lot!


Reply to this

-

 Conversion

 
 by markey on: Dec 29 2005
 
Score 50%

I offer to convert this script to Ruby for you, or help you convert it. If you are interested, let me know.


Reply to this

-
.

 Not all streams work

 
 by blujay on: Jan 21 2006
 
Score 50%

Here's one that streams fine but this script doesn't handle, because it doesn't end in ".mp3" or ".ogg":

http://64.236.34.67:80/stream/1005

Can that be fixed? :)


Reply to this

-
.

 Re: Not all streams work

 
 by tkaitchuck on: Jan 21 2006
 
Score 50%

This is a stream, not a podcast. If you add this as a radio station and start playing, it will get recorded. (At least it worked for me.) Clicking "Save Podcast" is only intended for podcasts and deliberately ignores streams. These two features are really unrelated I just happened to put them in the same plugin so they would not step on each other's toes. Handling podcasts and streams in the same way is not a good idea because if you just try to download a stream, you will get a never ending file that you can't easily deal with. Similarly using streamripper to download podcasts makes no sense as it will mess up the name and ID3 tags. I could make a feature to record a radio stream that you are not currently listening to from a right-click menu. However I have not yet done this, as I don't see any way to have a good interface so you can see what you are currently downloading, or a good way to allow the user stop the recording. If anyone has any ideas on how to provide such an interface I would welcome suggestions.


Reply to this

-

 Re: Re: Not all stre

 
 by blujay on: Jan 24 2006
 
Score 50%

Oops, I'm sorry, I didn't realize there was separate functionality for podcasts and streams. I just tried it, and indeed, it's recording. :)

Now, I do have a small feature request, if possible: could there be a button or menu item for recording streams, instead of doing it automatically? I don't want to record it every time I listen to it, but it'd be nice to be able to leave the script activated without it automatically recording streams.

Thanks for your great script. :)


Reply to this

-

 Re: Re: Re: Not all stre

 
 by tkaitchuck on: Jan 28 2006
 
Score 50%

0.2.2 now has a menu to do this.


Reply to this

-
.

 Re: Re: Re: Re: Not

 
 by blujay on: Jan 28 2006
 
Score 50%

Thanks for adding that, but wouldn't it make more sense to not record by default, and to use the menu to record it? I listen to this stream all the time, but I only record from it once in a while.


Reply to this

-

 Re: Re: Re: Re: Re:

 
 by blujay on: Jan 29 2006
 
Score 50%

Trying 0.2.3 now. You rock, thanks. :)


Reply to this

-

 Re: Re: Not all stre

 
 by blujay on: Jan 24 2006
 
Score 50%

By the way, Amarok isn't showing the stream metadata for the relay stream, but XMMS does. Is that a problem with this script, or Amarok itself?


Reply to this

-

 Re: Re: Re: Not all stre

 
 by tkaitchuck on: Jan 28 2006
 
Score 50%

It does display metadata, it's just not in the same format that is used for remote streams. It appears to use the same layout as it does for local files. I assume because amorok looks at the location where the data is coming from to determine what format to display things in.


Reply to this

-

 Re: Re: Not all streams work

 
 by tkaitchuck on: May 2 2006
 
Score 50%

This means that it was not able to connect to the relay server it spawned.

There are two possibilities that can cause this.
First is if you are using the "Always record" mode, the server may have accepted the connection from your computer, and allowed you to start listening, but rejected when you tried to reconnect, because it was busy. This should not happen in "record on demand" mode. So try that first.

The second possibility is that it simply did not wait long enough to try to connect to the server. This could simply be caused by your computer being slow. If this happens consistently go into the script manager and right click on the script and click edit. Then change the line towards the bottom that says: "sleep 2" to something like say "sleep 5", which will add an extra three seconds pause to get the relay server up and running.

If this continues to happen, even with the increased delay and in "on demand" mode. Then edit the script so that it sends it's log to a file somewhere, start amarok and reproduce the problem. Then send me the log file as well as a step by step list of everyting you did.


Reply to this

-
.

 Re: Re: Re: Not all streams work

 
 by tkaitchuck on: May 2 2006
 
Score 50%

Sorry posted to wrong thread.


Reply to this

-

 Doesn't work

 
 by Animatrix30 on: Feb 21 2006
 
Score 50%

Hi !!

I try your script, but it says me that :

"Impossible to open the URL http://localhost:8017/relay.mp3

I use Xine, but with Arts it is worse !

What can I do ?

Bye !


Reply to this

-

 Re: Doesn't work

 
 by tkaitchuck on: May 2 2006
 
Score 50%

This means that it was not able to connect to the relay server it spawned.

There are two possibilities that can cause this.
First is if you are using the "Always record" mode, the server may have accepted the connection from your computer, and allowed you to start listening, but rejected when you tried to reconnect, because it was busy. This should not happen in "record on demand" mode. So try that first.

The second possibility is that it simply did not wait long enough to try to connect to the server. This could simply be caused by your computer being slow. If this happens consistently go into the script manager and right click on the script and click edit. Then change the line towards the bottom that says: "sleep 2" to something like say "sleep 5", which will add an extra three seconds pause to get the relay server up and running.

If this continues to happen, even with the increased delay and in "on demand" mode. Then edit the script so that it sends it's log to a file somewhere, start amarok and reproduce the problem. Then send me the log file as well as a step by step list of everyting you did.


Reply to this

-

 Yes!

 
 by RyanDBair on: May 30 2006
 
Score 50%
RyanDBairRyanDBair
-
Ryan Bair 0

United States of America, Pittsburgh, PA
Last visit Jan 14 2007
0 Friends
0 Groups

More info
Send a message
Add as friend
Other contents
--

You are awesome! Thanks for the script.


Reply to this

goto page:  1  2  3 

Add commentBack






-
-
How do you like Plasma 5?
 The best KDE Desktop ever.
 Definitely a nice improvement.
 Not decided yet. Haven't tried it yet.
 I do not like some of the changes.
 KDE is taking the wrong way.
 I am still sticking with KDE 3.5.
 I have no opinion, but wanted to vote anyway.

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.