PlanetZ forums - scopeusers.com

I am attempting to integrate Sonar 5.2 and Adobe Audition 2.0, but each appears to require exclusive use of the Creamware ASIO 2 24 bit driver. Has anyone else encountered this problem and/or figured out a way around it? I seem to remember that driver sharing is not part of the ASIO standard, although it is enabled in some driver implementations - perhaps not in Creamware's.

Regards,

Mike

usually 'multiclient drivers' refers to a situation where one application uses ASIO and another WDM.
One would prefer a sharing based on ASIO pairs, but obviously that has never been implemented (afaik)

cheers, tom

Only if you have the capability to deactivate the input or output in your host (and the host must release the i/o).

use wav drivers for audition and everything will integrate nicely. latency won't be an issue if you minitor on the scope mixer and don't use dx or vst instruments in audition.

More hints.

If you're looking to record output from Sonar, record it back INTO sonar onto a new track. Disable software monitoring or mute of course. This always works far far better than recording into a different app imo, regardless of your DAW application.

Secondly, if you experience dropouts with Audition using wav drivers while running Sonar with ASIO drivers, there's an output preload slider you need to adjust. Getting to it will probably require asking for directions (and stopping by the cafe on the way for a cuppa).

Thanks for the suggestions folks.


A couple of further comments:

Sonar has a "share drivers with other applications" option, but it doesn't seem to work in this instance.

I'm using Audition for per track editing - I prefer the interface to the Sonar audio editing view - so I'm not trying to mix-down to Audition. For mixdown I go (multitrack through Scope tools and out to a new track in Sonar, as suggested in one of the replies (Valis I think).

The problem arises because Audition 2.0 comes with the recommendation to use ASIO drivers. I understand from previous threads that the Scope WDM drivers are not as good as they could be, in any case.

However, I have a cunning plan - I also have a Tascam control surface which also has a 24 bit ASIO interface and an SPDIF output. So in the new world Sonar multitracks via Scope ASIO 24 bit, and Audition edit view outputs stereo to Tascam ASIO 24 and back into Scope via SPDIF. So long as I have the Tascam slaving its timecode from the scope SPDIF i/f this should get round my problem.

I'll let you know how I get on. Where's this cafe, I fancy a cuppa...

Cheers,

Mike

Mike, you're nuts, go back to writing SOS reviews or whatever you do for a living.

it could be good, if audition runs in rewire slave mode, as other applications such as melodyne.

Audition should actually work fine with the internal WDM Wave driver (24bit). Audition is 'recommended' with ASIO because Audition(aka CoolEdit pro) assumes you'll use it to multitrack audio recording from multiple inputs at the same time. You shouldn't have any issues with the CW Wave drivers instead (other than being limited to stereo i/o).

The only other issue you might have is the ULLI latency of your ASIO driver being set way too low for the CW WDM Wave drivers. There's a slider called "Output Preload" that I suspect increases the NUMBER of buffers (whereas ULLI sets the buffersize) for the WAV drivers. Getting to it is a bit convoluted as its buried under the properties tab for your Creamware card (accessed either from device manager or in Sounds & Audio devices, under the 'hardware' tab). You set the number of midi ports in a different section on the same properties tab..

I don't think the output preload slider is well documented by Creamware unfortunately.

On 2006-04-21 17:27, Shroomz wrote:
Mike, you're nuts, go back to writing SOS reviews or whatever you do for a living.

Someone called Shroomz from Liberty Cap is calling me nuts.... How can I live this down?

I've used audition 1.5 together with Cubase SX for many years, never had WDM-driver problems.

After recording (cubase), i delete the wave-files from pool, import to Audition; edit and rename them, drag/import the "new" files back to cubase.

(i admit; i hate names like xxx_01.wav)

<font size=-1>[ This Message was edited by: arela on 2006-04-25 23:17 ]</font>

Folks, thanks for all the useful suggestions and advice...

Much appreciated!

Mike