New audioctl coming soon

I integrated a replacement for mixerctl (and also removed mixerctl) back in build 130. Well, build 130 is coming out really soon (I believe it is available internally in SXCE form now.)

I think therefore that it is time to provide more detail here about the new audioctl syntax:

NAME
   audioctl -    audio mixer control command line application

SYNOPSIS

   audioctl list-devices

   audioctl show-device [-v] [-d device ]

   audioctl show-control [-v] [-d device] [control ...]

   audioctl set-control [-v] [-d device] control value

   audioctl save-controls [-d device] [-f] file

   audioctl load-controls [-d device] file

DESCRIPTION
   The audioctl command is used to control various features  of
   the audio mixer and to get    information about the audio mixer
   and the audio device.

   The audioctl command operates on the following data types:

  device
      An audio device, such as "audiohd#0".   The subcommands
      that accept this do so as an argument to an option -d.
      If not supplied, then the default audio device is assumed.
      Any device node associated with an audio device will work
      as well, such as /dev/sound/0, /dev/dsp1, or /dev/audio.

  control
      A mixer control name, such as "volume".

  value
      The value of a control.  The specific format depends on
      the type of control.  Monophonic values usually use a single
      whole number between 0 and 100, inclusive.  Stereo values
      use a pair of such numbers (representing right and left
      channels.)  Boolean values indicate either "on" or "off".
      Enumerations take a single value of one or more names.

  file
      An ASCII text file of control settings.

Options:
   Each subcommand has its own set of options that it takes.
   However, some subcommands support the special flag -v, which
   indicates a request for more verbose output.

SUBCOMMANDS
   The following subcommands are supported:

   audioctl list-devices

  List all the audio devices on the system.

   audioctl show-device [-v] [-d device]

  Display general information about a device.

   audioctl show-control [-v] [-d device] [control ...]

  Display the control setting values for the device.  The named
  controls are displayed.  If no control names are provided, then
  all control values are displayed.

   audioctl set-control [-v] [-d device] control value

  Changes the value of a control to the supplied value.

   audioctl save-controls [-f] [-d device] file

  Saves the current state of all mixer control values to the named
  file.  The command will abort safely if the file already exists,
  unless -f is supplied.

   audioctl load-controls [-d device] file

  Restores previously saved state in the named file for all mixer
  controls.


ENVIRONMENT VARIABLES
   AUDIODEV     If the    -d and -a options are not specified,  the
       AUDIODEV  environment    variable is consulted. If
       set, AUDIODEV contains    the full path name of the
       user's     default  audio    device.


I expect there may be some questions or concerns about the new syntax. If they are not answered by the manual page above, please don't hesitate to ask me.

Comments

Binary Crusader said…
This looks great Garrett! I can't thank you enough for the incredible work you've done with getting a modern audio subsystem in Solaris.
December 17, 2009 at 8:32 AM
Post a Comment

Popular posts from this blog

An important milestone

Yesterday, with very little fanfare, illumos passed an important milestone. This milestone was the integration of  195 Need replacement for nfs/lockd+klm This is work that I originally tasked Gordon Ross and Dan Kruchinin to work while we were colleagues at  Nexenta .  Gordon started the work, picking up bits from FreeBSD as a starting point and gluing it to the illumos entry points.  Dan continued with it, and fleshed out a lot of the skeleton that Gordon had started.  It was subsequently picked up by the engineers at Delphix , and -- after some important bug fixing work was completed -- was integrated into their product quite some time ago -- reportedly its been stable since December in their product. The reason this is such an important milestone, is two fold: First, this represents a substantial collaborative effort, involving contributions from parties across several organizational boundaries.  The level of collaboration achieved here is a w...
Read more

GNU grep - A Cautionary Tale About GPLv3

My company, DEY Storage Systems , is in the process of creating a new product around the illumos operating system.  As you might imagine, this product includes a variety of open and proprietary source code.  The product itself is not delivered as a separate executable, but as a complete product.  We don't permit our customers to crack it open, both from the sense of protecting our IP, but also to protect our support and release engineering organizations -- our software releases consist only of a single file and we don't supply tools or source for other parties to modify that file. One of the pieces that we wanted to integrate into the tree is an excellent little piece of software called Zookeeper , produced by the Apache organization.  Like illumos, Zookeeper has a nice non-viral copyleft license, which makes it nice for integration into our product. However, I discovered that as part of our integration, one of my engineers had decided to integrate GNU grep. ...
Read more

The Hand May Be Forced

Well, as you may have read , Oracle has decided that at some point very soon, we're going to lose normal regular access to the source code for OS/Net. (I.e. the Solaris kernel and supporting programs.) While I would have vastly preferred for Illumos to have a cooperative and collaborative relationship with Oracle , it appears that Oracle doesn't value this. In fact, the exact words were from the management at Oracle were as follows: Solaris is not something we outsource to others, it is not the assembly of someone else’s technology, and it is not a sustaining-only product. While I understand the need to own the technology, there are few things that could be stated that show a stronger NIH attitude than this. Its unlikely that there will ever be a way for Oracle and the greater community to have a collaborative relationship. This is a dark day for OpenSolaris -- its effectively dead now. (Its parent, Solaris, lives on however.) How unfortunate. For Oracle that is. Because...
Read more