Re: very significant merge in ardour git repository

On Sat, Sep 7, 2013 at 10:32 AM, Fons Adriaensen <[email protected]>wrote:

> On Sat, Sep 07, 2013 at 09:48:43AM -0400, Paul Davis wrote:
>
> > On Sat, Sep 7, 2013 at 5:56 AM, Fons Adriaensen <[email protected]>
> wrote:
> >
> > > So that means that you would connect a track input to e.g.
> > > 'input 17' using Ardours's connection dialog, instead of
> > > having a 'port' with a dedicated name (the track's name) ?
> > >
> >
> > Nope. There are no changes (so far) to the semantics of ports and wiring
> > arising from this change. The goal was to make "native" audio I/O
> possible
> > (i.e. non-JACK), not to alter the basic port model that Ardour has
> > inherited from JACK (and that in some senses JACK originally inherited
> from
> > Ardour).
>
> The context of my question above, which maybe wasn't clear, is
> 'when not using Jack, but a native interface, if and when that
> will be possible'.
>

that was the context of my answer as well. again, nothing about the changes
made thus far alter the basic usage of ports by ardour.

_______________________________________________
ardour-dev mailing list
[email protected]
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org