OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Sound On Resume
daniel3000
post Jan 9 2007, 02:07 AM
Post #1





Group: Members
Posts: 1,002
Joined: 28-April 05
From: Germany
Member No.: 7,027



Hi Meanie,

quoting your post from thread "Pdaxrom For C3000 (based On Beta1/beta3)":

QUOTE(Meanie @ Jan 9 2007, 08:04 AM)
There is a config file /home/root/Choices/pdaxii13.conf which specifies what happens during startup, ie load torsmo, play welcome sound, play beep during resume. These options can be set to true or false, but they only come into effect after X is restarted.

The volume is preset using mixmos. Just run mixmos and save the volume state after you have set your preferred settings.
*


this is funny, I also had the idea of adding a sound to the beginning of the resume process in order to let the user know that resume is going on, even while the backlight is still off.
However, it caused problems when I tried it. Maybe you have an idea about the reason?

I have created an apm script which does a mixmos -d /dev/dsp -s 4 on suspend and

mixmos -d /dev/dsp -r 1 (profile 1 stored manually before, loud setting)
esdplay /usr/share/sounds/resume.wav
mixmos -d /dev/dsp -r 4

on resume.
Have named the script links this way:

/etc/apm/suspend.d/500resumesound and
/etc/apm/resume.d/10resumesound

However, after suspend / resume the keyboard is dead! The sound works (even if too late for my taste, I hoped to get it almost directly after switching on the Zaurus). But no application gets keyboard input anymore. I have to reboot the Zaurus.

Maybe you know already what the reaons is? Is there a special order in the scripts I have to take care of when playing a sound or using the mixer device?

Thanks!
daniel
Go to the top of the page
 
+Quote Post
Meanie
post Jan 9 2007, 04:07 AM
Post #2





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(daniel3000 @ Jan 9 2007, 08:07 PM)
Hi Meanie,

quoting your post from thread "Pdaxrom For C3000 (based On Beta1/beta3)":

QUOTE(Meanie @ Jan 9 2007, 08:04 AM)
There is a config file /home/root/Choices/pdaxii13.conf which specifies what happens during startup, ie load torsmo, play welcome sound, play beep during resume. These options can be set to true or false, but they only come into effect after X is restarted.

The volume is preset using mixmos. Just run mixmos and save the volume state after you have set your preferred settings.
*


this is funny, I also had the idea of adding a sound to the beginning of the resume process in order to let the user know that resume is going on, even while the backlight is still off.
However, it caused problems when I tried it. Maybe you have an idea about the reason?

I have created an apm script which does a mixmos -d /dev/dsp -s 4 on suspend and

mixmos -d /dev/dsp -r 1 (profile 1 stored manually before, loud setting)
esdplay /usr/share/sounds/resume.wav
mixmos -d /dev/dsp -r 4

on resume.
Have named the script links this way:

/etc/apm/suspend.d/500resumesound and
/etc/apm/resume.d/10resumesound

However, after suspend / resume the keyboard is dead! The sound works (even if too late for my taste, I hoped to get it almost directly after switching on the Zaurus). But no application gets keyboard input anymore. I have to reboot the Zaurus.

Maybe you know already what the reaons is? Is there a special order in the scripts I have to take care of when playing a sound or using the mixer device?

Thanks!
daniel
*



accessing /dev/dsp after a resume somehow locks the keyboard. i don't know why, but if you disable respawning of esd in /etc/esd.conf, it doesn't happen so frequently.
also, i use the buzzer instead of the esd to have just a simple sound.
Go to the top of the page
 
+Quote Post
daniel3000
post Jan 9 2007, 05:07 AM
Post #3





Group: Members
Posts: 1,002
Joined: 28-April 05
From: Germany
Member No.: 7,027



aha.. thanks!
How can I control the buzzer?
I prefer a safe solution without the slightest chance to lock the keyboard. biggrin.gif

Or what about directly playing the sound over /dev/dsp without the use of esd?
Do you think that would be safe enough? But it would probably cause problems if another application is active which uses sound (maybe even esd locks /dev/dsp?)

Just trying... hm..
cat SOMEWAVFILE.wav > /dev/dsp sounds strange. Probably wrong format? But at least it sort of works.

daniel
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 29th July 2015 - 12:01 PM