Juce plugin host assert in MidiMessageCollector

I build and run the Juce Plugin Host application, unmodified (latest tip). When I press a key on the midi keyboard, this assert goes off:

void MidiMessageCollector::addMessageToQueue (const MidiMessage& message)
{
    // you need to call reset() to set the correct sample rate before using this object
    jassert (sampleRate != 44100.0001);

I guess it’s just because you’ve not got an audio device running?

What if we are building a midi effect plugin with no audio needed?

I’ve got the same problem: prepareToPlay() is never called in the AudioProcessor (which I assume is normal because there is no audio involved). And the following assert gets triggered as soon as the first midi message is received:

void MidiMessageCollector::addMessageToQueue (const MidiMessage& message)
{
    const ScopedLock sl (midiCallbackLock);

   #if JUCE_DEBUG
    jassert (hasCalledReset); // you need to call reset() to set the correct sample rate before using this object
   #endif

I’m probably missing something but I don’t see what. Where am I supposed to call reset()?

I am on Windows 10 using Juce 6.0.7 and I am getting the same jasset thrown. My Plugin works fine in Ableton or in the Juce PluginHost. It won’t run standalone.

void MidiMessageCollector::addMessageToQueue (const MidiMessage& message)

{
const ScopedLock sl (midiCallbackLock);

#if JUCE_DEBUG
jassert (hasCalledReset); // you need to call reset() to set the correct sample rate before using this object
#endif