Something Not Working?

We Fix It the Same Day

iNMR is actively developed and personally maintained by its author. When something goes wrong — whether it is unexpected behaviour, a confusing result, or an outright crash — you are not opening a ticket with a call center. You are writing directly to the person who wrote the code. Most issues are resolved within the same working day.

If something feels wrong but the program does not crash, describe what you expected and what happened instead. It may be a bug, or it may be a feature that can be improved. Either way, your feedback shapes the next update.

If iNMR crashes or freezes

A crash is always a bug — no exceptions. To get it fixed as fast as possible, follow these steps before writing to us:

1. Identify which command triggers the crash. It is almost always the last one you used.
2. Confirm that you can reproduce it consistently, step by step.
3. Save the spectrum file you were working on just before the crash occurs.
4. Quit iNMR, reopen it, reload the file, and verify that the same single command still causes the crash.
5. Send us the zipped spectrum and a short description of how to reproduce the crash on our end.

A reproducible bug with a test file is fixed in minutes, not days. The more precisely you describe the steps, the faster the solution.