Audacity Forum

yes, indeed, I had some Ideas which looked pretty promising at first glance. I've been pondering about an effect that should work as follows. no controls, one click only. During execution, the applied fade type is announced (Speech). successive pressing of the shortcut key (or the effect entry) with...

It gives me some relief that XLISP itself sometimes looses track of the parenthesises... ()"oops"+() How weird :grin: Any idea why it alternates? That's really hard to tell. It has something to do with the stacking of the different commands. You know, something is evaluated, an error detected, the ...

As Steve wrote somewhere before, it's pretty easy to achieve the different types with the oneclick solution (except Scurve). Firstly, the effect had to be made with the equal power curve. That means the square root of a linear ramp. This produces a curve that is shaped upwards. The linear value in t...

It gives me some relief that XLISP itself sometimes looses track of the parenthesises... ()"oops"+() Here, XLISP can't decide if there's a parenthesis too much or one missing... By the by, there's a method to count the tracks without the employment of *scratch* (For plug-ins prior to Audacity 1.3.1x...

I haven't thrown a glance recently at the source code. In any case, a variable can be sent to Nyquist wither by taking the loop max directly or by firstly sieving out the wrong track types. The fact that label tracks are greyed out doesn't say too much, this could be done in a total different module...

I wonder if not *scratch* itself could be used to hold the current number of selected tracks. Firstly, it hasn't assigned a value yet, secondly, as we have seen, it is preferable to use properties on *scratch* to ensure individual use by different plug-ins (and the symbol-value is therefore still ni...

Ok, it's fine when you used it on purpose. It's a nice option to be able to "ignore" tracks if it is not the last one. We could of course place our own "end-of-tracks" signal manually. Something like snd-from-array 0 44100 (vector 1.2345e-20)) from the prompt. For your code, we would simply remove a...

@Steve For your cross-split plug-in, I suggest that you change the last two lines to (t (format nil "nil~%") (sum s))) There won't appear any annoying messages anymore. However, if the code encounters at any time a new non-silent track, it starts the process again and tries to split up the sound. Pe...

Two features that I think it would be very useful to have: A symbol, which like *scratch* survives from one track to the next, but unlike *scratch* does not survive beyond one run of the plug-in. This would provide a simple test from which the track number could be counted. For Nyquist to be aware ...

Nice code, May come in handy at some time. A few remarks. *scratch* is a pipe between different plug-in calls. But it gets narrow as a bottle neck if different plug-ins make use of it. Therefore, we would normally assign the sound to a property of *scratch* rather than its symbol-value. Something li...