@Philipp Oeser (lichtwerk) Honestly, I didn't looked on why crash happens, knowing that use-case is not supported.
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.
If it helps:
Since rBd025119aeb12: Fix T69352: Audio strips don't update when changing `frame_start`, we are asserting here
Oops, Sorry about this. I got confused.
Reposting under another report.
@Jerome Scholler (jscholler) : cant see anything relating sound in your crash report...
Sure this is the right one? Sure this is the right report?
Full crash report
I know this is not the right place to ask questions, but now that I have the attention of knowledgeable people on the rather obscure and new matter of custom gizmos: How do I make a 2D gizmo pan and scale with the area? It seems like in the node editor as well as the sequencer preview the gizmo is always drawn relative to the area frame and not to the content of the area.
I made a stackexchange question as well, but I have a feeling it will go unanswered: https://blender.stackexchange.com/questions/155528/python-how-to-pan-and-scale-gizmogroup-with-background
The reason for closing this bug report is changing Blend Mode from Alpha_Over to Cross, but as mentioned above there are several additional reasons for poor playback rates in 2.80, as compared to older versions.
Confirmed, will check...
I'm sorry for digging this one up, but imo is the proxy panel still a mess.
Blend files attached. Thank you for looking into this.
Hello, it's a fresh 2.81 scene with nothing attached or modified. Should I upload it? Thanks.
Please always attach .blend file demonstrating the issue.
Mon, Oct 14
Well, I guess this should work for the other region_types as well...
Thank you so much! Using gizmos in the preview region is probably a more common use, but I didn't know about it. So I think you can also treat this as a matter of incomplete documentation.
This actually works for the preview area if you set
- bl_space_type = 'SEQUENCE_EDITOR'
- bl_region_type = 'PREVIEW'
Some time ago did @LazyDodo (LazyDodo) profile the export of the default cube with ffmpeg and in that case it was color management(implemented in april?), which caused slower exports. Maybe scene strip playback is affected by this too, but some non-ui option is set differently between 2.79 and 2.80?
@Sergey Sharybin (sergey) nope, for me as well speed are very high and similar.
@Bastien Montagne (mont29), can you reproduce the issue? For me both files are around 75 to 100 fps (jumping between those values).
Not sure whether that difference in speed is expected, maybe @Jeroen Bakker (jbakker) or @Clément Foucault (fclem) would know more? Or maybe @Sergey Sharybin (sergey), although I would not expect depsgraph to be a bottleneck with such a simple scene…
Sun, Oct 13
Actually this issue is not caused by moving the sequence.
Sat, Oct 12
I am not familiar with Blender's C code and really don't know if I am on the right track here, but there is one function that seems to be called in all spaces that I can get gizmos working and not in spaces that gizmos don't work for me (tested in text editor and VSE): WM_gizmomap_tag_refresh()
Fri, Oct 11
Thu, Oct 10
Wed, Oct 9
@Campbell Barton (campbellbarton) We need to exclude current scene in UI template listing. Should I create filter function using argument filter='AVAILABLE' for scene UI template? Or perhaps different filter type like 'NOT_ACTIVE'?
Tue, Oct 8
should be high if this is confirmed