Re: Here we go again...

[irsman@iastate.edu (Ian Schmidt)]

In article <14Nq03SRdatE00@amdahl.uts.amdahl.com> fadden@uts.amdahl.com (Andy McFadden) writes:

I'd not call what I got a bug report.  I got a "it doesn't work" report, which
I generally consider fair game to be treated with disdain.  For the record,
bug reports for MODZap should include:

a) The version of the program
b) applicable settings in the Options dialog
c) the MOD file in question, and where to obtain it
d) The location if applicable of the defect, from the readouts in the player.
e) The exact nature of the defect.

Neither posted report contains any of those 5 important pieces of information.
You'd not be amused if someone posted "HP doesn't work.  It sucks.", eh?

>So it plays perfect sound so long as the input is what you expect it to be?

Yes.  Most programs perform in this manner; a C compiler won't work right if
fed any random c.s.a2 posting.  It's not a new concept.

>If player (a) plays the songs I want to play without buzzes and clicks,
>while REVOLUTIONARY PERFECTO SUPER-DUPER-MEGA ADVANCED AS ALL HELL player (b)
>can't hack it, how can player (b) be considered superior?

Because on many songs, player (b) is superior and noiseless.  MZ was optimized
for the majority of songs, with plenty of special cases as well.  Since I
cannot physically try every MOD in existance, I rely on bug reports including
the 5 pieces of information above.

>You can't design and program in a vacuum.  If your design doesn't work
>with the //gs hardware, then your design is inferior to the ones that do,
>no matter how sophisticated it may be.

My program runs on the Mac.  What are you talking about?


-- 
Ian Schmidt        |"And so it crept out of the atomic mists --the incredible
Two Meg Software   | Silverware Creature.  Its only goal: to destroy
irsman@iastate.edu | mankind as we know it -- spooning and forking its way to
IRSMan@aol.com     | world domination" - J.M. DeMatteis, X-Factor #94.