How would it be possible to create a series of tones from a string of text using a Nyquist plugin? It seems like it should be simple to do but I can not figure out how. What I am trying to make is the following:
For instance, if I entered 18B2, I would get 274.033 Hz, 410.585 Hz, 488.271 Hz and 290.328 Hz in that order and I would be able to save as a sound file. I’d like to be able to input volume, length of each tone and (of course) the string. My purpose for this is to create music from the digits of the mathematical constant π in base 12.
You could try dissecting David Sky’s Morse code generator plug-in, (copy attached in zip file).
As it converts a string of characters (alphanumeric) into dah-dit-dah type sounds, which is similar to what you are trying to achieve. MORSE.zip (3.9 KB)
David R Sky was working on a “sequencer” plug-in, but sadly he died before it was ever released. I don’t think that it was quite complete but if anyone has a copy of what he was working on I’d be interested in finishing it.
Generate a tone at given pitch - “number” is the midi note number - 60 is middle C
(osc number)
Set volume with (scale …)
(scale amount sound)
Here’s a little bit of code that produces a series of notes at different amplitudes. You can run this by selecting part of a track and then click on “Nyquist Prompt” from the Effects menu, then copy and paste this code into the Nyquist Prompt text box:
(defun note (pitch dur amp)
(scale-db (- amp 12)(osc pitch dur *table*)))
(abs-env
(seq
(note c4 i lp)
(note d4 i lpp)
(note f4 i lmp)
(note g4 i lmf)
(note d4 q lf)))
Thanks to Trebor for bringing this up - it caused me to check the list and it appears that a working version of his sequencer is available on the Audacity site. It is called “Audio selection Sequencer 2”.
I note the zip-file from that page containing David’s “stereo widener” won’t open on my computer.
I’ve repackaged the NY file in a zip, attached. widener.zip (1.14 KB)
Thanks, Trebor. I finally got around to changing the corrupt zip on the server. I think it’s OK (works in IE and Firefox). Chrome insists on pulling the old corrupt file despite clearing the download list, but that must be a Chrome bug.
