From: "Niccolò Belli" <darkbasic4@gmail.com>
To: ffado-user@lists.sourceforge.net,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: My first recording session with a Focusrite Saffire PRO 40
Date: Sun, 27 Mar 2011 13:20:46 +0200 [thread overview]
Message-ID: <4D8F1D8E.4010802@gmail.com> (raw)
Yesterday I did my first session with my Saffire PRO 40, I initially
tried with kernel 2.6.33.7-rt30 and the old firewire stack, but I get
xruns even for a simple playback of a previously recorded session. I
also experienced lots of graphical problems because of the intel drivers
not playing well with old kernels. When I realized it was impossible to
record such a way I booted to a 2.6.38.1-bfq-ck1 I compiled for
recording purposes (Budget Fair Queueing I/O Scheduler, Brain Fuck
Scheduler and the whole Con Kolivas patchset with a 10.000 Hz timer
frequency). I obviously used the new firewire stack. This time it was
much better and I had no problems while playing a previously recorded
session. So I attached 8 analog inputs (two of them with inserts to
guitarix_head), another two inputs from Pianoteq and 10 outputs to
headphones for monitoring for a total of 10 inputs and 10 outputs.
I used hardware monitoring, with the only exceptions of the piano, the
guitar and the bass. Unfortunately even with a 17.4ms latency
(256/44100/3) I still got xruns and I had to restart the whole recording
lots of time because of that. My hardware isn't very powerful (a 1.4GHz
Core2 Duo ULV, 5400rpm serpent256 encrypted hard disk, 4GB ram) but I
think it can do much better, because I previously recorded without
problems with a Fast Track Ultra (USB) and 2.6.33-rt (when it wasn't a
useless, ancient kernel). Next time I will use a 3,3GHz quad core Sandy
Bridge 2500K with 8GB ram, I hope it will be enough :/
Cheers,
Darkbasic
reply other threads:[~2011-03-27 11:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8F1D8E.4010802@gmail.com \
--to=darkbasic4@gmail.com \
--cc=ffado-user@lists.sourceforge.net \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.