-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make VU Meter norm conform #7888
Comments
Commented by: daschuer We may look at this GPL2 code: |
Commented by: daschuer Software VU Meter Ideas: |
Commented by: daschuer Related: This will help to light up the correct LED on controllers with labeled VU-Meters. |
Commented by: daschuer Related: |
Commented by: xeruf Uff this is old. Trying to map the VuMeter to HID light output right now, but it's kinda hard without knowing the function to go from Mixxx's VuMeter to dB - is it somewhere? |
Commented by: daschuer Unfortunaely the VU meter is not scaled in DB: That's one reason why this bug exists. Do you have interests to adopt it? |
Commented by: xeruf I have interest in adopting any bug that I comment on, but I first need an introduction to C++ and the codebase ^^ |
Commented by: daschuer The best way is leaning by doing. This one is too advanced for the beginning. Take one "easy" tagged bug and follow https://www.mixxx.org/wiki/doku.php/bugfix_workflow |
Commented by: Be-ing I've been thinking it would be helpful to have a psychoacoustic perceived loudness meter. Can we do this with libebur128? |
Commented by: ywwg Let's be careful how we adjust the VU meter. We need to make sure the clipping indicator is still accurate and intuitive. It could look strange if either the VU meter looked low and was clipping or looked very hot and was not clipping. |
Commented by: Be-ing Right, we still need to know whether the deck is clipping regardless of the perceived loudness. It may be a good idea to not make EBUR128 the default but have it as an alternative option for users who understand how it works. I tried using the x42 EBUR128 LV2 meter plugin on some tracks in Ardour and it is clear to me that this provides more useful information than Mixxx's current metering. Tracks that look approximately the same with peak metering can appear very different with EBUR128 or K20/14/12. |
Commented by: daschuer
Yes. I think we face here different use cases. The current Mixxx VU meter is somewhere between a paek meter and a VU meter, offering a reasonable one fits all type, unfortunately not comparable to other devices or any standard scale. The clipping LED works always and independent of the VU-Meter scale. If one likes to monitor the loudness of the mix, knowing that there is enough digital headroom anyway, a LUFS meter will be a better choice. This is relevant especially for MIC and Aux input, because we can trust the ReplayGain adjustment for tracks blindly. If one likes to get all out of an underpowered PA System, True Peak meter be the best choice. It helps to predict digital clipping clipping after DA conversion. Both meters would be a nice preferences option. |
Commented by: ywwg We also got this feature request over email: """ |
Commented by: atskler Regarding post #13 probably they can use the professional x42-meters through Jack, or the lv2 versions with a Jack enabled plugin host. The x42-meters can be found on distribution repositories also. https://x42-plugins.com/x42/x42-meters For precise results they may need levels allowed above 0dBFS at Mixxx's Jack output. -> See: Bug #1959153 |
Commented by: Be-ing I don't think Mixxx should need LV2 plugins for metering. However we could copy code from x42-meters into Mixxx. |
Reported by: daschuer
Date: 2015-03-09T09:00:06Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1429760
The VU meter is normed in IEC 60268-17 and the Peak indicator at IEC 60268-18
http://en.wikipedia.org/wiki/Peak_programme_meter
http://www.soundonsound.com/sos/jul13/articles/qanda-0713-2.htm
The text was updated successfully, but these errors were encountered: