Talk:Nyquist Audio Programming

From Audacity Wiki
Revision as of 18:27, 13 February 2008 by Galeandrews (talk | contribs) (answers)
Jump to: navigation, search

Edgar: The link confusion was on these pages page was probaly started by me myself. There had been in the beginning a few more links on the "Nyquist Prompt" page, which then seemed to me as too many, so I started to reduce them to a reasonable number by probably deleting the wrong parts so everything was messed up in the end. Sorry for the confusion.

What is really important to know: In Nyquist 3.0 the language notation in Nyquist has changed from Lisp, like used in Audacity, to SAL, like used in "Common Music" by Rick Taube. Also the Nyquist manual on the CMU homepage the notation of all example code has changed to SAL, so it cannot be used for Audacity any longer, at least as SAL is not integrated with Nyquist in Audacity (what probably still will need another year if not longer).

So there are TWO DIFFERENT links:

http://www.cs.cmu.edu/~music/music.software.html  - the Link to the Nyquist homepage. I think this should be left as-is because Nyquist users should be given the information, that beside Nyquist in Audacity, there also exists a Nyquist stand-alone version.

http://www.cs.cmu.edu/~rbd/doc/nyquist/root.html  - the link to the Nyquist 3.0 manual with the incompatible SAL notation.
This link should be changed to http://www.audacity-forum.de/download/edgar/nyquist/nyquist-doc/manual/home.html  at least until the SAL question is clearified.

Then I will make some appropriate change to the Audacity SF Nyquist page . As for this Wiki page, I still think it is a mistake to link to the Nyquist homepage without explanation, and I still think people could go there and get the v3 Manual without realising the problem. I think your first paragraph on this page should explain the difference between the Nyquist 2.36 that Audacity can use and the current v3, but that there is nothing to stop someone using the current v3 in its own environment. I would not fully understand this from your page if I did not know it already.




Edgar: I'm sorry but I can't read neither the pink nor the orange text of the below

(if (arrayp s)         ; IF s is an array [= stereo]

The problem is, that there probably will be no other solution but plain white or plain black if you want to use colored text. The reason is that CRT and LCD/TFT monitors have different gamma values ('middle' grey on CRT is darker than on LCD/TFT) and the reason why I use blue comments (which, I agree, can be easily confused with hyperlinks) is that beside dark red and dark blue there is no other color that can be read with light grey background on CRT as well as LCD/TFT by all people without problems. In other words: I do not even like my own color choice (blue comments) but I don't know any other solution. Sorry, but I have no better ideas on store...

I am really not keen on a single mix of (1) black with (2) either blue or red. Maybe if it is multi-coloured code (green, red, blue, orange and black or similar) where it is obvious the blue and red cannot be links, it is OK. Also the grey background in code template does not have to be so dark - it could even be white or nearly so. Are these dark violet and dark brown colours any better:?

(if (arrayp s)         ; IF s is an array [= stereo]
    (stereo-function)  ; THEN use the stereo function
  (mono-function))     ; ELSE use the mono function

Otherwise I think you must stay with black and change the comments to italic:

(if (arrayp s)          ; IF s is an array [= stereo]
    (stereo-function)  ; THEN use the stereo function


Gale