|
From: Tim C. <tc...@ra...> - 2010-05-17 00:23:43
|
So, if you set the espeak volume via pavucontrol, do you still get the initial high volume next time you run the application or is it then staying at that volume? Soumen banerjee writes: > HI, > eSpeak does register with pulseaudio, and users can set the volume > from pavucontrol, the problem is the initial spike in volume. I > checked with ldd and the libespeak.so Im using is built against > pulseaudio instead of portaudio. > Regards > Soumen > > On Mon, May 17, 2010 at 5:29 AM, Tim Cross <tc...@ra...> wrote: > > > > > >> Hi, > >> Im sure the other applications are indeed using pulseaudio. As such, I > >> can see their names in the "applications" tab in "Sound Preferences" > >> in Gnome. > >> I can see that eSpeak comes up as an application in the above > >> mentioned place as well. The volume to eSpeak is set to full, while > >> the other apps like mplayer etc are set to less than half. As far as I > >> can see, since pulseaudio supports different volumes for different > >> applications, and since pulse has no idea of what volume we want, it > >> just defaults it to 100%. Since it isnt possible to have that high > >> volume at 40% of speaker output, it sets the speaker volumes to 100% > >> as well. > >> Perhaps I need to use pulse-audio development libraries to set the > >> volume for this app before pulse does it for me ;) > >> Do any of you have an idea of what exactly I need to do? > >> Regards > >> Soumen > >> p.s. This is all conjecture based on what is happening at the > >> volumes.. If any of you have a better method of fixing this, please > >> let me know. I know this is beyond the purview of espeak but still, I > >> would appreciate some help :) > > > > I'm only guessing here, but as other apps appear to somehow register > > themselves with pulseaudio i.e. the fact you see them listed in the > > pavucontrol program with a name, then it should be possible to also name and > > register your own application. This would then allow the end user to use > > pavucontrol to set the volume, which I blieve, will be carried across > > settings. I'm not familiar witht he pulseaudio API, so don't know how this is > > done. > > > > Something else that may be worth looking at is verifying how libespeak has > > been built. I found the problems I had were all due to espeak being linked > > against portaudio. Once I re-built the package to link directly to pulseaudio > > rather than portaudio, all the issues I had were resolved. > > > > Some distributions are still linking the epseak library against portaudio as > > this enables the lib to work on both pulseaudio and non-pulseaudio based > > systems. If your distro is doing this, it is possible the volume issues you > > have observed are related to portaudio rather than pulseaudio i.e. there is > > another layer of abstraction that could be affecting things. > > > > You can probably determine this by running ldd on the libespeak shared > > library. > > > > Tim > > -- Tim Cross tc...@ra... There are two types of people in IT - those who do not manage what they understand and those who do not understand what they manage. -- Tim Cross tc...@ra... There are two types of people in IT - those who do not manage what they understand and those who do not understand what they manage. |