Bidule seems really cool and i love all the variaitions and possible combination of crazy sound one can get out of it, but i'm curious on how people really use it and integrate it into their workflow.

do you just record like a 5 minute "jam" and cut that up?
or use a recorded sequence and take it into a another multi-traker program, then build on that?

or possible use the LSR Free vst and record out 1 or 2 bar loops and build trks that way?

do people make whole trks with Bidule or just sound snippets that they take and build trks with in other programs?

i wish it could be used as a VSTi like Chainer within another program

i'd like to hear how some of you power users use this gem.

thanks
-k-

Kusser, you naughty multi-poster, you! I just posted a lengthy list of suggestions to your identical question in the other thread on Bidule right now, but I'll describe another one of my methods here.

I like using the multi-channel Audio File Recorder and Player bidules for multi-tracking songs.

E.g., I start with an 8-channel Audio File Recorder bidule. I'll record one instrument into the first channel. Then I'll load that WAV into an 8-channel Audio File Player bidule, and with the first channel playing, record a new instrument overtop into the second channel of the Recorder bidule.

And so on, until I'm satisified with the number of layers. Then I just take the completed 8-track WAV file, load it up into Audacity (which can handle more than 2 tracks at once) and edit as needed.

Now, all I have to do is learn to actually finish a song this way.
-K

heheheh
i felt bad about hi-jackin someone elses thread....

Quote:

Now, all I have to do is learn to actually finish a song this way.

yea. thats what i mean. there are a super amount of cool tools and toys that make friggin awesome sounds, but its being able to take the resulting output and say....make a chrous or hook out of it.

havent went back to the other thread yet, but i'm thinkin of using the Lrs Free to export little 2 bar loops and constructing choruses, verses, riffs, and hooks that way.

but, man, sound exploartion is fun......

-k-

DOH!

you already suggested LSR Free.

good one!

when it becomes a plug-in, i'm just going to go all mad scientist-like and have Cubase--> Chainer--> Bidule-->Chainer---> Reaktor

MUGWHAHAHAHHAHHHA!

thanks

-k-

I fought with this myself just last night.. I really sat down in an attempt to explore Bidule in depth last night (until almost 4am!!). It really is a wonderful program.. but I asked myself the same question... like how can I integrate this into my main host. The day it becomes a VSTi is the day that I think I'll really be able to unleash it's potential.. as I really hate bouncing stuff then going from one host to the next..

What I'd really like to do with Bidule is build some kinda project that is a huge drum/break programming mangler.. just the fact that every parameter on the thing can be linked in some fashion would lead me to believe this is more than possible.. but it requires a great deal of thought.

ModuLR wrote:

What I'd really like to do with Bidule is build some kinda project that is a huge drum/break programming mangler..

Heh. This reminds me of a small trick I came up with in Bidule the other day. Essentially, a way to constantly mutate a plugin's parameters. For example, you could make a perpetually-changing series of breaks using SupaTrigga.



Connect the following bidules as shown above. Open the Parameters dialog box, and link the Parameter Modulation [Modulation] parameter to the SupaTrigga [Mutate] parameter.

What happens is this: at the beginning of every bar, the Sync Extractor bidule sends a trigger to mutate all of SupaTrigga's parameters. You can open SupaTrigga and use the Parameters Properties dialog box to lock certain parameters from being mutated, or to define the range within each parameter will mutate.

For example, I like to restrict the Granularity to values between 4 and 32 slices (0.275 and 0.700, respectively, in the Parameters Properties) with a mutation factor of 35%, so the break never gets completely out of control.



Once Bidule is available as a VSTi, you'll be able to use this as an effect and pipe a whole track through it - all synched to host tempo, and you'll never hear the same break twice. That should be fun.
-K

kyle, you madman!


oh, the right URL is http://www.smartelectronix.com/~bram/ by the way

- bram

dam, Kerrydan, that sounds like a bomb-ass idea.

i use Supatrigga almost religously myself.
i'm still figuring out what ports can be plugged into what ports on the seperate bidules.

when i get home , i'm gonna try a (drum machine and audio looper) both running thru Metal Mickey and Suppatrigga.

i think my first experiment will be to see if i can get a decent drum trk out of this combo. then take the output and chop out drums for the verse, drums for the chorus, and various breakdowns; then port all that into maybe ACID to lockdown the tempos.

thanks for the info.

-k-

any idea onthe timeframe for the portover to plug-in format?

That is a really a cool idea there... I'll be exploring aspects of that with supatrigga (naturally one of my favorite plugs)!

So hey... Kerrydan or any other resident dsp type care to explain the results of applying basic mathematic functions to audio? I'm just starting to get my feet wet with this dsp stuff, so what is really happening if I +,-,/,* two streams of audio together. I can hear it distort at times, or the level change.. but I really have no idea what I'm doing. Anyone care to share some knowledge?

not much help but ill offer my limited knowledge -

adding two audio streams does just that - a 50/50 mix

multiplying is [afair] ring modulation

beyond that im as blank as you are really

slainte rob