This content has been marked as final. Show 5 replies
What type of source footages do you use? To what format are you rendering? Sounds very much like a CoDec problem.
2.75 GB of RAM? That's an odd number. You do know you need matching sticks of RAM (size / speed / etc), right?
What operating system are you using and to what codec are you rendering? What version of QuickTime do you have?
More trouble-shooting tips are found here:
- Jonas Hummelstrand
Mylenuim, working with quicktime h.264's. maybe this is the issue. I'm on a pc with quicktime 7.4.1 (not pro). I thought the latest quicktime came packaged with a lot of the codecs like h.264?
silversurfer, yah i didn't even pay attention when i wrote that. i copied it from My Computer properties. maybe that's all its recognizing.
Jonas, I'm on XP v5.1.2600 Service Pack 2 Quicktime 7.4.1 I'm working with h.264's. I've had this issue on my home computer as well which is also a fairly fast PC with quicktime 7.3 pro.
Mmh, yes, indeed that very likely would be to blame on Quicktime. You probably had better luck with CS3 which handles H.264 natively via MediaCore. My guess that it is simply some odd allocation of the compression which could be fixed, probably even a simple export from QT Pro to the same format. Do the files correctly play in QT player? As an alternative to QT Pro I recommend attempting to run it thru SUPER©, which is free. Perhaps this will repair the streams and prevent the errors. If not, you will have to shelve out some money or find otehr ways of converting your footage, I'm afraid.