Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Comp missing frame that is fine in PreComp. Can't render. Can't export. Error 25::244

New Here ,
Jul 18, 2024 Jul 18, 2024

Hello,

 

I have encountered a very odd issue where my main composition is unable to (0ms apparently) render a single frame and it appears black. When pressing space to playback, I receive the following error when pressed BEFORE the missing frame OR during export: After Effects error: bad checkout ID passed to checkout_layer_pixels (25 : 244). This happens on both 2023 (ran on rosetta so I can select more choice of 3rd party plugins) and the converted proj file on 2024. 

 

I am on a 16GB MBP M1, Sonoma 14.1.1.

 

The suprising part here is that the frame is totally fine in my precomp. It runs smoothly and renders it, so something is unable to communicate that frame back to my composition, clearly. 

Bug Unresolved
TOPICS
Troubleshooting
3.8K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
8 Comments
New Here ,
Jul 18, 2024 Jul 18, 2024

I personally wonder if the issue has been caused by some sort of corruption for that frame between compositions that could have happened during a crash that occurred earlier on possibly due to me leaving rotoscope unfrozen. Is there a way I can see my crash log history

Translate
Report
Adobe Employee ,
Jul 18, 2024 Jul 18, 2024

If you're submitting the crashes, we can look them. 

 

That checkout message is definitely something to do with data being corrupted. Can you turn off the various layers and/or effects and see if one in particular is causing the error?

Translate
Report
New Here ,
Jul 18, 2024 Jul 18, 2024

I'm pretty sure I hit submit when I crashed earlier. All my autosaves on both versions of AE I run in my autosaves folder continue this issue. I have tried disabling multicore render and cleared my cache. If the frame is not an issue within the pre-comp, surely no effects in there can be causing this?  In my main comp there are no effects applide to this layer so it surely can't be that? 

Screenshot 2024-07-19 at 00.41.57.png

Screenshot 2024-07-19 at 00.42.20.png

Screenshot 2024-07-19 at 00.42.46.png

Translate
Report
New Here ,
Jul 18, 2024 Jul 18, 2024

Just an update; 

 

I made a brand new comp (3) and copied over my darkness comp into it and it now renders the frame. The issue must have been with comp (2) for some unknown reason. Doens't make logical sense to me, so must have corrupted. I will try to export. On another matter, after copying in another comp into this new comp, which was not a problem earlier, I get this weird blue effect which did not exist previously as shown in the earlier screenshots. I simply copy pasted this out of comp2 into comp3 and this has happened.

Screenshot 2024-07-19 at 00.49.00.png

Translate
Report
New Here ,
Jul 18, 2024 Jul 18, 2024

To outline more clearly how strange this is, look here at my comp 'darkness' which is on the left, that is inside comp 3, on the right, with nothing applied to it.

Screenshot 2024-07-19 at 00.59.03.png

Translate
Report
New Here ,
Jul 18, 2024 Jul 18, 2024

It's only impacted the area of the layer which wasn't covered by my solid

Screenshot 2024-07-19 at 01.09.16.png

Translate
Report
New Here ,
Jul 18, 2024 Jul 18, 2024

Oddly, after exporting, I cannot see the artifact so the problem is with my preview.

Translate
Report
Engaged ,
Sep 11, 2024 Sep 11, 2024
LATEST

I have had this many times over the years.

You have to manually delete all adobe caches and restart your machine.

purging cache through the app or preferences does not fully clear the cache.

I suspect it is something to do woth a bad block on SSD.

I call them cache ghosts, and the do soemtimes render.

But often they are simply stuck in a previous version of the frame so you can't tell what you are actually working on now.

Not sure what the fix is, I think it is just AE hasn't joined the SSD world properly yet

Translate
Report