From: Rob Janssen <pe1chl@amsat.org>
To: alsa-devel@alsa-project.org
Subject: Re: Control the exact moment of output
Date: Wed, 30 Apr 2014 10:11:28 +0200 [thread overview]
Message-ID: <5360B030.7010805@amsat.org> (raw)
In-Reply-To: <51940.86.107.254.57.1398840206.squirrel@boosthardware.com>
Patrick Shirkey wrote:
>
> Have you looked into netjack?
>
> Several of the network timing issues have been worked through quite
> extensively. We have used it to distribute data across several machines in
> a cluster and find it to be very stable and workable with acceptable
> latency over gigbit lan.
>
> You might find netjack gives you a good headstart on this project.
>
> Adding support for JACK is a minor task compared to rewriting (and
> testing) netjack. You will also gain access to a host of other
> professional functionality and ALSA, OSS, FIrewire support too.
>
> In addition your software will play nice with other professional software
> and have direct access to data on the JACK graph as a bonus.
>
Thanks for the pointer! It indeed appears that this project is trying the same thing as
we are doing.
It will require some further study. Documentation appears to be scarce, I have not been
able to locate a document yet that describles what it actually achieves and what caveats
there are. I saw one thing on the Wiki: it transmits data all the time. We will probably need
some form of on/off control to avoid wasting bandwidth, but maybe it can be done in a CODEC.
I also saw it has fixed network latency setting, while I had already envisioned a system for
automatically determining the added latency based on feedback from the remotes.
But at least it provides a lot of insight into using Alsa in timing critical applications, something
I had been looking for.
(I know that writing documentation is a drag, but projects like Alsa and this one would be so
much more useful and accessible when there would be more detailed documentation that
goes beyond an installation HOWTO and a plain listing of available functions and parameters)
Rob
prev parent reply other threads:[~2014-04-30 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 18:21 Control the exact moment of output Rob Janssen
2014-04-29 7:50 ` Clemens Ladisch
2014-04-29 8:25 ` Rob Janssen
2014-04-30 6:43 ` Patrick Shirkey
2014-04-30 8:11 ` Rob Janssen [this message]
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=5360B030.7010805@amsat.org \
--to=pe1chl@amsat.org \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox