Bug reporting

From VidvoxWiki

Bug Reporting

Bug reporting is the process by which you communicate a problem or a crash or other problem with VDMX to us. Most of the time, the built-in bug reporter is all you need: just relaunch vdmx after a crash, and if your machine is connected to the internet the bug reporter will appear.

If the problem doesn't involve a crash (if vdmx locks up, also known as "hanging" or "beachballing"), you can still submit a bug report- in fact, you're strongly encouraged to do so, because that will improve the chances of the bug getting fixed immensely. You can use the online bug reporter, or you can send an email to support[at]vidvox.com when you've assembled the below information.

Good bug reports consist of the following:

1. If vdmx crashed, we need the Crash Log. If it hung/beachballed, we need a Stack Trace. Regardless as to whether or not it crashed, we need the Console Log. All of this information is extremely easy to obtain (just follow the links for explicit, illustrated instructions), and is very important to your bug report, because they contain descriptions of what your computer was doing when it ran into problems.
2. A description of your computer setup, including: what kind of computer, how much RAM it has, what kind of graphics card it's got and how much VRAM is on the card, what OS it's running, what version of QT it's running, and any additional information you think is necessary.
3. A quick description of the bug- and any events which led up to it- is usually helpful.
4. Is the problem is repeatable? If a problem is repeatable, we can probably reproduce it on our machines- which means there's an *excellent* chance that the bug will be fixed very soon.
5. How many clips did you have imported into vdmx, and what kind of clips were they? Specifically, we're looking for their resolution and codec; a clip's size on disk is irrelevant.
6. What's your e-mail address? Many times, we'll have follow-up questions about a bug report, or we may have a sample app for you to try, a workaround, or we may just want to thank you for your contribution, and let you know that the bug's been fixed.