
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
Versatile alarm script for Amarok. Includes the ability to set different alarm times for each day, control volume fading, use wakeup playlists, enable snoozing, and take a nap.
12 years ago
1.4.0:
- nl translation (thanks to garo)
1.3.3:
- fix crash when amarok stop playing
1.3.2:
- fix configuration not being shown
1.3.1:
- Fixed problems with accents in the playlist box.
1.3.0:
- French translation
- Italian translation (thanks to Guybrush88)
- some minor bugfixes
1.2.0:
- Added dynamic playlists support
- Repeat option
1.1.1
- Retro-compatibility with python 2.4
- bugfixe (handling volume option)
1.1
- Adding some options: volume update when fading; stop fading when amarok is stoped or paused, etc.
- some bugfixes
- reorganisation of gui
1.0.1
-updated README. we need python 2.5.
1.0.0 Rewrittal of much code
- fading stop when amarok pause, stop or has it's volume changed. To work with replaygain, an option is added to decrease sensibility
- stop more cleanly when killed by amarok
- somme bugfixes to avoid problems with accents
0.9.1 Bugfixes
- disable launch by KDE session manager
- fix custom playlist startup
0.9
GUI and code overhaul. Added option for random track on startup. There are many changes in this version, please let me know if you encounter any bugs.
0.6.1
*Hotfix* fix custom playlist startup
0.6
- changes to volume fading (bug fixes and feature add)
0.5.1
- use kdialog so snooze pops into foreground
0.5
- added snooze feature
12 years ago
1.4.0:
- nl translation (thanks to garo)
1.3.3:
- fix crash when amarok stop playing
1.3.2:
- fix configuration not being shown
1.3.1:
- Fixed problems with accents in the playlist box.
1.3.0:
- French translation
- Italian translation (thanks to Guybrush88)
- some minor bugfixes
1.2.0:
- Added dynamic playlists support
- Repeat option
1.1.1
- Retro-compatibility with python 2.4
- bugfixe (handling volume option)
1.1
- Adding some options: volume update when fading; stop fading when amarok is stoped or paused, etc.
- some bugfixes
- reorganisation of gui
1.0.1
-updated README. we need python 2.5.
1.0.0 Rewrittal of much code
- fading stop when amarok pause, stop or has it's volume changed. To work with replaygain, an option is added to decrease sensibility
- stop more cleanly when killed by amarok
- somme bugfixes to avoid problems with accents
0.9.1 Bugfixes
- disable launch by KDE session manager
- fix custom playlist startup
0.9
GUI and code overhaul. Added option for random track on startup. There are many changes in this version, please let me know if you encounter any bugs.
0.6.1
*Hotfix* fix custom playlist startup
0.6
- changes to volume fading (bug fixes and feature add)
0.5.1
- use kdialog so snooze pops into foreground
0.5
- added snooze feature
Bezierk
11 years ago
Two days ago my weekalarm didn't start when it was supposed and since then I'm unable to open the configuration page. Meanwhile I've formated and reinstalled my system and I'm now running debian testing (squeeze).
The test script opens the config dialog and in general terms it all works fine except for weekalarm. It used to open underneath amarok but right now it will simply not respond to the button.
the versions are:
Amarok - 1.4.10-3+b1
Python (minimal)- 2.4.6-2 (i also have 2.5 just in case)
Python-qt3 - 3.17.4-1
Python-qt4 - 4.4.2-4
Weekalarm - latest from amarok's "get more"
Taking in consideration that i run gnome and that amarok runs just fine: could there be any KDE component that could be missing and that's necessary?
Any help will be as appreciated as the script itself as it will make me wake up in a better mood.
Report
bitlz
11 years ago
$ ln -s ~/.kde/share/apps/amarok/scripts/weekalarm/weekalarmrc ~/.kde/share/apps/amarok/scripts-data/weekalarmrc
After creating symlink, config dialog will work.
Report
Bezierk
11 years ago
i've just deleted the scripts folder, reinstalled weekalarm from the get more button, activated it and clicked configure. this is the log file of these actions:
Quote:
04/28/2009 02:12:33 AM weekalarm beginning (in MainThread) [INFO]
04/28/2009 02:12:33 AM [<Thread(sdinReader Thread, started)>] (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM [<Thread(sdinReader Thread, started)>, <_Timer(Thread-1, started)>] (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM executing `amarok.player.getVolume()' (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM got `100' from amarok (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM creating config dialog (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM None (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM load config at weekalarmrc (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM Reading configuration has failed, using default (in MainThread) [WARNING]
04/28/2009 02:12:33 AM saving settings (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM t:u'null' -> 'null' (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM write config to weekalarmrc (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM update (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM weekalarm.read (in MainThread) [DEBUG]
04/28/2009 02:12:33 AM Setting timer to None seconds from now (in MainThread) [DEBUG]
04/28/2009 02:12:34 AM ^configure$ match configure (with {}) (in sdinReader Thread) [DEBUG]
04/28/2009 02:12:34 AM loading settings (in sdinReader Thread) [DEBUG]
04/28/2009 02:12:34 AM update (in sdinReader Thread) [DEBUG]
just like before no response from the button and i'm hoping this helps.
have i thanked you for writing this script?
Report
maxischmeii
11 years ago
Report
Bezierk
11 years ago
if i run amarok/scripts/weekalarm/config.py the config dialog appears and is editable and it will save the settings under amarok/scripts/weekalarm/weekalarmrc. the other weekalarmrc file will remain unchanged.
Report
maxischmeii
11 years ago
Report
filpiranesi
11 years ago
It seems that this is the only way to run it :\
Report
filpiranesi
11 years ago
I have exact the same problem.
I upgraded to 9.04 and then uninstalled amarok 2 and installed amarok 1.4.10.
Well on 8.10 the configure page was always hiding somewhere but i could always find it.
Now it seems that it just doesn't open.
Every other script works fine on amarok exept the weekalarm.
I hope you can fix this because it is a very nice script and very helpfull!
Thanx in advance.
Report
kamaraju
11 years ago
$python ./weekalarm.py
12:55:16 AM weekalarm beginning [INFO]
call failed
12:55:16 AM Return code of amarok.player.getVolume() was 1 [ERROR]
Traceback (most recent call last):
File "./weekalarm.py", line 386, in <module>
main()
File "./weekalarm.py", line 379, in main
app=WeekAlarm()
File "./weekalarm.py", line 78, in __init__
self.dcop.send("player", "getVolume")
File "/home/rajulocal/weekalarm/weekalarm/amarok.py", line 40, in send
raise self.DCOPError
amarok.DCOPError
^C12:55:28 AM got EOF [INFO]
Exception exceptions.KeyboardInterrupt in <module 'threading' from '/usr/lib/python2.5/threading.pyc'> ignored
I am using Debian, python 2.5.2, amarok 1.4.10.
If amarok is already running, then there is no problem.
Report
maxischmeii
12 years ago
This is still pre-alpha, and so has only a small subset of the weekalarm features, but it works for me (tm).
Note that it is based on pygtk, so you will need to install the python-gtk package.
Report
laiseng
12 years ago
but i cant seems to start it
Report
maxischmeii
12 years ago
Report
laiseng
12 years ago
I've clicked on install button and choose week alarm tar.bz2 file and it says install successful
then i dont see any week alarm icon in the list of plugins windows
Report
maxischmeii
12 years ago
Report
jupiterzoom
12 years ago
Report
staudi009
12 years ago
"Repeat" turns on "Repeat Track", definitely wrong, I would expect "Repeat Playlist".
"Random" switched on "Random Albums", I feel correct with "Random Tracks".
Would not it be good to be able to define the modes within a ComboBox?
Regards, Staudi
Report
Hydranmenace
12 years ago
Report
maxischmeii
12 years ago
Report
Norwat
12 years ago
heres the log... i can post the hole thing offline if necessary
09-10-2008 23:11:50 ^engineStateChange\s*:\s*playing$ match engineStateChange: playing (with {}) (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 ^engineStateChange\s*:\s*(empty)$ match engineStateChange: empty (with {}) (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 exiting (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 setting finished flag (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 waiting for the finished flag (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 [<_MainThread(MainThread, started)>, <Thread(sdinReader Thread, started)>, <_Timer(Thread-2, started)>] (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 [<_MainThread(MainThread, started)>, <Thread(sdinReader Thread, started)>, <_Timer(Thread-2, started)>] (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 Joining:<_Timer(Thread-2, started)> (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 done (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:53 amarok wait returned, joining timer (in sdinReader Thread) [DEBUG]
09-10-2008 23:11:54 weekalarm finished (in MainThread) [INFO]
09-10-2008 23:11:54 [<_MainThread(MainThread, started)>] (in MainThread) [DEBUG]
Report
maxischmeii
12 years ago
Report
Norwat
12 years ago
thanks
Report
antieuclid
12 years ago
"Traceback (most recent call last):
File "/home/wiley/.kde/share/apps/amarok/scripts/weekalarm/weekalarm.py", line 40, in <module>
import amarok
File "/home/wiley/.kde/share/apps/amarok/scripts/weekalarm/amarok.py", line 3, in <module>
from qt import *
ImportError: No module named qt"
I'm running Ubuntu 8.04 with Gnome 2.22.3 and Amarok 1.4.9.1.
Report
antieuclid
12 years ago
Report
Contrast
12 years ago
Report
XaMou
12 years ago
- fix configuration not being shown
I'm using Amarok 1.4.9.10 on Ubuntu 8.10, and the configuration windows are not bing shown :/ .
Report