- User Since
- Nov 1 2015, 9:16 AM (128 w, 6 d)
Aug 31 2017
I support this change; in fact, I never use the scene itself in the VSE, because somehow I conceptually found it wrong (kind of self-recursion :-) ). I think we should try not to break existing files, so my vote goes for:
- Allow existing files to render, just disallow the operator in to add the scene to its self, so newly created files don't suffer the problem.
Apr 11 2017
I've added the missing UI option to toggle whether the user wants this fix or not.
Apr 6 2017
Mar 27 2017
Mar 12 2017
This is essentially the same as T49261
Thanks for working on this!
I've spent some time trying to undestand how this works, and I got something which is more or less working, though for some reason the image in the sequencer sometimes is updated in the wrong way.
Mar 11 2017
Sergey, forget my last question; I see that blender files are supposed to be both backward and forward compatible, so we cannot play tricks based on the blender version.
Ouch, this is quite annoying, I just hit this bug.
Sep 22 2016
Aug 31 2016
Aug 9 2016
I'd like for this bug to be reopened. The current implementation makes it rather troublesome to import high resolution images and have them rendered at a lower scale, like the bug description says. This becomes even harder when importing videos, because doing similar preparation works for videos is far from trivial.
And, most importantly, the current implementation makes it impossible to animate the scale property on such imported images or videos: imagine having a project for a 640x480 video, and importing a 1920x1080 video, which we want to show with an animated scale ranging from 0.4 to 1.0.