(old)Puppy Linux Discussion Forum

Brad, (And everyone else that reads this post)

Please execute the following command and attach resulting amixer.tar.gz file

Rarsa: I must thank you for your work. I have no time to try your mixer, but as it is stated in another threads, there is a mess with the voip phones as Skype or Xten-Xlite (a generic one).
With Puppy 2.02 and its mixer xtmix, both phones run ok.
In the new versions, 2.13, 2.14 and Pizzapup, they don't works.
The remote user tell us not hearing our voice.
Xtmix have a small button, like a dot, that enables the mic capture. Zmix does not have it.
I think was Gen Too that kindly suggest to enable directly the mic through the order "amixer set mic 98% unmute cap".
It is not possible you include the mic capture on/off button into your mixer?.

I think in the new versions Alsa install was too much trimmed lacking drivers for legacy cards and so on. But perhaps this may be the subject of another thread.

Thanks
Xan

xandas wrote:It is not possible you include the mic capture on/off button into your mixer?

It's in my plans but first I need to have the output of the command in my previous post from as many users as possible. Please execute it and post the file.

Shut up phpBB! I don't need no stinkin' message! MUahaahahahahahaahhaaahaaaahaaaaahahaaaaahahaaaaahahahaaaa.......

...erm.... ..as you were...

I'll post mine tomorrow, I'm in another OS right now and have a few downloads going that I don't want to interrupt.

Nathan

...as requested.

Cheers

Here's the output from one of my boxes.

Nathan

text

Amixer, posted

Here's the output from my other computer at home.

Nathan

This is good, keep them comming, the more I have the easier it will be to have a (now for real) fully functional mixer.

Why another mixer? Well, I searched up and down for Mixers, GTK based mixers in particular, and for whatever reason they are either quite ugly with a lot of functionality or nice looking with very limited functionality. There were even the ugly looking with very functionality.

I am sure that whatever I come up with will not support 100% of Alsa's functionality, it will just be a volume level mixer not a full mixer but it will allow users with a broader range of audio devices to control them.

A bit slow.. sorry.

rarsa, I haven't given it any kind of test but at least I figured out how to use it. I had assumed it would replace the single slider bar that pops up when you left-click the speaker icon. I finally found the Puppy sound mixer in the multimedia menu.

Speaking of that slider bar, it doesn't always go away when I'm done with it and move the cursor. Anyone know why?

Flash wrote:I had assumed it would replace the single slider bar that pops up when you left-click the speaker icon.

If you use the most recent tray mini-volume, it shows a menu on right click from where you can select "mixer" which will open the mixer.

Flash wrote:Speaking of that slider bar, it doesn't always go away when I'm done with it and move the cursor. Anyone know why?

Yes, the mouse must move over the open slider. The slider closes 0.5 seconds after the mouse leaves it.

Dear rarsa,

I did get pvolume to work on my machine but have the following observations.

(a) it controls my alsa Audigy 2ZS just fine, but 13 options aren't really enough. I'll try to tweak the code a bit to inlcude a toggle for analog on/off, since I had that problem for about a week and was getting no sound out of the Audigy until I toggled that setting in the alsa console mixer.

(b) Pvolume opens up a small 8x8cm grey window, in addition to the mixer window. Is there any way to turn that annoyance off? There must be some tktcl initialization setting setting.

(c)The mixer app, at least on on my machine (xorg at 1028x768 TTL), starts off at about horiz. pixel 950, which may be part of the reason I wrote earlier that the app wasn't working. It may be that I simply didn't see it materialize on the screen. I think an initial placement parameter, say 100h, 100v for most users, might be a good idea in a future release.

In any case, thanks and nice work.

With kind regards,
vovchik

vovchik wrote:(a) it controls my alsa Audigy 2ZS just fine, but 13 options aren't really enough. I'll try to tweak the code a bit to inlcude a toggle for analog on/off, since I had that problem for about a week and was getting no sound out of the Audigy until I toggled that setting in the alsa console mixer.

Please read up in this thread. About 16 or 17 posts before this one.

vovchik wrote:(b) Pvolume opens up a small 8x8cm grey window, in addition to the mixer window. Is there any way to turn that annoyance off? There must be some tktcl initialization setting setting.

My guess is that you are using puppy 2.15CE or did the wrong MIME association for TCL applications. That screen is not a problem with the script but the way you are executing it (or the puppy you are using). WhoDo, already fixed Puppy for the next version of 2.15.

vovchik wrote:(c)The mixer app, ...starts off at about horiz. pixel 950

I don't specify the position. It is responsibility of the WM to position it.

Thanks rarsa,

I fixed the mysterious grey window problem. You were right. My ROX run default was set to "wish" and not "tclsh" as a result of some earlier fiddling on my part. As for direct Alsa mixer support, that would be great. I read the previous posts you mentioned and am looking forward to it, if, that is, you ever find the time. One problem I see right off the bat is that some sound cards have a ridiculously large number of controls and toggles (such as mine). That would make for a very unwieldy mixer (if there were no separate configuration dialog to disable most of them) and require a large array for their storage. Your code, as it now stands, is simple, elegant and straghtforward.

With kind regards,
vovchik

PS.To get sound out of my card I had to run the following:

amixer set 'Audigy Analog/Digital Output Jack' unmute

and it took me some time to figure that one out...and that it was muted by default.

vovchik wrote:That would make for a very unwieldy mixer (if there were no separate configuration dialog to disable most of them)

That's one of the reasons I added the configuration window.

vovchik wrote:and require a large array for their storage. Your code, as it now stands, is simple, elegant and straghtforward.

No problem with the way I coded it. The code is the same whether there are 10 or 100 controls.

Thanks for the kind words, though.

I take it this thing dosen't work with the XFCE.pup , Seeing as i have installed it and never got it going , or showing up anywhere...

Puppy volume mixer is a standard application, It does not depend on the Window Manager.

I don't know what kind of setup you have so I don't know why it is not showing in your Multimedia menu but you can execute it from the command line