Where to Get HelpIf you don't find the answer to your question on this web site, there are other resources available to help you. Some of the places you can find additional help are the SDK samples, the SDK docs, MSDN, newsgroups and forums.
Please read the all the information below before posting your question online.
Before you post a question, search on the available archived information to see if it has already been answered. The most likely places to find information are:
Realize that nobody knows anything about the background to your problem or about your environment except what you write in your post.
Use a descriptive subject line in your post. Example: Preview pin will not connect to VMR7 in capture graph. Words like "urgent," "newbie" and "please help ASAP" in the subject line or body are a distraction and do not help anyone help you.
Provide information in your question about your environment. Example: I am using the DirectX 9.0 Summer 2004 SDK with VC7.1 and the February 2003 Platform SDK.
List any errors that you are receiving from the debug runtimes or failed HRESULTs. Post the result in hexadecimal and its equivalent text definition from the DirectX Error Lookup tool, found in the DirectX SDK, or the system header files (look in <winerror.h>, <vfwmsgs.h>, <dxerr*.h>, etc.)
If applicable, provide a short code snippet that illustrates your problem. Remove error checking if it will make the code clearer and indicate where you are getting any failures.
List the things that you have attempted to fix your problem. It is a waste of everyone's time to have someone take time to respond to a post only to get a follow up that the suggestions had already been attempted.
If you receive an answer or post that helps you, acknowledge the response you get. It will help others who subsequently search the archive identify a solution to a similar problem.
If you need further clarification, trim and quote the part of the response you need explained and ask for additional information.
Never be rude or impatient. Don't bump threads within a day of posting and if you do bump a thread after a day, state what you have tried in the meantime. Virtually all of the responses in the dshow groups are from volunteers. If you are asked for clarification or requested to post somewhere else, there is probably a good reason. If you don't understand, ask politely for clarification. Review Microsoft's Rules of Conduct for its community newsgroups and forums. Keep your writing professional, technical and courteous at all times.
A person who responds to your post may be on a different time zone and continent so it make take time before you get a response.
If it is about managed dshow (C#, VB.NET), support is not provided in the MSDN forums because Microsoft does not support dshow with .NET. Instead, ask in the DirectShow.NET forum here.
The MSDN Forum for DirectShow is a good place to post questions if you can't find an answer using the help above.
Here are some specific guidelines for using the forums effectively:
TMH first used newsgroups in the mid-1980s. Here are a few guidelines based on his experience that will help you get your question answered promptly:
IMPORTANT NOTE: Microsoft is closing their newsgroups. Although some external NNTP servers continue to carry Microsoft newsgroups, the ones marked RETIRED below are no longer supported on Microsoft's servers.
There are a number of forums newsgroups in the DirectX area and it is difficult to know which is most appropriate for a dshow question without some guidance. There is no clear information available on microsoft.com for this. The information below will help you.
If your question is about using dshow in .NET, the best place to ask is on the DirectShow.NET forum on SourceForge.
There are two classes of groups:
Here are the programmer groups. Please post only in the first group listed that covers your question.
The .sdk, .misc, .input, .graphics and other DX groups are not dshow groups.
There are separate groups for Windows Media specific programming questions:
Finally, there is an email alias at Microsoft that is monitored for dshow issues. These are not for requesting support nor for asking questions but you can use it to submit bug reports and suggestions: email@example.com. While it is monitored a response is not guaranteed. Use the guidelines above for writing an effective email.
The following are some common abbreviations used in newsgroups and forums:
Copyright © 2010 by The March Hare. All Rights Reserved. Last modified: August 07, 2010