Hi Saurabh, > 1. Is libmm-sound module is referred to as Tizen sound-server?
Yes, that's the case. Sound-server is build from libmm-sound sources. > 2. Apart from disabling sound-server anything more needs to > disabled/enabled in order to route the sound? Murphy ASM plugin is not related to sound routing. Murphy will just use it for resource management. You will need to figure out the particular audio routing in PulseAudio or similar. I think the following is the original patch that removed ASM functionality from sound-server. Later on the #defines were improved. Are you using the same source code? You might want to build libmm-sound so that the ASM support is disabled; sound-server can still be used for things other than resource management then. https://review.tizen.org/gerrit/gitweb?p=platform/core/multimedia/libmm-sound.git;a=commit;h=3dd41e09fc74d8d1c425d3014060e80937429d54 > I am encountering the following errors: > > audio-session-mgr.c: ASM_register_sound_ex(841) > failed to > __ASM_init_msg(), error(3) > > m_session.c: mm_session_init_ex(210) > failed to ASM_register_sound(), > sessiontype(10), error(0x3) Hmm. Check the Murphy logs (start Murphy with 'murphyd -vvvv') and tell if you see anything in the logs when you try to register a session. Check also that ASM plugin is loaded properly -- the logs should indicate if something goes wrong. > 3. Is there any reference explaining the steps to migrate Tizen > sound-server functionalities to Murphy. There is no documentation for that. We just did it once for Tizen IVI. The Murphy resource system was also working on Tizen Mobile -- I did some performance comparisons with it at some point. I remember that a key testing tool was the ASM test client. You need to define the matching resource types in Murphy configuration that you have in ASM (there is a mapping table for conversion). Ismo _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
