austrianaudiogmbh / polardesigner Goto Github PK

Even though I don't own any of your mics (but would like to try and experiment with PolarDesigner using my two AKG C460B).

Under the name of Geekos DAW we're packaging audio/multimedia software for openSUSE Linux.

On my request our JUCE expert created a PolarDesigner package in no time, providing a standalone app, and LV2, VST2 and VST3 plugin binary subpackages, but none of them work for me. I've tried to instantiate the LV2 variant in Ardour 7.2, on an empty audio stereo track but as soon as I try and open the GUI, a massive feedback starts to build up. I can push down the track volume fader and it goes silent again.
also parts of the GUI (most obviously the polar pattern circles) don't scale and aren't in their intended positions.
Before spending any serious amount of time on further testing, I thought I'd get in touch here and ask if there is any interest in supporting native Linux builds?

Thanks, Edgar (a Vienna based theater technician and amateur musician)

When comparing two instances of the plugin, one oversampled, the frequency response is different when the equalization control (diffuse field/free field) is activated. This could be related to not updating the filter coefficients when the sample rate is different from 48kHz.

Test setup: Two instances of the plugin on two different tracks (the tracks contain exactly the same audio) in Reaper, one oversampled. Both tracks send to a third track, but one send is polarity inverted (this can be easily done in Reaper with a polarity switch in the send menu). The two plugins are synced with sync-channel "one". The third track remains silent as long as the equalization control is disabled, as the output of the plugins is exactly the same. When activating the equalization control, the third track is outputting a signal indicating there is a difference between the outputs of the plugins.

The current Frequency Axis goes from "20 .. 50 .. 10 .. 20 .."

It should be: "20 .. 50 .. 100 .. 200 .."

Minor bug, UI only.

A trim slider has been added to v2.1.0 to allow all EQ settings to be bumped/trimmed with a simple UI - a much-requested feature. See right-hand side trim slider:

the frequency labeling is wrong.

status quo:

20 / 50 / 10 / 50 / 1k / 2k / 5k / 10k / 20k

should be:

20 / 50 / 100 / 500 / 1k / 2k / 5k / 10k /20k

In the void PolarDesignerAudioProcessor::setProxCompCoefficients(float distance) function in PluginProcessor.cpp the calculated variable r can never go below 0.05 when the input variable distance stays in the range -1...+1. Therefore the condition r < 0.01 is never satisfied.

Currently its a bit cumbersome to get the PolarDesigner_Pattern_Presets installed for use in the iOS (AUv3) version of the PolarDesigner plugin - the user has to add the presets to a specific known path on their iPad, or else PolarDesigner won't find them. This might better be replaced with a system for downloading the content remotely, i.e. IAP (free) or some such mechanism.

We need to add the M1 architecture to our build targets, and the next release should include a native M1 build.

Our plugins should be modified to allow the UI to be scaled .. this would make the plugin more useful for higher-res and lower-res environments.

Habe gerade eine Kundenrückmeldung rein bekommen zu folgenden Problem.

PolarDesigner verursacht in Cubase beim offline bouncen (export) zerstörtes Audio.

Cubase 11.0.30
Win 10 up to date
Focusrite Scarlett

Beim realtime export tritt der Fehler nicht auf.

We are discussing adding various emulations of microphones to PolarDesigner.

In PluginProcessor.cpp, in lines 289, 293, and 297 different impulse responses are loaded into the same convolution unit "dfEqOmniConv". To fix this bug, the units "dfEqEightConv" (line 289), "ffEqOmniConv" (line 293) and "ffEqEightConv" (line 297) should be loaded with their appropriate impulse responses.

The bug was confirmed by testing the plugin in Reaper: the free field EQ has no effect on the processed audio.

This bug was introduced in the update to JUCE 6 (commit 48ca6cd).

We would like to ensure all of our plugins are usable within Waves Soundgrid, in Zero Latency Mode:

https://www.waves.com/soundgrid-systems

When testing the plugin with pluginval v0.2.7 (https://github.com/Tracktion/pluginval) at strictness level 7, the Plugin State Restoration test fails (the recovered values are slightly different from the actual values). This could be related to converting doubles to floats in a lot of places (the VS compiler gives warnings when building the plugin).

It would be good to get the plugins built for AU v3 targetting Mobile (iOS).