Skip to contentSkip to conversation

Question about control names.

DISCUSSION Manuel Jander 4 participants 6 messages Jul 3, 2003 – Jul 15, 2003

lore
Share & tools
lore
#0 lore raw

Hello,

I wrote support for the Hardware Equalizer (10 band stereo = 20 controls) for the Aureal Vortex cards. For testing purposes i used the controls as "MIXER" type controls, so they are visible from any mixer. The question: How should they be named ? Is the type "MIXER" acceptable ? In my opinion it is at least pretty convenient.

Now that the EQ is done, i would like to write support for a EQ peak visualization support that the AUreal cards provide. That is there are hardware registers that can be read to obtain the peak values of each frequency band. The same question as above: How should that readonly control to be named ?
I guess it would be bad idea having it added like a MIXER type control. I was thinking of using HWDEP instead, and write a special graphical application for the visualization purpose (accessing the ALSA controls). Is there something like this done before ??

And at last, could someone please with suggar on the top update the ALSA support matrix ???!! The Aureal Vortex cards -YES THEY ARE- supported.
(http://savannah.nongnu.org/projects/openvortex/)

Best Regards

Manuel Jander.

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

#1 lore raw

At 02 Jul 2003 21:24:57 -0400,

Quoted 8 lines · Manuel Jander

Hello,

I wrote support for the Hardware Equalizer (10 band stereo = 20 controls) for the Aureal Vortex cards. For testing purposes i used the controls as "MIXER" type controls, so they are visible from any mixer. The question: How should they be named ? Is the type "MIXER" acceptable ? In my opinion it is at least pretty convenient.

MXIER should be fine.

the name is still an open question, but it's not strict at all. i would use a name like "XXX Playback Volume", where "XXX" would be likely "Equalizer" or "Aureal Equalizer", etc.
anyway, it's your choice, since you are the first conqueror :)

Quoted 5 lines

Now that the EQ is done, i would like to write support for a EQ peak visualization support that the AUreal cards provide. That is there are hardware registers that can be read to obtain the peak values of each frequency band. The same question as above: How should that readonly control to be named ?

it's also not defined well. i'd suggest you to use an intuitive name such as "VU Meter", "Equalizer Peak", etc.

Quoted 4 lines

I guess it would be bad idea having it added like a MIXER type control. I was thinking of using HWDEP instead, and write a special graphical application for the visualization purpose (accessing the ALSA controls). Is there something like this done before ??

usually this type of control is implemented in MIXER or PCM. for example, ice1712 driver provides peak meters over MIXER. HWDEP should be used really for the hwdep devices.
you can add READ|VOLATILE attribute flag to indicate the frequent changes of values.

Quoted 3 lines

And at last, could someone please with suggar on the top update the ALSA support matrix ???!! The Aureal Vortex cards -YES THEY ARE- supported.
(http://savannah.nongnu.org/projects/openvortex/)

please ask Patrick Shirkey <[email protected]>, the maintainer of the web page.

ciao,

Takashi

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

#2 lore raw
Quoted 10 lines · Takashi Iwai
Quoted 5 lines

And at last, could someone please with suggar on the top update the ALSA support matrix ???!! The Aureal Vortex cards -YES THEY ARE- supported.
(http://savannah.nongnu.org/projects/openvortex/)

please ask Patrick Shirkey <[email protected]>, the maintainer of the web page.

Curently we have Aureal listed as bankrupt.

What should it say instead?

Ideally we need chip, driver name, web link, product name for each supported device.

Signature · 17 lines
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
#3 lore raw

At Thu, 03 Jul 2003 22:17:37 +0900,

Quoted 9 lines · Patrick Shirkey
Quoted 7 lines · Takashi Iwai
Quoted 5 lines

And at last, could someone please with suggar on the top update the ALSA support matrix ???!! The Aureal Vortex cards -YES THEY ARE- supported.
(http://savannah.nongnu.org/projects/openvortex/)

Quoted 7 lines
Quoted 3 lines

please ask Patrick Shirkey <[email protected]>, the maintainer of the web page.

Curently we have Aureal listed as bankrupt.

What should it say instead?

i think Manuel wanted to tell us the gray color :) (btw, was aureal bought by creative?)

Quoted 2 lines

Ideally we need chip, driver name, web link, product name for each supported device.

yes, Manuel, please send him the detailed information to be shown there.

Takashi

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

#4 lore raw

More Questions about control names.

In reply to Takashi Iwai
Quoted 11 lines · Takashi Iwai

At 02 Jul 2003 21:24:57 -0400,

Quoted 7 lines · Manuel Jander

Hello,

I wrote support for the Hardware Equalizer (10 band stereo = 20 controls) for the Aureal Vortex cards. For testing purposes i used the controls as "MIXER" type controls, so they are visible from any mixer. The question: How should they be named ? Is the type "MIXER" acceptable ? In my opinion it is at least pretty convenient.

Quoted 3 lines

MXIER should be fine.

the name is still an open question, but it's not strict at all.

I think this is true for all control names, isn't it. At least I have not found a naming scheme (just tell me if I have missed the corresponding docs). I actually would prefer if it would be more strict. Or to have a method to know what the function of the control is.
I find it very hard to write a generic mixer application without knowing the function of the control. If I knew the functions, I could do better grouping in kmix. Currenty the controls/sliders are just sorted by ID, which sometimes is not-so-userfriendly.

Chris

-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1

#5 lore raw

Re: More Questions about control names.

At Tue, 15 Jul 2003 00:43:26 +0200,

Quoted 13 lines · Christian Esken
Quoted 11 lines · Takashi Iwai

At 02 Jul 2003 21:24:57 -0400,

Quoted 7 lines · Manuel Jander

Hello,

I wrote support for the Hardware Equalizer (10 band stereo = 20 controls) for the Aureal Vortex cards. For testing purposes i used the controls as "MIXER" type controls, so they are visible from any mixer. The question: How should they be named ? Is the type "MIXER" acceptable ? In my opinion it is at least pretty convenient.

Quoted 6 lines
Quoted 3 lines

MXIER should be fine.

the name is still an open question, but it's not strict at all.

I think this is true for all control names, isn't it. At least I have not found a naming scheme (just tell me if I have missed the corresponding docs).

alsa-kernel/Documentation/ControlNames.txt

Takashi

-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1