Anyone wants some basic JUCE video tutorials by me?

[WilliamK]

Just checking if anyone would like to see some basic tutorial videos on how to start with JUCE. Maybe I could even do some C++ tutorials too. I just need some ideas on what to talk about.

Cheers, WilliamK

[quikquak]

A good idea but I think The Audio Programmer may have beaten you to it.

[deastman]

A good idea but I think The Audio Programmer may have beaten you to it.

Ooh! Thanks for the tip! I just subscribed.

William- I say the more the merrier! Anything you’d care to share would be most appreciated. I would suggest sitting down and working out a comprehensive outline of topics before you get started, rather than a more impromptu, off the cuff sort of approach.

[Topiness]

Personally I find tutorial videos a bit irritating - it's hard to skip forward and back to the interesting bits; you can't copy and paste code samples; you need to be in a situation where you can listen to the audio to watch them. I much prefer a good blog article with downloadable code samples.

( ..but I'm not really looking to learn JUCE right now, so ignore me...)

[stratum]

Well, I think you can find things that are more interesting than JUCE to write about. It's not too difficult to figure out how to use well written class libraries, especially after being mentally tortured by the open source community for about a decade.

[quikquak]

I found JUCE much easier second time around, it just seemed far too overly complex first time, what with learning to use the editor, and everything associated with it. Now I understand why they using the “Projucer”, and the only reason I started using it again was that YouTuber made it seem so much easier to start a project. So I say, do it, man. But please fill it with useful information, rather than a whole bunch of “errr,” “umms,” and “oookays”

[giantelk]

Fill in the gaps where the JUCE online tutorials are lacking. I followed their tutorials mostly for audio plugins, the missing holes I can think of right now are:

1. Displaying images, i..e. using SVG images for custom knobs / dials. I got basic SVG to work as a logo, but can't rotate it. Yet to attempt SVG for rotating slider.

2. License key management, JUCE tutorial only shows RSA pub/private key stuff. Need something more useful in the real world.

3. It took me ages to figure out how to use buffer.getWritePointer() and add the second for loop. Simple now, but tutorials and auto generated stub code were lacking.

for (int channel = 0; channel < totalNumInputChannels; ++channel)
{
auto* channelData = buffer.getWritePointer (channel);
const int numSamples = buffer.getNumSamples();

for (int i = 0; i < numSamples; ++i)
{
channelData = channelData * myGainParam; // Do processing here.
}
}

4. Getting the automated white-box cases framework to work with my code, took a few hours and some ugly hacks. Maybe best to use a non-JUCE testing framework, with better UI/report, that isn't so hard to get working.

5. Getting params to save settings when reopen the GUI/editor was painful.

6. Still not sure how to save and manage basic VST presets. Sure I'll figure it out with some messing around. Tutorial would be nice.

7. Logging debug messages to a file, so beta testers can send me logs. After 2-3 hours of trying and getting nowhere I moved on to more important dev DSP coding.

8. Some of the Projucer features are a bit of a mystery: live build, adding SVG images as binary or not.

9. How to get a look ahead buffer?

[SoundPorn]

You should check out the Tracktion Presents program they're offering all that and more

Fill in the gaps where the JUCE online tutorials are lacking. I followed their tutorials mostly for audio plugins, the missing holes I can think of right now are:

1. Displaying images, i..e. using SVG images for custom knobs / dials. I got basic SVG to work as a logo, but can't rotate it. Yet to attempt SVG for rotating slider.

2. License key management, JUCE tutorial only shows RSA pub/private key stuff. Need something more useful in the real world.

3. It took me ages to figure out how to use buffer.getWritePointer() and add the second for loop. Simple now, but tutorials and auto generated stub code were lacking.

for (int channel = 0; channel < totalNumInputChannels; ++channel)
{
auto* channelData = buffer.getWritePointer (channel);
const int numSamples = buffer.getNumSamples();

for (int i = 0; i < numSamples; ++i)
{
channelData = channelData * myGainParam; // Do processing here.
}
}

4. Getting the automated white-box cases framework to work with my code, took a few hours and some ugly hacks. Maybe best to use a non-JUCE testing framework, with better UI/report, that isn't so hard to get working.

5. Getting params to save settings when reopen the GUI/editor was painful.

6. Still not sure how to save and manage basic VST presets. Sure I'll figure it out with some messing around. Tutorial would be nice.

7. Logging debug messages to a file, so beta testers can send me logs. After 2-3 hours of trying and getting nowhere I moved on to more important dev DSP coding.

8. Some of the Projucer features are a bit of a mystery: live build, adding SVG images as binary or not.

9. How to get a look ahead buffer?

[Richard_Synapse]

Personally I find tutorial videos a bit irritating - it's hard to skip forward and back to the interesting bits; you can't copy and paste code samples; you need to be in a situation where you can listen to the audio to watch them. I much prefer a good blog article with downloadable code samples.

It depends, in general I agree however since JUCE involves both graphics and audio, I imagine great tutorial videos could be made about it. I certainly wouldn't mind to see more

Richard

[DJ Warmonger]

I looked at JUCE once, but didn't quite know where to start. Any tutorials would be greatly appreciated