CompuServe Messages

I guess what it really comes down to, James, is this: If you are looking to get maximum image quality from your PAR system at all times, then using the PAR drive for animation "storage" is pretty much out of the question. As the drive fills, you will definitely start to see a degradation of quality, due to the HD's decreasing efficiency reading from inner tracks. This is only an inconvenience if we assume the PAR drive is a viable place to store multiple animations for future use while still maintaining optimum throughput/image quality for subsequent animations, which it's just not. So, like many operations in the 3D animation business, it's probably a good idea to plan our projects around the limitations of the HW involved with the project. Here's some of the things I consider: 1) If image quality is an issue for the animation (and it probably usually will be) always start with a relatively fresh PAR drive. If I cannot get an animation compiled with a BL of at least 250 (depending on the characteristics of the animation itself), I'll delete stuff from the PAR drive until am assured that I am getting the best possible quality for the project. You be the judge of the level of image quality your project demands. 2) Always keep in mind that, in order for the PAR to work properly, all frames (in an animation) have to be contiguous, and be in an area of the disk that supports the BL used to compile that particular animation. If the data gets moved around (say, through copying, splitting, joining, restoring, etc.) to an area that doesn't support it, you can have problems. 3) NEVER erase .TGA frames from your system (at least back 'em up!) until the animation is safely on video tape, and the client has signed off on the project (read: you've gotten your check!<g>). Consider adding HD space (it's gettin' really cheap these days) to your PAR system to safely store .ANI files while you are keeping your current PAR work at highest quality levels. As far as appearing professional to your clients goes, you don't need me to tell you that a thorough understanding of your tools is essential to "delivering the goods", and this forum is a great way for all of us to extend our knowledge. That being said, I always try to minimize potential problems by only promising what I'm *absolutely sure* I can deliver, and try to *never* rely on specualtion or an assumption. In other words, no matter what I read or am told, until I see something actually work, know how it works, and pretty much make it work myself, I will not promise a client that something is a reality. This may seem a little restrictive, but I cannot tell you the amount of times this atitude has saved my butt. It usually only means a little extra time to get familiar with a new piece of equipment or operation before offering the service to a client. And this, I feel, is a good part of what the client is paying for when he hires an expert or consultant. I hope this is taken in the proper context! I do not wish to sound "preachy", but you brought up a good point, and I just wanted to let folks know what works for me…. Thanks. Best of luck, -Alan