next »

[nadia]

Hi 

I need a suggestion about a way to resolve an issue.

Suppose that you have a sound card which supports both ASIO and DirectSound.
If I call BASS_Init on that sound card and then call BASS_ASIO_Init on the same device, I'm able to load a playback stream through BASS_StreamCreateFile but if I try to put it in playback through BASS_ChannelPlay it will fail returning a BASS_ERROR_BUFLOST error.

Although I can understand that a single device cannot manage using ASIO and DirectSound at the same time, I would like to have an advise about which would be the correct way to manage the situation in which I need to access a certain device alternatively in ASIO or DirectSound: the main problem is the fact that I have now way to say that a certain DirectSound device, enumerated through BASS_GetDeviceInfo, is the same physical device enumerated through BASS_ASIO_GetDeviceInfo.

Any suggestion would be more than welcome.

Kind Regards 

Nadia

[radio42]

As far as I can see you can still initialize both devices (BASS_Init and BASS_ASIO_Init), but you should avoid calling BASS_ASIO_Start on a device which you like to use with DirectSound.

[nadia]

As far as I can see you can still initialize both devices (BASS_Init and BASS_ASIO_Init), but you should avoid calling BASS_ASIO_Start on a device which you like to use with DirectSound.

Hi 
Yes, you can initialize both devices, but I cannot play on the DirectSound device if I have called BASS_ASIO_Init on the same device: BASS_ASIO_Start is still not being called at all at this point.

Kind Regards 

Nadia

[radio42]

OKi, I didn't know that - then this is really an issue!

[nadia]

Hi 

any suggestion at all? 

Kind regards 

Nadia

[radio42]

Hi Nadia,

I just double checked it here with a M-Audio Delta1010 card - which also comes with WDM and Asio drivers.
I first initialized the card with BASS_Init and then with BASS_ASIO_Init.
After that I am able to either use the normal BASS system or ASIO...of course not both in parallel.
But I can easily switch between the two models without any problems.

So might it be a certain card where your issue occures? Or might it be a driver issue?

[nadia]

Hi Nadia,

I just double checked it here with a M-Audio Delta1010 card - which also comes with WDM and Asio drivers.
I first initialized the card with BASS_Init and then with BASS_ASIO_Init.
After that I am able to either use the normal BASS system or ASIO...of course not both in parallel.
But I can easily switch between the two models without any problems.

So might it be a certain card where your issue occures? Or might it be a driver issue?

Hi 

probably you are right: that could be a driver issue.
I made my test using an Aureon 7.1 Universe and the behaviour is the one I described in my original post.
This morning I tried making the same test using a Numark DJ IO card and I was quite surprised about results: not only it will work as you described, but you can also play both channels (DirectSound and ASIO) at the same time on the same device: this shocked me a bit 

It would be interesting to know if other users experienced similar issues with other ASIO aware sound cards...

Kind Regards 

Nadia

[Ian @ un4seen]

From what I've seen, Creative Audigy/X-Fi drivers allow simultaneous ASIO and DirectSound output (presumably input too). The Asus Xonar drivers appear to do so too.

[WarMacre]

In my experience of using Multi-Track Audio applications, you can only normally select one driver, ASIO or Multimedia/DirectSound, etc.

The driver for your Aureon may be locking-out all other driver options once one has been chosen and loaded. Your drivers may not support multi-client access, but 3rd party drivers (ala ASIO4ALL) may allow you to override this feature.

[nadia]

Hi 

In my experience of using Multi-Track Audio applications, you can only normally select one driver, ASIO or Multimedia/DirectSound, etc.

Yes, I've seen that certain application, like Traktor Dj, don't allow selecting more than one output driver: this certainly simplifies a lot.

The driver for your Aureon may be locking-out all other driver options once one has been chosen and loaded. Your drivers may not support multi-client access, but 3rd party drivers (ala ASIO4ALL) may allow you to override this feature.

This is an interesting point: do you mean that faulty drivers could be replaced for example by ASIO4ALL? Or only sound cards which don't support ASIO natively can make use of ASIO4ALL?

Kind Regards 

Nadia

[WarMacre]

I believe that both sound cards that don't support ASIO and ones that do can reap benefits from a 3rd Party Application like ASIO4ALL. Obviously, the driver supplied with your soundcard is designed to work with your soundcard and ASIO4ALL may not work with some soundcards and maybe be limited with those that is does work with.

However, the whole idea behind ASIO4ALL is to enable capabilities in hardware that the existing drivers may not allow, for whatever reason, whether it be compatibility or deliberate limitation for marketing purposes, i.e. your Soundcard maybe exactly the same as a model above, except that the better version comes with different drivers to enable more features, etc.

[radio42]

And...just to complete it...ASIO4ALL or other use KernelStreaming internally.
KernerStreaming is quite efficient, but a well designed hardward based ASIO driver an leverage the soundcard often much better.
In essence, all depends of the quality of the origin ASIO driver/soundcard. This is also the reason, why some some ASIO drivers might limit the capability to use other drivers in parallel.