4.1 WASAPI Init Error

I can report exactly the same behavior with my two M-Audio (440 and 66) cards in WASPI and exclusive mode.

Same here with my M-Audio cards…

Does the problem persist in the latest snapshots? (We’re at 1413 now.)

Yep, it was 1413 I tested it with yesterday. Works perfectly fine with DirectSound though.

Hm. Something must be special about these Delta cards…

Everybody check their e-mail please. I sent you a debug version with further instructions.

Thanks Torben. Got the DLL, will reproduce the problem and send you the log file asasp.

Marcus

Can you try b1416 please?

Quick 5 minute test with all devices set to WASAPI seem to play fine. Well done. Not exhaustive testing though but players, pfl and cartwall all play.

Just recorded an one hour show with VT’s and all seemed find (in WASAPI).

Now all I need is the track names/artists on the VT window ;D

What was the issue?

It turned out that the M-Audio driver expected COM to be initialized, which wasn’t the case for the background thread that is preparing the next x items in the playlist.

Ah, so the log files helped. I love it when a plan works :slight_smile:

Thanks Torben, I can confirm that the Delta 1010LT is now working via WASAPI.

I noticed a new behaviour in this build though: In the voice tracking module, if I move the volume slider for Player A, the interface starts to flicker (that is, UI elements flicker, the window itself does not). This does not happen if I move the volume slider of Player B.
Also, when recording and using the volume slider for Player A, the track’s volume (envelope) does not start at 100%, but at 0% (at the beginning of the song, running up to the moment I use the slider). Again, this does not happen with Player B.
I’m using Windows 7 (64 bit), with a second soundcard for PFL in shared mode (WASAPI) for VT playback.

Marcus

Thanks for feedback, Marcus.

Could you please open a new thread for the other issues? Chances are that I lose track of the problems if they are only mentioned deep down in a totally unrelated thread.

I suspected a relation to the WASAPI fix as no other changes were listed for that build and the problem did not occur in the previous build as far as I recall.

I will open a new thread though.

Thanks Torben.