JUCE Assertion failure in juce_NormalisableRange

Musicman · August 17, 2021, 6:42pm

When I try to run and build it succeeds but the plug-in does not show up as expected and just loads forever or does not show up, it works and shows up on EQ but not with the compressor, any ideas for the reason why? do i need to use a different range function if it is below a value of 0 if so which one?

here is the repository (GitHub - Musicmastermatt/MusicMasterMattCompressor: The main repository)

Kind regards,

Matt

daniel · August 17, 2021, 6:55pm

In the output (lower right) it says it stopped because of a jassert was triggered in the juce_NormalisableRange.h line 242.
A jassert is a check in debug builds to find mistakes early on.
If you click the call stack (the lines on the left) successively, you will see where this was called from.

I looked this line up, and it checks that the end of the NormalisableRange is greater than the start:

github.com

juce-framework/JUCE/blob/master/modules/juce_core/maths/juce_NormalisableRange.h#L242

    
      
                  constructor of this class then the skew value is ignored.

              */

              ValueType skew = 1;

          

              /** If true, the skew factor applies from the middle of the slider to each of its ends. */

              bool symmetricSkew = false;

          

          private:

              void checkInvariants() const

              {

                  jassert (end > start);

                  jassert (interval >= ValueType());

                  jassert (skew > ValueType());

              }

          

              static ValueType clampTo0To1 (ValueType value)

              {

                  auto clampedValue = jlimit (static_cast<ValueType> (0), static_cast<ValueType> (1), value);

          

                  // If you hit this assertion then either your normalisation function is not working

                  // correctly or your input is out of the expected bounds.

If you go further down the calls you might end up where you created this NormalisableRange (I assume for a AudioParameterFloat). Make sure that the parameters to construct this range were valid, i.e. that the end is greater than the start.

Good luck

EDIT: just checked your repo link and it is indeed the threshold parameter:

github.com

Musicmastermatt/MusicMasterMattCompressor/blob/master/Source/PluginProcessor.cpp#L196

    
      
              // You should use this method to restore your parameters from this memory block,

              // whose contents will have been created by the getStateInformation() call.

          }

          

          juce::AudioProcessorValueTreeState::ParameterLayout

          MusicMasterMattCompressorAudioProcessor::createParameterLayout()

          {

              juce::AudioProcessorValueTreeState::ParameterLayout layout;

              

              layout.add(std::make_unique<juce::AudioParameterFloat>("Threshold",

                                                                     "Threshold", juce::NormalisableRange<float>(0, -60, 0.5f, 1), 0.f));

              

              layout.add(std::make_unique<juce::AudioParameterFloat>("Ratio",

                                                                    "Ratio", juce::NormalisableRange<float>(1, 40, 1.f, 1), 4.f));

              

              layout.add(std::make_unique<juce::AudioParameterFloat>("Attack",

                                                                    "Attack", juce::NormalisableRange<float>(0, 200, 1.f, 1), 13.f));

              

              layout.add(std::make_unique<juce::AudioParameterFloat>("Release",

                                                                    "Release", juce::NormalisableRange<float>(5, 5000, 1.f, 0.25), 30.f));

It should go from -60 to 0 not the other way round…

Musicman · August 17, 2021, 7:25pm

Okay thank you i’ll swap it around,
works now,
cheers

Matt

daniel · August 17, 2021, 7:50pm

You’re welcome, glad I could help.

Topic		Replies	Views
JUCE Assertion failure in juce_NormalisableRange.h:272 (lldb)	4	1227	March 8, 2019
Need help debugging a plugin Audio Plugins	8	951	December 5, 2019
Normalisable Range file problems The Projucer	5	234	September 5, 2023
jassertfalse hit when JucePlugin_MaxNumInputChannels==0? Audio Plugins	6	572	November 16, 2011
JUCE Assertion failure in juce_VST_Wrapper.cpp:1783	3	835	January 14, 2017

JUCE Assertion failure in juce_NormalisableRange

Purchase

Discover

Learn

Support

About

Events

JUCE Assertion failure in juce_NormalisableRange

Related Topics

Purchase

Discover

Learn

Support

About

Events