Re: [Jack-Devel] Writing an IEEE 802.1BA (AVB) compliant network backend for Jack2

PrevNext  Index
DateTue, 01 Mar 2011 13:35:54 +0100
From torbenh <[hidden] at gmx dot de>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToAdrian Knoth Re: [Jack-Devel] Writing an IEEE 802.1BA (AVB) compliant network backend for Jack2
Follow-UpAdrian Knoth Re: [Jack-Devel] Writing an IEEE 802.1BA (AVB) compliant network backend for Jack2
On Tue, Mar 01, 2011 at 10:24:07AM +0100, Adrian Knoth wrote:
> On Tue, Mar 01, 2011 at 04:45:48AM +0100, torbenh wrote:
> 
> Hi!
> 
> > the problems start when there is packet loss and high jitter.
> > (such as an internet connection over the atlantic or somthing, here it
> > gets interesting.)
> 
> Don't get me wrong, but may I, for once, question this assumption?
> I know there are some remote jamming tools available, but I don't know a
> single musician using them.
> 
> Given the inherent latency on the WAN, there's no real "together"
> anyway, so the whole thing degrades to simple asynchronous streaming.
> (read: icecast or whatsoever)

thanks for a demotivating me.

> 
> If you know a sane use case where one needs a distributed synchronous
> transatlantic setup, then I'll stand corrected, but within this
> AVB/Ravenna discussion, let's talk LAN and only LAN.

you deleted the part about LAN.
tip:core/timers is already carrying code for in kernel ptp clocks.

there are patches for IXP46x, National Semiconductor PHYTER and MPC85xx
that build up on this.

as i see it... we could make a 10lines patch to the dummy device,
and have jack synced to a ptp clock.

then you just need a non-resampling rtp streamer. 


-- 
torben Hohn
PrevNext  Index

1298982988.25495_0.ltw:2,a <20110301123554.GD23120 at siel dot b>