Yahoo Groups archive

Doepfer

Index last updated: 2026-04-29 00:15 UTC

Message

Re: [Doepfer_a100] MOTU Volta

2009-01-17 by Guy Drieghe D.

> I agree that the VOLTA looks amazing at first glance, but for me, the
> great strength of analogue synthesis is the hands-on control and the
> luxury of being able to get away from the screen. Sure, it's cool to
> be able to get the better control output resolution from your DAW,
> but it's still fundamentally unsatisfying to rely on drawing ramps,
> curves and other control data rather than feeling them.
>
It's no different than, say drawing envelopes and lfo's in Absynth or  
any other sophisticated softsynth. Most "chicklets" (the functions of  
Volta) bear a lot of similarities to Motu's MX4 functions (they're  
actually lifted out of MX4), so they're very flexible and farreaching.

For me, it will be the combination of having a complete DAW  
functionality combined with modular hardware that will be the killer  
app. Since Volta is just a plugin, it's no problem to use an external  
hardware controller to control it, just like you can with any other  
VSTi.

> Perhaps I'm mistaken but from what I understand, VOLTA is only a one
> way system which, because of DC protection on all (?) interface
> inputs, does not allow for CV control i.e. actual performance - to be
> recorded.
>

No. Volta is a 2-way system.
You can feed a signal from your modular (any signal) back into Volta  
and process it any way you like. That way you can for instance host- 
sync your CV's and signals with any effect (or soft-synth or whatever)  
in your DAW. Or you can record the output of your ribboncontroller and  
treat it as data. In fact, once you feed signals back into Volta it  
becomes kindof a virtual instrument. The possibilities are endless.

So, since you can feed your modular signals back into Volta, it gets  
really powerful to send these signal backs to your modular, once  
you've ehm, done things to them (in Volta).


> ... so we're still waiting for somebody to design a DC capable, CV
> recorder.
>
Why ? Volta can do this, no problem.
Your DAW becomes your CV recorder, and it's only limited to your  
available memory/HD space.

> Otherwise, even with this new VOLTA app, we're still going
> to have to use Morton Subotnik's ghost tracks method if we want to
> record actual performances of CV data.
>
This is the exact reason why I'm gonna use Volta. No more ghost  
tapes... :-)
It's no problem to record/output a whole composition with and through  
Volta, since it can use your DAW's automation system as a CV source.  
I'll be working with a 9.1 kinda-surround system soon, and you can bet  
I'm gonna use Volta to control it (over a whole composition at once).

> (I'll probably buy VOLTA when it's released though as I'm sure it'll
> be useful for lots of stuff!)
>
Volta is huge !

It's exactly what I have been dreaming of (and promoting) for at least  
10 years. It's also very similar to what I proposed as a new Doepfer  
module in the last poll... Only, Volta is much better than what I had  
in mind.

Regardless, the real power of Volta lies in it's ability to process  
signals at 192KHz rate (or whatever you DAW is capable of), which  
gives for sikly smooth and stepless CV's, even over very long  
durations. That, and the fact that you can feed everything from your  
modular back into it. Just think of all those wild things you can  
dream up with that, and still be in sync with anything you do on your  
DAW....

Altough it's already a very capable product with step-sequencers,  
endless LFO's and EG's, S/H's, S/T's, Heisenberg functions, ramp  
generators (via automation), MIDI effects on the input (real-time),  
etc... it's not finished yet. A contour sequencer will follow soon,  
and perhaps also some functions to do stuff with incoming CV's (touch  
& ribbon controllers. etc)...

And it costs no more than one module.... replacing many of them in one  
go.


Personally, I can't wait to get my hands on one.


PS. Anyone has a Motu Ultralite III for sale ? ;-)


_g




>
>
> sean
>
> >David wrote:
> >>
> >> The idea has been around for a while with a few academics in the
> >> world
> >>
> >><http://www.muffwiggler.com/forum/viewtopic.php?t=1992>http://www.muffwiggler.com/forum/viewtopic.php?t=1992
> >>
> >><<http://www.muffwiggler.com/forum/viewtopic.php?t=1992>http://www.muffwiggler.com/forum/viewtopic.php?t=1992 
> >
> >>
> >> SO had the internet :-).
> >>
> >>
> >
> >
>
> [Non-text portions of this message have been removed]
>
> 
> <!-- #ygrp-mkp{ border: 1px solid #d8d8d8; font-family: Arial;  
> margin: 14px 0px; padding: 0px 14px; } #ygrp-mkp hr{ border: 1px  
> solid #d8d8d8; } #ygrp-mkp #hd{ color: #628c2a; font-size: 85%; font- 
> weight: bold; line-height: 122%; margin: 10px 0px; } #ygrp-mkp  
> #ads{ margin-bottom: 10px; } #ygrp-mkp .ad{ padding: 0 0; } #ygrp- 
> mkp .ad a{ color: #0000ff; text-decoration: none; } --> <!-- #ygrp- 
> sponsor #ygrp-lc{ font-family: Arial; } #ygrp-sponsor #ygrp-lc  
> #hd{ margin: 10px 0px; font-weight: bold; font-size: 78%; line- 
> height: 122%; } #ygrp-sponsor #ygrp-lc .ad{ margin-bottom: 10px;  
> padding: 0 0; } --> <!-- #ygrp-mlmsg {font-size:13px; font-family:  
> arial,helvetica,clean,sans-serif;*font-size:small;*font:x-small;}  
> #ygrp-mlmsg table {font-size:inherit;font:100%;} #ygrp-mlmsg select,  
> input, textarea {font:99% arial,helvetica,clean,sans-serif;} #ygrp- 
> mlmsg pre, code {font:115% monospace;*font-size:100%;} #ygrp-mlmsg *  
> {line-height:1.22em;} #ygrp-text{ font-family: Georgia;	 } #ygrp- 
> text p{ margin: 0 0 1em 0; } #ygrp-tpmsgs{ font-family: Arial;	  
> clear: both; } #ygrp-vitnav{ padding-top: 10px; font-family:  
> Verdana; font-size: 77%; margin: 0; } #ygrp-vitnav a{ padding: 0  
> 1px; } #ygrp-actbar{ clear: both; margin: 25px 0; white- 
> space:nowrap; color: #666; text-align: right; } #ygrp- 
> actbar .left{ float: left; white-space:nowrap; } .bld{font- 
> weight:bold;} #ygrp-grft{ font-family: Verdana; font-size: 77%;  
> padding: 15px 0; } #ygrp-ft{ font-family: verdana; font-size: 77%;  
> border-top: 1px solid #666; padding: 5px 0; } #ygrp-mlmsg  
> #logo{ padding-bottom: 10px; } #ygrp-reco { margin-bottom: 20px;  
> padding: 0px; } #ygrp-reco #reco-head { font-weight: bold; color:  
> #ff7900; } #reco-grpname{ font-weight: bold; margin-top: 10px; }  
> #reco-category{ font-size: 77%; } #reco-desc{ font-size: 77%; }  
> #ygrp-vital{ background-color: #e0ecee; margin-bottom: 20px;  
> padding: 2px 0 8px 8px; } #ygrp-vital #vithd{ font-size: 77%; font- 
> family: Verdana; font-weight: bold; color: #333; text-transform:  
> uppercase; } #ygrp-vital ul{ padding: 0; margin: 2px 0; } #ygrp- 
> vital ul li{ list-style-type: none; clear: both; border: 1px solid  
> #e0ecee; } #ygrp-vital ul li .ct{ font-weight: bold; color: #ff7900;  
> float: right; width: 2em; text-align:right; padding-right: .5em; }  
> #ygrp-vital ul li .cat{ font-weight: bold; } #ygrp-vital a{ text- 
> decoration: none; } #ygrp-vital a:hover{ text-decoration:  
> underline; } #ygrp-sponsor #hd{ color: #999; font-size: 77%; } #ygrp- 
> sponsor #ov{ padding: 6px 13px; background-color: #e0ecee; margin- 
> bottom: 20px; } #ygrp-sponsor #ov ul{ padding: 0 0 0 8px; margin:  
> 0; } #ygrp-sponsor #ov li{ list-style-type: square; padding: 6px 0;  
> font-size: 77%; } #ygrp-sponsor #ov li a{ text-decoration: none;  
> font-size: 130%; } #ygrp-sponsor #nc{ background-color: #eee; margin- 
> bottom: 20px; padding: 0 8px; } #ygrp-sponsor .ad{ padding: 8px 0; }  
> #ygrp-sponsor .ad #hd1{ font-family: Arial; font-weight: bold;  
> color: #628c2a; font-size: 100%; line-height: 122%; } #ygrp- 
> sponsor .ad a{ text-decoration: none; } #ygrp-sponsor .ad  
> a:hover{ text-decoration: underline; } #ygrp-sponsor .ad p{ margin:  
> 0; } o{font-size: 0; } .MsoNormal{ margin: 0 0 0 0; } #ygrp-text  
> tt{ font-size: 120%; } blockquote{margin: 0 0 0 4px;} .replbq{margin: 
> 4} -->

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.