05-05-2010, 11:13 AM
Quality control check has revealed a discrepancy that would not affect the quality or effectiveness of the program, but it puts the program out of the build specifications by 3 seconds over 74 minutes. Because I am a perfectionist on this stuff, this is going to drive me crazy if I do not make it conform to my specified limits (1/10th of a second or less deviance over the length of any program), so I am going to re-do Phase 5 of the build for all six stages to adjust it. This will require more time, but shouldn't prevent me from being able to release either today or tomorrow. I just need it to be exact.
Subliminal Audio Specialist & Administrator
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!
