Copy link to clipboard
Copied
I am getting this error in the beta 25.4.0 build 83
All I have done to generate this is drop the warp stabilize effect on 3 clips, turned on detailed and turned off fast.
the error appears a short time after the the clip starts to analyze for warp stabilize.
Not sure if the timeline itself is generating this error when it draws the thumbs, or the warp stabilize effect is generating it as it processes the clips.
CPU and GPU are not very busy when this happened, or SSD's
In this state while warp stabilize is running, premier is highly non responsive on Time line scroll, other windows are performing fine. If I move to a place on the timeline where none of the clips I have warp stabilize working on, the timeline returns to normal performance, and can play video smooth in the program monitor also.
it seems that the thumbs for the time line stopped drawing after these errors appeared: I had continue thumbs on at the time, but I changed it back to show head and tail only when this screen shot is taken:
If I zoom into the time line more the heads or tails still don't redraw:
Copy link to clipboard
Copied
FlyingFourFun >>In this state while warp stabilize is running, premier is highly non responsive on Time line scroll >>
have seen this for a while (thought it was my machine).
Copy link to clipboard
Copied
Thanks Ann, I dont typicaly use warp stabilzie (I'm pretty commited to Mocha Pro for this) but since I was testing the Beta, I thought I would try the built in effects and stumble into this as a result. It might be 'normal' but its not very pleasent either.
The error was also concerning - and seems to have some effect on UI element rendering if nothing else.
Copy link to clipboard
Copied
Having the same issue. But it only exists in this one project with these clips. I have done nothing different than normal.
Copy link to clipboard
Copied
Facing same issue.
Following up for resolution I was using warp stabilization and getting this error
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Same error, using Gaussian Blur mask path auto-tracking feature. It times out after a few frames.
Copy link to clipboard
Copied
Also just experienced this error when tracking a Lumetri-based mask on Canon C500 Log Footage.
Saving the project, closing Premiere and re-opening everything and I can track mask again for a while, then the error occurs again.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now