Background or feeder thread in plugin?


#1

Hi,

I have a newbie question about using background or feeder threads in a Juce Audio Plugin Framework-based plugin.

Background:

I currently have some virtual instrument-like code in a standalone application. The implementation includes threaded streaming of audio data from disk and some other threaded computation. I would like to port the implementation to work as an audio plugin. Juce and the JAP Framework look amazing, so I am looking at it for this purpose.

Question:

I am not a programming newbie, but am an audio plugin programming newbie. I’ve looked at Apple developer documentation to get acquainted with AUs. And I’ve looked at Juce and the JAP Framework and think I understand how to use it.

However, it’s hard for me to see if it’s appropriate for an audio plugin to manage threads (for disk streaming and/or computation). And if it is appropriate, where and when they would be managed (AudioFilterBase::prepareToPlay and AudioFilterBase::releaseResources look like likely candidates).

Can any Juce and JAP Framework experts provide guidance on this? It’s greatly appreciated!


#2

Yes, it’s totally fine to use threads, and you could indeed start/stop them in the prepareToPlay call, though TBH you might as well just leave one running to avoid slowing down starting/stopping playback. You could also share the thread amongst instances of your plugin to make it more efficient.

(Note that a lot of this is already done for you by the AudioTransportSource class…)


#3

I looked at the AudioTransportSource class, as well as the related BufferingAudioSource and ResamplingAudioSource classes. Nice! The functionality is similar in my analogous classes, so I’m increasingly optimistic about the porting of my existing implementation.

Thanks for the guidance, appreciated!


#4