PlanetZ forums - scopeusers.com

Which ASIO driver should I use with Bidule? I've tried "ASIO Source," "ASIO 24-bit Source" and a few others. Thanks.

i use the asio2 24bit source and asio2 dest, but any proper pair would work.

bidule is a little tricky to make work the first time. after that it's easy. if bidule(or any asio host) crashes, it will hold on the the asio driver which will not be available again before reboot. this is because of the way that asio functions making, as it were, a locked connection between hardware and software. this is the purpose of the "release driver in backround" function on steinberg apps allowing more than one app to use the asio driver, but i suspect you know all this.

the first time with scope, open bidule, remove the default bidules and put the creamware bidules(asio scope duplex and creamware midi) and then make this the default project(edit/makedefault project). restart bidule and everything should work. i've found that if bidule starts with the default modules which access systems that won't be available with a scope card, bidule disables all it's ports, bother. after making the default project with available ports, everything seems to work great from then on.

sorry if i went into more detail than needed or told you things you already know, i just felt like typing for a change....

btw- just in case..the proper modules for bidule(sequencer midi source and dest, and asio source and dest) must be in your scope project with the proper number of i/o channels before opening bidule!

GaryB is correct as usual as he found the bug which proves that Muse and GVI share the same unique ID which won't allow both dll. files to run simultaneously.

Plogue is working w/ Tascam for a fix, as they fear my postings on several forums. Actually, they know I will post their excellenet customer service contributions and generate a few sales, as well as steal some K2 guys and bring 'em over, as there are many unhappy K2 buyers on the forums.

Their sniveling is a constant source of depression, as well as irratation.

Cool, I will try this over the weekend.

scope4live, you're about to get the flaming sword in the battle of software samplers. We're posting a white paper that is going to drive the Kontakt and Halion guys to sob in their litterboxes.

open bidule, remove the default bidules and put the creamware bidules(asio scope duplex and creamware midi) and then make this the default project(edit/makedefault project). restart bidule and everything should work.

I finally had to save a blank Bidule project as my default. Now it seems to work, thanks.

When I launch Bidule, I get the message, "XTC plug-ins are not available while another Creamware application is running." How do I get rid of the XTC plug-ins? I don't see them in my VST folder and don't intend to use them.

no problem,
on the scope live bar, go to set/settings/general and uncheck "enable xtc mode". message disabled.....