Support
Looper's Delight
|
Support |
|
|
Hmmm, that's surprising. Maybe this is one thing Usine can do that Bidule can't. Usine has low level math modules that should make a division between the LFO speed and Usine's internal clock straightforward. I haven't tried it, I just looked it up in the manual. And hey--there' s another point in Usine's favor--It's got a good manual in .pdf form. I've got to say that the recent discussion on Bidule's audio switcher really intrigued me. Since Bidule has independent sync generators (with independent tempos) and since with the audio switcher the chains that aren't in use apparently don't bog the cpu down, it's seems to me like you could have one Bidule patch for an entire live show. Very, very cool. On 11/4/06, Per Boysen <perboysen@gmail.com> wrote: > > 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 > > > > -- Art Simon simart@null.net http://art.simon.tripod.com http://www.myspace.com/artsimon