[sdiy] Re: [AH] UIs and GUIs - Re: Tetra You Tube demo

[cheater cheater]

I would rather have a few hot lab assistants with perfect bodies,
wearing labcoats and stilettos

although it depends on the synth

I could have a lab in the living room with the 'lab pets' and then
have a gimp in an austrian-built dungeon downstairs with some
metasonix things all around and some tesla coil transducers at that

he could wear a leather mask and I could feed him raw meat

or how about a bavarian version with 5 lederhosen clad bavarians
playing in formation, kinda like Kraftwerk?

D.

On Thu, Aug 13, 2009 at 4:39 PM, Scott Fox<bagofskin at gmail.com> wrote:
> You could also ask for a gimp that you can let out of the box to move patch
> cables at the point if a finger...;)
>
> On 2009-08-13, at 9:28 AM, Greg Morgan <greg.morgan at gmail.com> wrote:
>
>> Here is what I am looking forward to:
>>
>> An ethernet-based (FCOE?) standard to replace MIDI.
>>
>> Then I want a standardized "hardware control interface" so that my hundred
>> of awesome little ethernet-based modules can be mounted into racks, and I
>> can call up each module in my HCL, that could be a euphonix-type
>> controller
>> connected to a PC, or some standalone device, whatever. Give it a sound
>> card
>> with DC-coupled outputs and embed the Volta into it so that I can control
>> my
>> analog modules.
>>
>> Hell, connect it to a studio console that uses the same technology to
>> connect to outboard effects, compressors and whatnot.
>>
>> It sucks having to learn a new UI with every synth. "patch" it out to a
>> control system and focus on making the internal routing possibilities as
>> flexible as possible, I mean, how much development work goes into figuring
>> out how the knobs will work? If you as a designer could just pop that out
>> to
>> an embedded ASIC that speaks FCOE or Ethernet would it give you more time
>> to
>> work on more groundbreaking things?
>>
>> Greg
>>
>> On Wed, Aug 12, 2009 at 5:36 PM, Mark Pulver <mark at midiwall.com> wrote:
>>
>>>
>>> Yeup.. that was my point with that example. It's a prime case of someone
>>> that would be a Tetra customer.
>>>
>>> The librarian functions of software (in general, I dunno what the DSI
>>> stuff
>>> is like) will far exceed whatever could be grafted into an embedded
>>> platform. Plus, the session player can (will/does) work out sounds at
>>> home
>>> where he can sit in front of a computer clicking and dragging away.
>>>
>>> I think this is Tetra's prime audience, and I'm thinking Dave saw it that
>>> way as well. The most used "session" knobs are right there on the box.
>>> Cutoff, Resonance, Attack, Decay/Release.
>>>
>>> -----
>>> John Mahoney (03:23 PM 8/12/2009) wrote:
>>>>
>>>> This is a very good example of a user's needs, but it's essentially
>>>> the setup/headaches issue, again. And, consider the other side of it:
>>>> A session player could travel with a slew of Tetra-sized boxes if
>>>> they all used one PC for their programming interfaces; add to this
>>>> the superior searching and storage options provided by software, and
>>>> there's a good case to be made for the Tetra model.
>>>>
>>>> At 05:49 PM 8/12/2009, Mark Pulver wrote:
>>>>
>>>>> - Studio session players. They want to walk into a studio session
>>>>> with a minimal amount of gear, all preloaded with their portfolio.
>>>>> Minimal programming will be done at the session. Computers are used
>>>>> only for the MIDI NOTE ON/OFF interface.
>>>
>>>
>