On September 5, 2012 2:23:42 PM Florian Jung wrote:
> Am 05.09.2012 08:48, schrieb Tim E. Real:
> > On September 2, 2012 8:39:53 PM Florian Jung wrote:
> >> Am 28.08.2012 22:01, schrieb Robert Jonsson:
> >>> 2012/8/27 Florian Jung <florian.a.jung@...>:
> >>>> i'd like to work on that feature.
> >>>> just tell me, which places are affected? is it only that single "select
> >>>> plugin" window which opens when double-clicking an entry in the effects
> >>>> rack?
> >>>> or is there more?
> >>> Hmmm. Thinking.
> >>> I think that is the only place where it would make sense. Solving it
> >>> with tabs sounds ok to me.
> >>> Regards,
> >>> Robert
> >> done.
> >> in the plugin select menu, there's a tab bar with by default only the
> >> "all" tab. right-click there and you will be able to create new tabs.
> >> right-click on plugins and check/uncheck the groups you want them to
> >> appear in.
> >> hope this is what you wanted, geoff
> >> greetings,
> >> flo
> > I now have no plugins listed at all.
> > I know they are there because a previous build shows them.
> > Can you take a look? ...
> > Wait... I just now read your above instructions.
> > I will try again later, it's on my Lubuntu partition.
> > Still, shouldn't 'all' tab show them all by default at first?
> definitely, and i can't think of any bug which might cause that behaviour.
> you btw can't make "all" not display everything.
> maybe you're starting muse with one of -apIL?
Aha! Apologies yes false alarm, was starting with -p.
You know how the other apps are able to sort ladspa plugins into categories
and retrieve important metadata such as the various texts for enumerated
controls? They use LRDF.
Some day we should add it, but it's a bit of a kludge, a sort of workaraound
for the lack of info in ladspa plugins, it is a database that relies on
current information which might not always be correct.
I think LV2 may use LRDF or a successor or something like that...
Anyway, anything to help sort this very long list of plugins helps.
> if not, try adding breakpoints or debugging statements in fillPlugs() in
> it shall be executed when the dialog is opened, and on every tab change.
> > Thanks!
> > Tim.