CompuServe Thread

Autodesk Multimedia Forum · Hware/OpSys/video

Par Join Problem

12 messages in this thread

#134681From: Andrew SinagraNov 9, 1994 1:30 PM

All, Up untill now I haven't had any problems with the PAR. For some reason, when I join two ani's I get frames that are ruined some how. It looks like this giant mess of colors and I usually get one or two per join that I do. I recently started using the 1.30b software, but I can't remember if this started before or after I switched. How can I cure this? Andrew

#134785From: alec jasonNov 9, 1994 8:53 PM

Andrew, I have had the same problem but the sad news is that NO ONE knows why this happens: neither DPS nor Micropolis. I've talked to everyone about it and all I get are shrugged shoulders. At least there are two of us reporting the same problem. Be sure to contact DPS and let them know about our problem. Alec Jason

#134789From: Tim c BrananNov 9, 1994 9:05 PM

It sounds more like you need to optimize the PAR drive. I find I have to do this very frequently when joining animations, as I sometimes get frames that sort of "freak out" color-wise. Usually when I optimize, they play fine. I'd try this first before leaping into anything more drastic.

#134890From: Andrew SinagraNov 10, 1994 10:01 AM

>>It sounds more like you need to optimize That's what I thought the problem was, but I optimized right before I did the join and it still happened. I tried it several times with different animations and it never fails to get the messed up frames. I have 900 meg worth of animation on a 2217A, and I heard once that the PAR's performance degrades as you fill up the drive. Is this true and could this possibly be related to my problem?

#134923From: Tim c BrananNov 10, 1994 12:07 PM

try optimizing after you join. I also have heard that the performance degrades on certain tracks of the hard drive, but I only have about 800 meg worth of stuff on my 1.7 gig drive, so I am only about half full.

#134930From: ROBERT RITGERNov 10, 1994 12:24 PM

Andrew: I just got a coupla' frazzled frames as you've described. Optimizing immediately AFTER I joined the segments completely cured the problem. I would delete the original segments, rename the TMP.ANI and then optimize if your close to maxing out your drive. Bob

#134992From: Andrew SinagraNov 10, 1994 4:36 PM

Thanks for the help. I'll try optimizing after the join on the next job. Thanks again, Andrew

#135725From: Hansoo KimNov 13, 1994 10:46 PM

Hi, Do you have lots of still images in your PAR? If you have, that might be the problem. When you store stills, they are stored in the middle of the disk while animations are stored in the outer edge of the disk. So even if you have, let's say, 300meg free on Par, if you have stills in Par you don't have continous 300meg. Hope to cure your problem. bye.

#135850From: Andrew SinagraNov 14, 1994 12:20 PM

I do have several stills, so that may be a problem. I did not know that the PAR stored stills in the middle. Why wouldn't it just store the files between animations or after animations to make it continuous?

#135955From: ALAN IGLESIASNov 14, 1994 6:32 PM

As far as I know, Andrew, the PAR stores. STLs on the slower, inside tracks of the HD to leave room for the more demanding .ANIs on the outer, faster tracks.

#136126From: Andrew SinagraNov 15, 1994 8:01 AM

This makes sense, rather than putting stills within an animation. Andrew

#136003From: Gus GrubbaNov 14, 1994 8:48 PM

>> So even if you have, let's say, 300meg free on Par, if you have >> stills in Par you don't have continuos 300meg. Not so… Animations are written from the outer edge in. Stills are written from the inner edge out. Nothing gets "started" from the middle of the disk.