Here’s an email love story between a studio user and a member of our development team. Well, OK, it’s only messages from the user in crash reports, and there’s no love of which to speak…
Here’s what he actually wrote over the course of three consecutive crashes:
|1||I was making a music video, then it crashed.|
|2||I was making a music video again, then it crashed again. You suck!|
|3||This thing keeps crashing when making music videos! I want to punch your faces in!|
The poor guy hit a bug, and Studio crashed. Then he tried it again a couple of more times, and every time, Studio crashed in the same place. It rightfully made him angrier and angrier.
We fixed the bug, but not because of his vitriol. But (partly) because there was other useful diagnostic information in the bug report.
So, in case you’ve ever wondered: Yes, we read what you write. And yes, sending us those crashes does lead to fixes.
You don’t have to send in the crash reports, of course. If you do, you can choose to helpfully let us know what you were doing when it crashed, or you can vent. We’ll read it. We regret the bug regardless of whether you vent.
Finally, there’s a secret feature where if you put the email address of a developer (Mine is the subdomain of this blog with @pinnaclesys.com.) in your feedback, that particular crash will go directly to their email inbox. So, yeah, you can send me hate mail.