{"id":930,"date":"2009-06-11T15:14:21","date_gmt":"2009-06-11T13:14:21","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=930"},"modified":"2009-06-11T15:21:29","modified_gmt":"2009-06-11T13:21:29","slug":"hint-on-how-to-easily-find-your-filter-graph-on-running-object-table-rot","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/930","title":{"rendered":"Hint on how to easily find your filter graph on running object table (ROT)"},"content":{"rendered":"

With a lot of DirectShow Filter Graphs<\/a> published on Running Object Table<\/a>, especially those automatically published by Filter Graph Spy utility<\/a>, it might be a bit tricky to locate your graph of interest in the list.<\/p>\n

Filter graphs are published with a textual moniker item name<\/a> of predefined format, which is recognized by GraphEdit<\/a> or GraphStudio<\/a>, or similar utilities as an item corresponding to a filter graph. A template for such a string is “FilterGraph %08x pid %08x<\/em>“, which obviously only contains raw pointer address and process identifier, which only help a bit in looking up for proper graph interactively. However, it is important how exactly applications are recognizing filter graph related names. For example, GraphStudio does it<\/a> the following way:<\/p>\n

rot-<\/span>><\/span>EnumRunning(<\/span>&<\/span>emon)<\/span>;<\/span>\r\nemon-<\/span>><\/span>Reset(<\/span>)<\/span>;<\/span>\r\nwhile<\/span> (<\/span>emon-<\/span>><\/span>Next(<\/span>1<\/span>,<\/span> &<\/span>moniker,<\/span> &<\/span>f)<\/span> =<\/span>=<\/span> NOERROR)<\/span> {<\/span>\r\n\r\n    \/\/ is this a graph object ?<\/span>\r\n    LPOLESTR    displayname;<\/span>\r\n    moniker-<\/span>><\/span>GetDisplayName(<\/span>bindctx,<\/span> NULL<\/span>,<\/span> &<\/span>displayname)<\/span>;<\/span>\r\n\r\n    CString<\/span>        name(<\/span>displayname)<\/span>;<\/span>\r\n    if<\/span> (<\/span>name.<\/span>Find(<\/span>_T(<\/span>\"<\/span>!FilterGraph<\/span>\"<\/span>)<\/span>)<\/span> =<\/span>=<\/span> 0<\/span>)<\/span> {<\/span><\/pre>\n
The items that match are then listed in GUI with an original string, which means that it is possible to provide an informational suffix to be able to locate the graph in a more convenient way, e.g. with a process image name, not only identifier (“; process: …” was appended to the item name):<\/p>\n
\"GraphStudio's<\/p>\n
GraphEdit is using another method and is more strict in selecting among available items. AFAIR earlier versions did not allow custom suffixes in item names, however the latest version still picks the items up from the global list. However, GraphEdit does not show graph’s original item name, so suffixes are merely useless with GraphEdit.<\/p>\n
\"GraphEdit<\/p>\n
Filter Graph Spy utility<\/a> was updated to automatically append process name suffix, which should be OK for both GrapEdit and GraphStudio. Still, the feature can be disabled through registry DWORD value named “Enable ROT Moniker Item Name Suffix<\/em>” under HKEY_LOCAL_MACHINE\\SOFTWARE\\Alax.Info\\Utilities<\/em>. The value of zero, or missing, is the default behavior to enable suffixes. The value of 1 disables the feature, the value of 2 makes sure it is enabled.<\/p>\n
static<\/span> CConstIntegerRegistryValue g_nEnableRotMonikerItemNameSuffix(<\/span>_T(<\/span>\"<\/span>Enable ROT Moniker Item Name Suffix<\/span>\"<\/span>)<\/span>)<\/span>;<\/span> \/\/ 0 Default, 1 Disable, 2 Enable<\/span>\r\nif<\/span>(<\/span>g_nEnableRotMonikerItemNameSuffix !<\/span>=<\/span> 1<\/span>)<\/span>\r\n{<\/span>\r\n    TCHAR<\/span> pszPath[<\/span>MAX_PATH]<\/span> =<\/span> {<\/span> 0<\/span> }<\/span>;<\/span>\r\n    _W(<\/span>GetModuleFileName<\/span>(<\/span>NULL<\/span>,<\/span> pszPath,<\/span> DIM(<\/span>pszPath)<\/span>)<\/span>)<\/span>;<\/span>\r\n    CString<\/span> sItemName =<\/span> AtlFormatString(<\/span>_T(<\/span>\"<\/span>%s<\/span>; process: <\/span>%s<\/span>\"<\/span>)<\/span>,<\/span> m_RunningFilterGraph.<\/span>GetDefaultMonikerItemName(<\/span>GetControllingUnknown(<\/span>)<\/span>)<\/span>,<\/span> FindFileName(<\/span>pszPath)<\/span>)<\/span>;<\/span>\r\n    m_RunningFilterGraph.<\/span>SetFilterGraph(<\/span>GetControllingUnknown(<\/span>)<\/span>,<\/span> CStringW(<\/span>sItemName)<\/span>)<\/span>;<\/span>\r\n}<\/span> else<\/span>\r\n    m_RunningFilterGraph.<\/span>SetFilterGraph(<\/span>GetControllingUnknown(<\/span>)<\/span>)<\/span><\/pre>\n
With a lot of DirectShow Filter Graphs published on Running Object Table, especially those automatically published by Filter Graph Spy utility, it might be a bit tricky to locate your graph of interest in the list. Filter graphs are published with a textual moniker item name of predefined format, which is recognized by GraphEdit or… <\/p>\n
Read the full article<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,2],"tags":[487,78,119,163,204,205,203,202,164],"class_list":["post-930","post","type-post","status-publish","format-standard","hentry","category-atl","category-utilities","tag-atl","tag-directshow","tag-filter","tag-graph","tag-graphedit","tag-graphstudio","tag-moniker","tag-rot","tag-spy"],"_links":{"self":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts\/930","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/comments?post=930"}],"version-history":[{"count":0,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts\/930\/revisions"}],"wp:attachment":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/media?parent=930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/categories?post=930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/tags?post=930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
A partial Visual C++ .NET 2008 source code is available from SVN<\/a>, release binary included<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"