- User Since
- Jan 17 2010, 3:58 AM (508 w, 3 d)
Sep 30 2016
Feb 20 2016
Sep 6 2015
Alright, updated diff, hopefully threadsafe check for refcounter added.
I added a generic check function to the ImBuf interface, since the spinlock
is static in that module, and this could be useful elsewhere. Also the correct
value to check seems to be refcounter==0 instead of refcounter <=1?
At least IMB_makeSingleUser() does that, but it also does that without
Aug 31 2015
Okay, so this checks the refcount now, but looking at
the values it seems a little unpredictable when the refcount
will actually be <= 1... whether the clip was loaded in the
sequencer or the movie clip editor seems to make a difference?
Anyways, this shouldn't hurt now, but these allocations seem to
be the thing that hurts performance the most during "normal"
playback, without effects, scaling or other compositing. Maybe
this could use some more refactoring to use a small pool of
already allocated frames?
Aug 21 2015
Interesting, this is what I get on 2.75a, on Windows7 64bit and OSX 10.9 64bit:
Aug 16 2015
The default antialiasing filter (Mitchell-Netravali) has negative lobes, meaning it produces sharpened edges.
While these edges look sharper, it can create pixel values outside the range of the original image.
Aug 15 2015
As the sample file demonstrates, a workaround is to bake the animation into keyframes, removing the constraint.
Aug 18 2014
Ah, okay. If fixing this is difficult I'm fine with closing this bug.
For any somewhat complex volumetric rendering scene I expect that value
has been touched, and I only found this in a simple test scene.
Okay, I was a little bit too quick with reporting this...