Defiler
11th December 2005, 05:11
I've noticed that Haali's (very cool) splitter registers itself under HKCR\Media Type\ in the Windows registry.
According to MSDN, this section contains byte patterns that, when matched by a particular file, point DirectShow at which file source filter to use. Cool so far.
However, Haali's splitter sets itself as subtype:
49952F4C-3EDC-4A9B-8906-1DE02A3D4BC2
..which doesn't seem to be a GUID associated with any particular subtype.
How does this work? Does Windows just look through all of the entries for a particular major type until it finds one that matches? Does that means that 49952etcetcetc could just be renamed to DEAD_BEEF, and everything would still work?
Sorry for the 'non-practical' thread, but I started to get curious about it when I noticed that GSpot didn't enumerate any of the types that Haali's filter was handling.
According to MSDN, this section contains byte patterns that, when matched by a particular file, point DirectShow at which file source filter to use. Cool so far.
However, Haali's splitter sets itself as subtype:
49952F4C-3EDC-4A9B-8906-1DE02A3D4BC2
..which doesn't seem to be a GUID associated with any particular subtype.
How does this work? Does Windows just look through all of the entries for a particular major type until it finds one that matches? Does that means that 49952etcetcetc could just be renamed to DEAD_BEEF, and everything would still work?
Sorry for the 'non-practical' thread, but I started to get curious about it when I noticed that GSpot didn't enumerate any of the types that Haali's filter was handling.