I've taken a couple of days to respond to this to get my thoughts in order, and not knee-jerk respond to your veiled comment at the start of your last post. Perhaps I may or may not be a better player, but that has zero to do with the issue, but, in all fairness, the idea of concentrating on what you are doing once you KNOW something is going to crash is part of basic troubleshooting... at least, in my experience as an end user of computer based products, and from ALL my conversations with tech support lines for different software and products.

I can only imagine the result were I to voice your attitude to a guy on a support hotline for a major piece of software when he asks me (as they ALWAYS do ) "what were you doing prior to the crash?' 'Only a fool would ask such a question' would probably get me hung up on...

But something that concerns me a LOT more, on the whole, is the thought that, even though you KNOW that, if you stick to making registrations and playing it from them you will get as few crashes as Don gets, rather than do things the way they DO work and enjoy your purchase to at least a degree, it sits, unplayed while you wait for it to be PERFECT (in your estimation). You neither get your money back and WAIT for it to be perfect in some alternative future dimension (unpopulated by any other arranger... they ALL got something wrong with them! ) when you could buy it again, nor do you accept it for what it DOES do well, play it within the limitations of how it does operate at the moment, which apparently is just FINE for some people, and at the very least, be making some awesome music (which I would HOPE is why you bought it in the first place, rather than an exercise in finding out - or rather, NOT finding out - how easily you could make it crash if you jackhammer away at the buttons) within the parameters that it DOES operate acceptably on...

Now, of course, it is entirely your choice how to go about your business, don't get me wrong, but I am convinced that, if I were faced with the same situation, I would be either getting my money back IN FULL with a warranty claim, or I would be playing it and enjoying it for what it DOES do well, while waiting for an OS update that may or may not fix the problem. But your path of NONE of those, just let it sit while you post incessantly about the problem (but try nothing to fix it) is, IMO, simply designed to give you that high blood pressure you talked about!

Perhaps every tech support guy and computer technician I have ever talked to is wrong, and you are the ONLY person right, but apparently, the computer world is populated by fools that think that knowing what you did prior to a crash is valuable information...

And perhaps, if you looked at this problem from a different direction (as a USER, rather than as a designer or lecturer), you might understand that, if a product works well enough to be used on a gig, even if it does impose limitations on what you can or cannot do, NOW is the time to decide whether you want to continue playing it, or whether you should move on completely. Sitting in limbo, doing nothing but gripe just seems so pointless...

I can see we are very different people. I have been a pro player all my life, and you have been a computer interface designer and lecturer. But perhaps my approach is what is needed here. We are talking about a MUSICAL INSTRUMENT, not an exercise in man-machine interface. ALL musical instruments have SOME kind of flaw... guitar strings break, pianos go out of tune, brass valves stick, sax reeds crack, and arrangers sometimes crash. Each musician deals with the problem, but with the goal of 'playing music', NOT perfecting the un-crackable reed or the unbreakable guitar string. Waiting until the Audya NEVER crashes before you use it at all seems to me, at least, the response of a man-machine designer, rather than a MUSICIAN.

Musicians make do, not make excuses...