LMMS needs default guis

[Reaper10]

LMMS needs default guis beause I have plugins with a lot of controls but there is no way to get to them.
Ie when I load the in a fx box there is controls button to click on.

[tresf]

Please retitle, reword, provide an example as well as steps to reproduce and reopen. We've warned you about the quality of these bug reports several times before.

[unfa]

LMMS provides GUI for LADSPA plugins. And there is a button to access them.
Could you drop in a screenshot?
28 sty 2015 18:01 "Reaper10" notifications@github.com napisał(a):

LMMS needs default guis beause I have plugins with a lot of controls but
there is no way to get to them.
Ie when I load the in a fx box there is controls button to click on.

—
Reply to this email directly or view it on GitHub
#1713.

[badosu]

A valid issue though is that our LADSPA interface do not describe very well what some controls are.

Example. on CALF Vintage Delay you can select the mix type, this is the LV2 interface:

The LADSPA interface on LMMS:

What's mix type 1? And 2, 3, 4?

I don't know if LADSPA exposes this information, and we should refer to this in another issue, was just commenting that always bothered me...

[tresf]

I don't know if LADSPA exposes this information, and we should refer to this in another issue, was just commenting that always bothered me...

IIRC LADSPA has no GUI interface available. If that is what the OP is describing then this is a duplicate of #562.

[tresf]

That said, I agree we can automagically interpolate some better GUI components for LADSPA.

[badosu]

@tresf

IIRC LADSPA has no GUI interface available.

I am aware of that, what I am saying is exposing that the value 1 for the mixer type has the label "Ping-Pong" on our interface. If LADSPA enables this, we should totally do it.

[Reaper10]

oh sorry they are vst plugngs

[tresf]

oh sorry they are vst plugngs

Oh sorry your bug report is closed until you fix it. 🍺

If LADSPA enables this, we should totally do it.

Hmm... The Calf plugins have them defined the metada code, but I've no idea how to programatically cherry-pick them or if this is even normal LADSPA API . plugins/LadspaEffect/calf/src/metadata.cpp#L145

Some googling shows that RDF files are the desired approach, which some of our LADSPA plugins do have bundled. Shall we file an enhancement for an LADSPA RDF parsing/GUI support?

[badosu]

@tresf

Hmm... The Calf plugins have them defined the metada code, but I've no idea how to programatically cherry-pick them or if this is even normal LADSPA API . plugins/LadspaEffect/calf/src/metadata.cpp#L145

Great find!

Some googling shows that RDF files are the desired approach, which some of our LADSPA plugins do have bundled. Shall we file an enhancement for an LADSPA RDF parsing/GUI support?

Totally! Imagine two producers collaborating:

• So, I love vintage delay, I use it on Ardour all the time
• Yeah me, too, I use it on LMMS via LADSPA
• Cool! I just love it's Ping-Pong mode running as a Tape! Which mode do you use?
• Huh? Type 1 with Medium 2?

If we could fix this, it would be amazing!

[tresf]

Great. We should crawl Ardour code to see if we can steal some of their code. From what I can see, they are GPL2 just like us.

I'll file the enhancement now. In terms of the Calf stuff, we may have to write our own RDFs for them to display properly, but a few XML files would probably be worth it.

[badosu]

@tresf They have LADSPA support as far as I know, but if we already know where the information is, I don't think we need to take a look at their code.

[tresf]

I don't think we need to take a look at their code.

Yeah, its not helping much lol. I've created a new bug report... #1717

[badosu]

@tresf Sorry :-). Thanks for the research, really nice work! I was reading http://www.ladspa.org/ladspa_sdk/ladspa.h.txt instead, I guess your approach was better.