View Issue Details

IDProjectCategoryView StatusLast Update
0009367ardourbugspublic2023-10-12 03:34
Reportergaybe Assigned Tox42  
PriorityurgentSeveritycrashReproducibilityalways
Status resolvedResolutionno change required 
PlatformGNUOSOpenSUSEOS Versiontumbleweed
Product Version7.4 
Summary0009367: Ardour crashes trying to create a new MIDI track.
DescriptionI was trying to start and learn how to use this software, but I just can't do it. If I try to run it in ALSA, any sound device starts to not being detected by the system, I can't here Ardour not even other app. If I try to run it in JACK, as I pretended at start, it just crashes everytime I try to create a MIDI Track.
Steps To ReproduceOpen a new session with JACK.
Right click on the track area.
It will open a window to create a new track, select the MIDI Track one.
Click in the button to create it.
TagsNo tags attached.

Relationships

has duplicate 0009416 closedx42 Ardour 7.5 get blocked when try to load any plugin in midi tracks 
has duplicate 0009479 new adding zynaddsubfx lv2 to a track crashes ardour 

Activities

x42

2023-06-10 13:25

administrator   ~0027733

Are you perhaps using pipewire as JACK server?

If so, please see
https://discourse.ardour.org/t/ardour-crashes-when-trying-to-load-synth-with-jack/108700
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3183

> If I try to run it in ALSA, any sound device starts to not being detected by the system,

Perhaps the device is in use? Ardour requires exclusive access to the soundcard, This usually works fine (Ardour requests the device from pipewire or pulseaudio).

kmarty

2023-07-14 18:24

reporter   ~0027895

I have the same issue. When JACK (pipewire-jack) is used, Ardour freezes immediately after add midi track is attempted.
Ardour is 7.5.0.
Pipewire is latest possible (commit 0a13d37e5, Jul 14 2023).

Doesn't happen when Reaper (instead of Ardour) is used.

x42

2023-07-14 18:38

administrator   ~0027896

If this does not happen with JACK (no pipewire) or Ardour/ALSA (no pipewire) then this is a pipewire bug.

I cannot reproduce this with pipewire/git. If you can could you get a bactrace?

PS. are you certain Ardour actually use latest pipewire on your system (see comment https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3183#note_1922014)
PPS. Reaper internally works significantly different.

kmarty

2023-07-14 20:43

reporter   ~0027897

> PS. are you certain Ardour actually use latest pipewire on your system (see comment https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3183#note_1922014)
Oops, damn. You're right.
Ardour was loading the old libraries :-(

with correct LD_LIBRARY_PATH, PIPEWIRE_CONFIG_DIR and PIPEWIRE_MODULE_DIR (all pointing to the new pipewire tree) Ardour works.

Issue History

Date Modified Username Field Change
2023-06-10 05:02 gaybe New Issue
2023-06-10 13:25 x42 Note Added: 0027733
2023-06-10 13:25 x42 Assigned To => x42
2023-06-10 13:25 x42 Status new => feedback
2023-07-10 17:01 x42 Relationship added has duplicate 0009416
2023-07-14 18:24 kmarty Note Added: 0027895
2023-07-14 18:38 x42 Note Added: 0027896
2023-07-14 20:43 kmarty Note Added: 0027897
2023-07-18 04:33 x42 Status feedback => resolved
2023-07-18 04:33 x42 Resolution open => no change required
2023-10-12 03:34 x42 Relationship added has duplicate 0009479