zl-audio / zlequalizer Goto Github PK

Hy there,

thx for this great plugin.

there is a very heavy cpu consumption on cubase with the plugin, it drives asio-guard very high. its also higher when gui is open.

i did a demasking tool with all 16 bands enabled, listening to a sidechain with detection circuits set. dropouts get that heavy that it gets hardly usable.

it also would be nice to be able to enable/disable the detection circuit if wanted.

it would also be great to just display the sidechain in addition inside the fft display without having to enable the "headphone" button. maybe in a different color?

fft display settings don't get saved to cubase presets. i always have to reset my preferences when the plugin gets inserted. it doesn't save those settings inside the "cubase default" setting for the plugin.

again thx for this great plugin.

greetings
zag

Hi i just recently found this plug-in from a youtube video and was interested in trying it out. Tried to download it a few weeks ago and upon opening Logic I got a message along the lines of "ZLEqualizer cannot be opened because the developer cannot be verified". I figured I'd try again today and after downloading and opening up Logic I got a message that said "ZLEqualizer can't be opened because Apple can't check it for malicious software". Following that message it says "This software needs to be updated. Contact the developer for more information". The message doesn't pop up every time I open Logic, but in the Plug-in Manager it says cannot be opened under ZLEqualizer. Was wondering how I can fix this. I am running Logic 10.8.1 and Sonoma 14.4.1.

How to reproduce:

1. Open ZL instance in a mixer
2. Make a band
3. Switch windows focus to other things in FL studio (e.g Playlist)
4. Go back to ZL window and try to adjust Q with middle mouse scroll

• It starts to work again after you close the ZL window and reopen it (without completely removing it in the mixer)

It worked for the first time I used it but after that any time I would add a band or manipulate it in any way the plugin itself would freeze and then Reason would freeze causing me to have to "end task" in windows.

Reason 12, Windows 10

Hi, ZLEqualizer and ZLWarm are the only two that don't want to work. I've tried all the others from ZL without any problems.
I have two OSX intel systems, 10.13.6 and 10.15.7.
On both, ZLEqualizer and ZLWarm appear in every DAW in AU format, but they don't open at launch. While in the VST3 format they're not even displayed. I'm sorry because I would have especially wanted to test ZLEqualizer.
Thank you

A more accurate solution for gain compensating static EQ bands is as following:

A static output gain is to be applied based on the frequency, gain & Q of a single band. At 2khz, the amount of gain compensation is roughly half of the inverse of the band.
So, a bell boost of 6db at 2khz will apply a static ~-3db gain to the output.
As you go higher up the spectrum, the amount of gain compensation lessens. Likewise, ultra-low frequency boost/cuts don't necessitate as much gain compensation on the output.
Bell cuts should be compensated slightly less in general as it's easy for the entire spectrum become too loud.

Hi/Lo-cut filters shouldn't be compensated at all for the same reason we lessen the compensation of bell cuts, just the issue is magnified (potentially) infinitely.

Q affecting the gain should be simple to implement, I don't know the specific formula though.

A note for lessening the gain compensation around the bass region; this should be done very low down in the spectrum to avoid bad results with sub-heavy music. TDR SlickEQ starts slightly lowering the compensation at around 300hz, and then sharply at around 30hz.

Examples of plugins which, more or less, use the method I have described are: SlickEQ M, Pulsar Massive & AOM factory EQs.

Overall, this method leads to fairly effective results without any of the uncertainties of dynamic processing. If it fails to work, it's as simple as a manual adjustment from the user, which most are accustomed to anyways.

Dynamic bands are a different story. Personally, I'm not a fan of AGC in general, whether it be in a dynamic EQ or a single band compressor, however, if we want to keep this feature to help with dynamic band compensation I'd imagine it'd be best to have AGC after all of the static gains are applied to potentially correct any mistakes from static gains, getting the most out of the dynamic process per-say.

Hi!

I heard about ZLEqualizer through commit 1059bc8 and the related CI issue…

I noticed that the Git repository does not have an topics associated. Here's what it looks like for https://github.com/libexpat/libexpat and where to find the related button if interested:

The auto-completion in there helps finding the right topic names, e.g. whether it's audio-effects or audio-effect (singular). What do you think?

Best, Sebastian

Hi!
Thank you very much for a great free product!
I was wondering if it's possible to add OpenGL support (or something similar) for machines that aren't very Metal/Direct2D friendly or just aren't the most productive? I've been experiencing some serious freezes and lags on my not-so-new laptop. I don't know what API Frequalizer uses, but its interface is pretty fast and responsive. Perhaps this will help in some way.

Will be fixed in the next release.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

On Linux (Debian/KDE/X11) there is a massive graphics lag with the plugin (concerning as well the host's Ardour GUI) since about a week.

It must have happened in the past week, but I'm not sure if it was after d72acee or only after 23f4fcd . I guess the probability is high that it could be related to the JUCE update, what do you think?

Discussed in #52

https://github.com/ZL-Audio/animator/blob/1836239545ad48910c363dab6ae92d28ecd2b897/Source/.clang-format#L1C25-L1C25

It does sounds strange for this to be a link to a file on a personal computer

Hi dev:
Thanks for this wonderful plugin!
Looks like the collision detection is making both plugin and host laggy, running at extremely low frame rate. See the video below:

Above was recorded in REAPER; also tested with FL Studio which gives about the same result.

I'm running ZL Equalizer 0.1.9 on Win11 22621.3155, also tested on my old computer which is on Win10 19044, the problem seems to be a little better, but still exist.

Hi!

It seems like ZL Eq's LV2 and VST3 versions are named differently: "ZLEqualizer" vs "ZL Equalizer".
Also the author and tags are missing in Ardour's plug-in manager.

I'd also suggest to change the tags to "effect, equalizer, compressor" rather than "plugin" :D

When I try to use this plugin as a dynamic EQ and change some parameters it causes Ableton Live to crash unexpectedly. Could you please fix that? I would highly appreciate it if you could do that! 🙏

Hi!

Current LV2URI var in CMakeLists.txt is https://github.com/ZL-Audio/${PRODUCT_NAME}/tree/${VERSION}
which is https://github.com/ZL-Audio/ZL Equalizer/tree/ in result, which is confusing.

I think the correct URI should be like that https://github.com/ZL-Audio/ZLEqualizer without space.

Hi, changng rotary values with mouse wheel is complicated, jump to much. Maybe with key combination like shift wheel, allow small steps.

Also, show rotary values when you move pointer on the graph.

Thanks.

Hi,

first of all, congratulations and thank you for your great work. Much appreciated!

I've noticed that in the pre-built release you are providing the plugin only in VST format. For me that's just fine, but for Pro-Tools users that's a no-go (PT does not support anything but AAX).

OTOH, Ardour (and Harrison's MixBus) users may prefer LV2 over VST (I don't know if that changed lately, but in the past VST and particularly VST3 support in Ardour was sub-optimal, LV2s worked much better).

AFAIK Juce can produce many more formats, including AAX, AU and LV2 (and, via a 3rd party extension, possibly also the new CLAP).

Are there any reason why you choose not to provide other formats? Can they be built from the current sources, or there are problems preventing to do so?

If there are no problems, could you be so kind to provide those other formats too in the binary releases? :)

Thank you again, and keep up the good work!

Hello!

It is good when is working but when I try to active the collision it is taking me out of my Daw even without any other plugin, can you fix please!

Thank you your plugin is amazing just that is the problem.

Hi

Many thanks for your hard work on this collection of plugins. It's really cool to have these available :)

I have built all of them for linux and they all have one common issue with the dropdown menus. I guess it's some kind of transparency bug (perhaps due to the lack of hardware acceleration on linux?)

It's easier to see on one of the others like ZLEComp:

But it is also present in ZLEqualizer, though the shadow / background is much smaller so it only shows as white corners:

The other UI elements work fine. It's just the dropdown menus that have an issue.

I also spotted a typo in the Collision menu: Strength is Stength.

Using 0.1.16 LInux VST3:

• create a high pass filter (it defaults to 12 dB)
• select 6 db per octave and it becomes a low pass

AGC (Automatic Gain Compensation) is an amazing feature, but it can be challenging to determine when it is active and how it is affecting the audio levels. Sometimes I switch it on and off and the levels don't seem to change, it would be much more valuable if it had visual feedback to show it in action.

To enhance the usability of AGC, I propose adding a small meter that displays a single number indicating the difference between the input and output levels. While AGC is actively adjusting the levels, the meter should be red. Once AGC has stabilized and the output is steady, the meter can turn green. This visual feedback would allow users to confirm AGC's operation and effectiveness.

The meter should be prominently displayed in the main interface to ensure it is visible as adjustments are made.

Thanks for the great plugin!

$ ldd /usr/local/lib/vst3/ZL\ Equalizer.vst3/Contents/x86_64-linux/ZL\ Equalizer.so 
/usr/local/lib/vst3/ZL Equalizer.vst3/Contents/x86_64-linux/ZL Equalizer.so: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/local/lib/vst3/ZL Equalizer.vst3/Contents/x86_64-linux/ZL Equalizer.so)
/usr/local/lib/vst3/ZL Equalizer.vst3/Contents/x86_64-linux/ZL Equalizer.so: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/local/lib/vst3/ZL Equalizer.vst3/Contents/x86_64-linux/ZL Equalizer.so)

This happens on Ubuntu 22.04 "Jammy" (latest LTS release) and derived (such as latest version of Mint), as well as Debian Stable, etc.

You've used a way too bleeding edge version of libstdc++... most people will be unable to use your binary release.

Please rebuild them with something older (GLIBCXX_3.4.30, that is libstdc++6 version 12.x or earlier), which are available on most current stable distributions...

Hi!

I would like to start by saying thanks for the regular updates to this great product. In addition to adding useful customizations, the performance and responsiveness have really improved and it is now quite comfortable to use. Thank you!

I also found a few bugs and wanted to suggest a few improvements:

1. When clicking on the analyzer values pre, post, side (quick change or using the dropdown menu) the plugin/DAW freezes/crashes.

2. Sometimes the equalizer curve just stops displaying.

3. After several color scheme changes, the ability to adjust values with the mouse wheel is lost. After reopening the plugin everything returns to normal.

4. Returning to the first bug - is it possible to add resetting of the analyzer graph, for example, on a single click on it?

5. Is it possible to add a permanent display of parameter values? Perhaps as a separate option.

6. And lastly, what about zero delay? :) Right now it is 1 ms even in minimum phase mode.

Windows 10/Studio One 6.6.0/VST3 0.3.0

Is this meant to work on Debian Bookworm based distros? Complaining about the GlibcXX version. Does not work.

OS: Linux Debian, KDE Plasma X11

In git head I have some strange behaviour on the plugin window size, where it got stuck at h=950 / w=1859 without being able to reduce the size. Even when using the plugin "internal" corner resize tool to drag it smaller, it jumped back.

So I had to edit $HOME/.config/Audio/Presets/ZL/ZL\ Equalizer/ui.xml , in order to bring it back again to a reasonable size.

<PARAM id="window_h" value="450"/>
<PARAM id="window_w" value="690"/>

Could a "Reset window size to default" button in the UI section make sense? And choosing a default size, which could be usable as well on e.g. 1600x900 wide laptop screens?