DirectShow is a Microsoft Windows multimedia streaming API. A DirectShow graph is a collection of connected multimedia components configured to achieve a particular multimedia processing task (e.g. media playback, capture or conversion). A DirectShow graph editor such as Microsoft GraphEdit is a test environment and UI for creating and testing DirectShow graphs interactively. Once a graph has been tested in a graph editor it can be created programmatically in a programming language such as C++ using the DirectShow API.
DirectShow is an exclusively Windows technology so GraphStudioNext is Windows only and not designed for portability to other platforms.
win32 (32bit) and x64 (64bit) refer to the platform that GraphStudioNext is built for. The x64 version has a "64" in the bottom right corner of the application icon. If you're running on a 32bit version of Windows you can only use win32 GraphStudioNext. If you're running on a 64bit version of Windows you can use either win32 or x64 GraphStudioNext. GraphStudioNext can only use filters of the matching platform. This is a fundamental Windows limitation, not a GraphStudioNext limitation. If you're testing a graph in GraphStudioNext before creating it in another application then use the platform of GraphStudioNext that matches your application platform. Most Microsoft filters are available for both 32bit and 64bit platforms but this may not be true of third party filters. 32bit and 64bit platform versions of a filter are never implemented in the same DLL or EXE file though they may have the same file name, filter name and filter CLSID. "Graph/Insert Filter..." lists all the filters available for the platform of GraphStudioNext you're running.
No. Media Foundation is a later Windows API that has similar concepts to DirectShow. DirectShow and Media Foundation are not currently designed to interoperate. Hybrid components could be written to transfer data between DirectShow and Media Foundation but it would be a non-trivial task. If such hybrid components existed there might be a case for adding Media Foundation support to GraphStudioNext. There is already an analagous editing tool in Media Foundation, Microsoft TopoEdit
Possibly, but consider some further steps to isolate the problem:
- Does the same problem happen in Graph Edit, Microsoft's own graph editor in the Windows SDK?
- Do the filters you are using support the operation you are attempting? Many filters do not support all DirectShow features. For example some filters don't support seeking or only support specific time formats. Consult the documentation for the filters you are using.
- Are all the filters or DLLS you are using in GraphStudioNext available for the same platform (Win32/x64) as the platform of GraphStudioNext you are running? It may be possible to connect to a GraphStudioNext process of the other platform remotely ("File/Connect to Remote Graph..") but there may be some limitations on the operations you can perform on remote graphs.
- If the graph throws an exception, attach a debugger to see whether the exception happens in graphstudionext.exe or a filter DLL.
- Do you have other applications installed or running that are affecting the operation of DirectShow? A notable example is the excellent tool, Filter Graph Spy, which hooks DirectShow throughout the system at a low level and can change DirectShow behaviour (as the author himself warns).
- Some diagnostic features in the GraphStudioNext "Options" menu can cause unexpected behaviour by design. For example, "Reserve Memory below 2GB" may cause graphs to run out of memory or fail if some filters aren't flagged as LargeAddressAware. Behaviour may also be different if using "Options/Filter Graph CLSID" menu item is set to "CLSID_FilterGraphNoThread" or "CLSID_FilterGraphNoThread".
- https://github.com/cplussharp/graph-studio-next/issues
- Search including closed issues to see if the bug or feature request is a duplicate.
- Report what you expected to happen and what actually happened
- Say which version of GraphStudioNext are you using. Does the problem happen in both win32 and x64 versions? If possible, reproduce the problem using the latest official build of GraphStudioNext. Which version of Windows are you running GraphStudioNext on? Any custom hardware considerations that could affect your particular issue?
- If using third party non-Microsoft filters, please say what they are and which versions of them you're using.
- If possible, create a graph that shows the problem and save and include all the GRF/GRFX/PNG/TXT files in the issue
- If reporting a crash, consider capturing and including a minidump of the crash. Normal minidumps are fine, full memory minidumps with heap are huge and too large to attach to an issue.
- Include any sample code if relevant
Do I have to install the Windows SDK?
No, GraphStudioNext will work without it, but the Windows SDK does include some very important tools:
- Graph Edit, Microsoft's own graph editor.
- proppage.dll and evrprop.dll which provide property pages and the ability to connect to graphs in other processes.
- OLE-COM Object Viewer, useful for looking at registered COM classes and looking at COM type libraries packaged inside filter DLLs.
- Header files and libraries for building DirectShow applications and filters.
- DirectShow sample code.
- The DirectShow baseclasses. Mainly useful for building filters though there are some classes and functions that can be used for developing DirectShow client applications.
These tools are included in the Windows SDK tools for desktop development, there is no need to install Universal Windows App development tools unless you want to.
- As a first step read the MSDN DirectShow documentation. It is well written and is the definitive documentation for DirectShow. Many important details can be missed on the first reading, so read it again!
- Is there a relevant Microsoft DirectShow sample to refer to?
- Search engines are your friend. There is loads of DirectShow sample code and discussion on the web.
Have you installed the Windows SDK and registered proppage.dll using regsvr32? Proppage.dll implements the property pages for many Microsoft filters. Similarly, registering evrprop.dll in the Windows SDK will provide extra property pages for the enhanced video renderer filter.
Have you installed the Windows SDK and registered proppage.dll using regsvr32? Proppage.dll implements COM proxies and stubs that are required for calling DirectShow interfaces on a graph in another process.
Why can I see property pages for a particular filter or pin in a local graph, but not in a remote graph?
Has the filter implemented COM proxies and stubs for calling the filter's custom COM interfaces in a remote process? It's possible to build these yourself using code generated by MIDL if you have the type libraries for the filter's custom COM interfaces but it's beyond the scope of this FAQ. Sometimes the type libraries for these interfaces are included in the filter DLL and can be viewed using "View Typelib" in OLE-COM Object Viewer in the Windows SDK. Generally, COM proxies and stubs and property pages for Microsoft filters are implemented in proppage.dll in the Windows SDK.
Mainly because the authors don't have an interest in writing or using such a feature themselves. It's hard to write general purpose DirectShow code that would suit all users. However, we are not ruling such a feature out if someone else would like to write it. Feel free to write some code and get involved! There is one commercial graph editor, Graph Edit Plus, that supports code generation in C++ and C#.