not sure where you got the idea that I have multiple session managers at the same time, because I don't.
you think you don't
most if not in all pipewire installations out there you always have one session manager running all the time but hidden: wireplumber
for instance, if any one of the pinned connections on qpwgraph clashes with some wireplumber rule, then you have a problem: qpwgraph can't and won't help you there re. persistent connections. you'll have to fix it at the wireplumber side (now you run: there's prolly nothing in life more esoteric than just that:))
so, anyway, the most rightful answer above is therefore B. always; however, whether doing the A, B and a, b or c actually depends on each user case and configuration; proverbial YMMV.
as said on the previous answer rather esoteric for you, please:
unpin (ie. remove from persistence) all and any connections that are or can be managed by ANY session manager or DAW (implicit or not);
only pin (ie. include for persistence) those connections you know that are NOT managed elsewhere (eg. web-browsers, media-players, easy-effects, etc.)
do not switch pipewire/pulseaudio profiles at a wim; stick with one and only for ever more (Pro Audio is recommended)
qpwgraph may give you some tools to help you on the rescue and mitigation for a general problem (persistent connections) but surely is not, cannot, won't ever be, the one-stop and definitive solution. sorry.
you think you don't
most if not in all pipewire installations out there you always have one session manager running all the time but hidden: wireplumber
for instance, if any one of the pinned connections on qpwgraph clashes with some wireplumber rule, then you have a problem: qpwgraph can't and won't help you there re. persistent connections. you'll have to fix it at the wireplumber side (now you run: there's prolly nothing in life more esoteric than just that:))
so, anyway, the most rightful answer above is therefore B. always; however, whether doing the A, B and a, b or c actually depends on each user case and configuration; proverbial YMMV.
as said on the previous answer rather esoteric for you, please:
qpwgraph may give you some tools to help you on the rescue and mitigation for a general problem (persistent connections) but surely is not, cannot, won't ever be, the one-stop and definitive solution. sorry.
hyu.
cheers