jerryuhoo / fire Goto Github PK

This would make it possible to package it for source based distros.
I wuold like to package this for NixOS.

@baconpaul, You have done this a couple of times for other plugins, would you mind taking a look, or giving some advice?

Hi there ! First i have to say its a really helpfull and good sounding vst! But there is a bug, everytime i click on the High Quality (HQ) Button in the plugin it will stop working. Deleting the plugin from the channel and setting it new up works for fixing it.

i literally cant find it anywhere i removed what i could but its not changing anything in the menu button i just want to bulid off his and i can find basically everything esle but anything to do with that menu button where is it located what file i just want to remove it damn

Now JUCE 7 is out, how about an LV2 version of the plugin?

Hi

why can not ZERO equal to OFF?

thank you, great plugin !

A new Linux build would be much appreciated. Thanks

I am trying to build Fire 1.0.1 on Fedora 40 using gcc-14.1.1.
I met an error during link:

/usr/bin/ld: /tmp/ccyXj6FF.ltrans43.ltrans.o: in function `FireAudioProcessorEditor::~FireAudioProcessorEditor()':
/builddir/build/BUILD/Fire/Source/PluginEditor.cpp:184:(.text+0x321a): undefined reference to `SpectrumBackground::~SpectrumBackground()'
/usr/bin/ld: /tmp/ccyXj6FF.ltrans43.ltrans.o: in function `FireAudioProcessorEditor::FireAudioProcessorEditor(FireAudioProcessor&)':
/builddir/build/BUILD/Fire/Source/PluginEditor.cpp:17:(.text+0x502d): undefined reference to `SpectrumBackground::SpectrumBackground()'
/usr/bin/ld: /builddir/build/BUILD/Fire/Source/PluginEditor.cpp:169:(.text.unlikely+0x154): undefined reference to `SpectrumBackground::~SpectrumBackground()'
collect2: error: ld returned 1 exit status

First of all, congrats for this wonderful plugin! Was hoping to find a fully featured multi-band Distortion/Clipper plugin like this for a long time.

The only thing I am really missing is a little more gain for the drive knob. Seems to go up to +40dB, right? I'd love to have at least +60dB for really aggressive, fuzzy distortion which brings out all the overtones and noise even in low input signals with simple frequency spectrums and brings all the little noises from quiet parts in samples to the front.

If you feel the current drive range is good for most situations, maybe an implementation idea could be to add a third button under L and S buttons (perhaps something like A for "aggresive" or E for "extreme") which expands the range of the the drive knob when enabled?

In the most current version of Fire Release v1.0.0.2 (Beta 2) switching on HQ drastically alters the sound. I just tried it on a full mix and turning it on sounds almost as if all the side information gets collapsed to the center and there is a drastic loss of high frequency content in the mix.

I have the AU file in the component folder but Fire is not showing up in Logic.

Running Ventura 13.1 I've tried different versions but all lead to the same message: "Fire.vst3" can't be opened because Apple can not check it for malicious software. This software needs to be updated. Contact the developer for more information.

As someone suggested I tried downloading it with Safari instead of FireFox but alas. I'm using FL Studio 20, I don't have issues with other plugins so I don't think it's an FL issue. I've checked my system settings to allow from trusted developers as well as the App Store but it doesn't let me allow this plugin specifically like it would normally with an unverified app (I suppose because it is not an 'app' to the system unless it's loaded into the FL Wrapper).

Can anyone help me fix or circumvent this please? I saw the plugin in a video and it looks reaally good so I would be very thankful!

I think the title says it all, i really like this plugin, but i use mainly ProTools. Any luck in getting a support for it soon?

While playing with multiband distortion I have noticed that it is easy to get a pretty high peak level on the output. I think it would be nice if we had an option to link the global output level to some sort of safety limiter or clipper ceiling, meaning we will never get higher levels than what we set as Output dB.

Since commit 28f83fd the build is broken. This include CI.

The CMakeList.txt likely need to be regenerated and checked in as it is missing Source/Panels/SpectrogramPanel/SpectrumBackground.cpp

Was trying to gain stage my drumbus properly by manually setting the output (with the autolevelling (L button) off) but it would not accurately drop the output level or something of the sort. So I'd be doing comparisons and trying to do quick exports to send out but then the next moment my drumbus level drops significantly after reactivating Fire.

I think it could be a cool idea to have a Filter also as Band Effect, with the possibility to filter before distortion. Having a resonant filter going into the distortion and automating the cutoff frequency can give a very nice sweeping effect, specially on basslines. (A tempo-synced LFO to control it would be the cherry on top but maybe that would go a bit too far for what you intended Fire to be.)

Just noticed that my presets menu is empty

See attached video. The issue only affects the interface, the sound keeps getting distorted as it should.
The interface gets updated when new band is added, but if you max out the number of bands you're basically stuck.
https://youtu.be/GR2N_6abRn4

Hello,
The plugin cannot be loaded on my Linux system. It does not appear in the plugins list in bitwig and Carla says it failed to load the file as it could not find the VST main entry in the plugin library.

I do not know why but even though I place the extracted folder into the fl vst folder where I ALWAYS successfully am able to find downloaded plugins with the fl plugin manager, I cannot find or use this one at all, and I even did what a website told me to do and changed the .vst3 file to .dll and it still can't find it or use it, Could you please send a dll file soon or place it in the next update and stuff? please...

Thanks for this excellent open source multiband saturator! It has a great interface and is a pleasure to use.

One issue I have come across in my testing is regarding phase.

When the HQ mode is active, the mix control causes a lot of phasing that is not present in normal quality mode. The effect also sounds slightly different when running at 96kHz and when running at 48kHz. When doing a null test between a 96kHz rendered file and a 48kHz rendered file with the same plugin settings, it seems to be mostly low-end left
when the plugin is in normal quality mode and the plugin does not null very well at all in HQ mode, so there are some phase differences between sample rates. This doesn't happen with FreeClip (by Venn Audio). Maybe there are some filters or other operations that are sample rate dependent that are causing these issues when the HQ (oversampling?) mode is active and when the plugin is used at different sample rates.

Tested in reaper 6.61 at 48kHz and 96kHz (128, 256, 512, and 1024 buffer sizes) using the arctangent clipping modes in FreeClip and Fire for comparison tests (not using the multiband features for the null test).
These null issues at different sample rates are apparent in the other clipping modes as well, with the low-end being left.

(it also seems to make reaper's GUI freeze sometimes when the plugin is open, but I can open another issue if that problem persists)

• cannot save preset
• spectrum panel is black

The famous "underwater effect" of Drake / Noah Shebib is based on downsampling the signal without producing too much nasty aliasing. This revolves aound using two fillters in addition to the resampling module: one filter pre and one post the resampler. This reduces aliasing and leads to a smoother resample sound. See the manual of Decimort for more details.

Setting the compressor or width in the Band Effect tab and then switching to another band:

the other band will have the exact same compressor / width settings! Is it not supposed to work independently for each band?

Also Bias setting for each band's saturation is not kept independently for each band. Changing it in one band will also affect the other bands.

It seems as if only the chosen _Clipping type: (Tanh, Exp etcetera) and the Drive setting is retained correctly for each band independently.

Release v1.0.0.2 (Beta 2) Windows VST3, Ableton 11

I´ve downloaded the latest version of the plugin. As I tried to install the plugin it didn't work. I put the VST3 version into my VST3 folder but FL Studio didn't recognize the plugin, what shall I do?

First of all, your plugin is fantastic. I have been testing it and it is reaching the best ones. However, one major issue is that it doesn't work correctly on mono channels in Logic Pro. When I load a preset, made on a stereo channel, it crashes. Also if I turn on HQ mode.

Unable to write to an existing preset. (Due to JUCE 6.1.0 update)
"Enable buttons" wrong value when switching presets. (Due to v0.9.9 update)

There is a Git submodule (dependency fetching mechanism # 1) for JUCE that gets semi-regularly updated, but it's completely ignored by the CMake script which uses FetchContent (dependency fetching mechanism # 2) for JUCE and the other required dependencies instead.

Mixing these is weird because the submodule is essentially never used by CMake, it seems like a mistake? For me at least (trying to package this in a Linux/macOS package manager) it would be preferable to only use Git submodules and replace the FetchContent_* calls with add_subdirectory(<dependency> EXCLUDE_FROM_ALL) ones, because FetchContent isn't very compatible with the way we do fetching.

hi there, I have the plug-in in the correct VST3 folder. When I went to scan the folder in Ableton, a window popped up saying it cannot be used because it cannot be verified. I have since tried re-installing, but the plug-in is nowhere to be found. It also does not give me the pop-up window anymore.