Re: [Jack-Devel] Can't bring F/P below 128

PrevNext  Index
DateSat, 31 Dec 2011 10:59:27 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToNikos Chantziaras <[hidden] at arcor dot de>
Cc[hidden] at jackaudio dot org
In-Reply-ToNikos Chantziaras Re: [Jack-Devel] Can't bring F/P below 128
Follow-UpNikos Chantziaras Re: [Jack-Devel] Can't bring F/P below 128
On Sat, Dec 31, 2011 at 10:27 AM, Nikos Chantziaras <[hidden]> wrote:

> I do not record anything with the sound card.  I produce using software
> synthesizers and samples that are recorded elsewhere.  This whole process
> doesn't even touch the sound card, since it's rendered directly from the
> software to a WAV file.  So quality isn't affected by the sound card at all.
>  Only thing I need is fast response for my MIDI keyboard (software synths
> also add quite a bit of latency, which is why I feel a difference between 5
> and 2.6ms.)  And I only need 2 channels; only use stereo monitors.
>
> So a "professional" sound card is totally wasted here.  I just need it to be
> low latency with JACK.

you seem to be describing a process that seems a bit contradictory to
me: on the one hand, you say "its rendered directly from the software
to a .wav file", but then you later say "i need [] fast respond for my
MIDI keyboard", and mention software synthesis, which to me implies
that you want to listen to what you're playing on a MIDI keyboard.

the reason that the cards at the ardour FAQ are recommended is because
of their technical design, which involves a number of subtle details
that make a huge difference to their actual behaviour in use. i didn't
recommend them because of their earth-shatteringly good A/D or DA, or
because of their special linear whatnots. most consumer/game oriented
cards are simply not correctly designed to be used for simultaneous
playback and recording, or put differently, for simultaneous input and
output. the fact that someone might additionally copy the samples  to
disk for "recording" has nothing to do with the basic design of an
audio interface intended to be used in this way.

now, if its true that you only ever do playback via the audio
interface, and never accept audio input from it, then these design
considerations are not as important. but do you really want to buy a
device for doing musical stuff and then later find out that your
ability to process incoming audio (note that i did not say
"recording") is compromised by its inferior technical design?

also, if you really believe you can tell the difference between 5 and
2.6msec, i suggest you try that in a double blind test sometime.
unless you're in the upper echelon of time-sensitive humans, my guess
is that you won't reliably be able to say which one is in use. I'm
guessing you're already aware that the air distance between you and
your monitors is probably adding 3msec of latency compared to when you
wear headphones ...
PrevNext  Index

1325347179.3732_0.ltw:2,a <CAFa_cKmozQYWO4XivRxRe6QCeCFgUJ6fxmEnBa5xo4OsZHAdDg at mail dot gmail dot com>