Audacity Forum

If one doesn't mind cheating, there's also this variant ;nyquist plug-in ;version 1 ;type analyze ;name "1 Test For All" ;action "testing code" ;info "Nth Power of X" ;control x "Base X" real 7 0.001 1000 ;control n "Exponent N" real 7 0.001 1000 (Format nil "~a raised by ~a gives ~a" x n (expt x n)...

I haven't tested if a glitch appears in my version, it is very well possible. It is seldom a good choice to use the ramp function since it is calculated at the control-srate. It appends therefore a tail of 20 samples that gradualy dive down to 0. Snd-pwl is more precise when the rate is the *sound-s...

Or the shortcut: (setq test (peak s ny:all)) (format (= test 0) "~a~%" test) Ok, we see that it is no problem to stop the execution by any test imagineable. The bad thing is that we always have the standard error message, which can't be altered - not even temporaily. However, there's a silver streak...

It seems that the basic function is for all the same. If I take the code from the current crossfade-out and adapt it for a flexible Fade-in version, then this is what I get: (setf exponent 9); positive values above 0 (setf mid-point (linear-to-db (exp (* exponent (log 0.5))))) (format t "Volume at t...

I hope others will find the tool menu equal convenient as we do. Incidentely, there already some circumstances when Nyquist calls a plug-in only once. It is precisely then, when nothing (nil) is returned. You can test it by creating several tracks and then enter (Nyq-prompt): (print (random 100)) Th...

It certainly makes sense to collect those items in a tool menu that are currently kicking about in other menus. The help menu could be cleaned out down to 3 entries. Screenshot, Protocol and Audio Info are somehow in the wrong place there. Experimental features could also be listed under the tool me...

This decision should remain with the plug-in developer. To a large extent this decision will be with the person that programs the feature into Audacity. I mean that the decision if a passed sound from Audacity to Nyquist is used, is left by the plug-in writer. The programmer gets no head aches when...

That's interesting.
If I understand rightly, waxcylinder prefers a cubic curve (x raised by 3) which is therefore exponentially increasing.
I wonder if Edgar means a similar curve or if the curve is in fact the opposite i.e. truly logarithmic.

I'm a bit cautious about loading too many "features" on what a "tools" type Audacity plug-in should be. I would argue that the simple classification would be that: If the plug-in returns audio that is derived from one or more existing audio tracks, (ie. the audio is processed and returned to Audaci...

It's rather a difficult task to blend the two tracks. The transition is fairly long (6 s?) and the beats do not fit very well. However, Ive tried my Chain-it-up plug-in and had good results at a transition time of about two s and a double S crossfade. Also linear and cosine crossfades returned satis...