Home

Welcome to the pd-cyclone wiki!

cool info will be added here

#changelog:

1 Bug Fix:

• [train~]: now it gives us a click when width == 0 as it should.

---

7 Updated (now compatible to Max 7) and also eventually fixed objects:

• [pong~]: (considered related to Max 5), plus some bug fixes.
• [scope~]: (considered related to Max 4) plus some bug fixes (but has some known bugs yet to be fixed).
• [bitxor~]: (considered related to Max 5)
• [curve~]: (considered related to Max 4)
• [deltaclip~]: (considered related to Max 4)
• [trapezoid~]: (considered related to Max 5)
• [triangle~]: (considered related to Max 5)

---

9 New objects (compatible to Max 7)

• [atodb]/[atodb~]/[dbtoa]/[dbtoa~]
• [loadmess]
• [pong]: (introduced in Max 6)
• [round]/[round~]
• [trunc~]

---

12 New "Nettles" objects and individual help files

• [equals~]: (alphanumerical version of the nettles object [==~])
• [greaterthan~]: (alphanumerical version of the nettles object [>~])
• [greaterthaneq~]: (alphanumerical version of the nettles object [>=~])
• [lessthan~]: (alphanumerical version of the nettles object [<~])
• [lessthaneq~]: (alphanumerical version of the nettles object [<=~])
• [modulo~]: (alphanumerical version of the nettles object [%~])
• [notequals~]: (alphanumerical version of the nettles object [!=~])
• [plusequals~]: (alphanumerical version of the nettles object [+=~])
• [rdiv~]: (alphanumerical version of the nettles object [!/~])
• [rminus~]: (alphanumerical version of the nettles object [!-~])
• [rdiv]: (alphanumerical version of the nettles object [!/])
• [rminus]: (alphanumerical version of the nettles object [!-])

---

12 new Nettles abstractions: Abstractions to be loaded instead of the 12 nettles objects if the library is not declared - also included help files for each of them and new help files for the nettles library too. The abstractions just loads the object with the library declared. In the To Do list: - load these objects without the need to declare.

---

3 new abstractions (to hopefully become compiled objects soon):

• [thresh~]
• [downsamp~]
• [degrade~]

---

New redesigned [output~] abstraction

==========================================

In progress: new [scale] object;

To do;

• In modern mode, when you have "0" as the exponential factor argument, it actually loads "1" as the exponential factor. It should be actually "0" - going into that [max 0] function. Apparently you are doing something like if == 0, then 1. But you don't have to - just use [max 0].

• if I load [scale 0 1 0 1 1 @classic 1] it won't work, there's a problem in loading the exponential factor. I think this was happening before. I guess it has something to do with the [max 1] function and the idea you had that it shouldn't be == 1 - this happens either if you have an exponential argument of "1" or if you insert an exponential factor of "1" in the sixth inlet.

• You can include anything from 0 to 5 arguments. If you have 0 arguments, it loads default values (0 127 0 1 1). If you have less than 5 given arguments, only 3 for example - the 2 remaining arguments are loaded with the default arguments. Object will load in "classic mode" by default - unless you give it an attribute "@classic 0" - the usage of an attribute is independent of how many arguments you have given. So, it is possible to put 4 args plus @classic 1.