Yahoo Groups archive

MOTM

Index last updated: 2026-03-30 17:37 UTC

Thread

2 new Cloud demos w/'expander'

2 new Cloud demos w/'expander'

2007-09-02 by Paul Schreiber

Here are 2 more Cloud Generators showing features available with the
"Expander Module".

READ THIS FIRST TO AVOID PANIC

Both demos show how the internal parameters can be modified by the *ROTARY
ENCODERS* in real time. So, each 'detect' is a set parameter, and as we are
rotating through the sound 'jumps'. This *does not happen* with control
voltages, there will be nice smooth transitions (no zippering).

OK, now that we got that out of the way:

www.synthtech.com/m520/sine_2opfm.mp3

www.synthtech.com/m520/sqr_bwmod.mp3

The first demo is a simpe 2-operator FM patch changing the modulation index
(just like a DX-7). The second demo is a square 'cloud' that is having the
bandwidth of the noise for the chous/spread being varied.

Currently, there are ~50 different parameters that are under user control.
These can be saved as a general "patch". 6 parameters at a time are under
the rotary encoders, in 9 'pages'.

Paul S.

Re: [motm] 2 new Cloud demos w/'expander'

2007-09-03 by David Moylan

Paul, have you made any more decision regarding the digital interface to
the cloud generator? With all of these parameters being able to code a
computer based editor would seem a big plus. I know some people prefer
to keep their computer and modular segregated but I'm always looking for
more ways to use my computer with my modular.

Dave


Paul Schreiber wrote:
>
>
> Here are 2 more Cloud Generators showing features available with the
> "Expander Module".
>
> READ THIS FIRST TO AVOID PANIC
>
> Both demos show how the internal parameters can be modified by the *ROTARY
> ENCODERS* in real time. So, each 'detect' is a set parameter, and as we are
> rotating through the sound 'jumps'. This *does not happen* with control
> voltages, there will be nice smooth transitions (no zippering).
>
> OK, now that we got that out of the way:
>
> www.synthtech.com/m520/sine_2opfm.mp3
>
> www.synthtech.com/m520/sqr_bwmod.mp3
>
> The first demo is a simpe 2-operator FM patch changing the modulation index
> (just like a DX-7). The second demo is a square 'cloud' that is having the
> bandwidth of the noise for the chous/spread being varied.
>
> Currently, there are ~50 different parameters that are under user control.
> These can be saved as a general "patch". 6 parameters at a time are under
> the rotary encoders, in 9 'pages'.
>
> Paul S.
>
>

Re: [motm] 2 new Cloud demos w/'expander'

2007-09-03 by Paul Schreiber

> Paul, have you made any more decision regarding the digital interface to
> the cloud generator? With all of these parameters being able to code a
> computer based editor would seem a big plus. I know some people prefer to
> keep their computer and modular segregated but I'm always looking for more
> ways to use my computer with my modular.

Hmmm... I haven't really thought about it (having direct link from the
Expander to a computer). It could be:

a) serial port
b) MIDI port
c) USB
d) Ethernet

The added hardware cost is $10-$15 (my cost) per module, so I guess the
question to ask is:

a) who wants to volunteer to write the editors
b) is a burden cost of say $30/module worth it (everyone pays it)

This would push the planned cost of the Expander from $189 to say $219. Big
deal?

Paul S.

Re: [motm] 2 new Cloud demos w/'expander'

2007-09-03 by David Moylan

My vote is for USB or Ethernet, preferably USB. I use a laptop so don't
have a direct serial port. Midi is very standard but inherently limited
and again I'd need an adaptor. Although Midi might enable the CG to
respond to other hardware, I think the main point here is to develop a
computer to CG interface so why not use the standard computer
jack/protocols. Ethernet is cool (put your CG under internet control!),
but I think USB makes more sense overall.

I'll volunteer to write an editor (especially if it means I get hardware
early :) ). I can do it in Java which should be able to handle any of
the interface options and theoretically do it cross platform. I use OSX
so I will make sure it covers OSX as well. I'm a programmer by trade
but am more of the make-it-work type than the make-it-look-pretty type
so would be open to a collaborator on the graphic end even if just for
photoshop work.

Dave

Paul Schreiber wrote:
>> Paul, have you made any more decision regarding the digital interface
>> to the cloud generator? With all of these parameters being able to
>> code a computer based editor would seem a big plus. I know some
>> people prefer to keep their computer and modular segregated but I'm
>> always looking for more ways to use my computer with my modular.
>
> Hmmm... I haven't really thought about it (having direct link from the
> Expander to a computer). It could be:
>
> a) serial port
> b) MIDI port
> c) USB
> d) Ethernet
>
> The added hardware cost is $10-$15 (my cost) per module, so I guess the
> question to ask is:
>
> a) who wants to volunteer to write the editors
> b) is a burden cost of say $30/module worth it (everyone pays it)
>
> This would push the planned cost of the Expander from $189 to say $219.
> Big deal?
>
> Paul S.
>

Re: [motm] 2 new Cloud demos w/'expander'

2007-09-03 by Jonathan Snipes

my vote would be ethernet with control via OSC ... wouldn't require any proprietary software. could control it from almost anything.


On Sep 3, 2007, at 11:45 AM, David Moylan wrote:

My vote is for USB or Ethernet, preferably USB. I use a laptop so don't
have a direct serial port. Midi is very standard but inherently limited
and again I'd need an adaptor. Although Midi might enable the CG to
respond to other hardware, I think the main point here is to develop a
computer to CG interface so why not use the standard computer
jack/protocols. Ethernet is cool (put your CG under internet control!),
but I think USB makes more sense overall.

I'll volunteer to write an editor (especially if it means I get hardware
early :) ). I can do it in Java which should be able to handle any of
the interface options and theoretically do it cross platform. I use OSX
so I will make sure it covers OSX as well. I'm a programmer by trade
but am more of the make-it-work type than the make-it-look-pretty type
so would be open to a collaborator on the graphic end even if just for
photoshop work.

Dave

Paul Schreiber wrote:
>> Paul, have you made any more decision regarding the digital interface
>> to the cloud generator? With all of these parameters being able to
>> code a computer based editor would seem a big plus. I know some
>> people prefer to keep their computer and modular segregated but I'm
>> always looking for more ways to use my computer with my modular.
>
> Hmmm... I haven't really thought about it (having direct link from the
> Expander to a computer). It could be:
>
> a) serial port
> b) MIDI port
> c) USB
> d) Ethernet
>
> The added hardware cost is $10-$15 (my cost) per module, so I guess the
> question to ask is:
>
> a) who wants to volunteer to write the editors
> b) is a burden cost of say $30/module worth it (everyone pays it)
>
> This would push the planned cost of the Expander from $189 to say $219.
> Big deal?
>
> Paul S.
>


Re: [motm] 2 new Cloud demos w/'expander'

2007-09-03 by David Moylan

Although I have no major problem with using ethernet, I believe USB can
be done without proprietary software (via java wrappers for libusb and
libusb-win32) and the OSC protocol can be used on top of either ethernet
or usb, no? The problem with ethernet is that you have to deal with the
addressing. I guess you could assign a truly static IP but that might
not be compatible with every network setup or you would have to be able
to edit the units IP address via the encoders, then end users would need
to know how to assign their IP to be on the same subnet, etc.

Overall, I think USB tends to offer a more transparent solution if
properly implemented.

Dave

Jonathan Snipes wrote:
>
>
> my vote would be ethernet with control via OSC ... wouldn't require any
> proprietary software. could control it from almost anything.
>
>
> On Sep 3, 2007, at 11:45 AM, David Moylan wrote:
>
>> My vote is for USB or Ethernet, preferably USB. I use a laptop so don't
>> have a direct serial port. Midi is very standard but inherently limited
>> and again I'd need an adaptor. Although Midi might enable the CG to
>> respond to other hardware, I think the main point here is to develop a
>> computer to CG interface so why not use the standard computer
>> jack/protocols. Ethernet is cool (put your CG under internet control!),
>> but I think USB makes more sense overall.
>>
>> I'll volunteer to write an editor (especially if it means I get hardware
>> early :) ). I can do it in Java which should be able to handle any of
>> the interface options and theoretically do it cross platform. I use OSX
>> so I will make sure it covers OSX as well. I'm a programmer by trade
>> but am more of the make-it-work type than the make-it-look-pretty type
>> so would be open to a collaborator on the graphic end even if just for
>> photoshop work.
>>
>> Dave
>>
>> Paul Schreiber wrote:
>> >> Paul, have you made any more decision regarding the digital interface
>> >> to the cloud generator? With all of these parameters being able to
>> >> code a computer based editor would seem a big plus. I know some
>> >> people prefer to keep their computer and modular segregated but I'm
>> >> always looking for more ways to use my computer with my modular.
>> >
>> > Hmmm... I haven't really thought about it (having direct link from the
>> > Expander to a computer). It could be:
>> >
>> > a) serial port
>> > b) MIDI port
>> > c) USB
>> > d) Ethernet
>> >
>> > The added hardware cost is $10-$15 (my cost) per module, so I guess the
>> > question to ask is:
>> >
>> > a) who wants to volunteer to write the editors
>> > b) is a burden cost of say $30/module worth it (everyone pays it)
>> >
>> > This would push the planned cost of the Expander from $189 to say $219.
>> > Big deal?
>> >
>> > Paul S.
>> >
>>
>
>

Re: 2 new Cloud demos w/'expander'

2007-09-03 by strohs56k

--- In motm@yahoogroups.com, Jonathan Snipes <jsnipeslists@...> wrote:
>
> my vote would be Ethernet with control via OSC ... wouldn't require
> any proprietary software. could control it from almost anything.

My vote is also for Ethernet because:

1. you can talk to an Ethernet device with standard network protocols
(UDP or TCP) where as with USB you potentially need a device driver on
the computer end of the connection

2. like MIDI (by way of optocouplers), Ethernet (by way of pulse
transformers) has galvanic isolation = no ground loop between computer
and audio equipment

3. Ethernet allows for really long cables = computer doesnt need to be
located right next to the audio equipment to make the connection


My second choice would be MIDI but Ethernet is much cooler

-seth

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-03 by ac

Ethernet is a really really bad idea for anybody who intends to travel or tour with the module.
Having to carry around a hub and/or something to DHCP an IP to it, plus ethernet cables would all be a huge PITA.

Hey, why not make it WiFi! Or Bluetooth! Noooo!

;-)

KISS - USB or MIDI.

ac aka acronym boy

On 9/3/07, strohs56k <strohs@...> wrote:
--- In motm@yahoogroups.com, Jonathan Snipes <jsnipeslists@...> wrote:
>
> my vote would be Ethernet with control via OSC ... wouldn't require
> any proprietary software. could control it from almost anything.

My vote is also for Ethernet because:

1. you can talk to an Ethernet device with standard network protocols
(UDP or TCP) where as with USB you potentially need a device driver on
the computer end of the connection

2. like MIDI (by way of optocouplers), Ethernet (by way of pulse
transformers) has galvanic isolation = no ground loop between computer
and audio equipment

3. Ethernet allows for really long cables = computer doesnt need to be
located right next to the audio equipment to make the connection


My second choice would be MIDI but Ethernet is much cooler

-seth





Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/motm/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/motm/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:motm-digest@yahoogroups.com
mailto:motm-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
motm-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/


Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by Doug Wellington

> Ethernet is a really really bad idea for anybody who intends to travel or
> tour with the module.

Not sure I agree with that. I've been using my Looperlative LP1 with
my Macbook via a Netgear ethernet switch for performances for quite
some time. An ethernet switch isn't all that different from having a
USB hub. (Well, except it's harder to accidentally pull an ethernet
cable out!) It seems to me that more and more devices are using
ethernet all the time - check out the Muse Receptor - it uses an
ethernet connection - I know several guys who travel with Receptors.
Also, some of the new sample based orchestral production systems are
using ethernet for comms between multiple sample playback computers...

I've also used a Reactable with OSC over ethernet - it would be VERY
cool to control my MOTM with a Reactable!

Doug

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by groovyshaman

ac wrote:
> Ethernet is a really really bad idea for anybody who intends to travel
> or tour with the module.
> Having to carry around a hub and/or something to DHCP an IP to it, plus
> ethernet cables would all be a huge PITA.

Sorry not buying it.

Static IP via front panel controls -> no need for DHCP
crossover cable -> no need for hub/switch
Ethernet cables -> not bigger pain in the ass than USB cables
Ethernet == OS agnostic
Ethernet cables == longer distance than USB
USB == specific device drivers for Linux, Winbloze, OSX, ...
USB == potential ground issues

1st choice == Ethernet.

George

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by Stephen Drake

On 9/3/07, groovyshaman <groovyshaman@...> wrote:


Ethernet == OS agnostic





Maybe your definition of agnostic is different than mine. So be it. Makes me wonder... ;)


I have a bad feeling about this integration of computer and analog equipment - it seems that no matter what path is chosen, parts of the interface part of the deal is going to be obsolete in a few years, and/or software and drivers will be hard/impossible to find, and meanwhile the analog bits of all this are still going to be working perfectly. Computer systems tend to go obsolete very quickly, even when supported by the largest of companies, which isn't the case this time. Anyone remember the cassette based patch storage system that shipped with the yamaha tx81z? That was a case where "someone" had to make a decision about what kind of hardware<>software interface to use. I also think about the serial port that was on the back of my old paia proteus II - while it came with some scant documention that was supposed to be useful to potential programmers, no software was ever actually written for it according to John Simonton

That said, I'd vote for ethernet cables - they're a fairly well established, widely supported protocol. You're still going to have hardware/software issues that might be supported for a little while, but unless there's major money behind it, I'd seriously doubt if that support would last long.

A question along these lines, as I don't know nuthin' about the programming side of this - is the ethernet plug on my macbook easily accessible to a programmer who wanted to write the kind of code involved in this kind of hardware<>software interface? Is it similarly accessible on say, a standard pc type box - would the code be fairly easily portable? Implementing this interface and then only having software that works on pc's (for example) would be unacceptable to me. Would usb be more practical from a programming point of view? Midi? I'd assume that midi would be the least desireable, as it's such a slow protocol, but I could be wrong.


--
------------------------------------------------------------------
Stephen Drake
sduck409@...
makeme1witheverything@...

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by jfm3

On Mon, 2007-09-03 at 21:15 -0400, groovyshaman wrote:
> USB == specific device drivers for Linux, Winbloze, OSX, ...

Not necessarily. You could use one of the existing standard low level
data protocols. I would also worry about reliable low latency packet
delivery with ethernet. Does data need to move in performance
real-time? How much data?

--
(jfm3)

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by John Mahoney

At 10:52 PM 9/3/2007, Stephen Drake wrote:

On 9/3/07, groovyshaman <groovyshaman@...> wrote:

Ethernet == OS agnostic

Maybe your definition of agnostic is different than mine. So be it. Makes me wonder... ;)

I have a bad feeling about this integration of computer and analog equipment...


Maybe your definition of analog is different than mine. I though this thread was about the "DSP Engine"-powered Cloud Generator. ;-)
--
john

Re: 2 new Cloud demos w/'expander'

2007-09-04 by wjhall11

Whereas I suppose I can deal with however the consensus dictates, My
vote would be for midi - only because that's what nearly all my other
equipment uses - and because that's already how I control most gadgets
out of my recording / sequencing equipment.

Well - there is a big exception - my guitar stage rig is ultimately
controlled by a laptop to a Roland GT Pro via usb... the GT pro
attaches to its pedal board via midi and controls all other outboard
stuff via midi. But even so, I can control the GT pro via midi from
my sequencer if I ever needed to. Maybe that's significant.

I guess I'm trying to think of how the cloud generator would hook up
to and be controlled by my sequencer (isn't midi pretty universal?)and
how data would be downloaded (wouldn't sysex do?) in the context of my
own use.

As usual, guys, you're the engineers and are probably much more
informed about all this stuff than me - but that's how I look at it -
probably midi <shrug>

Whatever it is, thirty or so bucks isn't going to make a difference to
me about it at all... if both could be done, I'd go for it... a think
that costs a little more but is more usable is worth every cent.

So much for my two cents anyway.

Bill



--- In motm@yahoogroups.com, "Paul Schreiber" <synth1@...> wrote:
>
> > Paul, have you made any more decision regarding the digital
interface to
> > the cloud generator? With all of these parameters being able to
code a
> > computer based editor would seem a big plus. I know some people
prefer to
> > keep their computer and modular segregated but I'm always looking
for more
> > ways to use my computer with my modular.
>
> Hmmm... I haven't really thought about it (having direct link from the
> Expander to a computer). It could be:
>
> a) serial port
> b) MIDI port
> c) USB
> d) Ethernet
>
> The added hardware cost is $10-$15 (my cost) per module, so I guess the
> question to ask is:
>
> a) who wants to volunteer to write the editors
> b) is a burden cost of say $30/module worth it (everyone pays it)
>
> This would push the planned cost of the Expander from $189 to say
$219. Big
> deal?
>
> Paul S.
>

[motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by Seth Elgart

How long will all these technologies last?

USB: Been around only since 1999. Two jack styles, and one speed
change. On every computer at the moment, but for how long? And how
many of your old device drivers still work, given that operating
systems change so rapidly?

Ethernet: has been here for, what, 10 years? I don't mean in the lab,
I mean in general use. Built-in on Macs since 1993, but the first Mac
to have an RJ-45 style jack was 1996ish. (We still had some leftover
token ring going on in my office as recently as four years ago.)
Anyway, in 10 years, there have been three major changes to ethernet
speed (10Base-t, 100Base-t, 1000Base-t). They're all compatible with
each other, but the faster ones need high-speed cables. Plus, it's
being replaced by various types of fiber.

MIDI: Since 1982, unchanged, exists on almost every synthesizer in
existence for 25 years, and there are MIDI interfaces for every
computer ever made (plus, the MIDI interface makers will be
responsible for device drivers for new computers, not Paul). It's
popular now to say how the old MIDI stinks and we need something new
and better, but we all still use it every day, for everything. A
handful of synths now support USB, but -every- synth supports MIDI.
In music, MIDI is universal.

I vote for MIDI. It's the most likely to be still in existence in 5
or 10 years, and if by some miracle there's ever a MIDI 2, it will
most likely be compatible with the current MIDI. Long term, I would
think the best chance for continued use would be with MIDI.


Seth

Re: [motm] Re: 2 new Cloud demos w/'expander'

2007-09-04 by groovyshaman

Issues regarding low latency exist for most interfaces. One of the most
reliable-latency interfaces I am aware of is TDM, but we hardly want to
go that route. ;) Regarding Ethernet and latency, the biggest issues
are packet collision/retry when there are many devices on the same
subnet, and latencies introduced by switches & routers. There are
diffserv values that can be used to set packet priorities in switches &
routers. That's how VoIP phones work at all. But we could use a X-over
cable to attach directly to the Cloud and have the entire Enet to
ourselves. From there, latency would only be dependent on the hardware
Enet device implementation and software drivers in the OS - that would
also be true for USB.

In any case, I was under the impression that the Cloud Engine has analog
outputs and CV inputs, not real-time digital data stream ins/outs;
Ethernet would be for programming.

George

> On Mon, 2007-09-03 at 21:15 -0400, groovyshaman wrote:
>> USB == specific device drivers for Linux, Winbloze, OSX, ...
>
> Not necessarily. You could use one of the existing standard low level
> data protocols. I would also worry about reliable low latency packet
> delivery with ethernet. Does data need to move in performance
> real-time? How much data?
>

Re: [motm] 2 new Cloud demos w/'expander'

2007-09-04 by Scott Rider

USB. Do not use ethernet--it uses a collision-of-packets arbitration
scheme and not well suited for musical use.

Just use something like an FTDI USB serial chip, which comes with a
'free' vendor ID, works with native mac n doze serial enumeration and is
dirt cheap. I like the FT232R, myself.

http://www.ftdichip.com/FTProducts.htm#FT232R

Crow
/**/

Paul Schreiber wrote:
> Hmmm... I haven't really thought about it (having direct link from the
> Expander to a computer). It could be:
>
> a) serial port
> b) MIDI port
> c) USB
> d) Ethernet
>
> The added hardware cost is $10-$15 (my cost) per module, so I guess the
> question to ask is:
>
> a) who wants to volunteer to write the editors
> b) is a burden cost of say $30/module worth it (everyone pays it)
>
> This would push the planned cost of the Expander from $189 to say $219. Big
> deal?
>
> Paul S.
>
>
>

Cloud Generator / Morphing Terranium

2011-09-23 by Miguel Mendoza

Hello, I'm wondering if these modules will be ever available in 5U. Shall Bridechamber have 2.0 boards and front panels? will they be available directly from Paul?

Tired of waiting...

Cheers!

Re: [motm] Cloud Generator / Morphing Terranium

2011-09-23 by Jeff Laity

I agree, but he said not in 2011, possibly 2012.

In case anyone here doesn't know about it, this forum is much more active than this mailing list for news about MOTM:





On Sep 23, 2011, at 10:55 AM, Miguel Mendoza wrote:

Hello, I'm wondering if these modules will be ever available in 5U. Shall Bridechamber have 2.0 boards and front panels? will they be available directly from Paul?

Tired of waiting...

Cheers!


NOTICE: This electronic mail message and its contents, including any attachments hereto (collectively, "this e-mail"), is hereby designated as "confidential and proprietary." This e-mail may be viewed and used only by the person to whom it has been sent and his/her employer solely for the express purpose for which it has been disclosed and only in accordance with any confidentiality or non-disclosure (or similar) agreement between TEAC Corporation or its affiliates and said employer, and may not be disclosed to any other person or entity.