Beta 9.13: MAutoDynamicEQ produces pops when tracking pitch

[ALBurk]

Behavior: MAutoDynamicEQ produces loud pops at the fundamental frequency when tracking pitch.
I suspect it may have to do with the crossover of frequencies being processed, as the pops seem to occur close to the same point in the audio on each replay. However, with each replay the position at which the pop occurs does change within some limited range of milliseconds, and varies in amplitude by a wide range (from almost inaudible to blow-your-ears-off loud).

DAW: Logic X 10.2.0
Scenario:
- 24 bit at 44.1KHz
- Stereo audio track with no other plugins.
- Audio file: in this case, dual-mono vocal track that has previously been processed with lo-fi (bit reduction) effect, the result of which is stepped waveform. Both channels are identical and are in phase.

MAutoDynamicEQ setup:
Two bands are used, each of which is following fundamental pitch. One band lifts the fundamental and its harmonics, the other reduces enharmonics.
Band 4:
- General: Notch, Frequency controlled by modulator, Q 6.46, Channels Left+Right.
- Dynamics: Dynamics -24.00 db, Mode Filtered compensated, all others at default value
- Harmonics: Depth 100.0%, all others at default value
Band 5:
- General: Peak, Frequency controlled by modulator, Q 4.99, Channels Left+Right.
- Dynamics: Dynamics +12.00 db, Mode Filtered compensated, all others at default value
- Harmonics: Depth 100.0%, all others at default value
Modulator 1:
- Pitch: LFO and Min/Max at default values
- Shift: Semitones -6, all others at default values
- Autotune not enabled
- Detector: No side-chain input, Min Freq 155 Hz, Max Freq 400Hz (frequency within range of fundamental), Stabilization 10 ms, Speed 88.0%, Accuracy 100%, Threshold -20.0 db
- Parameters: a single Parameter: Equalizer Band 4 - Frequency 4, Range Mode Up and down, Value default (632.5 Hz), Depth 100%, NOT inverted
- Transformation Shape at default
Modulator 2:
- Pitch: LFO and Min/Max at default values
- Shift: all at default values
- Autotune not enabled
- Detector: No side-chain input, Min Freq 155 Hz, Max Freq 400Hz (frequency within range of fundamental), Stabilization 10 ms, Speed 88.0%, Accuracy 100%, Threshold -20.0 db
- Parameters: a single Parameter: Equalizer Band 5 - Frequency 5, Range Mode Up and down, Value default (632.5 Hz), Depth 100%, NOT inverted
- Transformation Shape at default

[ALBurk]

By the way, the way to solve for this issue - and perhaps the proper way to set up for this kind of processing - is to use two instances of MAutoDynamicEQ in serial on the track. Set one up for lifting the fundamental and its harmonics, set the other for reducing the enharmonics. Still, it would be great if it could be done cleanly inside one instance.

[MeldaProduction]

Hi Al,

please just copy the settings as text (button at the right bottom corner) and paste it here, I'll check it out then.

[vectorwarrior]

I've had problems with clicking when moving bands when an eq has both cut and boost on too. I'll also post settings if I can repro.

[ALBurk]

Ugh ... I remember reading about the copy-settings button. That would have been a lot easier!

Be careful when testing this. I have had pops that exceeded +35db.

Here are the settings:

Code: Select all

78DAED5A5B53EB38127EE757B8FC9EC4F738552153E14006AA08B0843A67F751C75612ED3892B16520F3EBA75BB21D3B173614676A77A98482C4ED564B6A757FFDB5C9F0B7B75562BCD02C67829F9B76D7320DCA231133BE38370B39EF84E66FA3B3E1745C4871B9E664C5A2ABE79C4A090AB9F14D240949731AE3EDABE707C2690256CCCD8D0BC2E3BC945B0DF9235B2C6553CE6506F76021579CFC4C68ACC4D7A0F540F2FC699DD273F3FAC1B01DD3B815AF1BD9AD96A524232B2A69764953B9544BA845BF13C695B596E4BE906D21CED549C130BAC1B56CCB190C067E10345460E652C33BA091AF84C0F9ADAEE537C433319733228B8C48E567CB1C0D7FCF48BA1C0D53C1B8344AD7E6DDD992E0B666CF05C9686C1A4D6F3CA3DDBED5B7ADBE6948BD7DF13A5BD2647E7D6F1AFFC48507FD60B3AC7FE999AE49B6121CACF746C37222F4809ACAB8CCC82B9CE554C4546B3FA8054D12B2C82FC0A2679BBDA385C69B72FD1AFF1EA3D0DB5E0E8894433EEB97074AFE501E71E020EC93475A1EF19CAF1923632949F40726A7350868C71A989B7B252E741CA71B7AA179D88DB523BA1B280177065D2FB0E0B5C79D8EED5883300C0781F7A5DC59EDDFF9B8B7BCEE6070C05B6EE040DC85A1EFDAA774048FB85DFF8B02549572B6DBF53CF3684FF95DC7F55DCC51ED29ACCBCD1AE742E9FD22F8D5D31CE06C38CE28C98D2979632BF6277D14AFB91E0C773849D67FD2CC1827E992601C01AFA884DF96840383D2FB9AB2B7B62FF5E71F4BCAAF591C53CD81668AA0708A244693949928B208C6BBA6F183F158BC96640B4CA3A7323A67095018F0DF317E549B6F91A3833EF2B6D57ACDC9706A11C13A4566216D14194C695963DB9B4C1AFB0453139668D2790F3C3663312DB5418259A65C69CC96E255C9BF93A4A0797578D514F63B53587B2C37C73A9F18EB7E62ACF7F1B133C1C5023869154D76CB93A0A094736DD852962D8DE34A625792B092385A3299E0EC4AE2A26432C1DF52E29D9B78AD2478CA55F46274ABB6A1200953211E9314F9F13859888CC9E5EADCBCA4735224D2C4DCA86E5F900C19B869DC51D8E27895266CBED6C1AD4259D9CF590E63192F9DF144B205957BEE8C8695D949469F0BE87DD653C68D178C12285716AE785783BC6D34D03DE8DA9444F4864316DE4212CBEA7EC7D326D446AFF80B4DC42700691B5ADA66F17C9B0EF8C874BB798BB374B403B6D52DA5EE1CBEE51E9BF56A12EDA2DEFEC5D7BB2CA304A2E676729F8FF0AFD5C681EA78D495DEEC0393D1128E3F233C67944B2DBDE2009C11D41E5864DDDBB15C02FE406BDB6B488D4991248F842F94E3300ABFEB7355385CABDDC11B98AD23F92774BD866774366B32205ED5D00BA0A8458A06BCC1E6052BF95CA9DA8E8CAAD2D44B1C0DA73797378FB841DCC69D903081AD63B70E9409B4E0E295667AFA5BB1202A0F59047BCDC4BF69A47BE6479A40BDA24F6C45CBDA43386C1D563B554DB0317E6339804527B4E20B535D394879E078B9CC41ED16323789413792229BC20A946BF043EBCE5385709349E055F8A1549F1AF5B08950A88A2FBDAF1B9E16F295BCD0B9C8568D21CEF6908DF59EDE0126FD8B8A11A3EA2AA05A8283F595DEF584E4804C189DA543662955A8D2B53774E7215F474B318E44914B16352B5CA348C73304EAA57A505196AD6B91C44D679766CBABE6020E9D86F1389DDD52BE289F476011AC6641CCD8548A5A0C7131A920AD25FD4719F01B19E34AB32182D0121C5D56925DC8BA6546E9C312D63669ED19E5F952EFAFEB627616546FD7D617B070FC0CE5089C2656DAE747E7C707A8D98EFD6ACAEA40FFB6399B1340EE6F0E66EBC1D091CF7FCAA73F7D671058B6E7C0CF5E66DC66EAC73F31B0FDD0EE3BA1EF84F62FB5EB8741DFF3C0AA1B1E61F7FD36CAB2A1A5F4FB1614965FB846EC5DDC30ECC30A7DE7F376EB66A6341EF61DCF0FFDA08F0F2BDE315E760A071B0500FC6608F52AF4828F9B428A05A086FA718494E67E3E874E4C8AD4C821C2136A56728E6292C98DFC72F6F84457A998AD79746EC240B3098D4E75557677B0FD4B1A9175053DEAA2792F219AB3D53877B35AD19811493780D7023FA7BEDA98D1DD4C852B33C8AC0A42B7963A1A3E65740570AF335AA7F21D5405C4C992AAF966A312FEC79C770FB31F58AB7F18112A9DBED6E9EC55724BD8E8B50E7026696ADC48BAB2D4A3FAB28AA1008B6D5BE26CABB83B2ADEB68ABFA3126CABF45B2AB8A0B2CD2FAF50E79B2838108510577F9F52FDD03BC723001686A5F897B19CDA226406F601B288E9876641831DFB9D83D8C3B977260261739BBD66A821A368A41D7602311375981DC3AA9AF5528DFE523CABD772C86808643B16AB3243757EB7C8279E11927A00AAA8C848C5F681B95454FB9146585B02CBB17CA0D6B60BC9847C65EBBE3DB05CD70E0650D9F0F1009BCB1985C64D707C3AD081D6A466736188B14D7E3220F7D53F7014A8B5888C6EB0D902FA9713BE9CF0E56FC4171D64705C50DE8C8AE1AB6EBC874DB16A8DEDFFE9D6D86FB5C6FE4E6B1C38DEA9353EB5C6A7D6F8D41A9F5AE3536B7C6A8D4FADF189BA9E5AE3536BFCDF688D4F6DF0094BFEFFDA605BBFE5A3B361E3CBC5F8951AECEFB644D32291ACEE0795088BFD0BD56DAFF1ADC832C08DA64CF7B5EA3B3AEF21CE9DE0D4441898F63497C5F7FB42E2DB0F16CBE5B4FAAFBDB1DD00E1462A1518813882574F4D98D15FB3F8CE7206D4AA1CA4206717B7F669ED0126FF3030E1F223E4510DE3961578BBC66BCD6326284DF4AA5D3EB57174D77AE98C234C97E31BA07A069FF67E977D74F6179AC55D35

[MeldaProduction]

Aaaaaha. Well, here's the thing - it's kind of inevitable, but you can simply enable the output safety limiter.
Moving filters quickly is always a dangerous business. It takes time for them to adjust to every change in the signal, that's often followed by a short instability. It gets worse if the resonance is high and and there is a signal in the affected part of the signal. You created about 20 such a filters even with dynamics, so I'm not really surprised. This would better be done in spectral domain, however that would introduce latency instead...

[ALBurk]

I believe I understand what you are saying, and I agree, it would be done more efficiently in the spectral domain. I eventually discovered the output limiter and engaged it. Of course the pops continue to be generated, but at least it doesn't alarm the neighbors (and my own ears) as much now when it happens!

From a consumer's perspective, I guess I find it a little disconcerting that the plugin (or any plugin, for that matter) would allow itself to generate artifacts that are so loud and so sudden without me specifically asking it to do so. I would encourage you to consider either turning on the output limiter by default, or adding an internal algorithm that automatically clips spikes at around +10db or so ... yeah, I know that adds processing :-/

When I first began experimenting with pitch following, I had hoped the plugin would allow me to enable cross-fade between the positions of the active band. In retrospect, I think it would also effectively nullify the instabilities. Again, it would require more processing, but is something I would gladly enable in a situation like this.

In the meantime, I will start saving my pennies to eventually get MSpectralDynamics!

[MeldaProduction]

hehe you know with power comes responsibility . No, really, with almost everything (except most one knob crap) you can cause some problems with well chosen signals...

Anyway I actually got a little interested in the idea about changing harmonics, so there may be a dedicated plugin for that, but I'm not sure yet, current results are ok, but nothing so miraculous..

[vectorwarrior]

Ohhh, any chance you could send that round the beta group. I would be interested in trying it out!

[steve2KVR]

...indeed, yes please...sounds (pun) very useful.../s~

[MeldaProduction]

Will do probably

[ALBurk]

Harmonics management is a real chore with some sound sources. I would definitely be interested in seeing something to help simplify the task!

[MeldaProduction]

Are you on the beta testing list?