[wdmaudiodev] AW: AW: Re: Midi In
- From: F.Hartge@xxxxxxxxxxx (Florian Hartge)
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Thu, 11 Dec 2003 15:13:47 +0100
Hello,
Has anyone some idea with this extra information from KS Studio?
The only critical missing property:
SyncIoctl: DeviceIoControl failed. Last Error = 0x000006f8
KSPROPERTY_PIN_DATAINTERSECTION: (ro, mandatory) [Not Available!]
// Array of KSDATAFORMAT to determine the first data format acceptable to a
pin given a list of data ranges.
// This can be used by a graph builder which has no knowledge of
specifics of data types to send the data range list of one pin to another
pin, and have an acceptable data format returned.
cDataIntersections = Not Available // Number of data formats
compatible to this pin type.
When a stream should be instantiated:
Instantiating Pin 1
Attempting to get preferred format for pin 1SyncIoctl: DeviceIoControl
failed. Last Error = 0x000006f8
Driver bug!! Querying property handler for data buffer size failed on
object handle 0x000000DC.
...Failed!
Failed to get preferred format for pin 1. Inferring format from
DataRange[0].
KsPinInst::KsPinInst: Instantiating pin #1
KsCreatePin failed. HRESULT = 0000001F
KsPinInst::KsPinInst: failed to create pin (Pin Id # = 1)
Any help would be appreciated.
Thanks,
Florian
-----Ursprüngliche Nachricht-----
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] Im Auftrag von Florian Hartge
Gesendet: Mittwoch, 10. Dezember 2003 17:12
An: wdmaudiodev@xxxxxxxxxxxxx
Betreff: [wdmaudiodev] AW: Re: Midi In
I tried it but there is no unusual request which is not handled (at least
none the SB Live! MIDI UART driver doesn't although fail) .
-----Ursprüngliche Nachricht-----
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] Im Auftrag von Evert van der Poll
Gesendet: Mittwoch, 10. Dezember 2003 16:14
An: wdmaudiodev@xxxxxxxxxxxxx
Betreff: [wdmaudiodev] Re: Midi In
Have you tried to monitor all requests sent to your driver? You can use the
tool KsStudio in the DDK. It might be some property request that is not
handled by your driver.
Evert van der Poll
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]On Behalf Of Florian Hartge
Sent: Wednesday, December 10, 2003 1:51 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Midi In
Hello,
I hope somebody can help me. I try to write a simple midi-in driver where
data is transfered from a device to some midi software application.
Therefore i took the DDK dmusUART sample as a basis and modified it to my
needs. Now the driver is just for input. By orienting at the sample and the
DDK documentation all pin declarations and property request handlers should
be correct. The device shows up correctly in the audio device listings and
can be selected as input. But when i try to connect the IMXF is created,
initialized and the output connects and immediately disconnects. After that
the IMFX is destroyed. This happens about 28 times and no data is
transfered. After that the application beliefs it ist connected but the
driver shows no singns of life anymore and does not react on any further
connection attempts. Can anyone help? Thanks.
Best regards,
Florian
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
- » [wdmaudiodev] AW: AW: Re: Midi In