Image 01
profile-image

tkaitchuck

Tom Kaitchuck
Amarok 1.x Scripts

RecordRadio

Amarok 1.x Scripts Dec 29 2008
Score 54%
54 Likes
46 Dislikes
Dolphin Service Menus
Various Stuff
RecordRadio

Amarok 1.x Scripts 32 comments

Score 54%
54 Likes
46 Dislikes
Dec 29 2008
One reason this can occur is that certain websites don't want to have their content recorded and will disallow anything with the user agent "StreamRipper" from connecting.

You can of course get around this if you really want to. If you look at its manpage, streamripper has an option to change the user agent to anything you want. All you have to do is to add this flag to the 'options' string specified at the top of the file.

This is not done by default, because I have no desire to conceal things from the site it is connecting to. - Jun 15 2009
Unfortunately this and almost any other complex plug-in is permanently broken in Amarok 2.0.

Someone decided that the only plugins that should be allowed must be written in Java script, not call any external libraries processes and only call these functions within Amarok: http://amarok.kde.org/wiki/Development/Script_API

I consider this very limiting and have filed a feature request: https://bugs.kde.org/show_bug.cgi?id=179015

I would encourage anyone who wants this plugin to continue to work in future version to vote for that feature.
- Dec 29 2008
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. - May 02 2006
Sorry posted to wrong thread. - May 02 2006
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. - May 02 2006
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. - Jan 28 2006
0.2.2 now has a menu to do this. - Jan 28 2006
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. - Jan 21 2006
Extract Here

Dolphin Service Menus 5 comments

Score 52%
52 Likes
48 Dislikes
Feb 20 2006
Simply copy the .desktop file to
the directory named
.kde/apps/share/apps/konqueror/servicemenus
within your home directory. - Feb 20 2006
Suggestion: AmaroRipper

Amarok 1.x Scripts 5 comments

Score 50%
50 Likes
50 Dislikes
Sep 16 2005
How do you like this? http://kde-apps.org/content/show.php?content=32842 - Dec 26 2005
*NEW* super fast kde startup

Various Stuff 20 comments

Score 46%
46 Likes
54 Dislikes
Aug 23 2002
it should be in /opt/kde3/bin/ (at least it is for me) and no, that is differnt from startkde.

If you don't have kde3 you may want to wait a few days for a kde 2.2 version. Or you could try inserting those 3 "Preload" lines into your startkde script and see what happens. - Apr 09 2002
Well, other than the Logout from the K-menu, the ktip, and the overriding fonts I mentioned, not anything.

Because it loads the Desktop/panel/window manager first, then does the usual kde stuff.

So then when the kdeinit discovers that the window manager desktop and panel are already running it just doesn't start another copy.

So after about 20 sec (usual kde load time) it is exactly the same as it would be with the default script.

All the problems I mentioned are either come directly from these thins not being session managed in the usual way. (So I don't think there will be any other problems)

About the fonts though, If you want to use font overriding, just copy that section from your existing startkde3 script. (I just removed it because it took time and it is not something most people need)

If you have any other problems just e-mail me. - Apr 08 2002