Yes, that is absolutely correct. The technicians are not conjurers or magicians. If they cannot reproduce it, how can they correct the problem?
Again, this is just to give perspective, not to argue whether someone's claim is valid or not. If a bug in Finale actually lost work, that's serious. What the non-developer should know is that in Windows and prob'ly in Mac operating systems, they use common system modules for processes that are shared by different end user applications. For example, there is one module (Mac OS or Windows OS) that adds, deletes and catalogs files on your disk. Each application developer is given protocols to call these modules and parameters to pass specific data to them, but the OS module actually does the work. As for functions such as playback, in the windows world, the application uses a wrapper but the actual work of sending the playback through the correct buffers/ports etc. is performed by Quicktime or Windows Media player or whatever product is registered to handle files of that type. This is why it is difficult to determine if the problem is Finale or the OS or perhaps if you have some other background process running, it could also cause problems as well. This is especially true when the OS' in either system appear to "hang". It's usually a conflict in these background processes trying to get to the same resource and ending up in a deadly embrace. For example, many many many years ago (~1989) I had a Mac Plus running MOTU Composer and Performer. I also had a modem connected. When I sequenced through Performer to my Kurzweil and someone called on that line everything would hang and I would have to re-boot. Was it MOTU's fault ? I really don't know 'cause I never pursued that path to resolve the problem. I merely disconnected the modem everytime I was doing anything with Composer or Performer. This is not a defense of MM Finale, it very well could be their problem. But knowing how to recreate the problem and what other things are happening at the time the problem occurs could help Mac or Finale Techs fix the problem for you and averyone else. Richard > > From: Noel Stoutenburg <[EMAIL PROTECTED]> > Date: 2005/10/18 Tue PM 06:04:22 EDT > To: [email protected] > Subject: Re: [Finale] Scary bug! > > Friends: > > Reading Chuck's comment, I can't figure out how from > > > they have not encountered this and cannot reproduce it > > Chuck predicates > > > (and are therefor unconcerned about fixing it - they can't find it) > > > Seems reasonable enough to me, no matter how much one wants to find a > problem, if one cannot do so, one cannot address it. > > This raises in my mind, exactly what those who make bug reports include > in those reports. I'd guess the chances that a bug report is going to > be taken seriously improves the more information one includes: and that > it would be helpful to MacSupport or WinSupport, besides knowing what > platform one is running, also to know how much memory is available, what > notation files are open, and what other processes might be running, and > what utilities might be running, and it would probably be helpful to > have include with the bug report a copy of any notation files being > edited when the problem was found. > > ns > > > _______________________________________________ > Finale mailing list > [email protected] > http://lists.shsu.edu/mailman/listinfo/finale > _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
