jassert() is a wrapper for the C++ assertion function. It will cause the program to halt just to show you that something isn’t right, but the program can actually continue normally if you choose ‘Continue’ in the debugger.
That specific assertion in
juce::NormalisableRange is for out of range numbers. This could be due to a parameter range changing, causing saved data to suddenly not be “in-range”. It basically happens any time you try converting a number and the result isn’t between
An example that will make that assertion fire is:
int main (int argc, char* argv)
NormalisableRange<float> range(0.0f, 100.0f);
When the assertion hits, you can use the stack trace view in Xcode’s left panel… the little sandwich looking icon It will let you see up the chain of function calls and find where the problem is really occurring.
To take the previous example, the assertion happens in
NormalisableRange::clampTo0To1(), but the cause of all of it was us calling
NormalisableRange::convertTo0to1() with an out-of-range number from within our
Not sure why the AudioHost project is causing the assertion to happen… but this should at least help you find the source of the problem!