Plogue Bidule
Plogue Bidule
I decided to get Bidule as a standalone app. in hopes of running VSTi's, and Creamware together in what appears to be a totally modular looking enviroment.
Brotha' Man Valis has spoken highly of it, and he always has given great advice here. Also, a new member synthetic88, who I know to be a fierce warrior has also told me how well GVI runs on it, so my problems w/ Cubase 4 being my live host, I hope will be over. I would rather use it as a recording app., where I know it excells.
Does anyone here use Bidule w/ Creamware?
I have just started it up and it already has a Creamware module displaying it's noble name.
Thanks,
Brotha' Man Valis has spoken highly of it, and he always has given great advice here. Also, a new member synthetic88, who I know to be a fierce warrior has also told me how well GVI runs on it, so my problems w/ Cubase 4 being my live host, I hope will be over. I would rather use it as a recording app., where I know it excells.
Does anyone here use Bidule w/ Creamware?
I have just started it up and it already has a Creamware module displaying it's noble name.
Thanks,
in the realm of modular vst hosts there is energyxt (http://www.energy-xt.com/) and console (http://www.console.jp/en/about/about_1.html). both are very cheap and have worked quite well for me together w/ scope. ext also has (at least from what i have read) a quite extensive 'live mode' which i have not explored personally.
i have used bidule brielfy on the powerbook and it seemed very nice too. having a modular interface to load vst ints/effects and route asio is much more intuitive to me than doing so in an app like cubase. much better workflow, especially if you dont intend to use the host sequencer ie.playing live...
yeah.
i have used bidule brielfy on the powerbook and it seemed very nice too. having a modular interface to load vst ints/effects and route asio is much more intuitive to me than doing so in an app like cubase. much better workflow, especially if you dont intend to use the host sequencer ie.playing live...
yeah.
Honestly I think in many ways console and EnergyXT are more straightforward for most uses. EnergyXT has the added benfit of actually being useful to non-gurus in its vst plugin mode (Bidule is very bare bones and u must load projects you built externally to make sense of it).
Personally I prefer Bidule because I think it's a bit more abstracted and offers more low level tools. It's actually missing some of the higher levels tools that the other 2 do, in the sense that things like the dedicated sequencer UI's that include all functions you'd want to do in simple menu commands. Instead in Bidule you get a few simplfiied sequencing modules which are really quite bare, and it seems overly simple and lacking in functions until u start to dig into Bidule and realize that with all of the low levels tools you can do things that aren't really possible anywhere else. For instance to quantize an imported midi file you will want to use a few modules chained together rather than setting a UI dropdown menu or menu command.
And by abstration I mean not only the low level tools that u can combine to achieve higher order functioins, but also things like the fact that there is no central timebase (every device can generate & recieve its own sync). The fact that it makes a quick & dirty VST shell is an added bonus.
There was an interesting discussion here as well:
http://www.analogindustries.com/blog/en ... 0487741988
Personally I prefer Bidule because I think it's a bit more abstracted and offers more low level tools. It's actually missing some of the higher levels tools that the other 2 do, in the sense that things like the dedicated sequencer UI's that include all functions you'd want to do in simple menu commands. Instead in Bidule you get a few simplfiied sequencing modules which are really quite bare, and it seems overly simple and lacking in functions until u start to dig into Bidule and realize that with all of the low levels tools you can do things that aren't really possible anywhere else. For instance to quantize an imported midi file you will want to use a few modules chained together rather than setting a UI dropdown menu or menu command.
And by abstration I mean not only the low level tools that u can combine to achieve higher order functioins, but also things like the fact that there is no central timebase (every device can generate & recieve its own sync). The fact that it makes a quick & dirty VST shell is an added bonus.
There was an interesting discussion here as well:
http://www.analogindustries.com/blog/en ... 0487741988
^^this is all true.
i would like to spend some more time w/ bidule at some stage, it did seem like a very nice app. i do think though, if one was using bidule to actually compose music (as opposed to just processing vst's, or building synths/effects) it could easily end up sounding like some 'idm' noodle type stuff. i mean i think it would be difficult to coax something musical out of it, although of course that would be possible.
i would like to spend some more time w/ bidule at some stage, it did seem like a very nice app. i do think though, if one was using bidule to actually compose music (as opposed to just processing vst's, or building synths/effects) it could easily end up sounding like some 'idm' noodle type stuff. i mean i think it would be difficult to coax something musical out of it, although of course that would be possible.
Well I think it depends on your method of composition. If you're a mouse-driven producer then yes I believe you could wind up with something 'noodly and idm-y' very easily. But if you're a live synth player as Scope4live is I can see setting up some rather incredible things that happen with each note press. Modulations and interactions that would even make John Bowen's creations blush. Also it should be clear that I use several machines here in my studio and Logic is my primary sequencer of choice. Bidule is one of the additional tools that I use. It's especially handy on my laptop when I am not running Live on it for quick edits.
-
- Posts: 134
- Joined: Fri Apr 06, 2007 9:48 am
Which ASIO driver should I choose in Scope for Bidule? I see:
ASIO 24 Bit Dest
ASIO Dest
ASIO1-16 Dest 64
ASIO1-32 Dest 64
ASIO1-Flt Dest 64
ASIO2 24 Bit Source (but not dest)
ASIO2 Dest
ASIO2 Dest-64
"ASIO 24 Bit Dest" and "ASIO2 Dest" don't show up as audio devices in Bidule. I only get MME drivers popping up.
ASIO 24 Bit Dest
ASIO Dest
ASIO1-16 Dest 64
ASIO1-32 Dest 64
ASIO1-Flt Dest 64
ASIO2 24 Bit Source (but not dest)
ASIO2 Dest
ASIO2 Dest-64
"ASIO 24 Bit Dest" and "ASIO2 Dest" don't show up as audio devices in Bidule. I only get MME drivers popping up.
I think you mean ASIO2 24bit Source and ASIO2 Dest as a pair, right? If so then it works fine here. When Bidule starts just delete the instance of "Microsoft Sound Mapper" and then add ASIO from Audio Devices > Duplex > ASIO > ASIO SCOPE (duplex)synthetic88 wrote:"ASIO 24 Bit Dest" and "ASIO2 Dest" don't show up as audio devices in Bidule. I only get MME drivers popping up.
Works fine here.
-
- Posts: 134
- Joined: Fri Apr 06, 2007 9:48 am