How to build the strangest Buchla Oscillator in VCV
Vložit
- čas přidán 24. 04. 2021
- In this tutorial we are looking at an early concept Oscillator from the 100 series that is quite unknown even by the biggest Buchla fans and try to reproduce its sound
Huh, randomly clicked on this video and it turns out this is a method I've discovered recently with my AE Modular system, using a sequencer as an oscillator, I've mainly used it for AM-ing and FM-img things though. Cool to find out who did it first and see it used, very powerful way to make some noise.
I used 2x PGMR because there’s no xpander in MiRack - with an 8 step sequential switch - seems to work 👍🏼 thanks so much!
I love the idea of this! I don't know much about Buchla, yet, but it's fascinating to learn. Thanks!
Proper
I love Your videos. You are a genius.
Thank you so much!!!
good stuff!
awesome work!
could you show how to make a gate at random beat synced rates? to chop an fm lead for example
Hi Zahasara, If i understand your question correctly then you are looking for a Bernouli gate. It does randomise a steady beat but needs a clock to function. Try out chances by count modular
@@crozpatching4598 hey, thanks for the quick response :)
I actually ment something different: i want a gate of lets say x1 clock, that has a controllable chance to accelerate to x2, x4 x8 etc, on every last 1/16 of the bar or last every 1/8 and so. hope that makes sense :) chrisGlitch vst is like what I'm going after, but its more of a glitch fx.
@@Zahasrara I think using chances with the combination of the 8face should get you there. With the clocked module you can program multiple subdivisions and multiplications ->run that into chances -> have the chances trigger out into the 8face that is saving your presets of clocked. Hope this helps :)
@@crozpatching4598 ill give that a try, thanks!
Is there any way in VCV to build a complex module (like this oscillator) and then wrap it up in a container, so that only selected inputs, outputs and controls show up on the outside of the container, and the wiring and non-modifiable controls stay on the inside?
The container would then (of course) behave just like a module...
In other words, a way of hiding the detail AND reducing the screen real estate?
Hi Paul, no unfortunatelly we dont have anything like this now, or at least not that i know of. What you are talking about would be a combination of a subpatcher (like in MAX/MSP) and perhaps a freeze option (like in Logic Pro). I have not seen anybody do this so far, but it would be a wonderful feature to use in the futer to safe patch space and CPU usage
@@crozpatching4598 What I'm proposing wouldn't same CPU - it's just a (helpful!) cosmetic presentation of the same underlying thing.
A computer programmer would call it a parameterized subroutine.