TC Loudness Radar Error

[jamesmonty76]

I'm experiencing an Unsupported Sample Rate error when I use the TC Electronics Loudness Radar plugin. I tried to applying the plugin to multiple tracks, not just the master track, and got the same results. I have also went to Save As... and changed the session setting and same results. As far as I know all software is up to date. Has anyone experienced anything like this? Please help!!!

[SteveG_AudioMasters_]

What's the sample rate of your file?

[jamesmonty76]

196

[SteveG_AudioMasters_]

IIRC, the restricted version of the TC Loudness meter doesn't run at elevated sample rates. These aren't used in broadcast, so there is very little call for anything like that. I don't know (and the specification is remarkably quiet about it) what the stipulated rates the 'posh' version (that you have to pay for) will run at, but it's more likely to support higher rates I expect.

Why are you recording at such a high rate?

[jamesmonty76]

Interesting! I feel like a sample rate of 196 isn't insanely high for recording good quality recordings. So, sounds like my options are probably some kind of work around, or purchase the next level of software. Thanks for responding as I didn't see this problem listed in anything published. Cheers!

[ryclark]

There isn't such a sample rate as 196. It's either 96kHz or 192kHz. Either of those is much more than is required to record any normal human hearable sound. Hence the normal use of 48kHz for video/broadcasting and 44.1kHz for CD/radio. Very high sample rates were only necessary some years ago when A/D converters and their anti aliasing filters weren't too good. So high sample rates make larger audio files to store and processing needs a lot more computing power. It makes no discernible difference to the audio with today's good converters.

[SteveG_AudioMasters_ · Accepted solution]

jamesmonty76 wrote:

Interesting! I feel like a sample rate of 196 isn't insanely high for recording good quality recordings.

Well, assuming that you meant 192ksamples/sec, that's going to let you sample frequencies up to 96kHz when the greatest frequency a human can hear (and only children at that) is around 20kHz. You get no benefit in terms of frequency range in any sample rate beyond 44.1k (CD rate). Raising the sample rate beyond that means that you are storing a lot of noise for nothing!

All modern A-D converters use a method called over-sampling, and it is this process that removes the need for anti-alias filters, and it was the phase changes in these that used to affect very high frequencies at lower sample rates. But now there's some good (and reproducible) research evidence that nobody at all can detect the difference between material sampled at 44.1k and anything higher, so it's simply not worth using, quite frankly. And, of course, if you are producing material that's to be broadcast, then you'll need it finally to be at a lower sample rate anyway (possibly 48k if it's for video, but nothing higher than that) and then the Loudness Radar will work fine!

[Underwood4774]

Hi Ive just upgraded to 11.0.2.2 and now when I insert the TC Electronics Loudness meter to any track I'm getting the "Unsupported Sample Rate" error also. Input Audio sample rate in preferences is 41KHz and the Output Rate is 48Khz. The Loudness Radar was working fine prior to the upgrade.

Im at a loss what to try now to resolve this issue. Any suggestions would be gratefully received as I value this effect in my productions.

Thank you in advance of any replies

[SteveG_AudioMasters_]

Underwood4774  wrote

Input Audio sample rate in preferences is 41KHz and the Output Rate is 48Khz. The Loudness Radar was working fine prior to the upgrade.

Does it work okay if the sample rates are the same?

[Underwood4774]

No afraid not, I've tried all config settings that I have used in the past, and have now set them to default Input and Outputs of the Mac, and still no change. It seems very strange that its only happened since the lates update. I'm wondering if its still to early for anyone else to have noticed he same error. I would be interested to know if thats the case.

[Underwood4774]

Hi steveg16669895, Problem resolved. The new update overwrote all my previous session settings which I had not noticed originally. Once these were reset to 41KHz instead of 32Khz which the new update has as a default the problem has resolved itself. Still seems strange but at least Im back with the Loudness Radar Meter effect working normally. Thank you for your suggestion.