Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4776511
Votes 0
Synopsis RFE: Setting the default MixerProvider
Category java:classes_sound
Reported Against hopper
Release Fixed 1.5(tiger)
State 10-Fix Delivered, request for enhancement
Priority: 3-Medium
Related Bugs 4487550 , 4666881 , 4667017 , 4927904
Submit Date 09-NOV-2002
Description
RFE: Setting the default MixerProvider




Currently, Java Sound uses a default mixer provider when you do not specify a specific Mixer. The spec does not define how this default mixer provider is chosen. 3rd party plugins can provide custom MixerProvider implementations, which will be taken as default in 1.4.2 (the last found provider will be used as default). However, it is impossible to use one of the provided MixerProviders that ship with Java Sound, e.g. to allow binary Java programs benefit of new functionality of secondary MixerProviders (e.g. ALSA on Linux).

The solution is to use a system property, similar as explained in the documentation of the method provider()in class java.nio.channels.spi.SelectorProvider. The system property would be named "javax.sound.sampled.spi.MixerProvider" and its content would be the fully qualified classpath of the class to be used as default mixer provider. If the specified default mixer provider class is not accessible, or does not exist, the system property will be ignored.

Such a mechanism allows portable code to use special features. It is also fully backwards and forward compatible: it integrates easily with the planned extension to Java Sound's service provider mechanism in 1.5.0 (see 4666881: RFE: Add methods to load and unload service providers at runtime).

This RFE applies equally to MidiDeviceProvider.


======================================================================
Work Around
 xxxxx@xxxxx  2002-11-08
	Currently, the only way of setting the default service provider is by putting a jar containing it and its service provider configuration file into the bootclasspath with the non-portable -X parameter to the java executable. This workaround is unusable for deployment of actual products like FreeTTS.
Evaluation
 xxxxx@xxxxx  2002-11-08
	Would be nice to have in Mantis.
Comments
  
  Include a link with my name & email   

Submitted On 04-AUG-2005
andywolpert
Can someone explain this to me?
I have been unable to add an extra mixer to my Java Sound (using JDK 5.0). I do care about the defualt I would at least like to see it in the list of all mixers. Is my problem related to this issue?


Submitted On 03-MAY-2006
Jonnathan Guambe
ghlegs@yahoo.com.br



PLEASE NOTE: JDK6 is formerly known as Project Mustang