Grammostola Rosea wrote:
You know that I completely agree not to recommend Linux real-time audio,
resp. it depends to the hardware and needs. 64 Studio 3.0-beta3 on my
machine is fine out of the box, excepted of the MIDI jitter sent to
external equipment and this wasn't solvable by using different sequencer
timer sources Rui added to Qtractor, just because of my troubles. Making
the USB MIDI device head of all MIDI devices by rtirq or anything else,
e.g. compiling and patching an individual kernel also didn't help for
other installations I tested.
I guess if somebody just want to use Ardour and Rosegarden or Qtractor
by using virtual synth only, this seems to work for most machines out of
the box by using 64 Studio. I guess for the beta there only needs to be
edit /etc/security/limits.conf if somebody wants to use Ardour.
I know a lot of people having the same trouble with JACK I had. JACK1
disconnected clients, but e.g. 64 Studio beta now comes with JACK2 out
of the box, so a newbie don't need to do anything, he won't run into
this trouble. Step by step some problems were solved.
There are some things missing for a Linux studio in the box, that is
available for Mac and Windows, but for people like me, having external
studio equipment this isn't a big problem.
If we don't no the needs of a user and what equipment he has got,
recommending Linux is impossible. For some machines there still seems to
be a problem to use the installers or they got troubles because even the
VESA driver isn't fine, but this isn't a problem just for real-time
OT: In theory the system timer for today's real-time kernels should be
the best solution, that's why Rui first made only this timer available
by Qtractor, but anyway, for my machine it's PCM playback, but even this
one isn't fine.
Linux-audio-dev mailing list