Stillwell Audio update: new site, updated plugins, Fe26 release
-
Winstontaneous Winstontaneous https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=98336
- KVRAF
- 2593 posts since 15 Feb, 2006 from Another Green World
Me too, the REAPER FX versions turned me on to Stillwell about 15 years ago! Glad to see new activity!!Naenyn wrote: Wed Apr 29, 2026 5:15 am This is awesome news! Thank you for the updates. I'm looking forward to seeing what else you create1
- KVRAF
- 7672 posts since 2 Sep, 2019
Do these support Apple Silicon and VST3 now?sstillwell wrote: Tue Apr 28, 2026 5:23 pm Plugin updates
A large portion of the lineup has been updated, including:
* 1973, CMX, Event Horizon
* v4 releases of Bombardier, Dyno, Major Tom, The Rocket, Transient Monster, Vibe EQ, Bad Buss Mojo, Oligarc Filter, Verbiage, Bitter, Psycho Dither, and schOPE
Focus is on:
* improved performance
* resizable, high-resolution interfaces
* smoother workflows
Bitter is of particular interest to me.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
- KVRist
- 410 posts since 9 Oct, 2013 from uk
Trying out 1973 and Vibe EQ...
Even at 'Empty' or 'Track Default' presets, the 1973 plugin 'destroys' the audio here (a simple drum loop). Not pleasant. Using 'Bypass' on it, original sound is restored.
Using 'system 1' in my signature; have closed and re-opened Cubase twice now - made no difference... Anyone else.?
'Vibe EQ' sometimes produces a sharp, audible 'spike/glitch' when engaging or disengaging over-sampling whilst transport is running, coupled with a short audio gap. Is that to be expected.? i.e. only ever toggle this whilst transport is stopped (where no glitch/spike is heard).?
Even at 'Empty' or 'Track Default' presets, the 1973 plugin 'destroys' the audio here (a simple drum loop). Not pleasant. Using 'Bypass' on it, original sound is restored.
Using 'system 1' in my signature; have closed and re-opened Cubase twice now - made no difference... Anyone else.?
'Vibe EQ' sometimes produces a sharp, audible 'spike/glitch' when engaging or disengaging over-sampling whilst transport is running, coupled with a short audio gap. Is that to be expected.? i.e. only ever toggle this whilst transport is stopped (where no glitch/spike is heard).?
System 1 - Win11; i9 13900HK miniPC; 64Gb; Iris XE graphics; Cubase 15.0.30; Studio Pro v8.1;UR44 i/o
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
-
- KVRist
- 163 posts since 1 Nov, 2012
Same here with the 1973.thebutler wrote: Wed Apr 29, 2026 10:54 am Trying out 1973 and Vibe EQ...
Even at 'Empty' or 'Track Default' presets, the 1973 plugin 'destroys' the audio here (a simple drum loop). Not pleasant. Using 'Bypass' on it, original sound is restored.
Using 'system 1' in my signature; have closed and re-opened Cubase twice now - made no difference... Anyone else.?
'Vibe EQ' sometimes produces a sharp, audible 'spike/glitch' when engaging or disengaging over-sampling whilst transport is running, coupled with a short audio gap. Is that to be expected.? i.e. only ever toggle this whilst transport is stopped (where no glitch/spike is heard).?
Resizing vibe eq looks grainy, 1973 looks good.
First and foremost: We need great songs (again)
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
Any of the updated/new plugins are Apple Silicon Native and have vastly improved VST3 support. Bitter in particular was updated, yes.jamcat wrote: Wed Apr 29, 2026 10:05 am Do these support Apple Silicon and VST3 now?
Bitter is of particular interest to me.
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
I've reproduced the error in Live with 1973. I'm working on it now. It seems to be specific to Live, specific to VST3 only. It doesn't do the same thing in Pro Tools (AAX) or REAPER (VST3).
I'll look at the UI on Vibe EQ, but since those are bitmapped UI assets rather than vector-drawn, there's going to be some change in fidelity when scaling, it's kind of unavoidable. The thought was that having it be scalable and user controllable was preferable to having pixel-perfect UI that you can't change. I'll check anyway because I could have screwed up somewhere.
Thanks for the reports!
I'll look at the UI on Vibe EQ, but since those are bitmapped UI assets rather than vector-drawn, there's going to be some change in fidelity when scaling, it's kind of unavoidable. The thought was that having it be scalable and user controllable was preferable to having pixel-perfect UI that you can't change. I'll check anyway because I could have screwed up somewhere.
Thanks for the reports!
-
- KVRist
- 163 posts since 1 Nov, 2012
sstillwell wrote: Wed Apr 29, 2026 1:02 pm I've reproduced the error in Live with 1973. I'm working on it now. It seems to be specific to Live, specific to VST3 only. It doesn't do the same thing in Pro Tools (AAX) or REAPER (VST3).
I'll look at the UI on Vibe EQ, but since those are bitmapped UI assets rather than vector-drawn, there's going to be some change in fidelity when scaling, it's kind of unavoidable. The thought was that having it be scalable and user controllable was preferable to having pixel-perfect UI that you can't change. I'll check anyway because I could have screwed up somewhere.
Thanks for the reports!
First and foremost: We need great songs (again)
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
I've found the issue and confirmed that my patch fixes the issue. I'm working through one other reported issue and should have an updated build out later today. Thanks!
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
I've double-checked the image assets in the plugin. The @2x images are present and are in fact scaled up by 2x.
That said...if you're on a Retina screen (or HiDPI on Windows), you're already using the @2x images at normal 100% scale and resizing the plugin larger is done purely through scaling the image at runtime. On a "normal" monitor dragging the UI larger switches to the @2x image and scales down from there...usually remaining sharp...or at least sharper than it would be otherwise. There's not much I can do about that except to include @4x images in the build and that just bloats the plugin size unnecessarily, as well as increasing RAM requirements for the plugin.
How it visually appears is going to vary on a case-by-case basis depending on the images being scaled.
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
1973 version 4.0.13 and Vibe EQ version 4.0.4 have been pushed out to the website. All known issues should be fixed.
- KVRist
- 206 posts since 31 Mar, 2025
My licence files are not working anymore on Olga ,oligarc and sculpto , is this normal ?
-
- KVRist
- Topic Starter
- 210 posts since 14 Oct, 2005
No, that's not normal...but those plugins haven't been updated in years...if you downloaded and installed again it's the same as it's been for a long time. Make sure that your key file is still in the same folder as the plugin. For those plugins the key file still needs to be in the same folder as the actual plugin, so if you have AU, VST2, VST3, you need to have a copy of the key file in each location.
Once those plugins get updated (probably start working on that next week after I finish putting out any fires from THIS week's release) then we will have centralized key file locations and drag-and-drop installation of keys. For now those remaining five plugins don't understand drag and drop. (Olga, Oligarc, Sculpto, Spector, Tinman...anything marked v3.x on the Downloads page)
Once those plugins get updated (probably start working on that next week after I finish putting out any fires from THIS week's release) then we will have centralized key file locations and drag-and-drop installation of keys. For now those remaining five plugins don't understand drag and drop. (Olga, Oligarc, Sculpto, Spector, Tinman...anything marked v3.x on the Downloads page)
- KVRist
- 206 posts since 31 Mar, 2025
I will try to put the key in the same folder , I forget it was working this way since i ve moved to windows ! Thx for the tips !
-
- KVRist
- 163 posts since 1 Nov, 2012
https://streamable.com/2vl3oq
The 1973 works like it should
but the HPF knob is gone when it is set to 300Hz. Sonically the HPF works fine.
The 1973 works like it should
First and foremost: We need great songs (again)
