Core Delay - Filter Section

[bananadyne]

1) Filter frequencies are slidable, but not editable. Should be able to click on the LPF or HPF handles and specify  a frequency in Hz

2) Filter spectrum range is fixed, doesn't respect Nyquist at high sampling rates (running a 176.4K project here)

... and in other news, it would be nice to see ChannelTools come back as a VST3 and also, BitMeter!

 

[Glenn Stanton]

yeh, not being able to punch in numbers in the UI and only depending on turning knobs or moving sliders makes things much hard than they need to be. maybe enable the editable value boxes for desktop OS and disable for non-desktop OS if that was the intent of making the UI harder to use.

imho, honestly the old delay UI was great. finding another dual delay with the same ease of use and even functionality is limited.

Edited Saturday at 04:08 PM by Glenn Stanton

[Amberwolf]

One big reason the Sonitus stuff is in every project I have, instead of one of the many other similar-type fx of each one, is because of what I can do it their UIs (the other is their sound).

Personally, I despise knobs on a GUI.  It is much easier to precisely use and *see* slider positions, especially relative to each other (even if there are "modifier" keys or motions to use a mouse with a knob to make it closer to using a long-throw slider; it's just not as obvious and easy, etc).  

I also can't use anything that wont' let me type in a specific value when I need to. 

(Not that y'all have any reason to care, especially since I'm not yet a paying customer, but I have sometimes severe problems controlling my hands and body, so being able to type in numbers is frequently the only way I can set things the way I need them to be, so anything that doesn't let me do that is something I often won't be able to use at all--doing stuff with the trackball set to really slow tracking helps with a lot of things, but it isn't enough all the time.  I can't imagine that I'm the only person with such issues). 

 

I'm only going by the posted screenshots so far, and stated or implied things from other posters, not having yet used these new versions, so feel free to ignore anything that is incorrect because of that, and apologies if so: 

There are things in some of the new GUIs that are kind of a waste of space that could've been used for other things; for instance the "tempo bar" in the delay--in the original that is a small simple button that changes state as it's clicked thru it's options, and a readout for the tempo that is also a box you can type into. 

Having the "duplicated" space for the two different preset bars wastes space--the old one had a simple button-dropdown for it's internal presets that worked fine if you used those instead of the DAW's preset system.  

Entirely aside from the knobs vs sliders making it much harder for me to tell at a glance what relative values are in cases where that's desirable, there isn't a box to either see the values or change them direclty to a precise value by typing instead of fiddling with a knob.   

 

 

The two big things that would be real improvements to the Sonitus Suite:  fixing the automation parameter names, and adding the missing ones, and adding more feedback in the UI for what is actually happening, soundwise, to the output vs the input.   Somewhere around here is a post from the last few months with my thoughts on those things. If I find it I'll link / quote it here, in case it is helpful. 

[Amberwolf]

Found it:

  

On 8/15/2025 at 7:26 PM, Amberwolf said:

If I were to ask for just one thing to be updated on them, it would be to have full automation of every item and control in every plugin.   There are a number of things in various ones that don't ahve automation available.   It'd be nice if the names on all of them also completely matched the UI control names (most are close enough, but not all).  

 

The UI is fine for my purposes, being much more usable and readable than most, though if I could update those, I'd add a display showing the output results, as a vertically-scaleable spectrograph in the case of EQs, and as a waveform in the case of the others (ideally with input WF on top and output WF on the bottom, with a horizontally-scaleable time and vertically-scaleable level.  In the EQ, I'd stick that as the background for the EQ curve itself.  The others would require adding a spot for this.