From: Henrik Austad <henrik@austad.us>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
hansverk@cisco.com, alsa-devel@alsa-project.org,
haustad@cisco.com
Subject: Re: [RFC] AVB - network-based soundcards in ALSA
Date: Wed, 28 May 2014 11:43:18 +0200 [thread overview]
Message-ID: <20140528094318.GC26498@austad.us> (raw)
In-Reply-To: <5384C37E.8060404@linux.intel.com>
On Tue, May 27, 2014 at 11:55:26AM -0500, Pierre-Louis Bossart wrote:
>
> >This reminds me of the talk Pierre gave in LPC at San Diego a couple
> >of years ago. Although his topic was more about the audio time
> >accounting, the framework mentioned at that time would fit with this
> >scenario?
>
> Yes it is related but the overall architecture on a first pass of
> reading seems different: the ideas we presented were more along the
> lines of letting every subsystem provide an accurate accounting of
> time and have some userspace parts see and compensate the difference
> between system, network, audio, video, clocks.
Any documents/talks available for this? I found "Audio/system time
alignment" from Plumbers 2012 (link at the bottom), is that the one?
I see that this also covers AVB, but places everything AVB-related in
userspace and then lets the application tie everything together. What
was the design-rationale for this?
To turn it around; our idea of placing this in the kernel was
- easier to integrate with v4l
- single interface (ALSA) for userspace to play audio
- easy access to NIC internals to ship off frames and whatnot.
what we found to be a pretty neat solution
Did we miss something crucial?
> very interesting topic and RFC, thanks for posting this.
Thanks for providing feedback! :)
http://www.linuxplumbersconf.org/2012/wp-content/uploads/2012/11/2012-lpc-audio-time-alignment-bossart.pdf
--
Henrik Austad
next prev parent reply other threads:[~2014-05-28 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 13:03 [RFC] AVB - network-based soundcards in ALSA Henrik Austad
2014-05-26 16:21 ` Alexander E. Patrakov
2014-05-27 9:02 ` Henrik Austad
2014-05-27 12:10 ` Alexander E. Patrakov
2014-05-28 9:07 ` Henrik Austad
2014-05-27 13:47 ` Clemens Ladisch
2014-05-28 9:32 ` Henrik Austad
2014-05-28 13:12 ` Clemens Ladisch
2014-05-27 14:36 ` Takashi Iwai
2014-05-27 16:55 ` Pierre-Louis Bossart
2014-05-28 9:43 ` Henrik Austad [this message]
2014-05-28 15:14 ` Pierre-Louis Bossart
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=20140528094318.GC26498@austad.us \
--to=henrik@austad.us \
--cc=alsa-devel@alsa-project.org \
--cc=hansverk@cisco.com \
--cc=haustad@cisco.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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.