This is not an mFlare2 issue, the same problem occurs in Motion 5 when you attempt to, for example, use some GPU-accelerated filters on really large layers. ![]() This can be a problem when attempting to track a high resolution video from an integrated GPU as they can't handle large textures very well (most likely because they don't have their own video memory but "borrow" it from your RAM). ![]() Even though you're usually tracking a small portion of your video, there's no way of telling how the tracked object will behave so the entire frame needs to be sent to the tracker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |