9.13 MCompressor

[ALBurk]

I have been getting "clipped limiter" distortion (sounds like static) from MCompressor when using a hard knee with ratios anywhere above 5 or 6.

Metering in front of MCompressor shows a cool signal peaking at -10db being fed into the plugin. Any time the signal crosses the knee, it crackles.

Clipping artifacts would be expected if the compressor were driven particularly hard, but IMHO that is not the case here. I have experimented with a variety of other compressors - set up with the same parameters (or a close approximation) - on the same track and they do not regress into the clipped limiter behavior until much higher ratios. It is certainly possible that, despite my best effort, I am still doing something stupid with MCompressor.

Settings:

Code: Select all

78DA8D535D6F9B30147DEFAF407E2F8100119142AA362B5BA5A58BB66AEF1EDC80157F30DBA464BF7E179C4E90E4617E48E273EE39B6CFBD593D74827B47D086299991D00F8807B250259355465ABBBF4FC9C3FA6EB5DD28D16830466903D6226B3C2A1ACE6C5B82A696A98CA074A3A4D58A73F47B96F4178772806BCAF7156572D834545301B657595A1CA658D11AAB84A9690353C2C9EF133F59A423F82001842AE159B622235FA82E2F48C3FEF44EFE3C19119CC943515329811B7CF48811B463C24946A86A6DD35A7785B1CFF9E1A99FA4CB20598C19E040CD70F244200C0759D97AEA6F6B8CB656BC4FCB8F92380DA3285DCEA398783F58099B1A4F76790EBA7FD89676B986DF2D76EC949179806BCC32396147D48ED3536FB55E559A36B5F749D377ECE9169374F04E3169BD9CD3CA3C6142714466D7203A76D7373E5D4137A4E1200DCFD5711044C102D12512583D1B6E8563379AA7196E5F95850B68DB72CB761F413A68F8E53D76CC84383271503E916137CFC8AB9280CF7B915B3CE65B6BFBAFEFFDC7674C4543D916D851F98683CC95CE483E2C4C152BBEC2117889DE8555FA66C58BC42919310B7C579E13EF2733ECDCBB8FAA777A84BDD2E2CD7BE44D4D8739095CFF2EE5EEA25367B72E9D5DD9FF589FF57DD42E2D8C6D76E33FBEBEFB0BA4135354

[mesaone]

Tried your settings with a couple different types of material, didn't hear any issue. Tried again with different gain and threshold settings, still nothing.

What host are you using, and can you post a clip of the signal you're feeding the comp?

[MeldaProduction]

Well, you created a very hard brickwall limiter, so it actually could do that, depending on the audio signal. (just think about what it does when a high level wave with increasing level comes in, e.g. sine) Anyway please post the audio file you processed, I'll check it here.
Note that creating a brickwall limiter, that doesn't distort much isn't so simple

[ALBurk]

Hey folks, sorry it has taken so long to reply, the lead-up to Thanksgiving is always too busy. So I took a few minutes today to reproduce the issue ... and have not been able to reproduce it. The projects that I had tested the issue in are unchanged since reporting it.

I can say this: when I was experiencing the problem, all CPU cores were nominal and within normal operating temperatures, HD was showing no activity, network was inactive, memory utilization was normal, no unusual processes were running. The machine had been booted fresh that morning, and everything looked good.

I am not a big fan of wasting other people's time, or my own, so I am a little bit mystified now. In case you are still interested, I have attached a clip of where the problem had first been noticed. I had bounced this clip out so I could test in a new, empty project before reporting the glitch. It is a vocoded vocal, and I was preparing to process it for background fill. I had thought the issue might be due to the combed audio, but today that doesn't seem to be a factor.

@mesaone, I am on a 2012 MacBook Pro Retina, 8 GB RAM, solid state HD with plenty of space, still on the latest Yosemite (10.10.5), running Logic Pro X 10.2.0.

[MeldaProduction]

Hi AL, my guess would be that you accidentally clicked on some option, e.g. AGC, which caused this. Hard to say, anyway if it happens again, please just let me know.