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 plugin support #8402

Closed
mixxxbot opened this issue Aug 22, 2022 · 7 comments
Closed

LV2 plugin support #8402

mixxxbot opened this issue Aug 22, 2022 · 7 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: wolftune
Date: 2015-12-31T00:34:22Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp1530238
Tags: wishlist


LV2 plugin support has none of the legal problems as AU or VST, it would greatly enhance the effects options.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-12-31T00:45:07Z


Thanks Aaron -- we actually already have a proof of concept for LV2 support :). I could have sworn we already had a bug report open but it seems we don't. Regardless, this is indeed on our radar!

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-12-31T00:45:35Z


I believe the latest code for LV2 support is here:
https://github.com/daschuer/mixxx/tree/lv2_support2

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-11-12T21:17:15Z


This is in progress but stalled: #1240

There is quite a bit of work that needs to be done on the effects system before LV2 effects are practically usable. See also:
https://bugs.launchpad.net/mixxx/+bug/1653325
https://bugs.launchpad.net/mixxx/+bug/1653140

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2017-12-28T09:18:29Z


My plan was to have it in 2.2.
It is already usable as it is. If we do not merge this soon, it will start to rott even more, which is unfair to the original developer who has build a working solution.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-12-28T15:11:30Z


I already have enough (and maybe more than enough) plans for myself for 2.2. Are you planning to do it for 2.2? If not, then let's not keep it on the 2.2 milestone. Even still, I think doing this for 2.2 would likely be rushing it. I suspect there will be complicated issues that arise when interfacing with external software plugins that we have not thought about yet. I'd like to avoid burning out our small team of volunteer developers, so I think it would be wise to lay the prerequisite groundwork for usable implementations of external plugin support in 2.2 then deal with the details of implementing the external plugin support in 2.3. Perhaps we can revisit this discussion half way through the new feature development time for 2.2 when 2.1 final is released.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2017-12-28T16:16:07Z


Since it is almost ready, it should be doable for 2.1.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.2.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant