Jump to navigation Jump to search
228 bytes removed ,  14:47, 23 July 2008
* cleanup the API:
** get rid of the evil Mixer::setReady hack
** resolve the disparity between OSystem::getOutputSampleRate() and Mixer::getOutputRate(), probably by abolishing the former** instead, the mixer should probably receive the sample rate as a parameter to its constructor.** We could also make it possible to change the output sample rate the mixer uses on the fly (this would be a private API, only available to the backend, for backends which can change the output sample rate). This would essentially require changing the Channel::_converter objects
* Are there backends which could benefit from a 'custom' mixer? If so, what would be required to implement such a thing? Needs talking to porters


Navigation menu