After Effects error:attempt to get a value from a time stream with no key values.
Hi Everyone,
I recently bought a file (today) here an video hive, and I am having this issue, the author has made a few suggestions, unfortunately they weren’t really sollutions. He did offer the info that he had not encountered this but recalls only one other person having this issue.
Anyone have any suggestions?
Many Thanks,
TTD
Thats really weird. I think it has something to do with your machine, because if that had been an error the reviewer received the file would have not been accepted. Do you have any other machines with AE installed that you can try the file on?
I think you don’t have keyframes on some property there, or they are from a different range. If you have an expression applied, it may not evaluate correctly.
Try to create or adjust your keyframes(expressions) to the right format for that specific property.
hth
Can you tell me which frame exactly does your render fail? and which comp are you rendering?
I will look again closely at the file and try to offer a solution for you.
The user: HASSAS is the only other user who had this problem, did you manage to get in touch and ask about the his solution?
As Mark mentioned, it wouldn’t have passed testing if the file is at fault.
However I’d like to get to the bottom of it and figure it out if you haven’t already, you mentioned your AE knowledge is not vast, lets see if we can solve it!
Let me know about the items above, and I’ll investigate as much as I can for you.
I wonder if it’s to do with RAM. After Effects eats RAM, hates running out of it and can give weird errors if it’s short of the stuff.
How much RAM do you have?
Check if there are any really large bitmap images or compositions in the project (particularly ones whose in points are on the frame where you receive the message) These could be the problem.
Try turning up After Effects’ memory allocation in the preferences.
Make sure all other applications are closed before rendering.
Try rendering at half quality. Just to see if this helps.
If you’ve been working on the file, save it, quit After Effects and then re-open the project before you render.
-felt tips
I wonder if it's to do with RAM. After Effects eats RAM, hates running out of it and can give weird errors if it's short of the stuff. ...
If it’s such a specific error “:attempt to get a value from a time stream with no key values.” it has nothing to do with the RAM memory. I checked around and it’s exactly what I said before.
hth, regards
True, but stranger things have happened when a program runs out of RAM. In AE, I’ve had expressions spontaneously stop working, 30 lines that suddenly go missing from the end of an expression, odd errors out of the blue, complete wipe outs…
It’s possible that the AE gets its RAM in a tangle and the memory address of the key frames in question somehow becomes corrupted.
I can’t think of any plug-in that specifically requires that there be keyframes. Properties all have an implicit value whether keyframed or not. Likewise, an error in an expression should simply fail to compile and give an expression error. It also shouldn’t be intermittent. It either compiles or it doesn’t.
That’s why it’s such an odd error - and given the minimal information about it on-line, a rare one too.
As Mark pointed out, the fact that it only happens on some machines would suggest that it’s something specific to the set up of that machine. When it’s something to do with hardware, RAM’s gotta be the prime suspect.
I don’t say that’s definitely what it is, but it’s worth checking out.
After Effects error:attempt to get a value from a time stream with no key values.Hi Everyone,
I recently bought a file (today) here an video hive, and I am having this issue, the author has made a few suggestions, unfortunately they weren’t really sollutions. He did offer the info that he had not encountered this but recalls only one other person having this issue.
Anyone have any suggestions?
Many Thanks,
TTD
So I’m not sure if you ever figured this out. I just stumbled upon this and have a solution for you that usually works for me. I get that error sometimes if I drag a project into the project window to open it if the project has expressions in it. What works for me is to actually go to -file -open project. I usually stop getting the error after that. Its a weird bug thing when dragging and dropping projects to open them.