I've noticed that the sequencer when started up can get into a loop (I
suppose) and eat all cpu. So all normal operation (layout and stuff) is
considerably slowed down. I haven't investigated yet but I assume it happens
when it can't connect to arts or something similar (I don't have the proper
configuration at the moment). It also happens in case of a gui crash.
From: Richard Bown <bownie@bo...> - 2001-12-15 11:25:54
> It also happens in case of a gui crash.
The sequencer can run away with itself when DCOP messages go astray -
I haven't seen this behaviour much though and less still when I changed
the main playback loop to use non-blocking send()s instead of call()s.
If aRTS isn't around then the sequencer just won't start.
If this is just happening randomly then this is a cause to worry but
I'm sure any and all performance issues will soon come galloping to
the fore when we try to do audio.
On Saturday 15 December 2001 12:24, Richard Bown wrote:
> If aRTS isn't around then the sequencer just won't start.
aRTS is running, but without the OSS interface (and without the MIDI channel
> If this is just happening randomly
No, it seems it happens right at startup. I'll try to investigate a bit.
Get latest updates about Open Source Projects, Conferences and News.