newsAdvanced Gtk+ Sequencer - News: Got segfault after a while of recording

Latest News
GSequencer v2.1.53 for debian buster posted by jkraehemann, Fri 08 Mar 2019 11:01:12 PM UTC - 0 replies
Get emotional as debian buster is going to be released posted by jkraehemann, Thu 07 Mar 2019 12:46:59 AM UTC - 0 replies
State of GSequencer in debian buster posted by jkraehemann, Sun 03 Mar 2019 07:08:32 PM UTC - 0 replies
handling LV2 iriref posted by jkraehemann, Wed 13 Feb 2019 10:20:49 AM UTC - 0 replies
fixed ref-count posted by jkraehemann, Sat 09 Feb 2019 02:46:41 PM UTC - 0 replies
[Submit News]
[79 news in archive]

Got segfault after a while of recording

Item posted by Joël Krähemann <jkraehemann> on Thu 20 Sep 2018 03:04:31 PM UTC.

Capturing sound works good. However gsequencer crashed once, from my `journalctl -b`:

I think it is a bad file descriptor. Since the scheduling of IO makes trouble. In GSequencer you usually have this order:

  1. ... idle
  2. read input from soundcard
  3. compute audio data
  4. write output to soundcard
  5. idle ...

The problem now, is there is no hint where in attacks in the order. Ideally it would start during idle but there is no guarantee to it. One more problem is the library could yet have been starting playback and then you decide to do capture sound. One more is communication between GUI and audio layer happens async and non-blocking.

Anyhow, even as it would do proper order. Reading soundcard first is believed to be bad for ALSA because it expects output.

You should think about it. I tell you as figured out a solution.

by Joël

No messages in Got segfault after a while of recording


Back to the top

Powered by Savane 3.4