14 Apr
2010
14 Apr
'10
1:24 p.m.
On Wed, 14 Apr 2010, Paul Davis wrote:
if the disk drive is in the line of fire when they
start to play loud,
it really will be unable to keep up. this has nothing to do with bit
rates, but is (probably) caused by the the vibrations causing read
failures which necessitate a lot of retrys, thus slowing down the
effective streaming bandwidth of the disk. if the disk is kept out the
way of direct incoming sound, the issue goes away.
yes, really!
That makes more sense. In this case, the engineer was set up back in the
dressing room, much quieter than the music room.
Thanks for the tip. I'll add a spare mouse pad to my traveling rig, so
that when I'm recording from FOH, I can provide some isolation to the
drive from the vibrations of the table. I haven't experienced crashes
myself(yet!) during recording of up to 26 tracks via
firewire400(interface) and eSATA(drive).
I do experience JACK crashes with a complaint that "your aplication
couldn't keep up" from time to time, but they're associated
with closing one session and opening another, or exporting the session to
WAV (which is strange, because Ardour doesn't output thru JACK while it's
generating the export. But fortunately, it's always as it ends.) I'm
running an ancient 2-year-old version of Ardour, so I'm looking forward to
a clean install of UbuntuStudio 10.04 in a few weeks to see what wonders
you've come up with in the past two years!
--
Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
"As for our common defense, we reject as false the choice between our
safety and our ideals."
-President Barack Obama 20 Jan 2009