Audacity Forum

Very interesting. I tried the first example [with (result (sum t3 t2 t1))] in Nyquist, To be clear, my example doesn't actually contain the misbehaving code all in one piece. For me the necessary conditions include (sum t3 t2 t1) and also (t1 (shift-time s1 0.1)) (t2 (shift-time s2 0.2)) (t3 (shift...

And by the way, Steve, thank you for bringing the other strange edge cases I found, of hangs or crashes in Audacity, to the developers' attention. These reactions to stupid inputs I don't mean to produce don't affect me as much as this perplexity with snd-xform and sum, but it is good to know the pr...

If you will bear with one more example. Here is your fifth code example. (let ((sound s) (sr *sound-srate*) (time 2) (start 0) (stop 5) (scale 1)) (sum (s-rest 0.4) (snd-xform sound sr time start stop scale))) What I get is two seconds of silence and ten seconds of sound, but I think there should be...

but this will not work! We want snd-xform to set the start and stop time of "sound", but we are overriding it with (SIM (AT-ABS (CUE .... so snd-xform does not get evaluated. I can get the entire definition of at-abs and cue in my Nyquist prompt. at-abs is only a Lisp macro that changes *WARP* whil...

I agree that sim is another name for sum. I agree that your fifth example is the first one that surprises me. I do not agree that what you then link to explains the behavior. In that example the "surprising" but explicable behavior involves seq, not sim. The "surprise" was that the actual start of o...

I see that cue calls cue-sound which uses *START* and *STOP* which default to minus and plus 10^21. Extract does not use them. shift-time uses different variables called MIN-START-TIME and MIN-STOP-TIME (no stars in names) as infinities to pass into snd-xform. They have the same default values as *S...

You have not persuaded me that there is a sensible user model justifying all of this observed behavior. Explain why wrapping terms in (sum 0 ...) fixes the "bug" but (prod 1 ... ) does not. I do not see a coherent user model here. I find the global variables and environments and the local/global tim...

I tried transforming my t1, t2, t3, with (sum 0 ...) and that does fix the "bug." But (prod 1 ...) does not fix the "bug." Justify that behavior.

Can we drop the quotation marks from "bug" please?

You are not trying to tell me this bug is not a bug? I found an example where the sound returned by sum depends on the sequence of the summands. If I am encouraged to think about sound objects in mostly "functional programming" terms (so long as I don't use snd-fetch, snd-fetch-array, or snd-fft), t...

Here's an easy Nyquist prompt experiment. It reveals that the bug depends not only on how my extracted sounds are defined and transformed, but also, THE SEQUENCE IN WHICH THEY ARE THEN PASSED TO sum. First make a sine wave of 100 Hz, 1 second duration, 0.25 amplitude, and view it as Waveform. Select...