We have implemented a pulsemodule which listens on sink_input_new_hook and establishes connection with AudioManager and based on response from AudioManager, it sends PA_HOOK_OK or PA_HOOK_CANCEL.
And we trigger Stream event request-cork/request-uncork from the pulsemodule to the corresponding sink_input, so that it reaches corresponding client application stream.
This is working perfectly fine for play and pause use-cases.
But, we have also requirement to handle stop uses i,.e client application should be able to differentiate play/pause/stop events.
From our current understanding, the only way to notify client applications is through request-cork and request-uncork on stream events from server side.
On client side, those could be mapped like below.
Other possibilities we thought and also experimented to differentiate Stop from Pause are below:
Please provide your inputs or suggestions on this matter.
Any help would be highly appreciated.
This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss