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

Mod-ui should visually update to reflect connections broken or made using Catia or QJackCtl #115

Open
ericfont opened this issue Jan 25, 2021 · 3 comments

Comments

@ericfont
Copy link

If I break or make a connection between plugins or the input or output from inside mod-ui, then I nicely see that connection break or made immediately both inside mod-ui and as well as in inside a Catia and QJackCtl. However, the reverse does not happen... When breaking or making a connection from inside Catia or QJackCtl, then the mod-ui doesn't visually update to reflect the change (even though the change does affect the actual audio processing). Mod-ui also doesn't update upon refreshing the browser page.

So it seems updates are only visually processed from mod-ui to the rest of the jack ecosystem. But should also process in the other direction...updates made using another jack program other than mod-ui which affect the connection of plugins in mod-ui should result in mod-ui updating the wiring.

I am on latest arch-linux 5.10.10 running latest mod-ui master (commit d450d16) and latest mod-host master (commit mod-audio/mod-host@74cf4b8).

@ericfont
Copy link
Author

I guess this would require using jack api's set_port_registration_callback() and set_port_connect_callback() to receive the updates?

@falkTX
Copy link
Member

falkTX commented Jan 25, 2021

Should be possible to do yes, but it is not something the MOD team ever needed, as mod-ui is the highest-level of an application used on the platform.
PRs welcome :)

@ericfont
Copy link
Author

ok, I'll take a stab at it now while I'm thinking about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants