Open mxmilkiib opened 3 years ago
I can't seem to reproduce this on my machines. What plugins are you using?
This is straight after compiling from git. Not at my laptop with now, but do you mean plugins enabled in Helio or just plugins on my system? Because I've not done anything other than open Helio and try the chord functionality
Strange, I was suspecting some VST plugin misbehavior, but it's clearly not the case. Could you check if the crash reproduces in the debug build?
Yes.
Got a bunch of JUCE Assertion failure in juce_MidiMessageCollector.cpp:54
in the terminal, though those happen just after the point of double clicking.
The crash only happens after the pointer moves to a second chord element.
After some digging around it seems like the problem is that the audio device hasn't been initialized, probably because the audio settings are invalid, or just not auto-detected properly. Could you check the settings page to see if the audio settings section looks ok? Or, if it doesn't, is there's a viable combination of audio driver, device and sample rate/latency available?
I was using JACK. Now I'm using PipeWire, but, while JACK is selected and this is with the PipeWire drop-in JACK replacement, there are no items in the 3 menus below the menu with "JACK".
I change to ALSA, it fills those menus, but the app still crashes when I reopen the test project and try again.
If I were to rechange the menu to JACK after ALSA, it does then fill the 3 menus below.
So yup, something's up with auto-detection of audio settings, this issue is perhaps related to #155. Apart from that, I wonder if other JUCE-based apps work for you (like Traction Waveform or Carla)?
https://gist.github.com/mxmilkiib/c310adc5de7bd7f2bfafc0863b9a4ced
I double click, mouse over one of the chords, then the middle section again, then over the same chord or another chord and it crashes.