[wdmaudiodev] Re: Generic Virtual MIDI-driver...
- From: "Tobias Erichsen" <t.erichsen@xxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Wed, 15 Apr 2009 00:53:43 +0200
Hi everyone,
thanks to the feedback from Bob, I have been able to solve
the issue: in the heat of the battle I stripped one thing
too much from my driver: the ServiceGroup.
After I re-added this code-segment, I could now also instanciate
the capture-pin of my driver :-)
I have even managed to build the driver to support multiple
streams on one filter.
One question remains: If I try to "shut down" the port that
I created through my private interface while some streams
are open, I currently bug-check the system.
The question is now: how can I tell those streams that my
filter wants to shut down? Can I force them to close before
I unregister the subdevice?
Best regards,
Tobias
-------- Original-Nachricht --------
> Datum: Tue, 14 Apr 2009 20:51:06 +0200
> Von: "Tobias Erichsen" <t.erichsen@xxxxxx>
> An: wdmaudiodev@xxxxxxxxxxxxx
> Betreff: [wdmaudiodev] Re: Generic Virtual MIDI-driver...
> Hi Steve,
>
> actually my driver is just a normal "static" DMusUART & MPU401
> combination with some "dynamic" add-ons.
>
> Even if I only use the static part (the Subdevice created with
> InstallSubdevice in StartDevice and specified in the INF-file),
> I cannot instanciate the capture-pin of this filter...
>
> Have you also based your driver on DMusUART & MPU401?
> If so, have you changed any of the filter & pin-properties
> of the driver? My driver is based on the samples of the WDK
> 6000. I have seen that the sample in the 2000 DDK differs
> a little in the exposed properties...
>
> Best regards,
> Tobias
>
>
> -------- Original-Nachricht --------
> > Datum: Tue, 14 Apr 2009 12:14:21 -0400
> > Von: stevejet@xxxxxxxxxxxx
> > An: wdmaudiodev@xxxxxxxxxxxxx
> > Betreff: [wdmaudiodev] Re: Generic Virtual MIDI-driver...
>
> >
> > 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.
> > ? 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
> >
> >
> >
> >
> >
>
> --
> Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
> http://www.gmx.net/de/go/multimessenger01
> ******************
>
> 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.com/
--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss
für nur 17,95 Euro/mtl.!*
http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
******************
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.com/
Other related posts:
