BufferingAudioSource requires the Juce GUI to initialize?


#1

If I use BufferingAudioSource, and I don’t initialize the MessageManager via the regular channels (JUCEApplication or ScopedJuceInitialiser_GUI), it seems to die when the app exits, it creates a MessageListener which jasserts that MessageManager::instance != 0.

So, can I use BufferingAudioSource without initializing the GUI or what? Did something change?


#2

It probably uses a timer or some kind of event-based class. A lot of the audio stuff is like that, I wouldn’t expect it to work without the messaging system being active.