Hello, my friends
I've started using Reaktor and I felt the need to understand the function and how each building block works, I mean, for ex. gates, oscillators, note pitch, etc, etc.
Are there any good books that explain these things?
Thank you
Need some literature about sound design building blocks
-
- Banned
- 10196 posts since 12 Mar, 2012 from the Bavarian Alps to my feet and the globe around my head
Aren't there 4 different manuals included in REAKTOR that explain everything in depth? 
-
- KVRist
- Topic Starter
- 467 posts since 6 Feb, 2005 from Portugal
Yes, there are but they are written in a confusing way (for me, obviously).
Let me explain this better... it is written for someone who has an average/high knowledge of the concepts used. If someone who is not so "fluent" in this "language" starts to read the manual, they need to find a lot of explanations elsewhere. I had to look for sites, articles, run a search in all the Reaktor manuals and then "compile" all the info I got to reach a definition or a clear understanding of what I am looking for.
Basically, the explanations in the manuals are, many times, using a lot of technical terms which could be replaced by a day-today language.
For example, about Gates, the Modules and Macros manual say: "The Gate Module is a Polyphonic Event source for MIDI Note On and Note Off events."
Wouldn't it be easier to write something like "a Gate cuts the signal unless you strike a key that opens the signal circuit, which is called a MIDI Note On event." or something like this. Basically, replace many of the technical terms by examples of what happens in practice.
That's just my oppinion.
Let me explain this better... it is written for someone who has an average/high knowledge of the concepts used. If someone who is not so "fluent" in this "language" starts to read the manual, they need to find a lot of explanations elsewhere. I had to look for sites, articles, run a search in all the Reaktor manuals and then "compile" all the info I got to reach a definition or a clear understanding of what I am looking for.
Basically, the explanations in the manuals are, many times, using a lot of technical terms which could be replaced by a day-today language.
For example, about Gates, the Modules and Macros manual say: "The Gate Module is a Polyphonic Event source for MIDI Note On and Note Off events."
Wouldn't it be easier to write something like "a Gate cuts the signal unless you strike a key that opens the signal circuit, which is called a MIDI Note On event." or something like this. Basically, replace many of the technical terms by examples of what happens in practice.
That's just my oppinion.
-
- Banned
- 12367 posts since 30 Apr, 2002 from i might peeramid
some of the terms have a vernacular presence (they seem like they mean something obscure and specific) but are perhaps obscured by being less specific/vernacular than conventional uses.
eg. an event, in the most basic form, is an occurence, and if you think of it as such it is easier to read. gates are, at least here, either open or closed.. so we know a gate is simply like a key trigger.
i am sure this can be frustrating if english isn't your first language, i'm sure that if there were some video that illustrated these generalities the language would be less challenging. i don't know of one, and expect the best way is to nose through some simple example projects. once you've got a few down, the whole thing will start to make a lot more sense.
don't feel challenged, take a deep breath and swim in it for a while, it will be more familiar tomorrow
you come and go, you come and go. amitabha neither a follower nor a leader be tagore "where roads are made i lose my way" where there is certainty, consideration is absent.
-
- addled muppet weed
- 111329 posts since 26 Jan, 2003 from through the looking glass
a gate opens and closes with a midi signal 
