[wdmaudiodev] Re: Generic Virtual MIDI-driver...
- From: stevejet@xxxxxxxxxxxx
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Tue, 14 Apr 2009 12:14:21 -0400
Hi Tobias,
I'm waiting to see what better help you get than I can offer.
For me to help you, you would have to go the route I went, get a working
"non-dynamic" driver, and then advance it to "dynamic" yourself.
Regards,
Steve.
-----Original Message-----
From: Tobias Erichsen <t.erichsen@xxxxxx>
To: wdmaudiodev@xxxxxxxxxxxxx
Sent: Tue, 14 Apr 2009 15:48
Subject: [wdmaudiodev] Re: Generic Virtual MIDI-driver...
Hi again,
like I wrote before, I have taken the filter & pin defines
from the DMusUART sample unchanged, but unfortunately these
don't seem to work (they also don't work if I use the my
driver in "non-dynamic"-mode, creating a single subdevice
from the defines in the inf-file.
=0
AI have attached the properties that the KsStudio application
has read from my driver and also my inf-file. Perhaps
someone has an idea what is going wrong...
Best regards,
Tobias
-------- Original-Nachricht --------
> Datum: Mon, 13 Apr 2009 22:15:24 +0200
> Von: "Tobias Erichsen" <t.erichsen@xxxxxx>
> An: wdmaudiodev@xxxxxxxxxxxxx
> Betreff: [wdmaudiodev] Re: Generic Virtual MIDI-driver...
> Hi everyone,
>
> I have done a good bit of digging into the depths of PortCls
> over the weekend and also thanks to Jeff I have been able
> to get a good way towards a completely virtual MIDI-port-driver
> with dynamic friendly-names.
>
> I have succeeded in creating my private interface by hooking
> the major-functions in the Driv
erEntry.
>
> I have also been able to use this private interface to create
> my own virtual subdevices (and also to destroy them again).
>
> I have also been able to send data (KSCATEGORY_RENDER)
> from a standard-MIDI-capable application towards my private
> interface.
>
> So far so good. I still have one piece left which I currently
> don't seem to get going:
>
> Every time when I try to instanciate the capture-pin of my
> Miniport (KSCATEGORY_CAPTURE), it fails.
>
> In my debug-log I see that the new stream is being created,
> that the init-function is called, and the ::ConnectOutput
> method is being called. Unfortunately directly afterwards
> the ::DisconnectOutput-method of the stream is called again
> and the stream is destroyed...
>
> I currently have no idea what the problem is.
>
> I have tried to instanciate the capture-pin via KS Studio,
> it also fails and I have attached the logfiles from both
> instanciating the filter & the pin in this email.
>
> If someone could take a look at those files and give me
> a hint, I would be really grateful.
>
> Best regards,
> Tobias
>
> PS.: The driver is loosely based on DMusUART and MPU401,
> so I have not changed any of the filter & pin-stuff
> from those samples...
> --
> Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
> http://www.gmx.net/de/go/multimessenger01
--
Psssst! Schon vom neuen GMX MultiMessenger gehö
rt? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger01
Other related posts:
