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

PrevNext  Index
DateMon, 30 Sep 2013 22:13:29 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] JACK custom-data API
The "uuid" branch of JACK1 now contains a functioning but not necessarily
finished API and implementation for arbitrary meta-data for JACK clients
and ports. The implementation uses the Berkeley DB routines to painlessly
deal with interprocess issues including data sharing, locking and so forth.
It has been designed to be very fast for looking up or deleting specific
metadata, less efficient for looking or deleting multiple metadata (e.g.
all metadata associated with a given client).

There is a new tool in the (theoretically shared) tools/ folder called
jack_property which can be used to set/list/delete metadata. It not
finished and there is no man page for it yet.

Work continues. I promised that this would be fully functional by the end
of this week.

--p



On Tue, Sep 24, 2013 at 9:04 AM, Paul Davis <[hidden]>wrote:

> 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
>>
>
>
PrevNext  Index

1380593615.17922_0.ltw:2, <CAFa_cK==-e9i-6SfnOKaa3xOQg9LcqBaqampMquwhAT-Py1+6g at mail dot gmail dot com>