On Wed Mar 27 10:03:35 2024 +0000, Jinoh Kang wrote:
the only thing you need to know about
FWIW you also need to know about this implicit behavior if you expected +mfplat and GStreamer logging to be configured independently but the default behavior isn't. Well, I guess it isn't hard to figure out if you can grep `GST_DEBUG` in the wine codebase. I assume `GST_DEBUG` is and will ever be the only envvar responsible for controlling the source of "GStreamer-LEVEL: [...]" messages.[^1] In that case, I don't necessarily see a need for a separate channel? *Maybe* if Wine had hierarchical logger configuration, but that doesn't exist (yet). Wine debug channels have always been ad-hoc; I don't think there is a hard rule for strict separation. [^1]: which you can disable with `GST_DEBUG=0`.
Yes, GST_DEBUG=0 works.
After thinking about it I think I'm fine with GST_DEBUG=4,WINE:9 for a default. FWIW, it was just unsureness on my part, not trying to say it was a definitely better option.
Fwiw were it using Wine debugging facility as it probably should (but can't because GStreamer creates its own threads), it would be using TRACE everywhere and we wouldn't even have to argue about this.
Eh, well, it's less about the Wine traces than the GStreamer traces. GST_DEBUG=WINE:9 seems uncontroversial; GST_DEBUG=4,WINE:9 is maybe a little less uncontroversial, but I think it's probably fine nonetheless.