CGTalk - little problem QT

station75

06-01-2003, 08:08 AM

hello

i've one strange problem with cinema 8.1 and quick time.
a few days ago i've rendered small animation (sth about 8 s) - the output file was *.mov (with option 'animation') i everything was ok.
Yesterday i've rendered second part of this animation (with new enviroment - i've posted) with the options like above (mov, animation) and... the animation is hmmm 'strange...' i mean it looks like cinema don't put some frames in mov, when i import animation to adobe after effects it show that these frames are white in AF. i try render it to AVI format and everything is ok. I also try reneder it to mov with option - sorensen 3 - and the same, all is everything, but the size of the file is smaller (i know that the sorensen codec do that :).

i've updated QT but the problem is still present.

here is my configuration:
- Athlon 2200
- 1 gb ram - dual planes
- epox 8rda2+
- Ati 9500 pro

(i've installed Xvid, Divx and AC3 codec too, but before my work with animation) maybe someone of You know where is the point of this bug? or it's my fault. but before i do it and never had problems like these.

Per-Anders

06-01-2003, 08:58 AM

ok, strangely enough i got something similar yesterday, though i'm rendering out to seperate frames, but from what i can tell it's a quicktime encoding problem. if you render to sepereate frames and then clink them in after effects or whatever other app then it's easy to sort out as you can simply re-render the missing frames, and they come out ok. for me this happened with net. anyhow, in the end it all seemed to sort itself out after a restart, and a few test renders. and of course simply re-rendering.

another thing someone told me to do, was to simply (if you're using net that is), remove the job.ini file, and remove the mov file or other files from the results folder, then start the job again, if your client machiens are set up to keep teh b3d's on them then it wont re-render everything, but will instead just recompile everything adn re-encode it all. the result of this should be the frames will be re-encoded with quicktime, and hopefully all should be well.

station75

06-01-2003, 09:12 AM

ok, strangely enough i got something similar yesterday, though i'm rendering out to seperate frames, but from what i can tell it's a quicktime encoding problem.

right, i think that qt codecs are hmmm... damage, i render this animation on single machine, but it looks like my hdd is to slow :)
(8 mb cache is to small?) but You help me much, i didn't think about rendering frames seperately and join them in AF. it's good idea :) i've read about this before but i don't know why i'm don't use this in cinema :) thx again. but still this bug is strange, i alwas think that qt format is the best for postprocessing, but now... :) i write this problem to maxon - maybe they know whats is going on :).

CGTalk Moderation

01-15-2006, 07:00 AM

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.