Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#2 closed enhancement (fixed)

Support for extended system beeps

Reported by: axel.hagedorn@… Owned by: dmik
Priority: minor Component: psi
Version: psi-0.10-os2-b1 Keywords: beep, sound


As far as I have seen and tried out - if you want to use system beeps instead of real sounds you can only use "!beep" for one single beep for an event. It would be very nice to be able to specify more than just one beep and differences in frequency and duration between different beeps - like it was possible in pwICQ, where you could specify a beep event like %frequency1,duration1,frequency2,duration2,.... (I always used %800,100,800,100,800,100,500,150 for example.) Any chance this could be added to the !beep parameter?

Change History (5)

comment:1 Changed 14 years ago by dmik

Status: newassigned

Technically, it's not that difficult. I'll see if I can quickly add this functionality.

P.S. I did not know that !beep can be understood as a sound file name :)

comment:2 Changed 14 years ago by dmik

Resolution: fixed
Status: assignedclosed

Done in r54. The new format is !beep[:freq:duration], so it's backwards-comatible. So far, works on OS/2 and Win32 only. The frequency range is 37-32767 Hz, the duration is 1-3000 ms.

It took me a bit longer than I expected: I had to dedicate a thread for that task because DosBeep? blocks the execution until complete (so that specifying too long beeps would freese the UI). I hope it's worth it :)

comment:3 Changed 14 years ago by dmik

Resolution: fixed
Status: closedreopened

Oops, I didn't notice you meant the sequence of sounds. Will implement that, since it seems to be rather easy now.

comment:4 Changed 14 years ago by dmik

Resolution: fixed
Status: reopenedclosed

Ok, as of r55, the new format is !beep[:freq[,dur]]....

comment:5 Changed 14 years ago by axel.hagedorn@…

Thanks a whole lot! Was already wondering how to interpret the format when I wanted to have more than just one beep. :-) I'm eagerly awaiting next build!


Note: See TracTickets for help on using tickets.