Log messages from bevy dependencies displayed as `log` instead of their name

[Satellile]

Bevy 0.13.1 // Windows 10

When I create an AudioBundle to play a sound, I get

[timestamp] INFO log: found the format marker [ff, fb] @ 0+2 bytes.
[timestamp] INFO log: using xing header for duration

printed in my log/console output. I'm creating Audiobundles often to play sounds, and it makes my log output very noisy; however, I couldn't suppress it using a filter and LogPlugin, as I didn't know the source of the log message.

The expected output would be

[timestamp] INFO symphonia_core::probe: found the format marker [ff, fb] @ 0+2 bytes.
[timestamp] INFO symphonia_bundle_mp3::demuxer: using xing header for duration

as in this case, symphonia is the source of the log message. Passing filter: "symphonia_core::probe=warn,symphonia_bundle_mp3::demuxer=warn".to_string(), as my LogPlugin filter still correctly filters out these log messages.

Similar behavior is observed for some other Bevy dependencies (e.g. log messages from naga are also showing up just as log)

Additional information

My Discord help thread: https://discord.com/channels/691052431525675048/1239685546972938381

Discord thread of someone else with the same issue: https://discord.com/channels/691052431525675048/1222256688527310958/1222256688527310958

[theotherphil]

If I change examples/audio.rs to load an mp3 instead of an ogg file, then I get the expected output on current main on a Mac:

cargo run --example audio --features mp3

...
2025-06-08T18:58:17.296873Z  INFO symphonia_core::probe: found the format marker [ff, fb] @ 0+2 bytes.    
2025-06-08T18:58:17.297010Z  INFO symphonia_bundle_mp3::demuxer: estimating duration from bitrate, may be inaccurate for vbr files    
...

@Satellile is this still an issue in bevy 0.16?

[theotherphil]

If I checkout v0.13.1 then I see the same issue as reported here, so it looks like this isn't an OS-specific issue and this has been fixed at some point between 13.1 and 16.1

output at v.0.13.1
2025-06-08T19:06:25.923377Z  INFO log: found the format marker [ff, fb] @ 0+2 bytes.    
2025-06-08T19:06:25.923650Z  INFO log: estimating duration from bitrate, may be inaccurate for vbr files