12 May
2016
12 May
'16
1:26 a.m.
What about aliases ?
Dnia Czwartek, 12 Maja 2016 08:22 Hanspeter Portner <ventosus(a)airpost.net>
napisał(a)
On 12.05.2016 06:27, aledez0 wrote:
is there any way to list the connections by how
there are in the project file
instead of by alphabetical order?
YES (theoretically)
There is a way, by means of the metadata api [1] via the metadata key
'http://jackaudio.org/metadata/order' [2], but the trio of JACK client,
server and patchbay must support this for it to work.
* the client sets the order of its ports via 'jack_set_property'
* the server stores the metadata in a database
* the patchbay reads the metadata to order ports accordingingly
NO (practically)
* only few clients and patchbays support this yet
* JACK1 implements the metadata API, JACK2 still does NOT
in mixbus 3 once you have named the tracks
they don't show up in the connection window in the order they are in the
project window.
[1] http://jackaudio.org/api/group__Metadata.html
[2] https://github.com/drobilla/jackey/blob/master/jackey.h
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
12 May
12 May
1:49 a.m.
On 12.05.2016 08:26, Pawel wrote:
What about aliases ?
Which one? a port can have up to 2 aliases...
Dnia Czwartek, 12 Maja 2016 08:22 Hanspeter Portner
<ventosus(a)airpost.net> napisał(a)
On 12.05.2016 06:27, aledez0 wrote:
is there any way to list the connections by how
there are in the project file
instead of by alphabetical order?
YES (theoretically)
There is a way, by means of the metadata api [1] via the metadata key
'http://jackaudio.org/metadata/order' [2], but the trio of JACK client,
server and patchbay must support this for it to work.
* the client sets the order of its ports via 'jack_set_property'
* the server stores the metadata in a database
* the patchbay reads the metadata to order ports accordingingly
NO (practically)
* only few clients and patchbays support this yet
* JACK1 implements the metadata API, JACK2 still does NOT
in mixbus 3 once you have named the tracks
they don't show up in the connection window in the order they are in the
project window.
[1] http://jackaudio.org/api/group__Metadata.html
[2] https://github.com/drobilla/jackey/blob/master/jackey.h
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
6:27 a.m.
New subject: [Jack-Devel] Odp: Re: New build of QJackCtl for Windows
Port aliases were almost never used for anything, and the current build of
qjackctl has support for them removed.
On Thu, May 12, 2016 at 2:49 AM, Hanspeter Portner <ventosus(a)airpost.net>
wrote:
On 12.05.2016 08:26, Pawel wrote:
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
What about aliases ?
Which one? a port can have up to 2 aliases...
Dnia Czwartek, 12 Maja 2016 08:22 Hanspeter
Portner <
ventosus(a)airpost.net> napisał(a)
> On 12.05.2016 06:27, aledez0 wrote:
>> is there any way to list the connections by how there are in the
project
file
>> instead of by alphabetical order?
>
> YES (theoretically)
>
> There is a way, by means of the metadata api [1] via the metadata key
> 'http://jackaudio.org/metadata/order' [2], but the trio of JACK client,
> server and patchbay must support this for it to work.
>
> * the client sets the order of its ports via 'jack_set_property'
> * the server stores the metadata in a database
> * the patchbay reads the metadata to order ports accordingingly
>
> NO (practically)
>
> * only few clients and patchbays support this yet
> * JACK1 implements the metadata API, JACK2 still does NOT
>
> > in mixbus 3 once you have named the tracks
>> they don't show up in the connection window in the order they are in
the
project window.
[1] http://jackaudio.org/api/group__Metadata.html
[2] https://github.com/drobilla/jackey/blob/master/jackey.h
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
12:22 p.m.
New subject: [Jack-Devel] Odp: Re: New build of QJackCtl for Windows
On Thursday, May 12, 2016 07:27:40 AM Paul Davis wrote:
Port aliases were almost never used for anything, and
the current build of
qjackctl has support for them removed.
No!
If you are thinking of this, please don't remove alias support from Jack!
Or at least replace it with some default metadata containing similar
'friendly' port names, as I had requested some time ago.
Aliases (at least the default ones supplied by Jack)
are very important for MusE.
We use them to reconnect ports that are not available,
when those ports become available again. (USB midi etc.)
A sort of 'session management' feature. It works quite well.
The standard 'canonical' names (System::midi_playback_1)
provided by ports are /not/ sufficient for this task
since the numeric portion is derived from simple 'up counters'
which change value every time a device is re-plugged.
I can provide more details if needed.
We look for which ever port name or alias does /not/
contain the word 'System:', if possible.
Thanks.
Tim.
On Thu, May 12, 2016 at 2:49 AM, Hanspeter Portner <ventosus(a)airpost.net>
wrote:
> On 12.05.2016 08:26, Pawel wrote:
> > What about aliases ?
>
> Which one? a port can have up to 2 aliases...
>
> > Dnia Czwartek, 12 Maja 2016 08:22 Hanspeter Portner <
>
> ventosus(a)airpost.net> napisał(a)
>
> >> On 12.05.2016 06:27, aledez0 wrote:
> >>> is there any way to list the connections by how there are in the
>
> project file
>
> >>> instead of by alphabetical order?
> >>
> >> YES (theoretically)
> >>
> >> There is a way, by means of the metadata api [1] via the metadata key
> >> 'http://jackaudio.org/metadata/order' [2], but the trio of JACK
client,
> >> server and patchbay must support this for it to work.
> >>
> >> * the client sets the order of its ports via 'jack_set_property'
> >> * the server stores the metadata in a database
> >> * the patchbay reads the metadata to order ports accordingingly
> >>
> >> NO (practically)
> >>
> >> * only few clients and patchbays support this yet
> >> * JACK1 implements the metadata API, JACK2 still does NOT
> >>
> >> > in mixbus 3 once you have named the tracks
> >>>
> >>> they don't show up in the connection window in the order they are
in
>
> the
>
> >>> project window.
> >>
> >> [1] http://jackaudio.org/api/group__Metadata.html
> >> [2] https://github.com/drobilla/jackey/blob/master/jackey.h
13 May
13 May
3:55 p.m.
New subject: [Jack-Devel] Odp: Re: New build of QJackCtl for Windows
On Thu, May 12, 2016 at 1:22 PM, Tim E. Real <termtech(a)rogers.com> wrote:
On Thursday, May 12, 2016 07:27:40 AM Paul Davis
wrote:
Apparently you're not on the jack-devel mailing list.
Port aliases were removed.
Port pretty-names have a standard URI, and have since before the metadata
API was implemented. Anyone can define metadata URIs (keys). A few are
standard, as is
Qjackctl supports all this already.
Port aliases were almost never used for anything,
and the current build
of
qjackctl has support for them removed.
No!
If you are thinking of this, please don't remove alias support from Jack!
Or at least replace it with some default metadata containing similar
'friendly' port names, as I had requested some time ago.
6 p.m.
New subject: [Jack-Devel] Metadata
On Friday, May 13, 2016 04:54:59 PM Paul Davis wrote:
On Thu, May 12, 2016 at 1:22 PM, Tim E. Real
<termtech(a)rogers.com> wrote:
Ah, sorry for the noise, again. I'm an email dinosaur.
When I last tried metadata several months ago I didn't seem
to get any default pretty names. I was really worried...
So I just now built jack-1 and yes, pretty names are there in QJackCtl.
Tres cool !
Just to be clear, is it Jack which sets these default pretty strings?
Awesome, thanks Paul.
PS: Have you done anything with metadata tempo maps, in say Ardour?
Tim.
On Thursday, May 12, 2016 07:27:40 AM Paul Davis
wrote:
Apparently you're not on the jack-devel mailing list.
Port aliases were removed.
Port pretty-names have a standard URI, and have since before the metadata
API was implemented. Anyone can define metadata URIs (keys). A few are
standard, as is
Qjackctl supports all this already. Port aliases were almost never used for anything,
and the current build
of
qjackctl has support for them removed.
No!
If you are thinking of this, please don't remove alias support from Jack!
Or at least replace it with some default metadata containing similar
'friendly' port names, as I had requested some time ago.
6:43 p.m.
New subject: [Jack-Devel] Metadata
On Fri, May 13, 2016 at 6:59 PM, Tim E. Real <termtech(a)rogers.com> wrote:
On Friday, May 13, 2016 04:54:59 PM Paul Davis wrote:
When I last tried metadata several months ago I didn't seem
to get any default pretty names. I was really worried...
So I just now built jack-1 and yes, pretty names are there in QJackCtl.
there are no default pretty names.
Tres cool !
Just to be clear, is it Jack which sets these default pretty strings?
no, they have to be set by something that knows about the hardware. e.g. a
script that calls jack_property to set them.
Awesome, thanks Paul.
PS: Have you done anything with metadata tempo maps, in say Ardour?
I see no connection between the two concepts.
3069
days inactive
3071
days old
jackaudio@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Hanspeter Portner -
Paul Davis -
Pawel -
Tim E. Real