27 Nov
2012
27 Nov
'12
8:30 p.m.
On 11/27/2012 03:04 AM, Ralf Mardorf wrote:
My MUA is broken :(.
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] RTC/HPET timer permissions
Date: Tue, 27 Nov 2012 13:53:34 +0100
On Tue, 2012-11-27 at 12:54 +0100, Jeremy Jongepier wrote:
MIDI jitter.
XFCE works fine here on multiple machines. Unity sucks and GNOME3 is a
pathetic bloated resource hog that's an insult to a fine name. ;-)
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
What do you mean by hardware MIDI? External
synths? So when only using
soft synths using snd-hrtimer doesn't make any difference at all?
Yes, that's my experience. Perhaps it's tickless vs not tickless
regarding to IRQ handling of the hardware MIDI or simply the very high
resolution. A coder might give us some insight.
For MIDI internal Linux I guess there are no layers, excepted of bridges
between ALSA and JACK that might cause issues. perhaps I'm mistaken, but
I never noticed an issue for a stable DAW.
Usually
system timer (default) is the best way to go,
hr timer is better, but can cause issues,
What kind of issues? linuxmusicians.com Wiki
Take care to keep backwards compatibility, some people e.g. still use 64
Studio.
Other stuff at the moment is in a transition state. You never know what
services to start and stop by /etc/init.d/foo and what by the command
"service".
Better wait with editing until we all are forced to use GNOME3 or Unity
with hard dependencies to upstart or systemd, sorry I couldn't resist,
since current Xfce at the moment is a PITA