Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 641
    • Issues 641
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-basegst-plugins-base
  • Issues
  • #920
Closed
Open
Issue created Jul 05, 2021 by Gert-dev@Gert-dev

Support LUFS reference loudness values in replay gain plugin

Tools such as loudgain write ReplayGain 2.0 tags using a reference loudness of e.g. -18.00 LUFS. After being baffled for a while as to why the plugin didn't seem to be doing anything in Lollypop, debugging GStreamer yielded that this is being seen as a difference of 89 - -18 = 107 dB difference, likely because GStreamer always interprets replaygain_reference_loudness as dB.

It would be great if LUFS could also be supported, even if it is just by roughly converting it to dB in the background; LUFS -18.00 is approximately equal to the hardcoded 89 dB, at least according to the loudgain homepage above.

image

A workaround is to update the tags to not use LUFS.

Assignee
Assign to
Time tracking