(old)Puppy Linux Discussion Forum

I haven't been completely happy with with the volume control in dingo. In dingo alpha 7 it also seems to be hanging onto the mixer device making it hard to run the alsa wizard. I've done some tarting up and it is now nearly equal to Rarsa's original tcl applet.

The pet includes the icons.
It has a -u switch which takes a millisecond parameter for how long to wait between checking the current volume and updating the icon if necessary. By default this is off to avoid the alsa wizard problem and to minimise processor load.
The slider disappears automatically when you move the focus to another window.
The volume is updated as you move the slider rather than just when you let go of it.
I have removed the -bg option to set the background, it now works properly with gtk transparency and the citrus theme in the latest dingo.

If you want to mess with the icons they are in the same place as earlier pups in /usr/local/lib/X11/mini-icons

The source tar is available at
http://users.ecs.soton.ac.uk/wmd04r/pup ... ay-0.8.tgz

The command to start it is
absvolume
When you restart X it should start automatically

Awesome. Just the thing I need. Compiled on Puppy 3.01, but there's a problem. When I set volume by dragging slider - I get this error: Using mouse scroll wheel over volume slider works without errors.
I must note, that I have some problems with my notebooks' integrated sound card - it's impossible to change volume with master volume sliders in ALSA (it has only pswitch capability) , so I use the PCM slider for volume control.
It would be nice, that when starting absvolume one could use a command line switch to choose which mixer control to control.

Joshas wrote:Awesome. Just the thing I need. Compiled on Puppy 3.01, but there's a problem. When I set volume by dragging slider - I get this error:

Code: Select all

(absvolume:5106): Gtk-CRITICAL **: _gtk_marshal_BOOLEAN__BOXED: assertion `n_param_values == 2' failed

(absvolume:5106): Gtk-CRITICAL **: _gtk_marshal_VOID__INT_INT: assertion `n_param_values == 3' failed
Segmentation fault

...
It would be nice, that when starting absvolume one could use a command line switch to choose which mixer control to control.

Are you at the extreme end of the slider when this happens?
Is your window manager jwm (the default one)?
I will have a look at the mixer choice idea.

Whilst you're at it HW, maybe you can look at an opposite problem to Jos, please? I think it may have been discussed previously but couldn't find it amongst the millions of sound issues reported. I cannot get the Master Volume slider to stick. It constantly remains at 100%. Even if workarounds have been suggested, this has been an issue for so long that it's worth getting a permanent fix?

HairyWill wrote: Are you at the extreme end of the slider when this happens?
Is your window manager jwm (the default one)?
I will have a look at the mixer choice idea.

I am using IceWM as window manager.
On my setup master volume can only be at 100% and 0%, because of mixers' capabilities (pswitch). Crash happens when I try to move slider from 100% to any other position, except 0%. But when I try to drag slider from 0% to 100% - it crashes. Using mouse wheel to scroll works without crashes - I can set master volume either to 0% or 100% - no errors. Might be that mouse wheel and slider dragging are processed diferently.
I've tried the same setup in Qemu emulator, everything works fine (amixer shows that master volume has "pvolume" AND "pswitch" capabilities).
On a side note, it would be nice to control volume with mouse wheel while hovering over tray icon.

On a side note, it would be nice to control volume with mouse wheel while hovering over tray icon.

I might as well save HW from answering that question and perhaps others, by posting the suggestions/requests I made, and his answers:

I suggested:

1. being able to change the volume by scrolling over the icon, rather than having to click on it.
2. if you click on it, having the scroll bar disappear if you click elsewhere or at least if you press escape or something.
3. an accessible mute (personally I like using the middle button for this).
4. volume tooltips when you scroll the volume up and down (at the moment there are just tooltips when you hover over the icon).

HW fixed number 2, and said:

I've just checked
http://library.gnome.org/devel/gtk/2.11 ... sIcon.html
in more detail. Status icons generate very few signals. Unless someone tells me differently 1 and 3 are not possible, you could probably fudge 3 by implementing a right click menu like Rarsa did. I don't know how exactly and consider it a low priority. I don't know exactly how to do 4 and considering you can see where the slider is and the icon images indicate level as well it seems more trouble than it is worth. I would still like to get it to work when the tray is not at the bottom of the screen and maybe get more control of the slider placement. I'm getting bored of playing with it now as it has reached the point of diminishing returns.

I though I'd posted a reply to this.
I must have missed the submit button.

Though I converted the original absvolume to work in the tray for puppy I still have no understanding of how sound works, I just copied the relevant bits of code. The code is not particularly large or complicated for someone who has a rudimentary knowledge of C wishes to prod. You probably want to put some debugging output into the event handlers in interface.c. It is hard for me to debug because I have working sound and don't understand the fine details of the sound related stuff.

Joshas the error you are describing looks like a gtk problem. Moving the slider with the scrollwheel or by dragging fires the same event handling code. Is it possible for you to test my compiled code on a clean puppy install to ensure that the problem is hardware and not your software environment?

Original Absvolume works without errors. Maybe something was altered, when porting the code? I'll have a look in the patched code, when I finnaly set up my development enviroment.

I strongly suspect that this is a gtk problem not a problem with the sound setup. It would be very helpful if you could test it in a clean install or just boot from CD with pfix=ram so that I can replicate your software setup.

Testing on clean install gives me the same errors. I think that this bug is not very important, after (if ever) you'll add an option to select mixer by passing a parameter in command line.

If anyone ever plays around with absvolume they might like to look at the latest versions from the original author as well (I presume this is the original author - unless it is a different absvolume)
http://www.pcbypaul.com/software/absvolume.html

BTW see http://murga-linux.com/puppy/viewtopic. ... 43&t=46183 if you want to extract the slackware binaries

Haven't had any issues with the newest versions. Was this something that ended up being a big deal, or did it pass over with not much worry? I'm pretty new to this, ut I do believe in learning through history...

Blesphemy206 wrote:Haven't had any issues with the newest versions. Was this something that ended up being a big deal, or did it pass over with not much worry? I'm pretty new to this, ut I do believe in learning through history...

Sorry, I don't understand what you're asking. Perhaps you could rephrase the question.

The bottom line is probably that absvolume is no longer relevant because Pizzasgood wrote the much better Retrovol.

Pet won't install on luci 5.29 puppy

also should this topic be shifted to multi -media?

Source link in first post down - anybody have a copy of HairyWill´s source?
I found the original source viawayback machine.
Attached it for future reference...

According to my Gwhere catalogue I do
I'll go get it after dinner.

I'm quite sure I have a copy of the sources here, but, Oh My! it will take some time to find them.... I must have a petabyte of sources here - 'find -name puppytray' might take a few days to run....

Looks like the limit on attachment sizes has been reduced right back down. Here it is in my Dropbox:
http://db.tt/bioWmuz5
I can't imagine choosing to use it though, now that we have retrovol

Thanks a lot!
I have back ported the original to gtk1 but it lacks the features HairyWill added - so would like to have them as well.
Think back porting retrovol is a no go...

Oh, I see.
Are you backporting a lot of stuff? Are you making it available somewhere? I imagine Amigo would love to mirror it...
Are you building a GTK1 distro or something?