Re: [Jack-Devel] JACK custom-data API

Meta-data is not data.

Adding new port types is a totally separate task, and the jack-video stuff
was rejected because it didn't add new ports types in the way that we
intended when the API was designed.

This is about adding meta-data to existing objects (clients, ports) within
JACK, not new types of port-transferrable data.


On Tue, Sep 24, 2013 at 8:49 AM, Patrick Shirkey <[hidden]
> wrote:

>
> On Tue, September 24, 2013 10:27 pm, Paul Davis wrote:
> > On Tue, Sep 24, 2013 at 7:31 AM, Patrick Shirkey
> > <[hidden]
> >> wrote:
> >
> >>
> >>
> >> Sounds good, will these additions be compatible or extendable to support
> >> the iqm format for 3d modelling data?
> >>
> >> http://sauerbraten.org/iqm/
> >>
> >
> > what would this have to do with JACK?
> >
>
> There is this rumour of a 3d extension for JACK that would allow 3d
> applications such as Blender, Make Human, etc.. to share realtime 3d
> modelling data with other 3d engines such as source, tesseract, ogre,
> unigine, etc...
>
> IIUC, it is similar to the jack-video extension that salsaman provided but
> for 3d modelling data instead.
>
> Given that JACK is the defacto standard for open source multimedia (audio,
> midi, session, network), data sharing it makes sense to me that video and
> 3d data can be part of the API too.
>
> If you are going to go to the effort of adding support for arbitrary data
> formats it might be useful to know of this other project too.
>
>
>
> --
> Patrick Shirkey
> Boost Hardware Ltd
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

1380027882.14176_0.ltw:2, <CAFa_cKmq8-rHBxB-PyTVfBE9X7un+y==N2Yzq-0-YYmoUf4vhQ at mail dot gmail dot com>