4.1 WASAPI Init Error

Not sure if this a bug, hardware limitation or a config issue. (Windows 7 SP1 64bit)

I have the Delta 1010LT Card, so I imported my old 4.0 config, and then set the order as follows:-

Player 1 = WASAPI Line 1/2 (Delta 1010LT)
Player 2 = WASAPI Line 3/4 (Delta 1010LT)
Cartwall = WASAPI Line 5/6 (Delta 1010LT)
PFL = WASAPI Line 7/8 (Delta 1010LT)

Player 1 initialized and played fine, all the others (including the 12 slots on the cartwall) showed BASS_WASAPI_init error -1. If I dropped Player 1 to ASIO, still got the same result. It looks like BASS can’t initialize other players than 1/2.

Moved all to ASIO and we’re good.

I moved back to DirectSound. I was getting some minor distortion/clicks in ASIO in the VT tool and I had little time to experiment with the settings. :slight_smile:

Hm, -1 is the infamous “mystery” error.

On Windows 7, DirectSound is only a wrapper for WASAPI, so if the card works in DirectSound mode, it should work in native WASAPI mode as well. Perhaps it needs a little tweaking, or there is something wrong in BASSWASAPI.

Does the card provide a single virtual device with multiple speakers, or a separate virtual device for each speaker pair? (You better check that on the WASAPI or DirectSound page in mAirList.)

Regarding ASIO, you probably have to put up the buffers a bit.

[quote=“Torben, post:3, topic:7778”]Does the card provide a single virtual device with multiple speakers, or a separate virtual device for each speaker pair? (You better check that on the WASAPI or DirectSound page in mAirList.)

Regarding ASIO, you probably have to put up the buffers a bit.[/quote]

It reports each pair of outputs as seperate device. I’ll double-check when I get a chance this weekend. I’ll probably play around with the buffers too in ASIO.

I will try to put together a small WASAPI test application. Or perhaps there is already one in the BASSWASAPI archive.

This is what I see when I select audio devices. The Info button on Wasapi in Audi Settings doesn’t show anything.


audio.png

If that’s what you’re choosing, try the option below that one (front 1/2) and let us know if that works any better. :wink:

A little bell just rang vaguely in the back of my head. I’m sure Torben once mentioned that sometimes you need to choose the non-‘default’ version of channels on some sound cards. Just a hunch, but worth a try IMHO.

BFN
Cad

I got the same problem with my M-Audio 440 card and a M-Audio 66 in the same system. After configuring the sound cards everything seems to work. But if I start another player at the same time mAirlist gives an error (I did send a bug report :)) and WASPI isn’t working anymore, even after a reboot.

[quote=“Cad, post:7, topic:7778”]If that’s what you’re choosing, try the option below that one (front 1/2) and let us know if that works any better. :wink:

A little bell just rang vaguely in the back of my head. I’m sure Torben once mentioned that sometimes you need to choose the non-‘default’ version of channels on some sound cards. Just a hunch, but worth a try IMHO.

BFN
Cad[/quote]

The DirectSound ones all work fine (and the screenshot was just a demo), I do have the non-default ones selected. I too recall some issues a while ago. Can’t remember what but I tend to shy away from “Defaults” :), I would rather force a setting. I get less burnt that way!!! WASAPI options only offer specific groups.

By the way - it looks like Ian has put out a few updates for basswasapi.dll. The one shipped with mAirList is 0.0.0.9, the one posted here is 0.0.0.13: http://www.un4seen.com/forum/?topic=11170.0

Perhaps you can try with that latest version and check if the errors are still there.

Will try to this weekend.

Me too

No Go. In 1406 not even Player 1 (output 1/2) works any more. (even on original 0.9 dll).

Sorry.


wasapi.PNG

Can you please try if any of the BASSWASPI demo applications (in the c\bin directory of the BASSWASAPI download package) work for you?

It seems that the Delta cards don’t run fine in WASAPI mode, as several people report this. Some get an error during initialization, some an access violation all of a sudden, and so on.

[quote=“Torben, post:14, topic:7778”]Can you please try if any of the BASSWASPI demo applications (in the c\bin directory of the BASSWASAPI download package) work for you?

It seems that the Delta cards don’t run fine in WASAPI mode, as several people report this. Some get an error during initialization, some an access violation all of a sudden, and so on.[/quote]

They seem too. If I make each Delta output default device, speaker.exe plays the audio fine. If I run List, it reports back all channels etc. Rectest recorded on 2 input groups etc.

Can you post your devices.ini file please?

Right now I’m set to DirectSound, do you want me to change it all to WASAPI and then submit?

This all devices set to WASAPI.


devices.ini (1.63 KB)

Have you tried initializing the device in exlusive mode? (It’s an option in the WASAPI settings in mAirListConfig.)

That’s at least what the demo applications from BASSWASPI do.

[quote=“Torben, post:19, topic:7778”]Have you tried initializing the device in exlusive mode? (It’s an option in the WASAPI settings in mAirListConfig.)

That’s at least what the demo applications from BASSWASPI do.[/quote]

Just tried. No go. Same error, Init -1, restored all back to shared

However, I PFL’d a trtack and it played. So it appears that my Cue, Mix Editor, PFL and VT work fine, recording VT was fine, just the players and cartwall failed. Could that be an initialization thing?