@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.

• rebase, bump subversion

This crashes in my case, but I can see where the issue is.

I can confirm change of opacity not working.

This is covered by T59540
Speed fx basically changes framerate of strip, and Blender currently doesn't support this very well.

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.

I guess something like this could work, will have look into this in debug.

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
https://docs.blender.org/manual/en/latest/editors/preferences/system.html#memory-limits

I could reproduce this, but I haven't opened this because I wanted to confirm cause of this.

In D6110#146413, @Germano Cavalcante (mano-wii) wrote:

Honestly I am not very satisfied with this solution.
It does not follow a convention producing an unexpected result when more than one option is enabled.
If one option discards the other, then it is better to think of a different layout and change the rna property in C to become an enum.
I'm not sure how this effect works, but it seems to need to be rethought.

In T71734#816823, @Guillaume M (mathers) wrote:

Just pointing out that this is an issue for rendering, not preview !

Thanks for correcing me.

@Guillaume M (mathers)

Is there any way to cache these frames ?

Copying + paste should include all necessary data, so definitely a bug IMO.

In D6137#145117, @Julian Eisel (Severin) wrote:

Note that we're probably going to change the graph editor, so that Include Handles is enabled by default there, activated with B rather than Ctrl+B. See D6235.
Now, if that is good default for the VSE, I don't know.

There is scene strip using a host scene.

@Dalai Felinto (dfelinto)

Not sure if fallback should be 0 or seq->start.

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.

@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?

• 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

• Pass ReportList instead of wmOperator

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

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

@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.

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.

In T59954#798342, @Alessio Monti di Sopra (a.monti) wrote:

@Richard Antalik (ISS) What should be the behaviour for the operator? I see three main options:

1. Frame everything no matter where in the timeline
2. Frame everything starting from 0 (what it does now)
3. Frame everything starting from the start frame

It could also be a mix, for example using the start frame as min, unless there are strips left to it.

There is still crash when changing scenes, so I am reopening this.

In D6084#140179, @Sergey Sharybin (sergey) wrote:

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.

If scene is used as meta strip it should like (no pun intended :) the sound is expected to be playing?

Will look into this, still working on high prio stuff

In D6084#140079, @Sergey Sharybin (sergey) wrote:

Now even scenes using camera input will play audio.

Please elaborate.

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.

@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.

In rB64c222ff58577b80994a11fa63c137b89a3083fc#248958, @Hjalti Hjálmarsson (hjalti) wrote:

Can we have this be a setting in the preferences?
If you use Alpha Over 99% of the time (like myself), it becomes very frustrating to have to manually change this for every single strip, every single time. I spoke to other users that used to suffer from the same problem before we changed the default to Alpha Over. I can imagine the same frustration for users that want the default to be something else than Alpha Over (or whatever the default is) so a setting in the preferences would seem to be a good solution for everybody.

! In T70845#796716, @Philipp Oeser (lichtwerk) wrote:
It is not supported setting scene to self, but switching to a different scene (other than self) should be supported, no?

Abandon in favor of D6073

In D6053#139278, @Sergey Sharybin (sergey) wrote:

Probably is fine, but totally deserved more explanation about what exactly is causing the issue.

@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.

@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

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.