should work on the current developer build of Sierra. The only known problem at the moment is when saving documents to a networked volume, but this appears to be a bug on Apple's end which I expect them to fix.

If it still causes problems on your machine, could you please send me instructions on how to reproduce the crash so that I can fix it? Regards,

FYI Martin I am having strange behavior at various points in my workflow. Now that I know how to reach you I will gather documentation. My current work around is to force quit and restart, it then runs ok for a couple of audios and gets flakey. I know that is a useless explanation but I will gather doc and get it to you and look for patterns, The one area I know is problematic is splitting an audio on the sound menu. It works but has issues. AP is crucial app in my workflow once a month so I am motivated to help get it ready for the GM release.

I must correct my previous post to concur with others. Although it seems to be much better than 2.2 which was completely unuseable, Amadeus Pro 2.3 (1680) is still raising exceptions, or more often most controls becoming unresponsive, in Sierra 16A313a. If I figure out how to reproduce I shall post details.

For the last couple weeks I was sure that touching the Horizontal Zoom control in the lower-right corner of a document window was a sure way to make it fail, but today I'm able to drag that thing back and forth repeatedly with no trouble.

By the way, when it becomes unresponsive, it's not the classic behavior. There is no beachball. As I recall, ⌘S to save still works. And it still plays. But the play head does not move, and trying to select audio or move the play head does not work. Also, when I say raising exceptions, I mean you get that new dialog in the system with button choices to "Crash" or "Continue", etc.

2. I have reported the issue to Apple through their bug reporting tool. I have not heard back from
them yet, but there is a possibility that this is simply a bug in the preview of Sierra that will be fixed
for the release version (or the next point update after that).

3. Even when I run Amadeus Pro in the debugger, this problem does not cause Xcode to break into
the debugger, which again hints at a bug in the operating system. It also means that even if this is
triggered by a bug in Amadeus Pro, I currently have no way whatsoever to figure out where this bug
is located. I have asked Apple for code-level support on how to debug this issue, but since it only
occurs on a beta version of macOS, they refuse to provide this support. Looks like I'll have to wait
until the official release of macOS Sierra to do anything about it if it doesn't get fixed by Apple by then.

Lastly, I am regularly updating the preview version of Amadeus Pro 2.3 at

2. I have reported the issue to Apple through their bug reporting tool. I have not heard back from
them yet, but there is a possibility that this is simply a bug in the preview of Sierra that will be fixed
for the release version (or the next point update after that).

3. Even when I run Amadeus Pro in the debugger, this problem does not cause Xcode to break into
the debugger, which again hints at a bug in the operating system. It also means that even if this is
triggered by a bug in Amadeus Pro, I currently have no way whatsoever to figure out where this bug
is located. I have asked Apple for code-level support on how to debug this issue, but since it only
occurs on a beta version of macOS, they refuse to provide this support. Looks like I'll have to wait
until the official release of macOS Sierra to do anything about it if it doesn't get fixed by Apple by then.

Lastly, I am regularly updating the preview version of Amadeus Pro 2.3 at

@jhhl: would you be able to share a Dropbox link to the file you cannot open so that I can look into this? Thanks,

Martin

Hi Martin - I was still having crashes, so I updated to the latest Sierra and the latest (1712) Amadeus, and it hasn't crashed while playing with the Sonogram window after a few tries - which is a good thing, because it used to happen almost immediately!
So - it's a lot better and may be stable again! (my cautious remarks after a few minutes of testing)
Thanks!