Skip to content

Remove excessive logging when using symphonia features like AudioBundle #16277

Open
@Sigma-dev

Description

@Sigma-dev

Spawning a few AudioBundles generates a lot of logs that don't communicate any meaningful information to the user such as

2024-11-07T14:40:34.333068Z  INFO symphonia_bundle_mp3::demuxer: using xing header for duration.
2024-11-07T14:40:34.686982Z  INFO symphonia_core::probe: found the format marker [49, 44, 33] @ 0+2 bytes.
2024-11-07T14:40:34.687152Z  INFO symphonia_core::probe: found the format marker [ff, fb] @ 34+2 bytes.
2024-11-07T14:40:34.687253Z  INFO symphonia_bundle_mp3::demuxer: using xing header for duration.

An existing solution is manually filtering the logs, but I believe this is not that great for the developper experience.

A better solution would be adding built-in filtering of all INFO logs from symphonia in bevy, while keeping the warns and error logs.
I can probably come up with a PR if maintainers agree that there is a problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-AudioSounds playback and modificationA-DiagnosticsLogging, crash handling, error reporting and performance analysisC-BugAn unexpected or incorrect behaviorC-UsabilityA targeted quality-of-life change that makes Bevy easier to useD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions