Nyquist Wish List

Using Nyquist scripts in Audacity.
Post and download new plug-ins.

If you require help using Audacity, please post on the forum board relevant to your operating system:
Windows
Mac OS X
GNU/Linux and Unix-like

Re: Nyquist Wish List

Permanent link to this post Posted by pshute » Fri May 04, 2012 6:19 pm

How about a line control? E.g.
Code: Select all
;control line


All it does is draw a horizontal line across the window at that point. It would be useful for grouping related controls.

Resizable choice controls would allow for better descriptions of the choices.
pshute
 
Posts: 141
Joined: Sat Feb 18, 2012 9:39 am
Operating System: Please select

Re: Nyquist Wish List

Permanent link to this post Posted by steve » Fri May 04, 2012 6:23 pm

pshute wrote:How about a line control? E.g.
Code: Select all
;control line


I'm not sure that it would be appropriate to use the command ";control", but an option to add a line as an interface element, yes +1.

pshute wrote:Resizable choice controls would allow for better descriptions of the choices.

Agreed.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
steve
Site Admin
 
Posts: 44458
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Group Controls into sections.

Permanent link to this post Posted by Gale Andrews » Fri May 18, 2012 5:07 am

In longer plug-ins it would aid understanding and reduce the "intimidatory" effect if controls could be logically grouped into "panels" like the "static boxes" in built-in effects.



Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual
Gale Andrews
Quality Assurance
 
Posts: 26093
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Change the selection range [Re: Nyquist Wish List]

Permanent link to this post Posted by Paul L » Wed Mar 20, 2013 7:00 pm

Hi, newbie here who hasn't written any Nyquist yet but has a few ideas for my peculiar work editing narration.

I understand you can add to Generate, Analyze, and Effect menus.

My idea might require a fourth category, perhaps called Find, so it's radical.

To wit: allow Find scripts to run even with zero-length selections; allow inspection of samples beyond the boundaries of the selection; return some values to indicate a modified range of selection.

Thus, for instance, allow a Nyquist implementation of the Find Zero Crossings command under Edit. Allow us to invent other routines that finely adjust selection boundaries based on other criteria.

I'm not sure what these commands should mean in case of multiple track selections. But for that matter, what does Find Zero Crossings mean in that case?
Paul L
 
Posts: 863
Joined: Mon Mar 11, 2013 7:37 pm
Operating System: Please select

Re: Nyquist Wish List

Permanent link to this post Posted by steve » Wed Mar 20, 2013 7:30 pm

Thanks for the suggestions Paul.

Paul L wrote:My idea might require a fourth category, perhaps called Find, so it's radical.

There has previously been a suggestion of a "Tools" or "Utilities" menu (and in fact there was once a "Tools" menu in an old beta version of Audacity, but it was abandoned because at that time there was only one item in that menu). Would a "Tools" or "Utilities" menu be suitable for what you have in mind?


Paul L wrote:allow inspection of samples beyond the boundaries of the selection

That may not be possible (probably isn't possible) as it goes beyond the scope of the core plug-in support structure. In order to be able to operate on audio data, that data needs to be passed to the plug-in code. We usually don't want to pass "all" of the audio data in the project as that could be many hours of data in each channel, so we just pass the relevant part of the data - the "relevant part" is defined as "the selection". In order to have access to the full track, Nyquist would probably need to move from being a plug-in scripting language to being integrated into a "module", which would probably be quite a major undertaking and probably not compatible with current Nyquist plug-ins.


Paul L wrote:return some values to indicate a modified range of selection

Nyquist plug-ins currently have no concept of "real" (Audacity track) time. As far as a plug-in is concerned, the start of time is the beginning of the selection.
I agree that it would be a useful enhancement if Nyquist had access to the track time of the selection, which could then perhaps open up the possibility for Nyquist to redefine the selection region for the returned audio.


Paul L wrote:But for that matter, what does Find Zero Crossings mean in that case?

:D Not much. When there are multiple tracks (or channels) selected, "Find Zero Crossings" does not really work unless all of the selected tracks/channels happen to have zero crossing points in the same place.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
steve
Site Admin
 
Posts: 44458
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Nyquist Wish List

Permanent link to this post Posted by Paul L » Wed Mar 20, 2013 8:00 pm

Perhaps my idea is too radical then.

Or perhaps, if there was some arbitrary, hard limit, or Preference, for the amount of lookahead and lookbehind, it would be an acceptable compromise. Pass the selection, plus two seconds max (say) of context on each side, to the routine, just as now you can supply an Effect or Analyzer with a range. Some new global variable tells you where start and end of the selection are relative to the start of the range. (That may vary because you bump against the clip or track boundary.) The routine might communicate back the new start and end of selection, relative to the start of the larger range, in samples. I think that's how an Analyzer specifies labels?

An overgeneral ability to snoop minutes and hours of track data goes beyond what I want.
Paul L
 
Posts: 863
Joined: Mon Mar 11, 2013 7:37 pm
Operating System: Please select

Re: Nyquist Wish List

Permanent link to this post Posted by Paul L » Wed Mar 20, 2013 8:14 pm

As for "Tools" or "Utilities," I'm not particular what you call it, but I understand a Nyquist script includes a comment classifying it and determining the expected protocol of call and return. My idea requires a new kind of return.

Whatever menu it goes to, I want my new command to be bindable to a keystroke in Preferences.
Paul L
 
Posts: 863
Joined: Mon Mar 11, 2013 7:37 pm
Operating System: Please select

Re: Nyquist Wish List

Permanent link to this post Posted by steve » Wed Mar 20, 2013 8:30 pm

Paul L wrote:Or perhaps, if there was some arbitrary, hard limit, or Preference, for the amount of lookahead and lookbehind, it would be an acceptable compromise.
Any reason to not just make the selection a bit bigger?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
steve
Site Admin
 
Posts: 44458
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Nyquist Wish List

Permanent link to this post Posted by Paul L » Wed Mar 20, 2013 9:39 pm

steve wrote: Any reason to not just make the selection a bit bigger?


Yes, the precise endpoints of the selection are important data. I want that and some amount of context for calculations. I can't select an exact second before and behind it quickly by hand. I could in principle do mental math and use the number inputs in the selection toolbar, but that's hardly a convenience.

For instance, this is one idea I've had. When I edit narration, often the pauses between sentences need to be tightened. It's a judgment call. I'd like to playback and stop exactly where I want the pause to end. (Stop and set cursor bound to a key, no problem.) Then trim the pause. I wanted to experiment with something that could deduce "end of pause after this point" as crossing some sound threshold, thus figuring the length to delete, then calculate the selection to be deleted, which might not begin at the selection but earlier to preserve the breath and on-glides of the next word. I'd enjoy the exercise of figuring this out for myself in Nyquist, if I just had the means. Then my whole operation could be four neat keystrokes: play, stop and set cursor, calculate the new selection, delete it.

A "find zero crossings" implemented in Nyquist would be another example of a useful thing, except of course it's redundant. Except sometimes I wish I had one that worked with falling crossings instead of rising.
Paul L
 
Posts: 863
Joined: Mon Mar 11, 2013 7:37 pm
Operating System: Please select

Re: Nyquist Wish List

Permanent link to this post Posted by Robert J. H. » Wed Mar 20, 2013 9:45 pm

steve wrote:
Paul L wrote:Or perhaps, if there was some arbitrary, hard limit, or Preference, for the amount of lookahead and lookbehind, it would be an acceptable compromise.
Any reason to not just make the selection a bit bigger?


I see Paul's point.
Imagine you pick a vocal part within a single tune. You want to add a reverb that is only applied to the vocals, i.e. the selection.
In order to prevent the reverb from being cut off, you need the sound that comes after the selection to mix the decaying part smoothly into the tune.
The same holds true for such things like a reversed cymbal fade-in, where the original sound is selected and should stay at the same position.
We normally can circumvent these problems by multi-track editing. It is easy for the first case whereas the second case needs quite some fiddling to align the beats properly.
Robert J. H.
 
Posts: 1813
Joined: Thu May 31, 2012 8:33 am
Operating System: Windows 7

PreviousNext

Return to Nyquist



Who is online

Users browsing this forum: No registered users and 2 guests