16 Bug reporting
Even though I make every possible effort to track down bugs before
a new version of Amadeus Pro is released, the
complexity of the project makes it unavoidable that some of them slip
through. If you believe that you have found a bug in
Amadeus Pro, please report it to Martin@HairerSoft.com and I will
make every attempt to correct it. However, please make sure to respect
the following guidelines that will make things so much easier for both
of us since I will be able to provide you with a more useful reply and
there is a much higher chance that I will actually be able to fix
things:
- Make sure that you are using the latest version of
Amadeus Pro. It may well be that the bug has already
been fixed! You can check the number of the latest version (and of
course also download it) at http://www.hairersoft.com/AmadeusPro/. Please do however confirm in your
email that you are indeed using the latest version of
Amadeus Pro, as otherwise this will be first question
I’ll ask you.
- Please check the FAQ and read this manual to make sure
that your bug is not a well-known problem.
Example:
Please don’t report the fact that Amadeus Pro
cannot read protected AAC files!
- Describe the bug in a short but precise way and, if possible,
include detailed step by step instructions on how to reproduce it.
State precisely what the observed consequences of your manipulations
are and what consequences you expected instead. Include as much
relevant information as possible. This usually comprises at least the
version of your operating system and the characteristics of the sound
you were working with when the bug occured.
Example:
If the bug concerns the recording functions, state precisely what
hardware you are using for recording.
- If the bug leads to a crash of Amadeus Pro,
there should be a dialog appearing that gives you the possibility of
sending a crash log back to HairerSoft. Please do so, this will help
improving future versions. Adding information on what you were doing
when the crash occured greatly helps in tracking down the problem.
Copyright © HairerSoft
Last updated on June 22, 2015