BrainModular

So I thought hey we could help out newcomers to Usine.

Let's discuss some of our most used modules for patching.

Data-Data Manipulation-Change Scale
This one I find myself using constantly.
I find very useful for converting an XY which receives positional values between 0-1 to adapt to other values such as a filter with 50-2000 Hz.
This is just one example, where common 0-1 can be changed to adapt to "Real World" numbers. I find myself using this quite often in many cases.
Also very useful to add a range fader with the min/max pos so that you can modify limit the scale as well.
An example would be like with MIDI Control numbers, Input can be 0 to 1, and output 0 to 127, where the range fader limits the output to whatever you want...such as setting a cutoff filter of a synthesizer but not wanting to go to low in the frequency range.....you can set 50 to 127 by the range fader to limit the value to the output.


Interface Design - Range Fader
Just because I mentioned above. Ability to set Min/Max and have a visual control to limit these to feed to other controls.
Also includes a position cursor, which can be useful for display of the value within the range you are limiting to.


Flow Control - Pass Flow
This is a basic switch which allows you to completely disconnect the output if "not" activated.
I will commonly use a set of these with the not(A) module so if I have a single switch I can switch in a path, while disconnecting another.

Math-Logical-not(A)
This is a common digital logic not symbol if a 1 is present at the input a 0 will be at the output.
Alternately if a 0 is at the input a 1 will be at the output.

Flow Control - Pass only if has changed
This is similar to the Pass Flow, however it does not require a switch to enable/disable the flow.
As long as a change is detected at the input it will be forwarded to the output, if not then it will completely disconnect with [-1]
This is very useful when wanting to use a fader to control another fader, while retaining control of both objects.
Without this inline, the second fader cannot be modified and only displays the value of the first.
With this inline, the second fader can change the value...however if the first is moved it will overtake the second one.


So help keep the list going guys, at least with some common used modules and a short description to help.
Tell your favorite, your most used, the ones that surprised you the most and were very useful.....
This way people know where to start, maybe we will all learn something we didn't know....I know I keep finding new things out everyday.

-S

Nobody?

It's a good idea building a better library of modules definitions. I will try to find some inspirations during daily patching activities..

I've checked out the manual and wiki, and though found some info, not a lot of "how to" actual stuff. A few things I've wondered:

Clock - whats the deal with clock/sync. Things seem to just drive themselves, though signals can be fed into devices. What's the standard technique and modules for creating clock/sync?

Arrays - whats the deal with arrays? What are they, what are they used for? Are the FFT arrays different then the other arrays?

If anyone had some info about that, I and hopefully others would find it really useful -

Thanks!

I think "user-friendly" means more visual examples, not text, but, probably, it's only before you get in and start using "?" more systematically.

Yep that's what I am trying to start guys, I am updating the Wiki so examples you give and questions you have I will try to start searching for the right example and update it.
I would like to get examples for each module implemented, but want to start on some of the most common ones and how you use them.

psudaform wrote:I've checked out the manual and wiki, and though found some info, not a lot of "how to" actual stuff. A few things I've wondered:

Clock - whats the deal with clock/sync. Things seem to just drive themselves, though signals can be fed into devices. What's the standard technique and modules for creating clock/sync?


Arrays - whats the deal with arrays? What are they, what are they used for? Are the FFT arrays different then the other arrays?

If anyone had some info about that, I and hopefully others would find it really useful -

Thanks!

Clock can be considered as an alarm clock

Array modules are good for generating/manuplating array data (ahem!). Tremoresque addon may be a good example : )

recently I found "pass event flow" very useful and even non-replaceable. As user I want to send "only ON" or "only OFF" messages from different sources to the same target. So this I found most simple solution:


1. this allows conect multiple events to the same target because always ends with [-1] = that means nothing (nor 1 nor 0)
2. this allows to send the one and the same exact value(0 or 1 or 2 or 3 etc . . ) several times. It doesn't work if "pass if has changed" are used.

*logical modules with "bloc output" can be alternative only for sending value 1, but not for 0 ore any other value.

Awesome description r.error! Thanks for sharing!

-S

Hey sephult,

Let me know if you need some help updating the Wiki. I'll be happy to pitch in.

ahonoe, we can all work together on updating. Feel free to update and correct whatever you think necessary.
As long as you are making it better, and capturing good info there really is no concern

I am trying whenever I can to get things updated, I would appreciate everyone contributing.
That's why we are a community.

-S

Yes, all help is appreciated, cause as you know it's a huge work to maintain all infos updated.
Now we have a new user's manual, the next step will be a new patching tutorial manual, and all ideas, questions, examples are welcome too !

Most definitely,

I agree with all and want to put usage examples for each module, patch, etc.
It would be very nice to have and show an idea of what common usage is.
So if anyone has questions or needs help updating the Wiki, or if you have any material like graphics or anything you want updated I will help
Feel free to also contact sephult@hotmail.com if you have questions too.

-S

@psudaform :
about array, you can imagine a series of values like in a step sequencer, each value has a specific address (this succession of address is called an index) : An index always start with 0, so first value has the address 0, second value the address1



now you can, for example extract a value at a precise address of the index, here we extract the value of the address 2

It’s the same deal with a matrix, the data’s are organized on several rows but it’s the same principle.
Here we extract the value at the address 5: the cell of the matrix is ON so the value is 1

About clock modules, you can consider them as wifi peripherals linked to the master synchro of Usine.
if you don't need the big master synchro module, you can use them to drive any sequence or event.
if you change tempo in Usine, these clock modules will follow automatically the master tempo

Also with reference to an array, there are basic concepts in some Math Array educational videos you can search on YouTube or Google.
The most common you will find is related to arrays in programming languages. The Usine modular patching approach is exactly the same.
You have an array of values say:

4,6,8,2,13,23

This is an array the size of [6] because you have six values within the array. Arrays reference the index numbers from Zero, so it is like saying [0..5].
Arrays are almost like Multi-Variable storage containers (in many cases I call them like Buckets).
If you want to retrieve the 3rd value in an array, you just reference the index [3] to do so like in Nay's example using the ArrayGetVal.

In a programming language you would do something like this if you have a variable defined as an array.

Value := myArray[3];
setvalue(output,Value);

Hope this helps. Will do some updating on arrays first with some illustrations like Nay has.

-S

I have a light solution for sequence-free slicer you can trigger manually or playback pre-recorded slices. I use it for long field-recordings, so it's probably useless fore beats or very short slices.
touch_slicer