![]() ![]() I'm sure some of the DUC'ers here can assist you in concocting some utter drivel that will pass muster. The main winding was of the normal lotus-o-deltoid type placed in panendermic semi-boloid slots in the stator, every seventh conductor being connected by a nonreversible tremmie pipe to the differential girdlespring on the "up" end of the grammeters." ![]() ![]() The latter consisted simply of six hydrocoptic marzlevanes, so fitted to the ambifacient lunar waneshaft that side fumbling was effectively prevented. "The original machine had a base plate of prefabulated amulite, surmounted by a malleable logarithmic casing in such a way that the two main spurving bearings were in a direct line with the panametric fan. Send them a bunch of gobbledygook that they cannot possibly understand which was written by Professor James Audington, who is head of Yorktown University's Department of Atomic Audio Testing. then just tell your client that what they want in "Integrated RMS Averaging" does not pass the accuracy standard these days, and that it will be rejected by every major streaming platform, and they'll back down from their ridiculous "0.1dB tolerance standards". You’d see that average and all peaks within the meter range.īut anyway… it makes sense but isn’t really labeled or explained that well.Anyway, some people think what you want is not even accurate.Īsk your client what they are using to measure this acclaimed "0.1dB error". Mixing for streaming with an average of -16LUFS for example might make sense though. On the other hand your average signal will be below what the meter is showing since the lowest part is -20VU, not -24VU. But if you’re using default the peaks all fit up to 0VU because that’s 0dBFS practically speaking. I recommend that you use the free plugin VU Meter from TB Audio and lower the gain on each sample until its hitting zero on the meter. And if you have a loud passage where the average is about -18 for example then any peak 3dB louder than that will peg the meter. So if your average is -24LUFS then all peaks at or above -15 will peg the meter far right. Because you have 3dB above 0, and then you have (-24)-(-18) below that. By this I mean that if you’re mixing a TV show for example and you need to hit -24LUFS (which is a sort of (average’) then using a ‘normal’ -18dBFS = 0VU calibration your meter headroom is only 9dB. So I suppose it’s a somewhat useful default if you want the ballistics of a VU meter but also want to see more of the signal. Since our “-18” = 0VU a signal of -6dBFS is far higher than the additional 3dB we have available above 0VU on the meter (because -6 is 12 hotter than -18). ![]() When switching to VU dBFS the reference level is what you set using “offset” and it ‘shifts’ the entire scale accordingly, so that if you set it to -18 for example that same input signal of -6dBFS no longer “fits” on the scale. So it’s a 1-to-1 situation: an input of -6dBFS average will read -6VU on the meter. It looks like the meter when set to default basically just makes -20VU the ‘reference’, and it then shows absolute level measured as VU. I think the labeling is likely not very good here. Maybe someone knows that the “VU db” scale in broadcast standards is., Tbh, I am not sure what that even is, I mean, “dB” what? What reference level? The supervision manual just states “the scale allows you to select a scale according to different broadcast standards”., no more explanation. The default scale in Supervision is “VU dB”. ![]()
0 Comments
Leave a Reply. |