Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-01-10Task scheduler: Use const qualifier in callbacks for parallel rangeSergey Sharybin
2018-01-10Task scheduler: Use restrict pointer qualifierSergey Sharybin
Those pointers are never to be aliased, so let's be explicit about this and hope compiler does save some CPU ticks.
2018-01-09Task scheduler: Use single parallel range function with more flexible functionSergey Sharybin
Now all the fine-tuning is happening using parallel range settings structure, which avoid passing long lists of arguments, allows extend fine-tuning further, avoid having lots of various functions which basically does the same thing.
2018-01-09Task scheduler: Get rid of extended version of parallel range callbackSergey Sharybin
Wrap all arguments into TLS type of argument. Avoids some branching and also makes it easier to extend things in the future.
2017-12-15Tracking: Cleanup, fix typo in variable nameSebastian Koenig
2017-12-15Tracking: Pass all markers to autotrack at onceSergey Sharybin
This solves delay before tracking actually starts. The issue is reported by Sebastian over IRC, thanks!
2017-12-15Tracking: Cleanup, make autotrack context creation code more granularSergey Sharybin
2017-12-15Tracking: Cleanup, use more const qualifiers when appropriateSergey Sharybin
2017-11-27Tracking: Cleanup. make code friendly for multi-column editingSergey Sharybin
2017-11-26Removing OMP: autotrack BKE code.Bastien Montagne
Pretty straightforward this time, we already have a single struct pointer containing all needed data (or nearly). And we gain about 10-15% speed on tracking! :)
2017-08-14Tracking: Cleanup and some commentsSergey Sharybin
2017-08-11Cleanup: whitespaceCampbell Barton
2017-05-26Fix T50908: Motion Tracker ignored grease pencil maskSergey Sharybin
This feature got lost with new auto-track API, Added it back by extending frame accessor class. This isn't really a frame thing, but we don't have other type of accessor here. Surely, we can use old-style API here and pass mask via region tracker options for this particular case, but then it becomes much less obvious how real auto-tracker will access this mask with old style API. So seems we do need an accessor for such data, just matter of finding better place than frame accessor.
2016-07-21Tracking: Fix possible cases when tracker will try tracking failed tracksSergey Sharybin
2015-11-23Cleanup: shadowing (blenkernel)Campbell Barton
2015-04-22Tracking: Code cleanup, de-duplicate some code in tracking context finishSergey Sharybin
2015-01-23cleanup: styleCampbell Barton
2014-12-15Tracking: Fix wrong logic in tracks synchronizationSergey Sharybin
There was some stupidness in the way how tracks are synchronized from the job to actual DNA data leading to all sort of weird and wonderful failures again.
2014-12-15Tracking: Avoid possible treading issue reading the frame to syncSergey Sharybin
2014-12-15Tracking: Fix possible race condition accessing the tracksSergey Sharybin
Writing to the tracks was already inside the lock section, but reading was not. This could have lead to race condition leading to all sorts of weird and wonderful artifacts.
2014-11-02Cleanup: styleCampbell Barton
2014-11-01Cleanup/fix from latest coverity report.Bastien Montagne
Mostly harmless things, though the 'multires' error was a real bug.
2014-10-30Libmv: Support disabled color channels in tracking settingsSergey Sharybin
This was never ported to a new tracking pipeline and now it's done using FrameAccessor::Transform routines. Quite striaghtforward, but i've changed order of grayscale conversion in blender side with call of transform callback. This way it's much easier to perform rescaling in libmv side.
2014-10-30Libmv: Replace region tracker with autotracker in BlenderSergey Sharybin
The title actually tells it all, this commit switches Blender to use the new autotrack API from Libmv. From the user point of view it means that prediction model is now used when tracking which gives really nice results. All the other changes are not really visible for users, those are just frame accessors, caches and so for the new API.