chore: reduce the log verbosity for symphonia
see https://github.com/fishfolk/jumpy/issues/873
Do you have any idea why lots of the messages just say log for the target instead of the crate::module that they were generated from?
2023-12-04T16:30:34.592196Z INFO log: Guessed window scale factor: 1
Some of them have the module, like this one:
2023-12-04T16:30:34.591575Z INFO bevy_winit::system: Creating new window "App" (0v0)
But a lot of them don't, specifically from symphonia and WGPU it seems.
Apparently you were still able to exclude symphonia in the log filter. I think I want to exclude some of the more verbose WGPU messages, too, ( which apparently popped up after overriding the Bevy log filter ), but it's hard to tell which targets to exclude when they just show log for the target.
I'm not really sure, maybe some stripping/overriding happens along the way due to having so many layers. I looked around the bevy repo to see if there is anything reported before but couldn't find it.
Let me know if you find out why, I'm also curious 🐻