Re: [LAU] M-Audio fast track pro mic input fails with smaller buffer size

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Wednesday, October 31, 2012 - 12:20 pm

--20cf307abe3d74514c04cd59ed34
Content-Type: text/plain; charset=ISO-8859-1

On Oct 30, 2012 12:44 AM, "Lewis Pike" wrote:

Thanks for this... so, 46 ms latency in my concert and count myself lucky
it isn't worse. And, replace the ftpro when I can...

> If you are able to successfully configure this device for recording in

My experience using it with Jack is: if audio input is correct when Jack
starts, then it stays OK as long as the Jack server is running. I have also
seen the problem with default Jack settings, but rarely, certainly less
often than you report. The difference is that I start Jack and keep it
running for a whole session, maybe several hours, while in your case,
arecord connects to the hardware fresh on every take, raising the
probability of a failed take.

I'm fairly certain if you use Jack and keep one connection to the Fast
Track alive for a longer time, the issue will not go away totally, but it's
manageable. Check for good input at the start of the session, and then you
should be OK.

hjh

--20cf307abe3d74514c04cd59ed34
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Oct 30, 2012 12:44 AM, "Lewis Pike" <phaselocker@gmail.com> wrote:

's audio
d
br>
e
Thanks for this... so, 46 ms latency in my concert and count=
myself lucky it isn't worse. And, replace the ftpro when I can...
or recording in
My experience using it with Jack is: if audio input is corre=
ct when Jack starts, then it stays OK as long as the Jack server is running=
. I have also seen the problem with default Jack settings, but rarely, cert=
ainly less often than you report. The difference is that I start Jack and k=
eep it running for a whole session, maybe several hours, while in your case=
, arecord connects to the hardware fresh on every take, raising the probabi=
lity of a failed take.

I'm fairly certain if you use Jack and keep one connecti=
on to the Fast Track alive for a longer time, the issue will not go away to=
tally, but it's manageable. Check for good input at the start of the se=
ssion, and then you should be OK.

hjh

--20cf307abe3d74514c04cd59ed34--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] M-Audio fast track pro mic input fails with smalle..., James Harkins, (Wed Oct 31, 12:20 pm)