Ladder 4 Pole LP Filter

[d.healey]

@DanH

I don't have an answer because it's been a long time since I played with FAUST. But if you haven't seen this already you should check it out - https://www.kadenze.com/courses/real-time-audio-signal-processing-in-faust/info

[DanH]

Are we allowed to use the Moog name to describe the moog style filter on our UI?

[DanH]

@Christoph-Hart just digging into Juce.... Is there a reason all these Ladder filter options aren't included in Hise? And if it's possible to include them, please can you? Pretty please

namespace juce
{
namespace dsp
{

enum class LadderFilterMode
{
    LPF12,  // low-pass  12 dB/octave
    HPF12,  // high-pass 12 dB/octave
    BPF12,  // band-pass 12 dB/octave
    LPF24,  // low-pass  24 dB/octave
    HPF24,  // high-pass 24 dB/octave
    BPF24   // band-pass 24 dB/octave
};

/**
    Multi-mode filter based on the Moog ladder filter.

    @tags{DSP}

[d.healey]

@DanH I think if you called it Moog style you should be ok. Basically it comes down to trademark fair use. You are allowed to use trademarks as descriptors under certain circumstances, for instance if that's the only way to refer to a product.

If you run a phone repair shop you would obviously need to say somewhere in your advertising that you repair both iPhone and Android phones. Those are both trademarks but referencing them in this way wouldn't violate the trademark as it doesn't imply an affiliation with those brands or an endorsement from the brand owners.

So if you say your plugin contains a Moog filter that might be confusing - does that mean it was created by Moog specifically for you... so I think using Moog style would be the safe option because it's clear that it is not Moog. You could also include a disclaimer in your user manual/marketing material, etc.

Or talk to a trademark lawyer, or send Moog an email and ask them.

[DanH]

@d-healey Thanks, sensible thoughts! I can't think of an example of another dev using 'Moog-style' on their UI so maybe I'll avoid it :)