Forums
- Recent QjackCtl from Git -
When I set a pretty name, e.g. with
jack_property -p -s system:playback_3 http://jackaudio.org/metadata/pretty-name "Headphone L"
then Qtractor shows this name in the connections window but QjackCtl doesn't show it, neither in Graph nor in Connections.
re. Pretty names not displayed as expected...
confirmed
bummer... this one has been lurking in there for at least 3 years now...
maybe fixed in qjackctl >= v1.0.5.9git.c41ded but don't set off the fireworks just yet, this might summon some other old demons that are resting in there still ;)
thanks
Half way there (was: Pretty names not displayed as expected)
In the Connections window the pretty names are displayed fine.
To be displayed in the Graph window I have to disable and enable "Enable client/port aliases". But then QjackCtl wants to save them when I stop it which shouldn't happen because nothing changed.
EDIT:
When I start another jack client while QjackCtl is running then the Graph window is updated to show the pretty names.
re. Half way there...
all that's absolutely expected!
qjackctl actually integrates its native client/port name aliases, which predated by a long time the jack-metadata-pretty-names-whatever feature inception for a decade or so...
the said integration goes--or should go--like this: jack-metadata pretty-names will persist as native aliases as long qjackctl should be up and running; once saved there would be no need to you launch jack_property any long thereafter.
cheers
Eye candy only
I noticed that in Qtractor's qtr-files the original names are used, not the pretty names. So it can't be used to make qtr-files portable between computers with different audio interfaces and their routing.
I guess that's how it's designed.
This is interesting
Could this be applied to Qtractor for inserts audio/MIDI or controls MIDI with aliases?
If the pseudo-plugins have aliases, the "pretty name" appears in the Connections window.
I suppose a better approach would be to simply rename the port and re-establish the connections (as with buses).
I don't know if it's feasible, simple, or even worthwhile... but I always thought it would be useful for managing inserts.
re. This is interesting...
no.
these pretty-names business are dealt for the outside world, jack and ultimately qjackctl only.
the internal/original names for the qtractor's inserts send/return ports are not going to be affected by any of this--although it may be possible to show otherwise, even to outsiders, provided qjackctl is up and running, in qtractor they will obey and always be referred to the their original (port) names (and p-plugin aliases in titles if any).
seeya
Add new comment