mirror of
https://gitlab.freedesktop.org/pulseaudio/pulseaudio.git
synced 2025-11-09 13:29:59 -05:00
3d698d17af
When a stream is created, and the stream creator specifies which device should be used, that can affect automatic routing policies. Specifically, module-device-manager shouldn't apply its priority list routing when a stream has been routed by the application that created the stream. A stream that was initially routed by the application may be moved for some valid reason (e.g. user requesting a move, or the original device disappearing). When the stream is moved away from its initial device, the "device requested by application" flag isn't relevant any more, so it's set to false and never reset to true again. The change in module-device-manager's routing logic will be done in the following patch. |
||
|---|---|---|
| .. | ||
| headerlist.c | ||
| headerlist.h | ||
| module-rtp-recv.c | ||
| module-rtp-send.c | ||
| rfc2327.txt | ||
| rfc2974.txt | ||
| rfc3550.txt | ||
| rfc3551.txt | ||
| rtp.c | ||
| rtp.h | ||
| rtsp_client.c | ||
| rtsp_client.h | ||
| sap.c | ||
| sap.h | ||
| sdp.c | ||
| sdp.h | ||