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

 
 
Latest News
Implementing cache option for all output backends posted by jkraehemann, Mon 07 Jan 2019 11:37:40 PM UTC - 0 replies
merry Christmas posted by jkraehemann, Mon 24 Dec 2018 08:12:24 PM UTC - 0 replies
OSC client to server communication succeeded posted by jkraehemann, Sat 15 Dec 2018 09:31:38 PM UTC - 0 replies
Advanced Gtk+ Sequencer v2.1.2 released posted by jkraehemann, Fri 30 Nov 2018 06:55:47 PM UTC - 0 replies

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