- User Since
- Jun 1 2018, 3:52 AM (79 w, 1 d)
Wed, Dec 4
@Sybren A. Stüvel (sybren) I will try to apply my depsgraph-fu. this will probably be just bad "initialization" of scene_eval I assume.
Indeed. In best case we could re-use IMB_ functions and enums.
Mon, Dec 2
- rebase, bump subversion
This crashes in my case, but I can see where the issue is.
I can confirm change of opacity not working.
Sun, Dec 1
This is covered by T59540
Speed fx basically changes framerate of strip, and Blender currently doesn't support this very well.
Fri, Nov 29
Not quite, I have done some triaging, and assumed, that user may started to generate proxies for his files and process has been interrupted. In such case all generated proxies would be deleted. Not only those interupted and pending.
So technically this may be a feature request, but very reasonable.
Thu, Nov 28
I guess something like this could work, will have look into this in debug.
Wed, Nov 27
Please don't close this task, it has to be worked on.
No worries, I guess that nobody was injured figuring out what issue is and how it can be solved :)
I will add link to Blender manual
I could reproduce this, but I haven't opened this because I wanted to confirm cause of this.
Mon, Nov 25
Thanks for correcing me.
Is there any way to cache these frames ?
Thu, Nov 21
Copying + paste should include all necessary data, so definitely a bug IMO.
Mon, Nov 18
Thu, Nov 14
Mon, Nov 11
There is scene strip using a host scene.
Not sure if fallback should be 0 or seq->start.
Fri, Nov 8
Not commenting on code itself, but changes like this are discouraged unless there is very good reason to do them. Reason is, that it will break existing scripts or addons.
I just quickly skimmed over this. Seems OK, just please check when adding new region, if any versioning code is needed, so older files can use this feature.
Nov 3 2019
@Campbell Barton (campbellbarton), Honestly this time I just didn't check for errors - they were there, so this could be preventable. But there are cases, where you get warning on GCC and not on MSVC
@Campbell Barton (campbellbarton) Can I commit fix or do you want diff for this?
Nov 1 2019
Oct 31 2019
- Fix tool and operator names
- remove dummy fn
- Add cut type selection to tool panel (no icons)
- Rename operator run_as_tool property
- add comment
- Reimplement operator enum item as separate bool
Oct 30 2019
- Pass ReportList instead of wmOperator
Oct 29 2019
Digging through WM API, I realized, that the invoke method, was actually used as a confirmation.
It was quite poor in execution, so it would be better if we could explain to user, what is going to happen. Not quite sure if that is possible
- fix typos
Oct 28 2019
This action can not be undone, so confirmation dialog must be used.
"All proxy files for this strip will be permanently removed. Do you want to continue?"
Or something in that note.
In example addon operator was run with ctrl+b. Don't modify original function, make another mode of an operator and register it in keymap.
Deselect/append should work with shift and box-selecting handle so it would be ctrl+⇧+b
Oct 25 2019
Oct 23 2019
@Campbell Barton (campbellbarton)
I did not merge, because I acidentally changed addons_contrib - wasn't sure what would this cause, so I didn't merge.
I left immediately message in #blender-coders. I guess I could proceed with merge given that no files then I wanted were modified, but I didn't want to make more mess in case this would cause problems.
Oct 21 2019
Ah sorry, I see now
- Address points from review.
Have you tried, if this would work? I think, that it works when invoked by keyboard and resolve mouse position to channel you want to select.
Other than 1 nitpick looks OK.
Oct 20 2019
Oct 18 2019
There is still crash when changing scenes, so I am reopening this.
Oct 17 2019
Will look into this, still working on high prio stuff
Scene strip using camera input should not produce sound when played. With this patch it does because sound may not be removed, because scene strip for same scene is used in meta mode.
Oct 16 2019
@Fahad Hasan (cgvirus) if this fix breaks any fundamental workflow, I guess it should be reported as a bug explaining what is broken with reference to correct behavior and tag specific project.
Abandon in favor of D6073
@Philipp Oeser (lichtwerk) Honestly, I didn't looked on why crash happens, knowing that use-case is not supported.
I didn't know about PROP_ID_SELF_CHECK. I guess I should close D6054: Fix T69636: Crash when rendering scene srtip.?
Ok, but don't dig this one up pls :)
This report was closed, because changing default blend mode pretty much resolved performance difference in context of this report.
Oct 15 2019
@Campbell Barton (campbellbarton) I am not sure if T69636: Crash when rendering in VSE is even valid then, because you can choose camera "from another scene" even in properties editor as source for rendering.
I guess I could look up available camera in collection? But not sure if collection is filled by depsgraph or why it isn't available during handling RNA.
- Revert "Fix T69636: Crash when rendering scene srtip."
- Use poll function to filter scenes
Oct 14 2019
Oct 13 2019
There is also task T66461: Sequencer: Scene strips cameras from all scenes can be selected
I am not quite sure how to solve that. It would be nice to filter in context of some arbitrary data (or list of data) provided by argument, so I could filter all cameras of provided scene. I guess I could implement that, but I would like to hear feedback.