View Issue Details

IDProjectCategoryView StatusLast Update
0003292ardourbugspublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003292: A3 segfaults when creating a MIDI track
DescriptionA3 7304 under debian squeeze 64 segfaults as soon as you try to create a MIDI track in a new session
Additional InformationJACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
Mouse mode toggled to 1
Mouse mode toggled to 1
LV2: Discovering 19 plugins
Done LV2 discovery
MIDI port buffers = 4068
MIDI UI running
auditioner resetting write sources, recrodable 0 chans = 0
Mouse mode toggled to 1
Midi 1 use new write source for n = 0 recordable ? 1
Midi 1 use new write source for n = 0 recordable ? 1
subgraph starting at ardour timed out (subgraph_wait_fd=11, status = 0, state = Triggered, pollret = 0 revents = 0x0)


**** alsa_pcm: xrun of at least 1.436 msecs


subgraph starting at ardour lost client
bad status (-2) for client ardour handling event (type = 8)


**** alsa_pcm: xrun of at least 5.776 msecs


jack main caught signal 12
Segmentation fault
TagsNo tags attached.

Activities

danboid

2010-06-26 12:39

reporter   ~0008332

I put this down as occuring 'always' when in fact its most of the time- I have successfully got the latest build to create a MIDI track once o twice as thats how I verified the MIDI automation mode box was working.

danboid

2010-06-26 18:48

reporter   ~0008333

OK so this turned out to be a JACK prob more than an Ardour one.

Due to mainly power issues with my laptop in the vanilla lucid x64 kernel I have now switched to ze Debian Squeeze as my primary A3 testing platform.

qjackctl was set to use the 'default' audio interface device which used to work fine for me under lucid but squeeze sees my pc speaker as the first ALSA device (0) and my laptops real soundcard as 0000001. However, even then its more complicated as my sound is seen as 3 devices to alsa- HDA Intel (hw:1), ALC 883 Analog (hw:1,0) and hw:1,1 is the softmodem.

I actually had qjack set to using hw:1 Intel as thats what I set ALSA to to get that to work but qjack only works when I set it to hw:1,0- JACK seemed to start OK on hw:1 but Ardour crashed when I tried to make a MIDI track.

So, the real problem here is that hw:1,0 wasn't presented as an option to me by A3's JACK Audio Engine Setup Wizard -ALC883 was the only choice but I presume it was actually using hw:1 as it woud crash when I tried adding a MIDI track.

You can resolve this now- shall I file a feature request for more interface options in the Audio Engine Wizard?

cth103

2010-06-27 02:05

administrator   ~0008334

I don't think Ardour should segfault under any circumstances, so we probably need to figure out exactly what went wrong here ...

danboid

2010-07-21 06:43

reporter   ~0008524

Fixed some time ago - resolve please

system

2020-04-19 20:14

developer   ~0022146

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2010-06-26 12:37 danboid New Issue
2010-06-26 12:39 danboid Note Added: 0008332
2010-06-26 18:48 danboid Note Added: 0008333
2010-06-27 02:05 cth103 Note Added: 0008334
2010-07-21 02:26 cth103 cost => 0.00
2010-07-21 02:26 cth103 Target Version => 3.0-beta1
2010-07-21 06:43 danboid Note Added: 0008524
2010-07-21 12:23 cth103 Status new => resolved
2010-07-21 12:23 cth103 Resolution open => fixed
2010-07-21 12:23 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022146
2020-04-19 20:14 system Status resolved => closed