Dsp Sub-chains

[sodiufas]

1

[Garf]

@dblue

The doofer - it’ll do fer this and do fer that!

What a wonderful word!

[joyjoy]

doofer-device +1

[sunjammer]

Airmann, I’m sorry about the curt response. I was tired. First of all, you did a complete thread hijack with a topic that has no bearing on what we’re discussing. Much like dBlue did. But i know him so he’s more easily forgiven

The signal follower lets you base nearly any parameter change in any vst (instrument or effect) on a treated set of amplitudes. This is infinitely more powerful than dedicated sidechain compression. I’d like to know which sidechaining vsts you are using that don’t use it for compression or vocoding alone. As for the latter, if a vocoder doesn’t have the foresight to support left carrier right modulator setups, it’s not worth your time anyway.

But ARGH with this digression!

[Luke_Norland (jasper)]

The point is to create DSP chains that are more modular, more easily managed and stored for re-use, and to clean up the epic clutter of a complex chain and its frontend.

i like this idea- well done
+1
i come from devon too, but i call it a dibber…

[Airmann]

No Problem, was tired, too :-). Didn’t actually want to Hijack. But you’re right, if we’d go deeper into the topic this thread would be poluted.

So I open a new topic on that:

Signal Follower Sidechain Fake

[Ledger]

Just re-reading this thread, I see it goes along with this one:

http://www.renoise.c…showtopic=23646

This is Suva`s mod of my mock-up,

You get the modularity, extracting relevant parameters [e.g. depth from the chorus here], saving set-ups as presets (amoungst other things such as VSTi loading in tracks, MIDI VSTs etc.)

[BamBooli]

Yep …

it comes to the point to have an modular system like AlsaModularSynth (AMS) in linux and if you have test this beast you know how great it sounds ;o)

I dream of the possibility to have such a powerful routing with such massive modules like in AMS and this an all OS for swapping tracks.

See what comes …

[danoise]

@dblue

Imagine being able to take a huge, messy DSP chain like this:

And group it all into a single, smaller, more convenient device, which only showed the handful of parameters you actually needed to automate:

Cowbell? Radness? Awesome!!! Somehow I missed this beautiful exercise in simplicity from dblue.

[Suva]

This beautiful exercise in simplicity from dblue is full of cowbell, radness and awesome!

+7996

[svennarve (Sam)]

• one billion trillion

[Kameleontti]

Yay! Great post. I’m your henchman on this.

Been thinking of this solution before some. So this would be like Hydra that contains bind effects and routes the audio inside modular? And also allows meta devices control multiple parameters? Would be great if the devices could really be broken up for this. For example, if I could break up the delay effects feedback loop I could actually make modulated and EQ’d delay that builds effect on top of previous cycle. And such. Wasn’t this the original idea?

Think of it at least.

[Jonas (Djeroek)]

@Sam

• one billion trillion

lol

[vincentvc (woponep)]

+1 seems i never did…

[Lethargik]

+1

[datassette]

Just giving this thread a bump/addendum.

In addition to the original idea, hidden send tracks could be confined to a DSP sub-chain, or ‘Black Box’:

Say you have a multiband send going into 3 send tracks with different types of distortion - you have created native Multiband Distortion. That’s awesome, but if you want to re-use this in other songs you have to either save 3x DSP chains and 1 multiband send preset, or make a template song for it.

A better way to store this structure would be to wrap up those 3 tracks and 1 device into a single meta device, which you would then place inside a single send track - so we’re actually having a whole other track with 3 different send tracks actually contained WITHIN a send track inside Renoise - but these extra send tracks ‘inside the black box’ would not be addressable from anywhere else.

This device could contain any number of FX and send tracks, but appear in the Renoise Track DSP view as a single device, be isolated from other tracks elsewhere in Renoise, and with only the pertinent parameters that need automating exposed to Renoise automation and pattern commands via a user-definable GUI front-end.

(See other thread)

[rhowaldt]

bumping this thread, because i re-read it and completely agree with the awesomeness of dblue’s idea here, and because of this separate thread that brought i back up here.

dblue’s idea is a lot like what Reason’s Combinator does (although the Combinator is a bit more powerful, having its own keyzones etc), and i really loved that device in Reason to clean up your chain and organize things into one single device.

[vastique]

+1

[kurtz]

• • • • 1 + + + +

[rhowaldt]

i kinda feel this thread should be pinned. anyone agree?