From linux-audio-dev Thu Sep 11 22:09:32 2014 From: Arnold Krille Date: Thu, 11 Sep 2014 22:09:32 +0000 To: linux-audio-dev Subject: Re: [LAD] Open Source Audio Interface Message-Id: <20140912000932.4dcfa221 () xingu ! arnoldarts ! de> X-MARC-Message: https://marc.info/?l=linux-audio-dev&m=141047341119251 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============7041961215002777170==" --===============7041961215002777170== Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Foxzi0aQiDw=Z_Z1TpN5YEL"; protocol="application/pgp-signature" --Sig_/Foxzi0aQiDw=Z_Z1TpN5YEL Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 11 Sep 2014 14:24:56 -0700 (PDT) Len Ovens wrote: > Where I see your info as being useful though, is if I choose to send > data (which could be varying sized packets) I may still wish to set > the data packet size to a fixed size depending on what is left from > audio. The whole network end of things needs to be decoupled from > real time. That last sentence is a bit contradicting. You want to send audio over network, you want the audio to be near realtime. But you want to decouple network from realtime... (In math: A=3D=3DB && B=3D=3DC && A!=3DC) > To be honest, I have spent a lot less time thinking about the network=20 > traffic part of things than the audio part of things. The reason for > this is that the use cases for allowing network through our line is > small. As has already been commented, a desktop can have a second NIC > and the laptop generally has wireless. The main usecase for network > through the same IF might be radio work where one might have a SIP > connection (phone line) going through net. (anyone see others?) > Because the AI has a second NIC and an OS, it should be possible to > set up the SIP session on that box. There is a widespread use-case for audio and non-audio network traffic on the same segment: audio and control/midi messages on the same segment. And you don't want your fader moves to interrupt your audio. And your current thinking seems to be about using a dedicated network-link between PC and audio-interface with a possible chain-link to other interfaces. But what about a dedicated network (with switch) to connect multiple PCs and audio-interfaces? Then you have to deal with lots more channels, thus lots more realtime data and also lots more control-messages. Have fun, Arnold PS: Maybe this question sound foolish: Why not AVB / open AVB? --Sig_/Foxzi0aQiDw=Z_Z1TpN5YEL Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlQSHaAACgkQtuvagsE+DE5qXQD8DXD7BVodadr8+DZKWnD/zVgt AieyYvgP6TS+F4IgPRwBAIDfzwJrOqjbKdMQXjUGS3ieYR0IXIf1tyW9FUWiC+TU =1F5m -----END PGP SIGNATURE----- --Sig_/Foxzi0aQiDw=Z_Z1TpN5YEL-- --===============7041961215002777170== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev --===============7041961215002777170==--