Post

there are definitely scope apps for iPhone - probably for Android too -but you'd have to find the one that works for you - can't say I've ever needed a scope though in 5-6 years of modular - I'd rate them as nice to have, rather than crucial - except for a few DIY builds

I'm a very visual person, so I like having a view on how the wave reacts to certain changes, like modulation. So I'm going to get a headphone dongle for my iphone (like, yeah, it was too expensive to add one into the phone itself) and do some research on that.

headphone dongle wont' really help except for audio - for low frequencies you'd still need a dc-coupled interface and a usb dongle for the phone - nb you only get 2 channels this way

nb there's dc-coupled and there's dc-coupled - something advertised as such will definitely be dc-coupled on outputs - but not necessarily on inputs...

The Motu M4 indeed has DC coupled outputs. DC coupling is new to me (like so many things), so some work to do here. I guess DC coupled out only means I can use it to send data from VCV Rack to the modular, but not vice versa? In that case, tuning with VCV Rack won't work. I just read an RME is similar to my M4, so I'd like to understand what you mean exactly here.

Anyway, as my primary aim is to uncouple myself from the dreaded PC screen that I spend all day in front of, I consider this a nice to have. It will remain in my studio rack and I won't be moving it into the Intellijel 7U case.

having mostly been in the same situation for most of my adult life, I've never had an issue being in front of a computer for a bit longer in order to do stuff I want to do - use a DAW, etc and for a long time if I wanted to watch any tv or movies it was also in front of a computer...

they're much more like buttons - MPC style pads, I guess - not like drumpads you can hit with a drumstick!

Yes, but at least they're velocity sensitive, unlike the SQ-64.

not via the trigger outs they're not - via midi they are I guess - never used mine other than via cv though

Yeah, I'm not aiming at more. There's plenty of oscillators in the big version but they can be used for modulation as well.

-- Arrandan

I try to keep lfos separate - every time I buy a module that'll do both - I end up using them for vco's - tides, tides2, cali - all work as both lfos and/or envelope generators - but sound great as vcos - so they end up being used as vcos - and I try to forget that some of the lfos, filters, envelope generators etc I have can also be used as vcos - otherwise I'd end up with patches with all vcos and virtually nothing left for modulation, filtering etc

With modulation, I meant wave modulation actually. I agree that LFOs are better kept separate. It's why I have the A145-4 in there. LFOs serve one purpose, VCOs another and as with my short rant about O&C, I don't like tools that mix up purposes.

I don't really see any wavetable oscillators - I think I'd want a more ergonomic quad lfo...

Aside from this rather very interesting discussion, is there anything you think is wrong or missing from the basic setup? Having played with a similar setup in VCV Rack, it feels like a good starting point to me.

And thanks for all your help!
-- Arrandan

yes: there are still issues:

temps utile, random triggers, clock divider and multiplier, buffered mults and harmonaig all seem a little superfluous - you have 8 trigger outs and 2 cv/gate/velocity outputs (all with probability iirc) on the BSP and no percussion and only 2 vcos in the rack...

in the larger rack - the droid stuff seems to be in a similar place - the chipz I would replace with a Maths, the 2 dvcas I'd replace with a veils - and I'm not convinced of the need for 2 dplrs - and I'm not convinced about the mix solution - no panning and no send/returns...