How do you know, how to implement the classes of the documentation here:
JUCE: Class Index
if you are programing an audio plugin and you have the usual structure for an audio plugin. What is the best way to work with the documentation?
The documentation serves as reference. It is not so great to start from scratch.
The best way to learn is looking at the tutorials and then when you create a fresh project, you get a lot of boilerplate already which you can start fleshing out.
1 Like
I am doing that but I still struggle because often the tutorials are not written for the plugins and I am only interested into the code, that can be used for writting audio plugins.
Yes, it is not that easy for a beginner to port the concepts from one example to another.
Maybe someone else has another suggestion…
Good luck
1 Like
Yes, I have also found it difficult to start using classes when then are not direct usage examples in the docs. Aside from the tutorials, JUCE offers example projects, including a couple of plugin examples.
Moving out of what is directly in the JUCE repo, there are some other ideas in this thread:
1 Like
Ooh, more plugin code examples here:
A very good starting point in the ‘demorunner’ application included with JUCE. Lots of examples with code. You could also start a blank project and have JUCE create the necessary plugin code for you. That being said, it is a bit difficult to get started, but this community is friendly and helpful.
The best assistance currently is chatgpt, it offers you many solutions, although sometimes they are not the best or not correct, but it is compensated by the amount of searching or coding time you save.
You can use the Juce documentation as a reference on specific occasions to delve deeper into certain classes or methods.