Re: [Audacity-manual] TLC for Nyquist

[Peter S. <pet...@gm...>]

On Wed, Jan 30, 2019 at 1:21 PM Steve the Fiddle <ste...@gm...>
wrote:

> Off the top of my head, the "Plug-in Manager" could do with a lot of
> improvement. Currently it does what it was designed to do, but it is not
> user friendly,
>

For my money the most user-unfriendly part of it is having to remember to
click the OK
as well as the Enable.

The fact that it gets moved to the Enabled list rather than staying in the
New list, or shows
as Enabled in the All list, implies to users (and I know from Forum posts
that it's not just me)
that it *is* enabled - but that does not stick until you click the OK.  If
you exit the dialog via
the top-right "X" - you lose the enabling ...



> and lacks several useful features.
>

> Some features that would particularly benefit Nyquist:
>
> * Filter plug-ins by type.
> So that you can list only Nyquist plug-ins, or only VST plug-ins...
>

+1 to this idea

Peter.



> * Parse the names of new Nyquist plug-ins.
> If we are concerned about the speed of the manager scanning plug-ins, then
> this could be limited to when the manager filters by type.
> Currently, a new (not yet installed) plug-in, is listed as something like:
> trybeforeyoubuy /home/steve/.audacity-data/Plug-Ins/trybeforeyoubuy.ny
> Whereas after it has been installed, it will show the "name" of the
> plug-in. User's seem to expect to see the name of the *plug-in* rather
> than the name of the *file*.
>
> * Option to install a Nyquist plug-in from an arbitrary location.
> We may not be able to do this for all plug-in types (some plug-ins require
> running an installer), but we can certainly do it for Nyquist plug-ins.
> For example, if you have a /ny file on your Desktop, select "Install
> Nyquist Plug-in", and a file browser window opens. Browse to the .ny file
> and select it. Click the "Install" button, and the file is copied to the
> default plug-ins folder and enabled. A message is returned saying (for
> example):
>
> Plug-ins installed to "/home/steve/.audacity-files/" :
> ACX Check
> RMS Normalize
> Advanced Echo
>
> * A common problem for Mac users when downloading Nyquist plug-ins, is
> that their computer adds ".txt" to the file name.
> A plug-in installer could look for file names ending in ".ny.txt" and
> offer to fix them.
>
> * The Plug-in Manager should remember it's window size. On Linux it
> currently opens showing only the first 6 plug-ins.
>
> Steve
>
>
> On Wed, 30 Jan 2019 at 11:41, Peter Sampson <
> pet...@gm...> wrote:
>
>>
>>
>> On Wed, Jan 30, 2019 at 8:36 AM James Crook <cr...@in...> wrote:
>>
>>> I've been thinking recently about how Nyquist fits into Audacity and our
>>> documentation.  I think Nyquist in Audacity would benefit from some
>>> TLC.  Nyquist has recently become more important, more able to do things
>>> actually in Audacity with the addition of the tools menu and the
>>> extensions that aud-do have brought.
>>>
>>
>> Steve has been giving the Nyquist documentation a fair bit if TLC
>> recently.
>>
>> Most of this work is in the Wiki - but we have also worked on tidying the
>> 2.2.1 alpha
>> manual.
>>
>>
>> Aside: I thought we agreed we were dropping this manual mailing list in
>> favor of
>> just using quality (as we are so few in number).
>>
>> Peter.
>>
>>>
>>> What kinds of thing should happen next?  Not just new documentation, but
>>> also usability features that reduce the need to explain step-by-step -
>>> because the user interface becomes more intuitive.
>>>
>>> I'd like it to in time become much more mainstream for people to extend
>>> Audacity by adding Nyquist tools to the menu.  What needs to happen, and
>>> how should we see the priorities for that to be so?
>>>
>>> --James.
>>>
>>>
>>>
>>> _______________________________________________
>>> Audacity-manual mailing list
>>> Aud...@li...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-manual
>>>
>>