ComputerVoltageSources

Hi there,
my posting obviously was a bit misleading:
I'm just pondering over digital interfaces other than MIDI, USB, RS232, 
etc.
It's not my intention (for the time being) to involve a computer w/ Max 
or such. Connecting a controller which supports OSC could be a 
application, for instance.
I'm saying this to leave some doors open, or IOW you get my vote for an 
"open system" (whatever the precise definition will be).

   ;-) Michael. (off to the airport)


drmabuce wrote:

> Hi Michael
> --- In ComputerVoltageSources@yahoogroups.com, "Michael Zacherl (aka
> TonTaub) " <egroups@...> wrote:
> 
>>Anyone cares about OSC (Open Sound Control)?
>>I didn't dig into this so far but my co-musician is using that between 
>>his Lemur and Max/MSP on a PowerBook with great success.
>>
>>http://www.cnmat.berkeley.edu/OpenSoundControl/
>>
>>In our case OSC <-> CV is more likely the target configuration.
>>
> 
>  http://www.smartcontroller.com.au/smartController/smartController.html
> 
>>(also have yet to read it)
>>
>>Just a thought, 
> 
>  
> these are good topics to keep in mind....
> MBASIC code is not going to be everyone's cup of tea.
> Graphic "connect-to-dots" environments are a very attractive
> alternative to obsessing about the loading precedence of C include-libs!
> 
> In collaboration with some buddies, i have tinkered with gadgets that
> finagle CV's out of MAX MSP. National Instruments makes low-end Data
> Acquisition I/O boxes that, with LabView software, can do some very
> good tricks. The advantage is the intuitive nature of the graphic
> programming interface.
> 
> Here are the points i see that must be considered  
> 
> These solutions tether the hardware to a PC. Is the additional
> 'overhead' worth it to the user?
> 
> (speaking from my experiences with MAX MSP) I compare graphic modular
> development and low-level code development to the difference between
> writing a poem with 400 of theose magnetic refrigerator words and
> writing a poem with a typewriter. 
> Both can yield good poetry.
> 
> But having used the typewriter for many years , i prefer it. I always
> end-up feeling a little hobbled by biases that the designers of
> 'elements' build-in to them.
> Add that to the worry about the sheer number of tiny moving, humidity
> -sensitive parts in a laptop and the DIY'er in me just sorta takes over!
> ;'>
> 
> but that's just me,
> 
> I'm sure that BasicMicro ain't ABOUT to write a graphic code
> development environment for the BasicAtoms....  but somebody (with a
> lotta time on their hands) could!
> 
> i think it's worthwhile  to ask how many folks would prefer graphic
> development to low-level MBASIC or C or Forth coding.***
> The number might justify the effort of a (ie) graphic-to-MBASIC
> compiler .... to someone!
> 
>  
> 
> That's my  $.04
> 
> best
>  -doc