Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inconsistencies with jack1 meta-data #404

Closed
falkTX opened this issue Dec 24, 2018 · 2 comments · Fixed by #502
Closed

inconsistencies with jack1 meta-data #404

falkTX opened this issue Dec 24, 2018 · 2 comments · Fixed by #502
Labels
inconsistency A name, value, convention etc. which is used differently in ambiguous ways
Milestone

Comments

@falkTX
Copy link
Member

falkTX commented Dec 24, 2018

I can confirm now two things, maybe you want to write them down yourself this time: Jack1 cleans metadata automatically when a client closes. jack2 does not. I think that is good behaviour and in fact jack1 came first so jack2 should behave the same
and second: QJackCtl graph view updates automatically if I change pretty names or track order in jack1 but not in jack2. That maybe qjackctl but more likely it is jack2

@7890 7890 added the inconsistency A name, value, convention etc. which is used differently in ambiguous ways label Jan 20, 2019
@7890 7890 added this to the v1.9.13 milestone Feb 9, 2019
@falkTX
Copy link
Member Author

falkTX commented Mar 22, 2019

First issue is solved, jack2 now cleans up client properties.
2nd issue likely just needs notification callback to be sent whenever properties change.

@falkTX
Copy link
Member Author

falkTX commented Sep 1, 2019

First issue is solved, jack2 now cleans up client properties.

confirmed this is still an issue after all. I was testing with carla that cleans up the properties it registers.
but I have a simple way to reproduce the issue now, so this will be fixed soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inconsistency A name, value, convention etc. which is used differently in ambiguous ways
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants