Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[exmatproton]

Okay..sent an e-mail. Issue is also there in FLANGER. Opened MFM2 and tried some heavy and fast modulation on delays there; no such issue. Seems a UHBIK thing

Then you might actually be talking about something else entirely.
What we fixed was a scratchy sound that was caused with certain settings whenever the haas delay was active.
I guess you are talking about modulation artefacts when adjusting certain parameters.
We'll continue this via support.

Edited previous post. It was buffer timing stuff. Fixed it by altering FL Studio's wrapper settings

[Ploki]

I guess i should wipe the previous install?

[tasmaniandevil]

I guess i should wipe the previous install?

No idea how you managed to do that.
But yes, deleting the previous version might help. Although this shouldn't be needed, as the Mac installer usually takes care of this. And I have installed new over old versions (and vice versa) a million times during testing, and never had this glitch.

[tasmaniandevil]

Edited previous post. It was buffer timing stuff. Fixed it by altering FL Studio's wrapper settings

The wrapper setting doesn't really fix it, it just changes the sound of the scratching.
I just tried it over here, and this is one more of those issues that only happen in FL Studio, likely due to their unique audio engine. What you experience doesn't happen in other hosts.
We'll have a look, maybe we can find a workaround that doesn't require the wrapper settings.

[Shabdahbriah]

Yay for us!!! Congratulations.

[jtsterays]

For these effect plugins, and the others like Satin, CC, etc... It would be nice if they have pop up hints in the future.

[exmatproton]

Edited previous post. It was buffer timing stuff. Fixed it by altering FL Studio's wrapper settings

The wrapper setting doesn't really fix it, it just changes the sound of the scratching.
I just tried it over here, and this is one more of those issues that only happen in FL Studio, likely due to their unique audio engine. What you experience doesn't happen in other hosts.
We'll have a look, maybe we can find a workaround that doesn't require the wrapper settings.

Cool. Thanks

[EvilDragon]

Thankfully Image-Line is gonna rework their audio engine to use a more established buffering method, with proper timestamping of events within a buffer, so that option is gonna be history... I think that's next in line after the mixer rework.

[exmatproton]

Thankfully Image-Line is gonna rework their audio engine to use a more established buffering method, with proper timestamping of events within a buffer, so that option is gonna be history... I think that's next in line after the mixer rework.

indeed. They've been working on rebuilding the whole underlying code for quite some time now.

[Erik_Lucas]

This is great news. Thanks u-he!

[blumpy]

This is going to be awesome, thanks!

I have a little suggestion.

For the compressor, the linear rate of the ratio knob probably isn't the best for engineers. There should be a whole lot more resolution in the 1:1 through 2:1 and the 2:1 through 4:1 range. It really should be 75% the control's range, because that's where the greatest sonic changes will occur. After 8:1 through 20:1 there's not going to be a ton of difference.

Try this: set the threshold while you have a 1:1 ratio. Then slowly change the ratio. You'll immediately hear the changes at the lower rates but once you get to 8:1 the changes are minimal but it takes up 50% of the range.

[exmatproton]

This is going to be awesome, thanks!

I have a little suggestion.

For the compressor, the linear rate of the ratio knob probably isn't the best for engineers. There should be a whole lot more resolution in the 1:1 through 2:1 and the 2:1 through 4:1 range. It really should be 75% the control's range, because that's where the greatest sonic changes will occur. After 8:1 through 20:1 there's not going to be a ton of difference.

Try this: set the threshold while you have a 1:1 ratio. Then slowly change the ratio. You'll immediately hear the changes at the lower rates but once you get to 8:1 the changes are minimal but it takes up 50% of the range.

agreed

[Erik_Lucas]

This is going to be awesome, thanks!

I have a little suggestion.

For the compressor, the linear rate of the ratio knob probably isn't the best for engineers. There should be a whole lot more resolution in the 1:1 through 2:1 and the 2:1 through 4:1 range. It really should be 75% the control's range, because that's where the greatest sonic changes will occur. After 8:1 through 20:1 there's not going to be a ton of difference.

Try this: set the threshold while you have a 1:1 ratio. Then slowly change the ratio. You'll immediately hear the changes at the lower rates but once you get to 8:1 the changes are minimal but it takes up 50% of the range.

Completely agree.

Also, wanted to point out that the compressor's inflation function reminds me a bit of MDW's DRC2 input gain function. It's far more than merely input gain.

[JoSh_007]

Yeeehaaw!
This will be a great (sounding) weekend

[sl23]

Thanks for the updates! Shame I can't use it if you've dropped vst2 support though, MuLab doesn't support multi-vst3!