Hi Robert,

Yes it is totally possibly and should already work. 

We are tracking media.role in module-murphy-ivi so you can 
specify that to make your stream more "policy aware". No Murphy 
calls are needed. 

so for example: 

paplay --property=media.role=music mymusic.wav 

will tell policy you are music player.

paplay --property=media.role=navigator mymusic.wav 

will tell policy you are navigator.

These 2 streams are now interacting with each other differently 
than if they would have same roles (this depends of course 
on the policy configuration).

The downside is that you get little bit more "coarse" policy feedback 
through pulse API callbacks, so you might get corked, uncorked or even 
killed through pulse callbacks, but you don't know too much why 
this thing happened. But most of the stuff should work just fine 
with audio.

Also remember that Murphy resource API is not for audio only. 
You can ask resources simultaneously for audio, video, cpu 
(you name it). We usually say that you should use Murphy API's 
if you want detailed fine grained policy based functionality or 
you want to tie the app logic to use cases which require simultaneous 
separate resources.

br,
Jaska

________________________________________
From: IVI [[email protected]] on behalf of 
[email protected] [[email protected]]
Sent: Tuesday, April 22, 2014 11:02 AM
To: [email protected]; Kovacs, Janos
Subject: Murphy Unaware PulseAudio Application // Is it possible?

Hoi,

Does an application, which uses the PulseAudio Asynchronous API, needs to be 
aware of murphy? I mean, if an application connects to the PulseAudio server 
and creates a stream, it could pass all policy relevant information via 
pa_stream_new_with_proplist to the server, and the corresponding PulseAudio 
module grabs those information.

Please see:
pa_stream* pa_stream_new_with_proplist(..., pa_proplist*)
http://goo.gl/SphORL

The only problem is, how to clearly communicate stream changes, like Murphy's 
resource state changed callback. I think, using a PulseAudio Asynchronous API 
callback as substitute, would only lead to an ambiguous interface.


Cheers,
Robert



If you are not the addressee, please inform us immediately that you have 
received this e-mail by mistake, and delete it. We thank you for your support.

_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to