News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Steinberg ASIO

Started by Siekmanski, July 01, 2012, 06:32:10 AM

Previous topic - Next topic

Siekmanski

Who knows whats going wrong here?

I'm trying to translate the Steinberg ASIO C++ sources to Masm assembly.
First thing is enumerate the Asio sound devices.
So far so good.

I have a "M-Audio Delta ASIO" soundcard on board and I can get the Interface pointer without errors.

I have "ASIO4ALL v2" (a generic ASIO driver that works with most soundcards) installed on my computer.
I can get the Interface pointer, but with an error from CoCreateInstance.

   "can't find entrypoint of procedure NtAlpcSendWaitReceivePort in ntdll.dll"

But it still gives me back the interface pointer.
And the CLSID's are correct ( looked it up in the registry )

This is the output from my computer:


Siekmanski ASIO Soundcard Test..........


Total ASIO drivers found: 2

DeviceNumber: 0
ASIO driver name: " ASIO4ALL v2 "

An instance of the specified object class was successfully created.
CLSID: {232685c6-6548-49d8-846d-4141a3ef7560}
Pointer to ASIO interface: 10670720


DeviceNumber: 1
ASIO driver name: " M-Audio Delta ASIO "

An instance of the specified object class was successfully created.
CLSID: {615c2c81-f8eb-11d3-b0b2-0000e8ed4ad9}
Pointer to ASIO interface: 8680256


Press any key to continue...




Can not find out why I get the error........  :(

The attachment has some screenshots of the event and the sourcecode.
Creative coders use backward thinking techniques as a strategy.

Siekmanski

Problem solved!!!

Just installed "ASIO4ALL v2" on my Laptop and no error from the CoCreateInstance Api.
It seems that "ASIO4ALL v2" and my other computer don't like each other.....
Still don't have a clue why this driver creates an error but gives back the right Interface pointer on my computer.  :icon_confused:

Next step:
Setting up communication with the Asio Sound Cards to get really low latency audio in and output.  :biggrin:
Creative coders use backward thinking techniques as a strategy.

dedndave

i saw something on a forum someplace where uninstalling a previous driver worked
apparently, the ASIO driver had a conflict of some sort

Siekmanski

Yeah, it's a nice software solution for non ASIO Sound Cards.
I have installed differrent versions of ASIO4ALL all with the same error.

Just finished the com interface. ( what a horrible ASIO 2.2 SDK....... )
Tested some functions with good results on my M-Audio Audiophile 192 Asio Sound Card.
Still got a lot to do.  :biggrin:
Creative coders use backward thinking techniques as a strategy.