developing a macro library

here is a stereo version (with more written details, view has a visible text as well).

also, i have included "Shred", which is one of my favourite granular delays.

btw, there are a few snaps to here the different delays.

sowari

 

i am thinking about it since several months.
The clicks are only from changing reverbtime when changing a snap (same reverb time - no clicks!).
My idea is to have two memories for the reverb memory. One is active. When changing by a snap then change the signal path to the other (empty) memory. So there will be no glitches or clicks.
I have tested it manually - it works but i didn't solve it automatically by changing automatically (snapshot module is not the solution because of the globally reset).
Perhaps someone is very genius to memeries of reverb (or delay) and show the way?

ciao herw

 

i'm getting the feeling that the idea i had, inspired by herw, to create a set of essential building blocks for a device category and to house them in one 'master' macro (such as the delay maestro) is NOT the approach most of you want to take for the rb_macros library. rather, you'd like the library to offer a selection of macros for each category: a set of delays, of reverbs, etc. and that these would be customized versions of existing macros/instruments.

so the rb_macros library would be a grab bag of cool, bug-free, and well documented macros taken from ni and the user lib.

i'm fine with this way of working ... to build a 'best of the best' set of macros for all dsp categories. could be fabulous.

i'm happy to help, but i really can't do ALL layout/documentation myself, because it's very time consuming (if done well, and rb_macros should be done well ... or why bother?).

so if wonderful grab bag of macros taken from all existing sources (except commercial ensembles) is what we're after, then let's figure out a way to share the work.

if people submit macros to me that are tested, documented, and laid out clearly (to help users understand functionality), then i'd happily do 'final mixes' on them: clean up documentation, layout, and make sure they are consistent with the rest of the macros in the rb_macros library (credits, 'logo' perhaps, etc.).

the other project, a bare bones but powerful building block set, kind of like one step in complexity above built-in modules, could be something herw and i do together.

 

yes, for me a collection of macros is the important thing here.

the "Master Macro" is a good idea, but for me it is too early to think of this, in that we need to have a bunch of LFO macros and other bread and butter macros sorted out first. having said that, i enjoyed having a look at your delay maestros.

when i have the time, i will upload my delay macros with Jim's backgrounds and some more hints.

sowari

 

a request for Herw

i love your Event Buss

any chance of an Audio Buss?

i get the feeling there are one or two things you have to finish before

sowari

 

that's my goal. i have a small set of chorus/flange/phase effects that i put together that i'm going to try to format for you and then i'll upload them. it'll be a few days because my life is sort of getting in the way lately

 

okay just to formalize things ... here is what all rb_macros will share (i.e. what makes them rb_macros):

panel display

- simple streamlined understandable
- main controls in view a, all controls in view b
- easy to understand pop up info for all controls

structure

- open uncluttered layout with clear sense of signal flow
- all ports (that are not self evident) get popup info
- all sub-macros (not self evident) get popup info
- signal flow (not self evident) gets comment boxes

miscellaneous

- all rb macros get info text box: rb_macros library 'license' and original creator of macro
- usage overview presented in macro info popup
- control names and capitalization taken from original macros
- macro name taken from original but with rb_ prefix

please add and suggest improvements.

 

I'll offer my help. I don't feel too comfortable with my
building skills yet, but I can test, re-layout, and fix text,
maybe do some documentation, etc. I'll also be happy to
do any graphics work that's needed.

I know how these projects can start with a great deal of enthusiasm, then as time goes by, people get bored or
drop out for want of other stimuli.

I was a software engineer in networking for 30 years,
taught web design and photoshop, built lots of
Heathkits, built a Paia 3 Osc. computer controlled
synth in 1979, and now I'm retired, so I have a
lot of different skills and free time. I have read the
Reaktor manual several times and it sits handy right
next to me on the desk, but until you really get into
building something big it's hard to use with any
confidence.

The GUI for Reaktor is a bit odd to me. It reminds me of
the way Photoshop was ported from the Mac and shoe-horned
into a Windows frame. It never feels like a native Windows
application (compared to, say, Corel stuff). For example,
to load sample files, the load is in a pulldown menu, not
in a main window menu - things like that make you look extra
hard to find things.

 

cool.

how about if sowari and jopy and jim act as feeders/testers/reviewers?

1. you guys extract macros from wherever, make sure all the controls have at least some popup info, clean up the panel and structure a bit, then send them to me.

2. i'll do my bit then post them for testing.

3. you guys test, fix if necessary, add features if desired, then post, and i'll hone them.

i'll go through this thread now and make sure i have all the macros people submitted.

 

Version numbering in each macro. Probably not in
the macro name, just in the info text.

 

yes! let's all promise we'll do this.

how about we put the version number in the macro name.

 

audio bus ? - no chance at the moment (monophonic? perhaps, but in future) -
master macro - NO not my idea - in my opinion as simple as possible no "schnick-schnack". Simple panel and easy to understand for a newbee:
(see attachments)

 

Reverb

Here's a reverb I made based upon a waveguide feedback delay network. Similar to Gabriel's, though not optimized. This is a direct port of Sean Costello's CSound code. The interpolated LFOs (which can be run at audio rate) are nice, too, though take up some CPU. Feel free to use/modify.

 

you tease us with your attachments

sowari

 

?

sorry, i don't see the point in this.

i have no idea about my versions.

sowari

 

We start at 1.0 and increment for each change.
Or do we want to start with 1.00?

This is so we don't step on each others toes and make sure we have up-to-date macros.

Suppose I take rachmiel's lfo-mod macro from the last delay he uploaded. If he later updates that, at least I'll know which macro we are using, and that I may want to update mine.

It helps also if two people are modifying the same macro at the same time. (Although they may both upload the package with the same increment. That has to be avoided, there is no source control system here.) I guess that means someone has to be the official enumerator.

I'll start with an example.

I upload here the rb_graphics macros. They contain two images:

all_colors 9 1x1 pixel swatches - use the index to get the color

all_icons 3 31x31 icons for macro pictures - use index to select

I have tried to use our conventions on all the parts of this mute ensemble.

 

ok, i get you now.

sowari

 

Will Reaktor ever get wire anchor points?

It seems trivial to implement. Right now it must
save the two endpoints and use a drawto function.
All it needs is to save a set of points and iterate the drawto.

These straight-line wires make it hard to follow.

 

Tests and comments:

sowari delay 3

Many of these filters have quantised delays. There are no smoothers so this
causes a glitch in the delay line, but I guess the nature of these filters
is their beat orientation, so this is not such a big deal.

This batch of delays is getting a bit on the 'too-clever' side of Reaktor. I will follow this post with a comment on this.

Dub Delay:

should add comment that pitchbend can also adjust the delay
the signal flow is a bit hard to follow

A few clicks can be heard when sweeping the 'DELAY' knob, maybe it needs a smoother?

Everything seems to work right.



infinityFFb:

'Delay' dial is not annotated.
From the structure: 250/Tempo * Delay -> ms delay input of Single Delay.
This seems like an arbitrary function.

The two macros 'Fil' and 'Ter' (how cute) make up some type
of filter, but there are too many magic constants and no comments
so it is hard to understand how it works. It looks like some type
of bandpass filter.

This is a very nice filter, but quite messy under the hood.

Everything seems to work right; but sweeping the 'Delay' knob causes all sorts
of interesting artifacts. I suppose that's a feature.



Ugh Diffuser Delay:

'time' units are not clear - they seem to be beats per measure?
The 'time' knob needs a smoother, it's noticeable glitchy

Everything seems to work right.



Delay with Filter:

'Delay' needs a smoother. Easy to follow structure.

Everything seems to work right.



Pitch Delay with Feedback:

Even with delays set to 0, there is some audible latency between
'Direct' and 'Effect'.

Everything seems to work right.


Shred:

Although the structure looks simple, this is very hard for me to follow.
The 'init bang' stuff and the snapshot handling is a bit over my head, or perhaps
my eyes are glazing over trying to understand all these structures.

In usage, all the knobs seemed to function properly.

I tried this on a few sound sources and I'm not too sure what this is
best suited for. It seems to be more of a distortion effect than a delay
effect.

 

I have a follow-up to my last post on sowari delay 3.

I have seen a lot of software written in many styles.
Beginners have a style, more experienced people have another style,
and then there is a style one develops in an environment where
code is meant to be shared, extended, and maintained.

No matter how clever, something can be described in simple terms,
or it isn't easy to maintain or extend.

If it is too clever, only the original author understands how it works. Someone else will try to understand, but after a certain effort, just throw it out and re-write.

I feel some of these macros were designed to show how clever someone was.
There is probably a way of making them a little bit more clear. Or
maybe I just need more time to study them, my head is spinning
after spending the last four hours looking over these.