Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: Bidule (was: MAX/msp question)

> At 23:00 04/11/2006, you wrote:
>> Can't find any LFO's to drive parameter values from in
>> Bidule, though. Guess I'll have to make those things with Max?
>
> they're there somewhere,
> just keep looking.
> (don't remember where..sorry...but I have used them)
>
> I think you'll actually be able to do in Bidule anything you wanted  
> to do in max.
> (as long as you have a few vst plugs as building blocks)
>
> andy


There is a "LFO" among the Groups. But there is no way to set a  
division between this LFO's speed and Bidules internal sync clock.  
That's bad. It's a little disappointing with Bidule that they have  
designed this internal tempo clock but no object for mathematical  
division of it. As a comparison you can look at the OSX host  
application Numerology where every parameter of any loaded AU plug-in  
is directly accessible as a target for the internal control data (Num  
still lacking random generator though).

Greetings from Sweden

Per Boysen
www.boysen.se (Swedish)
www.looproom.com (international)
http://tinyurl.com/fauvm (podcast)
http://www.myspace.com/looproom