On Tue, Jan 18, 2011 at 1:04 AM, Counihan, Tom <tom.couni...@intel.com> wrote: > http://conference2010.meego.com/session/policy-framework-flexible-way-orchestrate-multiple-functionalities-meego-devices
See also: http://wiki.meego.com/images/Meego-policy-framework-developer-guide.pdf Meego really needs an overview document of the Multimedia subsystems similar to this one from Maemo: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain ... Regarding the ALSA layer, there is the potential overlap between ALSA "use case manager" and the aforementioned MeeGo policy framework: See: http://conference2010.meego.com/session/audio-hardware-use-case-management-mobile-devices .................. AUDIO HARDWARE USE CASE MANAGEMENT FOR MOBILE DEVICES Session Summary: Simplified audio hardware management with emphasis on performance, power consumption and audio use case flexibility. This session will explore the problems faced in abstracting complex audio hardware into simple portable use cases and how to overcome these problem areas with ALSA UCM. Session Abstract: Todays modern mobile devices must provide users with feature rich audio hardware functionality that must be seamlessly integrated with applications, optimized for power and provide excellent performance. The ALSA Use Case Manager (UCM) is designed to achieve the above and provide clients (like Pulseaudio) with a portable means of controlling audio hardware without any underlying hardware knowledge. The intention of UCM is to make audio applications portable between different Meego based devices and to simplify audio driver development by off loading complex routing sequences to UCM. This session will describe how to leverage the benefits of UCM into real devices. ALSA UCM is open source software and is in the process of being merged into alsa-lib. ..................... https://wiki.ubuntu.com/Specs/N/ARM/AlsaScenarioManager .................... http://opensource.wolfsonmicro.com/node/14 ////////////// The ALSA scenario manager is a LGPL library designed to allow high level control of audio scenarios or use cases in sound device hardware. It is intended to be used by applications to change the hardware audio scenario of a device in a generic and portable manner. e.g. a dialer application may want to set a "GSM phone call" scenario or a media player may want to set a "playback via headphones" scenario. This library is not meant to replace gstreamer, PulseAudio or a sound server, but is meant to work in tandem with such audio software. Features Simple API and standard scenario types for changing device hardware scenario. Scenarios are stored in standard ALSA alsactl file format and can be very quickly generated using alsamixer. Ability for applications to identify controls relevant to the current scenario. ////////////////// http://www.slimlogic.co.uk/?page_id=7 //////////////// The ALSA scenario manager provides the following features. Consistent and simple C API. The library provides simple and consistent methods to change scenario or use case and thus make applications more portable across different devices. Ability to change any ALSA audio control type. This includes signal gain and signal routing (through mixers and muxes). Gain and mixer aliasing. Different scenarios may use different hardware gain controls (e.g. some hardware has different hardware gain controls for headphone and speaker volumes) . The library can alias controls so that the correct volume control is updated no matter what use case is in operation. ////////////////// -- Niels http://nielsmayer.com PS: some of the above came from researching and writing http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego And also from previous discussions on Meego lists: http://lists.meego.com/pipermail/meego-handset/2010-December/000074.html http://lists.meego.com/pipermail/meego-handset/2010-December/000090.html _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
