- Kaunas, Lithuania
- https://aras-p.info/
- Joined on
2022-01-20 -
-
From what I saw, yes, that would be the "issue", but it should not be the issue for rendering.
@iss you sure it would not affect rendering? From what I can tell, there's a seek to keyframe…
As far as I can tell, this got fixed by merge of #126405 (commit 528471541b3c). Please comment or reopen if you still see the issue; I can no longer reproduce it.
@iss could it be that your change removed even "within one frame" image cache? From what I recall, the whole effects stack rendering does several passes over the strips within the whole stack…
@ThinkingPolygons @iss could this issue be caused by fairly large keyframe interval used in the video? I noticed keyint=250 among encoder settings, which is like keyframes every 250 frames.…
Most likely some image related code (still) uses 32 bit integers for size or address calculations -- whereas 16k x 16k float image is exactly 4GB size, which is the point where unsigned 32 bit…
Yes, anchor was dropped with this PR.
My thinking was that maybe anchor should not exist at all functionality wise. Like today, center alignment works as I would expect, all good: ![Screens…
To Harley's point about combining sequences etc., to me it seems like this branch, besides "wrong" glyph advancement, does not make things worse for VSE text strips. Some combining sequences were…