Hey, I created a 7 band filter. I get 164 errors but I don’t know why. I haven’t changed anything in this file. There are some errors like ‘A name followed by “::” must be a class or namespace name’ or ‘A “;” expected’.
Start with the first error, and fix it. Repeat until completion. Pay attention to the details in the error messages, they are your first clue in what to fix.
1 Like
But what can I do if FIR is not reachable. In juce::dsp::FIR?
I think it would be extremely helpful if you shared one of the errors along with the code where you are using it. There are quite a few possibilities what can be wrong here. One shot in the dark: In case you are not using JuceHeader.h, did you include <juce_dsp/juce_dsp.h>?
Ohh, thank you. The errors are gone, but there is one little thing. When I start do debugging, then I get an error, it works, but I don´t know if this is normal.
That means:
A breakpoint statement (__debugbreak() statement or a similar call) was executed in EQ.exe.
You are hitting an assertion here. Assertions are markers in the code that specify, “ok, from here on we assume that a certain condition is true, otherwise the following code is likely to not work as intended”. In case that assumption is false at runtime, the debugger will stop at this point, helping you to find an error that you introduced at some point. You should consider assertions as your friend and always try to find out why you hit them.
In this case, it means “from here on, we expect that the value of the variable order is greater than 0”. The fact that your debugger stops here means that this is not the case. You should be able to inspect the actual value in the debugger view of visual studio. The simple reason for that is that a value <= 0 has been passed as an argument to the function – but where does that argument come from? You can now step up the frames in the call stack in your debugger to find the origin of that unexpected value. So, happy debugging 
One personal advice that I would give you, looking at the screenshot: Better configure Visual Studio to emit english messages instead of the (sometimes not very accurate) german translations. You’ll find a lot more resources when googling for the english messages than when trying to figure out what these strange translations mean and you should get familiar to all the technical terms used in the programming world anyway in order to master C++ 
1 Like
Very interesting,
thank you