I set an alarm today for 4 pm EDT (or 16:00). Nothing happened at that time while the program was minimized to the system tray area. In fact, I was watching a video while waiting for the alarm, when I noticed that it was 4 minutes after the hour, and so I quickly switched to the other event.
At approximately 10 after the hour, I clicked on the icon to restore and heard a chime sound. I had to assume it was that, but no message popped up.
I'm not sure I can rely upon Reminders. I obviously do not know what I'm doing, but I feel that I am doing this according to the instructions.
I am using Debian 10 with Xfce 4.12.
Thank you.
I can only suggest that you do a few tests, for you own peace of mind.
I have just tested a reminder for 3 minutes into the future, with no repeat, whilst playing audio in a player, in full screen mode and designated "always on top", ditto for a video and both reminders popped onto the screen.
Neither a reminder nor a snooze should be out by more than 2 minutes.
Reminders does not attempt to be a stopwatch, it checks existing reminders and snoozes every 2 minutes to see if any notices should be posted.
Do reminders and or snoozes go missing, yes they do, if they are deemed past and therefore not relevant as a reminder. No point in being reminded that you should have done something yesterday. Missed reminders and snoozes are cleaned out when the program starts. The exception to this rule, is for those reminders which repeat weekly or a longer period or those reminders marked with "Keep a copy", although those are only available to view and are not active.
The devil is in the detail (semantics and punctuation).
1. The accuracy of the issuance of a reminder or snooze will be within a 2 minute window of its designated time, due to the fact that the program only checks, every 2 minutes, to be as lightweight a process, as it can be.
2, ...and snoozes every 2 minutes
"checks existing reminders and snoozes, every 2 minutes" (i.e. every 2 minutes, it checks for reminders and snoozes, that need to be issued)
3. There is no choice of chimes/alarms. What is "played" is /usr/share/reminders/sounds/reminder.ogg You may overwrite that file with the chime/alarm of your choosing. The command used to issue it is '/usr/bin/play -q ' So check beforehand that it will work and note it must be called reminder.ogg and be converted to ogg format. This might well be addressed in a future version.
Much of this is covered in the help documentation.
I laboured long and hard, documenting this package, it would be nice to think that people made use of it.
Can't get custom sounds to play
Last edit: pizzipie 2021-10-19
That url to the pdf is not working for me.
Perhaps you could try again.
Rolf
On 19/10/2021 19:28, pizzipie wrote:
Related
Tickets: #4
Reminders on Linux for issuing reminders of
things you might forget
HI, I have recently installed:
Reminders : Version 2.3.6
This python script was written specifically to run under Linux.
My Computer Setup is as follows:
System:
Host: rick-MS-7C02 Kernel: 5.4.0-88-generic x86_64 bits: 64
Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.3 LTS (Focal Fossa)
Machine:
Type: Desktop System: Micro-Star product: MS-7C02 v: 1.0
serial: <superuser root="" required="">
Mobo: Micro-Star model: B450 TOMAHAWK MAX (MS-7C02) v: 1.0
serial: <superuser root="" required=""> UEFI: American Megatrends v: 3.70
date: 06/09/2020
My Problem:
Reminders doesn’t play sounds that I have converted to .ogg format, confirmed to play
with Rhythmbox, and placed into usr/share/reminders/sounds. I have discovered a
discrepancy in documentation between:
The Manual 2.3.6 :
<quote>
You may choose a sound to be played when a reminder is issued, with a similar option for a
snooze being issued.
Available sounds/chimes are whatever you place in the /usr/share/reminders/sounds directory or the
option None, for no sound.
Take care that you place functioning audio files in /usr/share/reminders/sounds
Sound files may be manually entered which do not reside in /usr/share/reminders/sounds and will
be included in the list of available sounds for as long as they are a selected option. If they cease to
be a selected option, they are removed from the list.
Essentially, if it’s important to you, copy it permanently, into /usr/share/reminders/sounds
Upon selection, or manual entry, a sound file is tested.
Remember to click the Update button to save your changes.
</quote>
Reminders on Linux for issuing reminders of
things you might forget
and:
https://sourceforge.net/p/linux-reminders/tickets/4/
Linux-reminders
A simple reminder Gui for Linux using wxpython
Brought to you by: rolfofsaxony </superuser></superuser>
4 No Certain Alarm
Milestone: 1.0 , Status: open , Owner: nobody, Labels: None, Updated: 2021-06-04
Created: 2021-05-28, Creator: KitchM , Private: No
<quote>
Rolf - 2021-06-04
The devil is in the detail (semantics and punctuation).
1. The accuracy of the issuance of a reminder or snooze will be within a 2 minute window of its
designated time, due to the fact that the program only checks, every 2 minutes, to be as lightweight a
process, as it can be.
2, ...and snoozes every 2 minutes
"checks existing reminders and snoozes, every 2 minutes" (i.e. every 2 minutes, it checks for reminders
and snoozes, that need to be issued)
3. There is no choice of chimes/alarms. What is "played" is /usr/share/reminders/sounds/reminder.ogg
You may overwrite that file with the chime/alarm of your choosing. The command used to issue it is
'/usr/bin/play -q ' So check beforehand that it will work and note it must be called reminder.ogg
and be converted to ogg format. This might well be addressed in a future version.
Much of this is covered in the help documentation.
I laboured long and hard, documenting this package, it would be nice to think that people made use of
it.
</quote>
Question:
How can I get any .ogg Audio file to play???
Thanks in advance, RP
I don't believe there is a discrepency.
Sound file choices were added in version 2.3.6 and documented in the changelog, the Readme and the PDF documentation.
A test is performed on the selected sound file when you make the selection, within the configuration screen.
The command issued is:
/usr/bin/play -q /usr/share/reminders/sounds/your_sound_file.xxx
where the xxx suffix is any file type that the 'sox' program can play.
The sox program is a dependency of 'reminders' so it should on your system.
I suggest testing the file manually, on the command line ( command as above )
If all else fails, try running 'reminders' on the command line and see if you get any error messages when the sound should play.
It goes without saying, that for me ogg files do work.
Last edit: Rolf 2021-10-21
Thanks for reply Rolf!
So I used /usr/bin/play -q /usr/share/reminders/sounds/.ogg to play all sounds that I placed in that directory w/o a problem.
But *what about the names???
<quote> So check beforehand that it will work and note it must be called reminder.ogg and be converted to ogg format.
</quote> .
My version of Reminders came with an audio file named 'areminder.ogg' which works fine. Further, just tried setting a reminder and using an audio file named 'alarm.ogg' and it worked fine.
**Another Question: **
After Computer Shutdown is there a way to have 'Reminders' resume after re-boot w/o manually re-starting it?
In Control Center resides Startup Applications
Just add /usr/bin/reminders
On 21/10/2021 19:12, pizzipie wrote:
Related
Tickets: #4