om-synth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Om-synth] Re: Om problem, today's CVS


From: Dave Robillard
Subject: [Om-synth] Re: Om problem, today's CVS
Date: Sat, 25 Feb 2006 22:11:29 -0500

On Sat, 2006-25-02 at 07:48 -0500, Dave Phillips wrote:
> Dave Robillard wrote:
> 
> >>Thanks for the help, Dave, and thanks for Om. :)
> >>    
> >>
> >
> >No problem, let me know how it goes.  CVS is a little hectic right now,
> >getting all the features finished up for the 0.3.0 release, so don't
> >take bugs in CVS to be indicative of the stability of releases. :)
> >
> >I think I'll be able to eliminate this damn /etc/hosts alias requirement
> >as well (the fix will accompany the ability to work through NAT, which
> >is also nice).
> >
> >Unfortunately the example patch selection is a bit weak right now, but
> >you should be able to get the idea.  You might want to check out
> >http://atte.dk/om-wiki/UserSuppliedPatches for some other people's
> >patches (be warned you may need to add a MIDI input yourself on some
> >older ones though, due to a change since version 0.2.0)
> >  
> >
> Hi Dave:
> 
>   Just a quick note to say how I've been getting along with Om. It's 
> working fine, no outstanding issues, and its sound is excellent.

Good to hear

> Yes, it 
> needs more patches. I'd like to help out and design some, but my time is 
> socked. I had hoped to make some patches for Sean Bolton's WhySynth too 
> but I just don't have the time. I suggested to Sean that he consider 
> building a patch randomization utility into WhySynth. Would something 
> similar be possible in Om ? Seems like it kind of goes against the grain 
> of its design, but it doesn't hurt to ask. :)

Statistically speaking, the chances of generating a patch that actually
produces noise (let alone pleasant noise) are pretty much zero :)

If it's completely random anyway.. if it were much more clever, you
never know.  Playing around with stuff like this should be pretty easy
with the Python or SuperCollider bindings at least...

I'm talking about randomly generating patches themselves (ie loading
plugins and connecting them up) though.  Do you mean parameter
randomization (ie random knob twiddling)?  That wouldn't be very hard at
all (and I do need to add the concept of 'presets' anyway..)

-DR-





reply via email to

[Prev in Thread] Current Thread [Next in Thread]