Multi-File Parser Filter
[The feature associated with this page, DirectShow, is a legacy feature. It has been superseded by MediaPlayer, IMFMediaEngine, and Audio/Video Capture in Media Foundation. Those features have been optimized for Windows 10 and Windows 11. Microsoft strongly recommends that new code use MediaPlayer, IMFMediaEngine and Audio/Video Capture in Media Foundation instead of DirectShow, when possible. Microsoft suggests that existing code that uses the legacy APIs be rewritten to use the new APIs if possible.]
The Multi-File Parser filter parses a simple file format that enables multiple file names to be specified as though they were one file. These files have the format shown in the following example:
;MULTI
https://server/share/video.mpg
https://server/share/captions.smi
The use of this filter is deprecated. To render multiple files within the same filter graph, the application should simply call RenderFile or AddSourceFilter multiple times.
Label | Value |
---|---|
Filter interfaces | IBaseFilter |
Input pin media types |
|
Input pin interfaces | IPin, IQualityControl |
Output pin media types |
|
Output pin interfaces | IPin, IQualityControl |
Filter CLSID | CLSID_MultFile |
Executable | Quartz.dll |
Merit | MERIT_UNLIKELY |
Filter Category | CLSID_LegacyAmFilterCategory |
Remarks
The filter creates one output pin for each file listed in the source file. The output type is MEDIATYPE_File, and the format block for the output type is a wide-character string that contains the file name. Each pin connects to an instance of the File Stream Renderer filter. The File Stream Renderer filter creates one output pin, which exposes the IStreamBuilder interface. The output pin renders the specified file. No media data travels between the Multi-File Parser and the File Stream Renderer.
The filter's CLSID is not defined in Uuids.h. Use this macro in your own header file:
// {D51BD5A3-7548-11cf-A520-0080C77EF58A}
DEFINE_GUID(CLSID_MultFile,
0xd51bd5a3, 0x7548, 0x11cf, 0xa5, 0x20, 0x0, 0x80, 0xc7, 0x7e, 0xf5, 0x8a);
Related topics