Re: [fso based] Simplified mixer app

[Patryk Benderz]

Hi Al,
do you want me to add it to CU, or is it too early to show this app to
average user?

-- 
Patryk LeadMan Benderz
Linux Registered User #377521
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments


Email secured by Check Point

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Evgeniy Ginzburg]

On Tue, Oct 13, 2009 at 2:10 PM, Patryk Benderz patryk.bend...@esp.pl wrote:
 Hi Al,
 do you want me to add it to CU, or is it too early to show this app to
 average user?

It's newer to early, add it.

-- 
So long, and thanks for all the fish.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

On Tuesday 13 October 2009, Evgeniy Ginzburg wrote:
 On Tue, Oct 13, 2009 at 2:10 PM, Patryk Benderz patryk.bend...@esp.pl 
wrote:
  Hi Al,
  do you want me to add it to CU, or is it too early to show this app to
  average user?
 
 It's newer to early, add it.

I agree. It's on the community list so it's fair game for the community 
update.

The only cautionary note is to remember to back up any modified state files 
since there is a report of a messed up state that we haven't got to the bottom 
of yet.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

On Friday 02 October 2009, Laszlo KREKACS wrote:
 On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS
 
 laszlo.krekacs.l...@gmail.com wrote:
  But there is so many things what changed, that Im completely lost.
 
 Just wanted to notice you, that restoring the original
 gsmhandset.state file (and rebooting)
 does solve my problem. Im able to take call, and hear the other party.
 (and he able to hear me).
 
 Although your program was nice. It changed the mic way better, what I
 had. Other party
 said, its much louder and clearer.
 
 Hope you can sort out, why the broken .state file is broken. And where
 the bugs comes from ...

Updated version now available:
http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py

I can't reproduce your problem with faulty saves. You should find some extra 
debug output if you start it in a terminal, and message boxes so you know 
something has happened. This will show which scenario it asked fso to save, so 
you can check whether is asked to save the right one. It's possible we have 
different versions of frameworkd. I'm testing with:

r...@om-gta02 ~ $ opkg list_installed frameworkd
frameworkd - 0.9.5.9+gitr1697+ed29786daceccefe918ce3911e3b6fb7f2efb08c-r0 -

Other changes:
* More scenarios simplified.
* With unhandled scenarios there is a message instead of a blank screen or 
crash

I looked into adding the alsa channel number to the name in the advanced view, 
but pyalsaaudio doesn't make it available.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Mikhail Umorin]

Thanks for the app, Al (see below)

On Monday 05 October 2009 19:43:37 Al Johnson wrote:
 On Friday 02 October 2009, Laszlo KREKACS wrote:
  On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS
 
  laszlo.krekacs.l...@gmail.com wrote:
   But there is so many things what changed, that Im completely lost.
 
  Just wanted to notice you, that restoring the original
  gsmhandset.state file (and rebooting)
  does solve my problem. Im able to take call, and hear the other party.
  (and he able to hear me).
 
  Although your program was nice. It changed the mic way better, what I
  had. Other party
  said, its much louder and clearer.
 
  Hope you can sort out, why the broken .state file is broken. And where
  the bugs comes from ...

 Updated version now available:
 http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py


In simple view if I slide volume all the way to the right, it goes to 101 
(not 100) is that correct?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

On Tuesday 06 October 2009, Mikhail Umorin wrote:
 Thanks for the app, Al (see below)
 
 On Monday 05 October 2009 19:43:37 Al Johnson wrote:
  On Friday 02 October 2009, Laszlo KREKACS wrote:
   On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS
  
   laszlo.krekacs.l...@gmail.com wrote:
But there is so many things what changed, that Im completely lost.
  
   Just wanted to notice you, that restoring the original
   gsmhandset.state file (and rebooting)
   does solve my problem. Im able to take call, and hear the other party.
   (and he able to hear me).
  
   Although your program was nice. It changed the mic way better, what I
   had. Other party
   said, its much louder and clearer.
  
   Hope you can sort out, why the broken .state file is broken. And where
   the bugs comes from ...
 
  Updated version now available:
  http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py
 
 In simple view if I slide volume all the way to the right, it goes to 101
 (not 100) is that correct?

That depends which slider it is ;-)

It is correct. I map the alsa channels to a single slider giving equal 
increments covering the full range possible from those channels. For the 
outputs this is usually gives steps 0 to 101 while for the mic it is usually 0 
to 119. If you uncomment self.gta02mixer.PrintGains() and start it from the 
cli it will show you the gain setting in dB for each step in the debug output. 
Unfortunately pyalsaaudio only accepts integer percentages when setting 
volume, so there are rounding errors when actually setting the volumes. 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Mikhail Umorin]

On Tuesday 06 October 2009 12:28:37 Al Johnson wrote:
 On Tuesday 06 October 2009, Mikhail Umorin wrote:
  Thanks for the app, Al (see below)
 
  On Monday 05 October 2009 19:43:37 Al Johnson wrote:
   On Friday 02 October 2009, Laszlo KREKACS wrote:
On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS
   
laszlo.krekacs.l...@gmail.com wrote:
 But there is so many things what changed, that Im completely lost.
   
Just wanted to notice you, that restoring the original
gsmhandset.state file (and rebooting)
does solve my problem. Im able to take call, and hear the other
party. (and he able to hear me).
   
Although your program was nice. It changed the mic way better, what I
had. Other party
said, its much louder and clearer.
   
Hope you can sort out, why the broken .state file is broken. And
where the bugs comes from ...
  
   Updated version now available:
   http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py
 
  In simple view if I slide volume all the way to the right, it goes to
  101 (not 100) is that correct?

 That depends which slider it is ;-)

 It is correct. I map the alsa channels to a single slider giving equal
 increments covering the full range possible from those channels. For the
 outputs this is usually gives steps 0 to 101 while for the mic it is
 usually 0 to 119. If you uncomment self.gta02mixer.PrintGains() and start
 it from the cli it will show you the gain setting in dB for each step in
 the debug output. Unfortunately pyalsaaudio only accepts integer
 percentages when setting volume, so there are rounding errors when actually
 setting the volumes.


I was talking about Stereo Out for Speaker (when not in call). Sorry to be 
unclear. So, how does the simple slider correspond to Bypass and Headphone 
in the advanced view? Or are those things all different controls? Moving the 
simple speaker slider seem to change Bypass and Headphone, but at different 
rates for different ranges of the simple slider.  When I max out the simple 
slider (to 101), bypass and headphone are at 100, but at lower simple slider 
settings they change very non-linear.

This was probably discussed numerous times. But your visual  application makes 
the channels easier to control and I finally feel that I have a chance to get 
the volume I want during calls. It's all so confusing What's a good place 
to learn the relations between all the channels/controls/bugs that make sound?




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

On Wednesday 07 October 2009, Mikhail Umorin wrote:
 On Tuesday 06 October 2009 12:28:37 Al Johnson wrote:
  On Tuesday 06 October 2009, Mikhail Umorin wrote:
   Thanks for the app, Al (see below)
  
   On Monday 05 October 2009 19:43:37 Al Johnson wrote:
On Friday 02 October 2009, Laszlo KREKACS wrote:
 On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS

 laszlo.krekacs.l...@gmail.com wrote:
  But there is so many things what changed, that Im completely
  lost.

 Just wanted to notice you, that restoring the original
 gsmhandset.state file (and rebooting)
 does solve my problem. Im able to take call, and hear the other
 party. (and he able to hear me).

 Although your program was nice. It changed the mic way better, what
 I had. Other party
 said, its much louder and clearer.

 Hope you can sort out, why the broken .state file is broken. And
 where the bugs comes from ...
   
Updated version now available:
http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py
  
   In simple view if I slide volume all the way to the right, it goes to
   101 (not 100) is that correct?
 
  That depends which slider it is ;-)
 
  It is correct. I map the alsa channels to a single slider giving equal
  increments covering the full range possible from those channels. For the
  outputs this is usually gives steps 0 to 101 while for the mic it is
  usually 0 to 119. If you uncomment self.gta02mixer.PrintGains() and start
  it from the cli it will show you the gain setting in dB for each step in
  the debug output. Unfortunately pyalsaaudio only accepts integer
  percentages when setting volume, so there are rounding errors when
  actually setting the volumes.
 
 I was talking about Stereo Out for Speaker (when not in call). Sorry to be
 unclear. So, how does the simple slider correspond to Bypass and
  Headphone in the advanced view? Or are those things all different
  controls? Moving the simple speaker slider seem to change Bypass and
  Headphone, but at different rates for different ranges of the simple
  slider.  When I max out the simple slider (to 101), bypass and headphone
  are at 100, but at lower simple slider settings they change very
  non-linear.

The 'simple' slider controls all the sliders in that group in the 'advanced' 
view to give smooth control of the overall volume. In this case that's Bypass 
and Headphone. The changes in individual controls may look nonlinear, but 
their combination produces even steps while avoiding combinations likely to 
cause distortion. That's the idea anyway. You can see the combinations in the 
lookup tables in the top 3/4 of the script if you're interested.

 This was probably discussed numerous times. But your visual  application
  makes the channels easier to control and I finally feel that I have a
  chance to get the volume I want during calls.

Great! That was the intention.

  It's all so confusing

So people tell me ;-) Compared to most instrumentation systems it's a breeze!

  What's a good place to learn the relations between all the
  channels/controls/bugs that make sound?

Start with the wiki. The Neo1973 page has an annotated block diagram that's 
actually for the Freerunner. Both pages give some info on which volume 
settings affect what in different alsa states. With the information there, and 
by looking at the alsa state files, you will be able to see how the switch 
settings route audio signals through the mixer chip. You can then refer to the 
Wolfson datasheet.

http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem
http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Michele Brocco]

On 10/2/09, Al Johnson openm...@mazikeen.demon.co.uk wrote:
 On Friday 02 October 2009, Michele Brocco wrote:
 cool idea!

 would be nice if through this App we could finally make sound coming
 through earpiece with the voip-handset state file. Still struggling
 with it

 This app has nothing to do with that I'm afraid. It should eventually give a
 slider each for mic and earpiece, but that'll just tweak the settings in
 voip-
 handset.state slightly. It won't do state switching on answer or hangup, or
 sort any fundamental issues with the sound config. Problems with voip config
 are for another thread though.

I am aware of that, but u can sort of experiment with the volumes if
finally the sound can come through the earpiece which is not working
now.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

Thanks for the feedback. The local beer festival may slow down the fixes 
though. I'll try to pull everything into one reply...

On Friday 02 October 2009, Laszlo KREKACS wrote:
 There have been many attempts to implement volume control;)
 Angus looked into it, did two versions (gtk, and after elementary)

This one is derived form Angus's fso-mixer.py, and the Advanced view should 
look and behave almost identically. The novel part is bringing several alsa 
controls into one slider, so I was hoping for feedback on how well that worked 
at avoiding distortion on the gsm mic or the earpiece. Having said that I can 
see that I may need to improve the GUI to get more people testing it, and to 
make it more useful for people :-)

 I have also researched some of the things.
 
 Nice to see, that there is an another attempt. I hope you will done it
  right;)
 
 I have only one suggestion:
 Please implement a help button on every near every group, where you
 explain shortly the most essential infos about the options.

That seems reasonable. The aim is to have a single slider for each group in 
the simple view. Showing multiple sliders in the simple view is the fallback 
for where there isn't a lookup table for mapping them to a single slider yet. 
If I do it then it would appear for individual sliders whichever view they 
were in though.

 I just launched your program and it picked up the stereout .state file, and
 displayed the sliders. Screenshot:
 http://laszlo.krekacs.googlepages.com/fso-mixer-screenshot.png
 
 The screenshot is a bit wrong, because it does show the Stereo Out
  string, in the middle (above Microphone). So it looks normal in real life,
  dunno why the
 screenshot didnt included it. (maybe it was rendering while captured the
  screen)
 
 I would like see the following help buttons:
 Stereo Out [help]
 Microphone [help]
 Speaker [help]

I would like you to see only one slider in the simple view ;-) I just need to 
assemble the lookup table. I should have done that before release since it's 
the first one people will see.

 Help of the Stere Out page should be something similar:
 
 Stereo Out state is corresponds, when the phone is idle
 (ie waiting for incoming call, or playing music).
 Microphone is disabled in this state, and Speaker corresponds to
 the speaker at the bottom near to the Neo text.
 [Should show a picture with a neo indicating where the microphone and
 the speaker are.]
 
 
 Help of Microphone page should be something similar:
 
 Mic2 corresponds to XXX alsa settings (or group of alsa settings)
 Mono corresponds to XXX alsa setting
 Mono Sidetone corresponds to XXX alsa setting.
 Microphone can be altered also by this alsa settings: XXX,YYY, ZZZ
 However it is strongly discouraged to touch them.

The names are those returned by pyalsaaudio for that channel, and match the 
ones in alsamixer. I'll see if it can give me anything else like channel 
number though, or perhaps code it into the lookup. I sense some refactoring 
coming on...

 Advices:
 The monoside tone is used for XXX. You should hear XXX, when you
 raise it. Highest state does not automatically means better/louder
 voice transmitted.
 
 Also some other advices how to correctly adjust the sliders. Like on
 the wiki page:
 reduce #5 by some 15..30 steps
 do testcall:
 you get very low volume at far end. but tone should be clear, no
 clipping (sharp agressive noise)
 if there is clipping: reduce #48 by one step (i.e. to 2)
 then adjust #5 to your preferences and taste
 
 
 
 Keep in mind that your program should be self-explanatory and
 useful for even for the first time user.

That's the aim.

 If you want the explanatory pictures, Im sure somebody can draw it
 for you. If nobody step up, I look into what can I make;)
 
 
 There is also some AT command to affect the voice quality.
 Mickey told me, that on his freerunner, value 4 works better then
 value 5 (the default).
 I think it should also be included in your program, to give the
 ability to play with it...
 (if the user are still not satisfied with the result).

There is an AT command for the gsm playback volume, and an fso call to adjust 
it. I haven't found anything that gives a setting to dB mapping for this 
function though, so I can't easily include it in the gain mapping. The best I 
could do at the moment is to add an extra slider for it in the GSM states. If 
I do that I should probably add sliders for the bluez headset controls too. 

 Usability reports:
 
 IT is nice, that your program switch the display automagically when the
 incoming call happens.

You can thank Angus for that. I'm just building on his foundations.

 However I think these are defectives:
 1. when clicking on save there is no report what you did exactly, and was
  it successful.
 I think on shr, you should save the .state file to /usr/share/shr/scenarii/
  dir. So I expect something similar:
 Copying /usr/share/shr/scenarii/stereout.state to
 

Re: [fso based] Simplified mixer app

[Michele Brocco]

cool idea!

would be nice if through this App we could finally make sound coming
through earpiece with the voip-handset state file. Still struggling
with it

On Thu, Oct 1, 2009 at 11:24 PM, Al Johnson
openm...@mazikeen.demon.co.uk wrote:
 I've made mixer app that maps a single slider to multiple alsa channels, so
 you can have one slider for 'Mic' and another for 'earpiece'. It's based on
 Angus Ainslie's fso-mixer, but using lookup tables for which channels to show
 in which scenario, and for mapping the single slider to multiple channels.

 It's at proof of concept stage now, but should be as functional as fso-mixer.
 I hope. If you aren't using stock ones it would be a good idea to back them up
 before using it just in case! Feedback would be welcome.

 http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py

 Known bugs and missing features:
 * I haven't done mapping tables for all the mixer scenarios yet. Where they
 aren't done you will see the individual sliders as you would in fso-mixer.
 * Sometimes when the state changes a setting will be shown as 0 when it is in
 fact non-zero. If anyone spots why this happens I would love to know!
 * The volume sliders cover the whole possible range, while most people
 probably only ever need the top half or third.
 * pyalsaaudio only accepts integer percentages when setting volumes, not the
 actual mixer hardware values used in the lookup tables. This may give some
 uneven steps in volume.
 * When individual alsa channels are shown they use the alsa names. This is
 fine if you know that the 'headphone' mixer controls the speaker, and the
 'speaker' control is for the earpiece, let alone some of the more obscure
 names.


 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

On Thu, Oct 1, 2009 at 11:24 PM, Al Johnson
openm...@mazikeen.demon.co.uk wrote:
 Feedback would be welcome.

There have been many attempts to implement volume control;)
Angus looked into it, did two versions (gtk, and after elementary)

I have also researched some of the things.

Nice to see, that there is an another attempt. I hope you will done it right;)

I have only one suggestion:
Please implement a help button on every near every group, where you
explain shortly the most essential infos about the options.

I just launched your program and it picked up the stereout .state file, and
displayed the sliders. Screenshot:
http://laszlo.krekacs.googlepages.com/fso-mixer-screenshot.png

The screenshot is a bit wrong, because it does show the Stereo Out string,
in the middle (above Microphone). So it looks normal in real life,
dunno why the
screenshot didnt included it. (maybe it was rendering while captured the screen)

I would like see the following help buttons:
Stereo Out [help]
Microphone [help]
Speaker [help]

Help of the Stere Out page should be something similar:

Stereo Out state is corresponds, when the phone is idle
(ie waiting for incoming call, or playing music).
Microphone is disabled in this state, and Speaker corresponds to
the speaker at the bottom near to the Neo text.
[Should show a picture with a neo indicating where the microphone and
the speaker are.]


Help of Microphone page should be something similar:

Mic2 corresponds to XXX alsa settings (or group of alsa settings)
Mono corresponds to XXX alsa setting
Mono Sidetone corresponds to XXX alsa setting.
Microphone can be altered also by this alsa settings: XXX,YYY, ZZZ
However it is strongly discouraged to touch them.

Advices:
The monoside tone is used for XXX. You should hear XXX, when you
raise it. Highest state does not automatically means better/louder
voice transmitted.

Also some other advices how to correctly adjust the sliders. Like on
the wiki page:
reduce #5 by some 15..30 steps
do testcall:
you get very low volume at far end. but tone should be clear, no
clipping (sharp agressive noise)
if there is clipping: reduce #48 by one step (i.e. to 2)
then adjust #5 to your preferences and taste



Keep in mind that your program should be self-explanatory and
useful for even for the first time user.

If you want the explanatory pictures, Im sure somebody can draw it
for you. If nobody step up, I look into what can I make;)


There is also some AT command to affect the voice quality.
Mickey told me, that on his freerunner, value 4 works better then
value 5 (the default).
I think it should also be included in your program, to give the
ability to play with it...
(if the user are still not satisfied with the result).


Usability reports:

IT is nice, that your program switch the display automagically when the
incoming call happens.

However I think these are defectives:
1. when clicking on save there is no report what you did exactly, and was it
successful.
I think on shr, you should save the .state file to /usr/share/shr/scenarii/ dir.
So I expect something similar:
Copying /usr/share/shr/scenarii/stereout.state to
~/.simplemixer/backup/stereout-20091002-1424.state... Success!
Overwriting /usr/share/shr/stereout.state... Success!
Saving was successful, even after reboot you should have the same
voice experience as now.

2. When you adjusted the microphone while talking, and other hangup,
your program automagically switch back to stereout.state display
- no ability to save the adjusted gsmhandset.state (the state file
while talking)

We should be able to switch between states, and adjust/save them invidually.
Also you should display which one is active currently (bold text, or
something similar).

However I like your program! Keep it up!

Would be nice to create a googlecode project for this.

Best regards,
 Laszlo

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

On Fri, Oct 2, 2009 at 2:42 PM, Laszlo KREKACS
laszlo.krekacs.l...@gmail.com wrote:
 ps: Ok I stop spamming your thread.

Cant stand it...:(

After I adjusted the mic volume during call, and pushed multiple times
the save button.
We hanged up. AFter about half hour, I got a call, and nobody heared
anything (nor me, nor the callee).

Im examining the difference between the two state files right now:
Original: http://paste.pocoo.org/show/142502/
Broken: http://paste.pocoo.org/show/142501/
Diff: http://paste.pocoo.org/compare/142502/142501/

Also on the console I have seen:
Gain effectively muted. Returning 0

The Earpiece slider is at 0 (it was always at 0, and worked fine). If
I raise it, there is no
difference.
I see this in the console:
Speaker: 0 set to 92
Speaker: 1 set to 92
Bypass: 0 set to 71
Bypass: 1 set to 71
Speaker: 0 set to 94
Speaker: 1 set to 94
Bypass: 0 set to 100
Bypass: 1 set to 100


Do you have any idea whats wrong?

Best regards,
 Laszlo

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS
laszlo.krekacs.l...@gmail.com wrote:
 But there is so many things what changed, that Im completely lost.

Just wanted to notice you, that restoring the original
gsmhandset.state file (and rebooting)
does solve my problem. Im able to take call, and hear the other party.
(and he able to hear me).

Although your program was nice. It changed the mic way better, what I
had. Other party
said, its much louder and clearer.

Hope you can sort out, why the broken .state file is broken. And where
the bugs comes from ...

Best regards,
 Laszlo

ps: Ok. I seriously stop spamming...

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

On Fri, Oct 2, 2009 at 4:08 PM, Laszlo KREKACS
laszlo.krekacs.l...@gmail.com wrote:
 Do you have any idea whats wrong?

Im suspecting line 345:
value 'Constant PGA Gain'
versus:
value 'Mute ADC Output'

But there is so many things what changed, that Im completely lost.

Laszlo

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

First: sorry for the many grammar errors in my previous post.
I just sended it, without reread it carefully.

On Fri, Oct 2, 2009 at 2:27 PM, Laszlo KREKACS
laszlo.krekacs.l...@gmail.com wrote:
 1. when clicking on save there is no report what you did exactly, and was it
 successful.

Hmm, its not quite true. There is a dbus warning on stdout;)
Using **pending_return in dbus_connection_send_with_reply_setup()
without pending_setup is deprecated and strongly discouraged

So when saving there is some dbus messaging going on.
But there is no message what is really going on.

Best regards,
 Laszlo

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Laszlo KREKACS]

On Fri, Oct 2, 2009 at 2:37 PM, Laszlo KREKACS
laszlo.krekacs.l...@gmail.com wrote:
 So when saving there is some dbus messaging going on.
 But there is no message what is really going on.

Ok, after looking at the code (line 790):
   def SaveState(self, arg, scenario):
self.audio_iface.StoreScenario(scenario)

I didnt find StoreScenario on the docs.freesmartphone.org:
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html;hb=HEAD

Nice to see, there is such an option. I was completely unaware of this feature.
Btw, where should inform myself of the correct freesmartphone doc?
IS there somewhere a newer doc? How do you do it?

For you code: You dont do any sanity checking if the storing was
successful (what frameworkd returns by the way? True/False?)

Would be nice to check for it and display to the user about the outcome.

Best regards,
 Laszlo

ps: Ok I stop spamming your thread.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [fso based] Simplified mixer app

[Al Johnson]

On Friday 02 October 2009, Michele Brocco wrote:
 cool idea!
 
 would be nice if through this App we could finally make sound coming
 through earpiece with the voip-handset state file. Still struggling
 with it

This app has nothing to do with that I'm afraid. It should eventually give a 
slider each for mic and earpiece, but that'll just tweak the settings in voip-
handset.state slightly. It won't do state switching on answer or hangup, or 
sort any fundamental issues with the sound config. Problems with voip config 
are for another thread though.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[fso based] Simplified mixer app

[Al Johnson]

I've made mixer app that maps a single slider to multiple alsa channels, so 
you can have one slider for 'Mic' and another for 'earpiece'. It's based on 
Angus Ainslie's fso-mixer, but using lookup tables for which channels to show 
in which scenario, and for mapping the single slider to multiple channels.

It's at proof of concept stage now, but should be as functional as fso-mixer. 
I hope. If you aren't using stock ones it would be a good idea to back them up 
before using it just in case! Feedback would be welcome.

http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py

Known bugs and missing features:
* I haven't done mapping tables for all the mixer scenarios yet. Where they 
aren't done you will see the individual sliders as you would in fso-mixer.
* Sometimes when the state changes a setting will be shown as 0 when it is in 
fact non-zero. If anyone spots why this happens I would love to know!
* The volume sliders cover the whole possible range, while most people 
probably only ever need the top half or third.
* pyalsaaudio only accepts integer percentages when setting volumes, not the 
actual mixer hardware values used in the lookup tables. This may give some 
uneven steps in volume.
* When individual alsa channels are shown they use the alsa names. This is 
fine if you know that the 'headphone' mixer controls the speaker, and the 
'speaker' control is for the earpiece, let alone some of the more obscure 
names.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community