Open Sound System
|Do you have problems with sound/audio application development? Don't panic! Click here for help!|
oss_mixext extinfo; /* Values from prior call to SNDCTL_MIX_EXTINFO */
ioctl(mixer_fd, SNDCTL_MIX_WRITE, &vr);
The above code fragment lacks all error checks for clarity. Real world applications must always check for the errors and handle them as described below. Also most OSS ioctl calls will return information in the argument variable and it's usually necessary to check it too.
Before making this call the application should have read the mixer descriptor record for this control using SNDCTL_MIX_EXTINFO. The dev, ctrl and timestamp fields must be initialized to the values returned by SNDCTL_MIX_EXTINFO before making the call.
timestamp field is used for detecting asynchronous mixer interface structure changes initiated by the device. Some devices may purge parts of the mixer interface when the device mode changes. Ioctl calls accessing modified controls with expired timestamp values will return with errno=EIDRM. If this happens the mixer application should re-read the mixer descriptors and replace the GUI widgets with changed timestamp with new ones (all subsequent entries after the first changed one will have to be changed too).
The application should initialize the
value field to the new value of the mixer control. See the Scaling of mixer control values section for more info about encoding the value.
The return value from the OSS ioctl calls will be -1 if a fatal error occurred. Other values mean that the ioctl call was more or less successful. However in most cases the application must check the value returned in the argument to see what was the accepted value.
Please see the Possible error codes (errno) returned by OSS calls section for more info about the error codes returned by OSS.
|ossxmix.c||This is the ossxmix (GTK++ GUI) program shipped with OSS|
|ossmix.c||Sources for the ossmix command line mixer shipped with OSS|
|mixext.c||A simple sample program for using the new mixer API|