|
|
|
| Bug Reports | |  |
Even though I make every possible effort to track down bugs before a new version of Amadeus II is released, the
complexity of the project makes it unavoidable that some of them slip through. If you believe that you found a bug
in Amadeus II, please report it to me at Martin@HairerSoft.com
and I will try to correct it. However, please make sure to respect the following guidelines that will make things so much
easier for me (and for you since I will be able to provide you with a more useful reply):
- Make sure that you are using the latest version of Amadeus II. It may well be that the bug
has already been corrected! Please do however confirm in your email that you are indeed using the latest version of Amadeus.
- Please check the FAQ and read the manual
to make sure that your bug is not a well-known problem. Example: don't report the fact that Amadeus II cannot read protected AAC files!
- Describe the bug in a short but precise way and include detailed 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 II and you are using MacOS X, it is extremely helpful to include the crash log generated by the system.
This is a file called Amadeus II.crash.log.
On MacOS 10.2 or later, this file can be found in the folder ~/Library/Logs/CrashReporter/.
On MacOS 10.0 or 10.1, it can be found in the folder ~/Library/Logs/, but crash reporting has to be enabled first in the
preferences of the Console utility.
- If you are still using MacOS 9, try to reboot your computer with all non-Apple extensions turned off (you can use the Extension manager
for that). It may well be that a third-party system extensions causes the problem. Also, make sure that you are using CarbonLib 1.6.
|
|