Nyquist Suggestions

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

Nyquist Suggestions

Permanent link to this post Posted by dondiego929 » Fri Jun 04, 2010 12:10 am

<<deleted by user>>
Last edited by dondiego929 on Mon Sep 13, 2010 2:16 am, edited 1 time in total.
dondiego929
 
Posts: 54
Joined: Mon May 17, 2010 4:40 am
Operating System: Please select

Re: Nyquist Suggestions

Permanent link to this post Posted by dondiego929 » Fri Jun 04, 2010 6:36 pm

<<deleted by user>>
Last edited by dondiego929 on Mon Sep 13, 2010 2:17 am, edited 1 time in total.
dondiego929
 
Posts: 54
Joined: Mon May 17, 2010 4:40 am
Operating System: Please select

Re: Nyquist Suggestions

Permanent link to this post Posted by steve » Sun Jun 06, 2010 11:38 am

dondiego929 wrote:01. I'd like to see more FOCUS on the timeline as a whole. You know, treat a whole track as a SINGLE waveform, instead of just focusing on S.

Possibly not as simple as it might appear.

In the simple case of just one waveform in the track, you can simply select the entire track from time=zero, then everything will be referenced to the start of the track as you would like.

For many processes, such as apply a filter, the user just wants to apply the effect to the selected audio and return the result to the same place in the track. If Nyquist referenced everything to the Audacity time-line, would it then be necessary to specify the start position? If a selection was made from 3 minutes to 3 minutes and 5 seconds, would Nyquist need to process everything from time=zero?

What about time stretching effects? If for example, the output is stretched to double length, should the start time also be doubled, or remain at the original position of the start of the selection?

In more complex cases where there are multiple audio clips (a feature available in Audacity 1.3.12 but not in 1.2.6) I'm unsure how it could/should work. Would each clip be processed individually with t=offset, or would the whole track be treated as a single waveform with an origin at time=zero on the time line?

Should clip boundaries be honoured? What should happen if the result of the process is longer than the original audio? Should audio beyond the selection be overwritten, mixed with the new audio, or moved later along the time-line?

dondiego929 wrote:02. Less OOP, more SND. I'm sorry, but people don't DIG OOP languages.

Oop is supported in Nyquist, but you don't have to use it. I'm only aware of one publicly available plug-in that uses oop. The developers have used oop in the lisp source files for whatever reasons, but that does not really affect users or plug-in developers except for delving into the lisp code to try and work out how and why certain functions behave as they do. For creating plug-ins that will be compatible on other peoples Audacity installations, the code in the nyquist folder should not be modified - Nyquist plug-in code should only be as .ny files in the plug-ins folder.

dondiego929 wrote:I like making modules that link together rather than whole pages of code as it helps with the line numbering and logical construction of code. I've no idea how this could be implemented for plugin use with Audacity, but maybe you guys could come up with something.

Have you looked at defining functions?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
steve
Site Admin
 
Posts: 45650
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu


Return to Nyquist



Who is online

Users browsing this forum: No registered users and 1 guest