[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-audio-dev
Subject:    Re: [LAD] Open Source Audio Interface
From:       Paul Davis <paul () linuxaudiosystems ! com>
Date:       2014-09-11 23:56:20
Message-ID: CAFa_cK=Nupmi7kMXmE5jgaztbuFv34EE7GCM23+_rDgg5QXYxA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Sep 11, 2014 at 6:50 PM, Len Ovens <len@ovenwerks.net> wrote:


> Shouldn't be, The network traffic does not need to be real time, but the
> network does. In other words the way the host computer deals with network
> traffic does not need to be real time. The computer puts a packet into a
> buffer, this part does not need to be real time.


this is not correct. there's no difference between this operation and
putting audio into the h/w buffer associated with a PCI audio interface.
the entire transport chain must be RT.

The network sends it while there is no audio traffic, this part does need
> to be real time.
>

also wrong. it must be able to send it on demand, or at least within a
given (realtime) window.

but this then gets to the clocking part ... not word clock per se (although
that is related) but the question of how the entire transport mechanism is
driven.

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep \
11, 2014 at 6:50 PM, Len Ovens <span dir="ltr">&lt;<a href="mailto:len@ovenwerks.net" \
target="_blank">len@ovenwerks.net</a>&gt;</span> wrote:<br><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class=""><br></span> Shouldn&#39;t be, The network \
traffic does not need to be real time, but the network does. In other words the way \
the host computer deals with network traffic does not need to be real time. The \
computer puts a packet into a buffer, this part does not need to be real \
time.</blockquote><div><br></div><div>this is not correct. there&#39;s no difference \
between this operation and putting audio into the h/w buffer associated with a PCI \
audio interface. the entire transport chain must be RT.<br> <br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> The network sends it while there is no audio traffic, this \
part does need to be real time.<span \
class=""><br></span></blockquote><div><br></div><div>also wrong. it must be able to \
send it on demand, or at least within a given (realtime) window.<br></div><div>  \
<br></div><div>but this then gets to the clocking part ... not word clock per se \
(although that is related) but the question of how the entire transport mechanism is \
driven.<br></div></div></div></div>



_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


[prev in list] [next in list] [prev in thread] [next in thread]