Yes, I know about regsrv32; what I really meant was, in what categories?

As I understand things so far, ActiveMovie plugins are identified as either a
source filter, or a transform filter, or a renderer filter. A source filter has
no input pins, a renderer filter has no output pins, and a transform filter of
course has both. from my understanding of the DirtectShow documentation, it is
the presence or otherwise of these pins which tells the ActiveMovie graph
manager what sort of object the plugin is. If it has no input pin, it can never
be inserted as a transform filter, whereas if it has one or more, it cannot be
loaded as a source filter.  Is it therefore possible to make a single plugin
appear as either a source or a transform filter to ActiveMovie?

I understand that Csound as an ActiveX control is effectively a full-blown
application OLE-style (embed in a framework GUI, code, load, run), whereas
Csound running as a DirectShow/ActiveMovie plugin is an instance of a (possibly
infinitely) running Csound orchestra. In ActiveMovie, the only way the user can
control a plugin is through the property page. It is certainly possible to have
plugins without property pages - this applies to utility plugins such as tee
splitters, file parsers, and so on, but I don't see how this could apply to
Csound as a whole. Unless you do mean that each opcode could be coded as a
self-sufficient plugin, Csound itself will have to become an ActiveMovie plugin,
somehow.

My suspicion is that {Csound =  ActiveX control}, and {Csound = ActiveMovie
plugin} are separate entities, even if they do share a great deal of common
code.

Richard Dobson

Michael Gogins wrote:
> 
> >This sounds like very much like a full-blown ActiveX control. It should
> >certainly be reasonable  to add supoport for DirectShow interfaces (like
> any COM
> >interfaces). How would it be registered?
> 
> The usual way - drop it on RegSrv32.exe. It would come with a standalone
> "shell" that would register the COM library, also.
> 
> >As well as being an ActiveX control, in
> >DirectShow it could qualify as both a transform filter, and as a source
> filter.
> 
> That is exactly the idea.
> 
> >
> >Re a GUI: I think it would need to support a property page - or several.
> 
> It might need a property page for controlling how it would appear in the
> context of a containing window, like a Visual Basic form,
> but really it mainly needs an embedded window for the actual user interface.
> I have done these several times. Or maybe just a popup window.
>