CompuServe Messages

I had originally suggested this as a speedy way to resolve the dilema of multi channel rotoscope files and hard drive capacity and still be able to use the PAR for network rendering. I appreciate the double algorithm and the artifacts issue but maybe you'd care to comment on any possible way that network slaves can access the roto files on the PAR as animated tex. maps and then use NDUMP for the output back to the PAR. Greg P. says this network access is just about impossible and still keep the file sequence straight. Something about having to predict a future event (which file is going to be needed) and dumping it back to the dos path directory before the slave calls for it) and execut the future event just in time. In my simple way of resolving this issue is to put all the rotofiles on the dos drive in sequential order but compress the file to jpg size. I can do it now but it requires a slow VP rendering process to batch convert the *.ani's through the IFL procedure. Outputing from the PAR to JPG just seemed much simpler and faster. Maybe this reason will help you understand the 'why' behind this JPEG output request.