x42 / fil4.lv2 Goto Github PK

Ideally there would be every type between 6dB/oct and 48dB/oct.

Currently the Low Pass is a non-standard custom combination of two 2nd order and a low-shelf.
This is mainly to produce a flat 12dB roll-off while maintaining zero-phase at nyquist.

However, the resonance peak widens close to nyquist which impacts the filter steepness and reduces real-world usability to some extend.

Sometimes you really do want a HP at 15kHz, for example.
Also: sometimes you want to use all bell filters in the same frequency range.

Limited ranges are great if that is the only way you can get a precise setting, but in the plugin worls you can just CTRL-drag or even type in a value.

The visual representation of the transfer function near nyquist (around >= SR/3) does not match reality.

Not aware of any LV2 / LADSAP dynamic EQ implementations. This would offer opportunity to leverage the stability of the Mitra-Regalia lattice filter.

• Source dynamic triggers from either process input or sidechain.
• Independent threshold, attack & release setting for each band.
• Threshold could be either ceiling mode or floor mode. (i.e. triggered by rising above vs. dropping blow threshold)
• Trigger could be bound to influence one or both of gain and Q. (is there any real use for freq?)
• Amount of influence ratio/scale on gain and Q could be scaled for each independently, with possible values going in both positive and negative directions.

Ideally, every band would let you separately choose between:

• stereo
• left
• right
• mid
• side

Not needed often, but damn handy when you do need it.

An option to hear only the part that is being filtered.

Hi, thank your for the enormous contribution on for those quality opensource plugins on Linux.

Using Catia, the Windows scaling is not the correct one by default. :

Here it's my DPI and resolution according xrandr :

DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 382mm x 214mm
   3840x2160     60.02*+

This is more of a half-baked idea than a specific feature request.

I use Ardour. I use x42-eq as my go-to channel EQ. I have a Presonus Faderport 8.

The Faderport lets you edit controllable plug-in parameters, including for x42-eq. Presumably it's tapping into something in the LV2 layer. The way the x42-eq controls are presented in the Faderport seem to match the way they are presented in the Ardour generic controls for this plug-in.

The (slight) inconvenience is that the Faderport 8 only has 8 faders, but x42-eq appears to have 23 parameters that get mapped to faders. What would be ideal (for me, in this particular scenario with a Faderport 8, but not in the common case generally for everyone else in the world) would be to have the most generally useful parameters show up first.

The Faderport 8 workflow to edit the x42-eq on a channel is:

1. Select the channel
2. Edit Plugins
3. Select the x42-eq plug-in
4. Start moving faders around

Since there are 23 parameters mapped to faders, but only 8 faders, at this point you have to turn the pan/param knob back and forth to find the desired parameters. Which doesn't sound like such a big deal. But if you're working quickly and intuitively on a mix, imagine if the first 8 parameters were a four band EQ, with sweepable mid frequencies and adjustable bandwidth. Or in other words, the controls could be mapped out like this:

Fader 1: Gain 1
Fader 2: Frequency 2
Fader 3: Bandwidth 2
Fader 4: Gain 2
Fader 5: Frequency 3
Fader 6: Bandwidth 3
Fader 7: Gain 3
Fader 8: Gain 4

Instead of what they currently are:

Fader 1: Gain
Fader 2: Highpass Frequency
Fader 3: HighPass Resonance
Fader 4: Lowpass Frequency
Fader 5: LowPass Resonance
Fader 6: Lowshelf Frequency
Fader 7: Lowshelf Bandwidth
Fader 8: Lowshelf Gain

I realize this is a half-baked idea. I'm well aware. I'm not, even for a moment, suggesting that you just reorder the parameters for everyone, to benefit me with my particular control surface. I know better than that.

One other idea I had was to create my own local TTL file for fil4, but to change the LV2 index values around (or otherwise try and influence the order in which the controllable parameters appear). Would this even work? If it did, it seems like it might improve things for my idiosyncratic workflow. But how much trouble would I be asking for if I wanted to keep up with future changes to the plug-in? It seems like there are probably some traps for the unwary there.

Another possibility is some sort of configurable something-or-other to allow more generally creating local mappings that people could customize. That might be a whole lot of extra work and complexity for a feature that might not be used very often.

Or maybe there's something else that I haven't thought of.

Or maybe I should just do a bit more menu diving, or use the mouse.

Again, I really want to reiterate that I know this is kind of a strange request. Having been on the receiving end of requests that would make some strange workflow better for someone else at the expense of the general project, I know what you're probably thinking. So please interpret this as more of a report from the field, and some brainstorming about something that could be kind of cool, but only if it was possible to do so cleanly.

Finally, thanks for fil4, and the other x42 LV2 plug-ins. They are all uniformly fantastic!

have you ever thought about changing license to e.g LGPL2?
Library code as GPL makes is quite impossible to quarantee a legal usage in big commercial projects.
As a consequence it might be strictly forbidden to use any components based on GPL.
The GPL license is a big hurdle which likely restricts some users from using that nice plugin...

When you enable the analyzer, it's gain get's enabled, as it should.
When you close the window and re-open it, the analyzer is still enabled, but the gain is greyed out again.

It would be cool to have the option to activate a bandpass filter in any band for spotting problem frequencies.

It looks like the git:// if no more supported by github. So, cloning the robtk submodule hangs. Can you replace the url of the submodule from git:// to https:// ?

In EQ10Q, you can use the HP, LP and shelving filters with extremely high and low resonances, which is often useful.

Hey there! :)

It would be nice to have a piano roll below the frequency scale and tinting the aproximate keys corresponding to the set band frequency accordingly.

This would be very convenient if you communicate in more musical terms. Like, "Whenever I hit my low E on my Bass, I have this resonant frequency." ;)

Cheers
Bollie

we want to save our settings in home directory, and load them on startup, or by argument from commandline.

Hi,
On Fedora 24 x86_64 I had to manually change the Makefile with:

$(PREFIX)/lib64/lv2

Then do the make install PREFIX=/usr
to have it installed in /usr/lib64/lv2 (default for Fedora x86_64)

Not sure if there's a way to support this directly?

Thanks.

Hi,

when choosing a higher zoom level only the controls are scaled, but not the fonts in the graph. Therefore they remain unreadable.

Recently I became unable to change the Parametric-EQ plug-in settings from within Ardour's "Mixer" view. Whenever I try to open the Equalizer GUI Ardour crashes.

When running Ardour from console it crashes with

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
The program 'ardour-5.12.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 41 error_code 170 request_code 154 minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Since the equalizer is effective in Ardour and works until I try opening the plug-in GUI I think it might really be an incompatibility with recent updates of some Ubuntu libgl package. On May, 10th 2019 I received an update for package libgl1 which updated (presumably from libgl1 1.0.0-2ubuntu2 or 1.0.0-2ubuntu2.2) to libgl1 1.0.0-2ubuntu2.3.

The changelog for the versions as provided by Synaptic package manager

libglvnd (1.0.0-2ubuntu2.3) bionic; urgency=medium

  * aarch64-fix-address-passed-to-clear-cache.diff: Fix a crash in some
    GLX apps. (LP: #1816004)

 -- Timo Aaltonen <[email protected]>  Fri, 10 May 2019 15:17:37 +0300

libglvnd (1.0.0-2ubuntu2.2) bionic; urgency=medium

  * rules, libgles2: Add GLESv1 support. (LP: #1782285)
  * Always return an error from eglMakeCurrent if EGLDisplay is invalid.
    (LP: #1780039)

 -- Timo Aaltonen <[email protected]>  Wed, 15 Aug 2018 09:20:42 +0300

libglvnd (1.0.0-2ubuntu2.1) bionic; urgency=medium

  * control: Drop the alternate depends on lib{egl,glx}-vendor, the
    default provided by mesa should always be installed. (LP: #1770913)
  * control: Bump Breaks/Replaces on old mesa egl/glx packages to verify
    upgrades with xenial backports work. (LP: #1772607)

 -- Timo Aaltonen <[email protected]>  Tue, 05 Jun 2018 17:16:05 +0300

libglvnd (1.0.0-2ubuntu2) bionic; urgency=medium

  * debian/patches/fix-egl-platform-detection-crash:
    - Fix code in EGL platform detection that crashes when passed
      a Mir object

 -- Christopher James Halse Rogers <[email protected]>  Mon, 05 Mar 2018 10:45:22 +0100

Hi,

on my 260 dpi notebook display the 200 % zoom level still results in small control knobs in the x42-eq. Therefore please add a higher zoom level, e.g. 250 %.

Thanks!

Hi,

it would be nice to have some crosshairs in the graph that show the current values (Hz, dB). It may be even better to show a vertical crosshair only that shows dB of the current position in the graph.