LV2 plugin support

Bug #1530238 reported by Aaron Wolf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Wishlist
Daniel Schürmann

Bug Description

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

Tags: wishlist
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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!

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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

Revision history for this message
Be (be.ing) wrote :

This is in progress but stalled: https://github.com/mixxxdj/mixxx/pull/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

Changed in mixxx:
status: Confirmed → In Progress
Be (be.ing)
Changed in mixxx:
milestone: none → 2.3.0
Revision history for this message
Daniel Schürmann (daschuer) wrote :

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.

Changed in mixxx:
milestone: 2.3.0 → 2.2.0
Revision history for this message
Be (be.ing) wrote :

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.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

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

Changed in mixxx:
assignee: nobody → Daniel Schürmann (daschuer)
Be (be.ing)
Changed in mixxx:
milestone: 2.2.0 → 2.3.0
Be (be.ing)
Changed in mixxx:
milestone: 2.3.0 → 2.2.0
Be (be.ing)
Changed in mixxx:
status: In Progress → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8402

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.