Softube Modular

[tb1]

the experience of using a modular synth cannot be even close using a mouse

That`s for sure. It`s a matter of taste i guess. I like the hybrid-way. You know that its possible to control a real modular synth with mouse?

[jwise]

the experience of using a modular synth cannot be even close using a mouse

That`s for sure. It`s a matter of taste i guess. I like the hybrid-way. You know that its possible to control a real modular synth with mouse?

Wow this is like the argument against the move from vinyl to digital or how really old people complain about young people always texting.

It's another tool to make music with. It defeat's nothing, but I guess it gives people something to complain about as they perceive a change in technology intruding on their way of life or creativity, not complimenting it. With this kind of reasoning we should have never moved beyond the purity of banging our rocks on other rocks.

[hivkorn]

the experience of using a modular synth cannot be even close using a mouse

That`s for sure. It`s a matter of taste i guess. I like the hybrid-way. You know that its possible to control a real modular synth with mouse?

Wow this is like the argument against the move from vinyl to digital or how really old people complain about young people always texting.

It's another tool to make music with. It defeat's nothing, but I guess it gives people something to complain about as they perceive a change in technology intruding on their way of life or creativity, not complimenting it. With this kind of reasoning we should have never moved beyond the purity of banging our rocks on other rocks.

you're right .I wish something like that since a long time ago,but i've always think the first dev to do it will be Audio Damage with their own sequencer.I don't mind to don't have a controler , it is just a new ways to make sound , i know what i want and i know how to do it.Reaktor can do it but i don't find the 'modular' GUI easy/friendly to work during a song.

[Uncle E]

In its current state it does not even support native MIDI Learn, so you can use the
1. host automation features of the DAW or
2. the built-in MIDI assignment features, like Live MIDI Learn or Cubase Quick Controls, etc.

Do they plan to add these things?

Regarding a hands-on hardware controller, it would need to have all the modules in midi controller form and you would be limited by the number of midi controller modules you own. Fortunately, the midi controller modules could be a lot cheaper and smaller than the real things. It's actually quite easily possible and would be worthwhile if the market is large enough, we've gotten more pre-orders for Softube Modular than any other product this year so maybe it is!

[maschinelf]

Would be interesting if they made a dedicated controller for this. They've already done something similar with console 1, though this would undoubtedly be much more challenging and may not fully work with all the functions on all the 3rd party modules. I wouldn't be very surprised if they've already thought about doing this eventually.

[aMUSEd]

In its current state it does not even support native MIDI Learn, so you can use the
1. host automation features of the DAW or
2. the built-in MIDI assignment features, like Live MIDI Learn or Cubase Quick Controls, etc.

Do they plan to add these things?

Regarding a hands-on hardware controller, it would need to have all the modules in midi controller form and you would be limited by the number of midi controller modules you own. Fortunately, the midi controller modules could be a lot cheaper and smaller than the real things. It's actually quite easily possible and would be worthwhile if the market is large enough, we've gotten more pre-orders for Softube Modular than any other product this year so maybe it is!

They would need a system for making automation assignments work consistently when adding new modules. Assigning fixed automation IDs isn't going to work because you may have more than one of the same module in an ensemble, and if it just does it automatically you could end up with hundreds of params for a complex setup. I'm guessing either they will do what Spectrasonics do with Omnisphere and let users add automation IDs for params they want to control, or take the easy option and only allow the macro controller part to be automated and controlled using hardware.

[Uncle E]

take the easy option and only allow the macro controller part to be automated and controlled using hardware.

You're right, that makes the most sense. It'd be fun, though.

[maschinelf]

I imagine that if they were to make a dedicated controller, maybe it could work on a per module basis. Using a generic template design like the sl mk2 or Nektar panorama, with enough faders and knobs, and maybe a few more options like sequencer pads, xy controller etc., they could go well beyond macro controller assignments with pre mapped configurations per module. Or a dedicated controller that works similar to the nord modular g2 and saves mappings per patch could also work, though then it might as well be with a 3rd party controller. It would also offset and justify the relatively high price per module if there was a dedicated controller with pre mapped configurations, atleast for me.

[hivkorn]

just to make it simple for no english native people , midi learn is supported?

[VariKusBrainZ]

If Tunaknobs actually worked consistently they'd be good for this but they don't work on any of my screens

I got the 6 pack on Kickstarter, waste of $$$

http://www.tunadjgear.com

[aMUSEd]

I imagine that if they were to make a dedicated controller, maybe it could work on a per module basis. Using a generic template design like the sl mk2 or Nektar panorama, with enough faders and knobs, and maybe a few more options like sequencer pads, xy controller etc., they could go well beyond macro controller assignments with pre mapped configurations per module.

Unless there's a fixed number of modules, which I doubt, that's a hard thing to do. eg I can make a template per module easily for something like Zebra using NI Kore 2 because there are always only 4 OSCS, 4VCAs, 2XMFs etc so each one has its own dedicated automation ID for each param, which I can map to Kore knobs and buttons. However if there are unlimited modules, and since it's also an extensible system with potentially more added by Softtube and third parties etc, that's just not possible - everytime you added a module it would add more params to automate and each would need a unique ID or they would clash. That's why I can only see 2 ways of doing this, either allow the user to choose which knobs etc get automation IDs exposed to the host (as in Omnisphere and the Virus Ti Control plugin) or they only allow the customisable macro section to expose automatable params to the host.

[stikygum]

I don't enjoy soft synth modulars. It's so tedious to do all the patching. When I'm working with an actual modular it fun and I don't mind patching because of the tangible interaction. But in the software domain, it's too cumbersome. Uhe Ace was nice sounding, but not fun for patching. But more power to Softube for going the modular modeling route.

[BITWORD]

CPU usage? Anyone?

[spacekid]

just to make it simple for no english native people , midi learn is supported?

Bonne question.

[CrystalWizard]

For myself a large part of the fun of modular synthesis is the Knobs (and the versatility ofcourse.)
When i don't use my homebuilt modular synths i am quite happy with Reaktor which i personally think can sound fantastic depending on the ens. I haven't even explored Blocks that much but it would seem to have Softube beat.

I know Softube makes quality stuff but this just seems like a money grab, jumping on the modular synth fadwagon...
If you're going to start collecting modules (and you will!) you may as well buy hardware, lot more expensive and lots more fun (or get Reaktor, you should have it for more than just the blocks.)

Just my .02