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

lv2: A6 workaround, single output atom port #924

Merged
merged 1 commit into from
Jun 22, 2021

Conversation

jpcima
Copy link
Collaborator

@jpcima jpcima commented Jun 22, 2021

Previously, some patch:Set messages were directed to a distinct atom
port, when it was for notification purposes rather than automation.

Ardour does not support this, and the ports get assigned the same
buffer, producing corruption.

This commit returns to single-port behavior, and instead replaces
patch:Set notification messages with sfizz:Notify custom objects;
the UI processes these messages all the same, and they does not trigger
automation in the host.

Previously, some `patch:Set` messages were directed to a distinct atom
port, when it was for notification purposes rather than automation.

Ardour does not support this, and the ports get assigned the same
buffer, producing corruption.

This commit returns to single-port behavior, and instead replaces
`patch:Set` notification messages with `sfizz:Notify` custom objects;
the UI processes these messages all the same, and they does not trigger
automation in the host.
@jpcima jpcima merged commit 42ac729 into sfztools:develop Jun 22, 2021
@jpcima jpcima deleted the lv2-ardour branch June 22, 2021 15:29
@paulfd
Copy link
Member

paulfd commented Jun 23, 2021

Should we change the LV2 version number given that the ports have changed?

@jpcima
Copy link
Collaborator Author

jpcima commented Jun 23, 2021

Should we change the LV2 version number given that the ports have changed?

Yes, do you prefer now or before a release?

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

Successfully merging this pull request may close these issues.

2 participants