| Objects | page : 1 |
|
bufedit~
| External |
  |
It enables you to modify data in buffer~
It enables you to modify data in buffer~. It will be useful for making weird sound or impulse response. Don't ask me why don't you use peek~... I didn't know peek~ untill I've finished coding of bufedit~. bufedit~ has advantages and disadvantage with peek~. Advantage of bufedit~ is a lot of supported messages, for example, it is possible to make a window with a few command without Uzi, or when performing convolution and if impulse response is static or less changes, bufedit~'s fft command will help you with computational expences. And unlike peek~, bufedit~ can store value greater than 1. Disadvantage is that I strongly believe DZ's programming skill is superior than mine and I've not tested bufedit~ much yet (it seems stable for me). So please use bufedit~ at your own risk, I don't owe any responssibility to disbenefit caused by using bufedit~. |
|
Deal
| External |
  |
returns random integers within a specified range.
All numbers in the range are used before any is repeated. This is similar to the urn object introduced in Max 2.2. A single argument sets the range. If the argument is omitted the default size of 128 is used. The second inlet can also be used to set the range. The range must be at least 1. Anything less causes Deal to set the deck size to 1. Changing the value at the second inlet causes the "deck" to be "shuffled." You can also shuffle the deck by sending a "shuffle" message to inlet 1. A bang at inlet 1 causes output of the next "card." Use Uzi to deal multiple cards. |
|
defer
| External |
|
De-prioritize a message
When Overdrive mode is enabled, objects such as metro operate at interrupt level. This locks out other processing from happening, which may affect timing performance. If you want to execute a time-consuming task, such as using an Uzi for repetitive operations or the bang message to a table object, you can defer the interrupt level output to the lower priority main event level by passing a message through the defer object. |
|
izi
| Abstraction |
|
Like uzi, but iterates a list. |
|
jb.uzi
| Abstraction |
|
send out a fast-as-possible
linear count |
|
loadzi
| Abstraction |
|
A combination of uzi and loadmess. |
|
sluzi
| External |
|
slow uzi |
|
St.lowzi
| Abstraction |
|
Like Uzi but slower. |
|
tl.n++
| Abstraction |
|
Slow uppward uzi for large tasks.
Max is responsive while task is performing, as each count value is delayed by 0 and defered. |
|
tl.n--
| Abstraction |
|
Slow downward uzi for large tasks.
Max is responsive while task is performing, as each count value is delayed by 0 and defered. |
|
tl.uzi
| Abstraction |
|
uzi variant that keeps Max responsive, provides progress report and more. |
|
uzi
| External |
|
Sends out n bangs messages
Send a specific number of bang messages |
|
vDeal
| Abstraction |
|
eturns random integers within a specified range
All numbers in the range are used before any is repeated. This is similar to the urn object introduced in Max 2.2. A single argument sets the range. If the argument is omitted the default size of 128 is used. The second inlet can also be used to set the range. The range must be at least 1. Anything less causes Deal to set the deck size to 1. Changing the value at the second inlet causes the "deck" to be "shuffled." You can also shuffle the deck by sending a "shuffle" message to inlet 1. A bang at inlet 1 causes output of the next "card." Use Uzi to deal multiple cards. |
| page : 1 |
