Huang-Huang Bao f92a5b3bbd bluez5: emit node volume and mute right after bluez5 node creating ... bluez5 nodes will always be removed & created again during profile changing, hence node volume & mute will always be reset. This is OK if profile did changed, because session manager would carries volume & mute to bluez5 route param. But if profile was not changed after setting profile (a2dp-sink-sbc -> a2dp-sink -> a2dp-sink-sbc), session manager would think node volume & mute are not changed and no route setting is performed, causing route volume out of sync with node volume. To fix this, we emit node volume and mute right after bluez5 node is created. Fixes #1254		2021-06-03 07:17:41 +00:00
..
examples	treewide: replace plain strcmp() calls with spa_streq	2021-05-18 22:10:27 +10:00
include	alsa: rework UCM open	2021-06-02 17:25:21 +02:00
plugins	bluez5: emit node volume and mute right after bluez5 node creating	2021-06-03 07:17:41 +00:00
tests	spa/utils: add spa_atou32, spa_atoi64,spa_atou64, spa_atod, spa_atof	2021-06-02 07:39:41 +00:00
tools	treewide: replace strcmp() == 0 with spa_streq()	2021-05-18 22:10:27 +10:00
meson.build	meson: fix build if bluez5 option is disabled	2021-05-28 21:01:38 +08:00