- User Since
- Oct 17 2005, 10:10 PM (783 w, 2 h)
Nov 9 2017
@Brecht Van Lommel (brecht) : thanks for validating the compiler version, maybe someone should update the blender wiki then!
Nov 2 2017
@Sergey Sharybin (sergey): the only two clean solutions would be:
@Sybren A. Stüvel (sybren): because that doesn't work.
Nov 1 2017
I'm happy with the macro solution.
Oct 29 2017
... like code path number 3 in the new version:
Yieks, that's a lot of duplicated code!
I did some tests with GCC 6.3 (Debian Stretch) with a simple test-file (that makes it easier to understand the generated assembler output):
Oct 15 2017
Oct 8 2017
Looks good to me. If noone else has any objections, I can commit.
First: I think it is sensible to add those, since they are available as basic layer effects in Gimp/Photoshop too and have their places (provided, that you got your formulas right, though, haven't checked).
Mar 9 2017
Workaround is available, yes:
Jul 13 2016
Feb 11 2016
@Aaron Carlisle (Blendify): which comes to no surprise, since you didn't follow my instructions carefully enough.
Feb 10 2016
It isn't hard to get the picture (even without a picture :) ):
Feb 1 2016
since modern versions of the codec use obfuscation techniques and can't be used (or even reverse engineered without the fear of being sued for it), I'm okay with removal.
(ffmpeg has added at least a format reader anyways)
Jan 8 2016
in principal: good idea.
Feb 13 2015
this is actually a feature (added by Brecht long ago):
- if you tab into metastrip(s), you can show the output of the sequencer of the timelines, which include the metastrip
Aug 31 2014
it is also available in DNA using properties API (everything in blender goes into DNA, there is no other way that data can end up in a blend file :),
but Sergey's new python version patching for cycles looks like it is a lot easier to read and maintain, so go ahead :)
Regarding TODO 2 :
May 12 2014
Apr 27 2014
Closed by commit rBa8eb95c4e9d6.
Dec 25 2013
there isn't much more to tell about it.
Don't forget to render 25% proxies for the preview screens, that's all.
the final timeline layout, when everything is finished, looks most of the time like this:
real world timeline looks e.g. like this (theatrical production):
If I intepreted your timeline correctly, you are editing shows which were recorded using several cameras, different angles?
Dec 24 2013
I can remember there used to be a hack in code which freed FFmpeg buffers of strips which are not under the current frame during animation rendering. But seems it's no longer used. Need to investigate reason for this. Unless it was giving issues it might be nice to bring it back.
hmm well, you'd have to add some silly code that does things like:
The proper solution is: