Re: [Jack-Devel] Jack-Devel Digest, Vol 56, Issue 47

PrevNext  Index
DateSat, 26 Feb 2011 21:29:55 +0100
From Florian Faber <[hidden] at faberman dot de>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToArnold Krille Re: [Jack-Devel] Jack-Devel Digest, Vol 56, Issue 47
Follow-UpArnold Krille Re: [Jack-Devel] Jack-Devel Digest, Vol 56, Issue 47
Follow-Uptorbenh Re: [Jack-Devel] Jack-Devel Digest, Vol 56, Issue 47
On 02/26/2011 09:16 PM, Arnold Krille wrote:

> But afaik git has the advantage that one can move whole development branches 
> including history from one server to the other. So we could also start on 
> github or something and get it completely included in a more mainline jack-
> repository without loosing historic commits like "it works!" or "Initial 
> commit"...

I believe you guys see it with from the wrong perspective. I don't see
AVB support in jack as a backend, but as a simple bridge from AVB ports
to jack ports.  This can be achieved by simple stand-alone tools, much
like netjack.

If you want to provide physical inputs or outputs for Ravenna on your
machine, there's nothing you can do without special hardware - for the
moment. You have to produce a phase synchronous clock, synced via PtP,
and provide a means to timestamp incoming samples and output samples at
the correct point in time.


Flo
-- 
Machines can do the work, so people have time to think.
public key B3B9226C          x-hkp://wwwkeys.eu.pgp.net
PrevNext  Index

1298752223.13336_0.ltw:2,a <4D6962C3.7000406 at faberman dot de>