1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Suggestion for a new thread

Discussion in 'Building With Reaktor' started by arachnaut, Jul 12, 2011.

  1. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    This is a meta-discussion - a discussion about a discussion.

    I am pretty excited about the new serialization stuff. And it might be enough to get me programming in Core again.

    All my previous attempts left be baffled and frustrated and usually stuck with some stupid initialization problem.

    The new documents are starting to make sense to me. The frankness of the discussion is refreshing and I don't feel talked-down to. And yet, I'm not a DSP guy, so the level is right on that as well.

    This new stuff looks like things herw was talking about a while ago and is using now in his modular synth.

    When I saw that what they call serialization is what we have been doing for aeons in programming - things made a lot more sense.

    A common programming problem, especially across dissimilar architectures and different vendors, is to send a high level object from one part of a system to another.

    This is usually done via a method in OOP and even a compiler can do some of this work for the programmer.

    One of the most primitive ways (I don't mean simple, I mean low-level) is to take a big object, define it's BYTE LEVEL STRUCTURE and send those bytes in sequence over a wire to the receiver. The opposite is done at the other end.

    With this approach, anything whatsoever may be send down a channel even if it sends bits in series. (Bytes to bits convertor at the bottom and back at the other end).

    Usually the methods even have names like Object2Bytes() and Btyes2Object().

    This type of thing has been done in programming on internetworking projects probably since the 1980's.

    I would like someone to start a new thread (not this one) about some of these new documents and methods. We could discuss using the tools and methodologies and how to use modal banks and stuff like that.

    Basically an advanced Reaktor study group, focusing on Core and the Primary hooks in this method.

    I don't want to do that, because I don't feel smart enough to provide much more than what I just said and I haven't been doing any programming for more than a decade, so I don't know the current methodologies and terminologies. I also did something like this on the Reaktor Builder's project so I now what can happen. Also, event programming in Primary is my weakest area and we need to focus on that.

    However, I would be an active, enthusiastic participant.
     
  2. lunatic_machinist

    lunatic_machinist Forum Member

    Messages:
    145
    sounds great. I'd be interested in reading that discussion. I don't think I could contribute, though, only recently I've began exploring beyond the comfortable premises of primary into the mysterious lands of core, but it sure looks interesting.

    I do wonder, though, who could then lift this discussion. while there's life to be seen in reaktorlands, most of the really advanced reaktor builders have become silent (gabriel mulzer comes to mind).
     
  3. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    Reaktor has that effect, it seems.

    People get extremely excited, get very involved, sometimes for years, and then - maybe, they burn out.

    Nothing in the world comes without sustained effort.

    It's also possible that these people are working on beta versions of Reaktor 6 and prevented from talking about it.
     
  4. Iamblichus

    Iamblichus New Member

    Messages:
    9
    I would be up for following along. I am really interested in the modal stuff. I've read the introduction serialization pdf. and plan on reading the others. I thought it was really well written, though a good bit of it was over my head.
     
  5. herw

    herw NI Product Owner

    Messages:
    6,421
    As the scripts are like power-point-presentations read any script (with 128 pages too) very fast which means in 15 (!) minutes. Then a second and perhaps a third time to get the leitmotif.
    Then try to build simple examples while reading intensively.
    [proud]I am using an iPad to read the pdf-file parallel.[/proud]

    ciao herw
     
  6. salamanderanagram

    salamanderanagram NI Product Owner

    Messages:
    3,454
    heh, i think it may be a while before anybody can really understand all this. like herw, i prefer to read through these documents *really* quick, really just skimming and getting a grasp on what's covered. then i need to go back and find the relevant sections when building.

    anyway, i've been working on an ensemble that will demonstrate a few simple tasks, such as wiring the sine partial engine, making a sine bank with dynamic update rate / number of voices, sending and receiving event bus messages inside partial processors, using the chain iterator for calculating and modulating sine bank partials, displaying partial amplitudes and ratios, and anything else that comes to mind.

    to be clear, most of this stuff is really taken care of for you and the rest is simply filling in the blanks, but it took me hours to get running so maybe it'll save some people some time when it's finished.
     
  7. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    I have a few sine/modal bank projects in mind, too. It will probably take a month or two of playing with these to get familiar and then it will all seem easy (I hope).
     
  8. herw

    herw NI Product Owner

    Messages:
    6,421
    Uff, only two month? I think it's not so easy. We will see.
    Perhaps it's because i only had an intensive look into the first two scripts. I had a quick look into the introduction. The other two scripts are new to me too.
    As i am using first the eventbus for my modular project i will focus to them.

    ciao herw
     
    Last edited: Jul 16, 2011
  9. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    OK, 2 or 3 years....
     
  10. Iamblichus

    Iamblichus New Member

    Messages:
    9
    @herw- Thanks for the advice I will adopt that as my approach.