search

muse-sequencer / muse

MusE is a digital audio workstation with support for both Audio and MIDI
https://muse-sequencer.github.io/
Other
634 stars 67 forks source link

Many filters (Calf, BassUp etc.) crash MusE when trying to open native GUI #1266

Open razcore-rad opened 3 months ago

razcore-rad commented 3 months ago

Describe the bug Many filters (Calf, BassUp etc.) crash MusE when trying to open native GUI.

To Reproduce Steps to reproduce the behavior:

  1. Create a FluidSynth track.
  2. Add BassUp filter in the side chain channel strip.
  3. Double click the filter or right-click and try opening the native the GUI.
  4. Crash.
❯ muse
-> 19:00:22.961 Read configuration...
Config File </home/razcore-rad/.config/MusE/MusE/MusE-seq.cfg>
New Qt locale: en_US
-> 19:00:22.986 Load theme...
Config File </home/razcore-rad/.config/MusE/MusE/themes/Deep Ocean.cfc>
-> 19:00:23.077 Scan plugins...
-> 19:00:23.297 Init audio...
Denormal protection enabled.
Select audio device from configuration : 0
User JackAudio backend - backend selected through configuration
Using Jack
-> 19:00:23.560 Init MIDI...
Trying RTC timer...
fatal error: open /dev/rtc failed: Permission denied
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: HR timer
got timer = 41
-> 19:00:23.716 Init plugins...
-> 19:00:23.716 Init VST plugins...
-> 19:00:23.716 Init native VST plugins...
Initializing Native VST support. Using VESTIGE compatibility implementation.
-> 19:00:23.716 Init DSSI plugins...
-> 19:00:23.716 Init LV2 plugins...
Gtk-Message: 19:00:23.731: Failed to load module "atk-bridge"
Gtk-Message: 19:00:23.762: Failed to load module "canberra-gtk-module"
-> 19:00:24.029 Init OSC / metronome...
-> 19:00:24.408 Populating Track context menu...
-> 19:00:24.410 Show GUI...
INFO: Requested timer frequency:1024 actual:1000
Acquired timer frequency: 1000
-> 19:00:25.706 Load default project
starting with template /tmp/.mount_muse2WF0cD/usr/share/muse-4.2/templates/default.med
jack connect <MusE:jack-midi-0_out> - <Midi-Bridge:Midi Through:(playback_0) Midi Through Port-0> failed with err:17
jack connect <Midi-Bridge:Midi Through:(capture_0) Midi Through Port-0> - <MusE:jack-midi-0_in> failed with err:17
jack connect <MusE:jack-midi-1_out> - <Midi-Bridge:MusE:(playback_0) MusE Port 0> failed with err:17
jack connect <Midi-Bridge:MusE:(capture_0) MusE Port 0> - <MusE:jack-midi-1_in> failed with err:17
INFO: Requested timer frequency:1024 actual:1000
MidiJackDevice::queueEvent() evTime:437906739 < syncFrame:437908480!!
MidiJackDevice::queueEvent() evTime:437906739 < syncFrame:437908480!!
-> 19:00:27.416 Start application loop...
Total start-up time: 4544 ms
unknown NRT Msg 0x01
dump 4
7e 7f 09 01 
fluidsynth sampleRate 48000
fluidsynth: warning: SDL2 not initialized, SDL2 audio driver won't be usable
terminate called after throwing an instance of 'Gdk::PixbufError'
Aborted: oops, process 'muse' core dumped

Expected behavior No crashing...

Screenshots

Video: https://github.com/muse-sequencer/muse/assets/1177508/41831543-73ab-4e9d-b033-c43d3f13885c

Desktop (please complete the following information):

Additional context I'm not sure if it's relevant, but the native GUI doesn't render properly either. The plugins work fine in Ardour... well they did crash when the allocated memory was too low.

Video: https://github.com/muse-sequencer/muse/assets/1177508/58401fe0-a609-4a29-acb8-3ec8129a0e1c

razcore-rad commented 3 months ago

Seems like this is an issue with the Appimage package, but I have no idea how to further debug. Running muse -D doesn't help with any useful error messages. I just compiled from master and I'm not getting any crashes on a first check.

terminator356 commented 3 months ago

Thank you for the report. Sometimes the AppImage experiences some problems. We have had reports of FluidSynth not working, and so on. Likely some incompatibilities with system libraries which are later versions than the ones used in the AppImage.

Maybe @spamatica can look at the problem, maybe it is time to upgrade the AppImage build?

It is always best to compile from source. It is good to hear that it does work for you. Let us know if any more trouble. Improvements are always being worked on.

razcore-rad commented 3 months ago

Sure thing. If there's a way for me to provide a more detailed report somehow let me know. I'm not sure about the system libraries versions stuff.

My understanding is that AppImage prioritizes the bundled libraries kind of like how $HOME/.config is prioritized over system configs. So I'm guessing some of the AppImage bundled libraries are outdated.

edit nevermind, I just realized we pretty much agree on the library stuff, it's late here, I'm a bit tired :)

spamatica commented 3 months ago

Maybe @spamatica can look at the problem, maybe it is time to upgrade the AppImage build?

Yeah, I can have a look at the next opportunity!

--

Sure thing. If there's a way for me to provide a more detailed report somehow let me know. I'm not sure about the system libraries versions stuff.

I think the information you provided goes a long way, I will try to reproduce