From: Matt Flax <flatmax@flatmax.org>
To: linux-iio@vger.kernel.org
Subject: iio and jack - 1MHz sample rate success
Date: Wed, 12 Feb 2014 18:36:23 +1100 [thread overview]
Message-ID: <52FB2477.9080108@flatmax.org> (raw)
I have implemented the jack2 iio driver and have done a couple of tests.
In a preliminary finding, waiting for more time to test and re-test, I
have had success.
I don't see any overruns reported (when setup properly), and I haven't
put a signal through the system to highlight any un-reported overruns.
Next week I will look into this more.
Firstly I would like to say that writing a driver for jack2 is a little
difficult because there is not much documentation ... at least I
couldn't find simple information. Some inline src doc would be good ...
mind you, I could have put more into my driver as well :)
On the system with IIO devices I ran :
jackd -iio
I then setup and ran netjack on both computers.
On the other computer I used :
jack_capture -c 2 -p system:capture*
... wahlah ... it worked ! with an MTU of 1500. Thats 2 channels @ 1 MHz
Everything reporting 1MHz sample rates and so on a so forth, no xruns
and the wav file looked like what I expected ...
When I tried to record 4 channels @ 1 MHz, I had to increase the MTU to
6000 to get rid of xruns on the ARM core. But still ... 4 channels @
1MHz over a network ... pretty good start !
I would like to integrate my both of my iio branchs into the jack1 and
jack2 repos, but for now I have forked the jack2 repo here :
https://github.com/flatmax/jack2/tree/iio
I have some questions for other developers of jack2.
is it necessary to use :
JackDriver::CycleTakeBeginTime();
and
JackDriver::CycleTakeEndTime();
?
thanks
Matt
p.s. Don't forget that these findings are very preliminary and things
need to be neatened up, debugged more and so on and so forth.
next reply other threads:[~2014-02-12 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 7:36 Matt Flax [this message]
2014-02-14 0:47 ` iio and jack - 1MHz sample rate success Christian Gagneraud
2014-02-14 0:51 ` Matt Flax
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=52FB2477.9080108@flatmax.org \
--to=flatmax@flatmax.org \
--cc=linux-iio@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.