Video Editor: Opening several Sequencer area instances will cause bad playback rate #69927

New Issue

tintwotin · 2019-09-16T09:10:27+02:00

tintwotin commented

2019-09-16 09:10:27 +02:00

Opening more sequencer timeline areas will cause bad playback rate, but in preview mode it doesn't.

Have a Video Editor area open with a Sequencer and Preview and notice the playback rate.
Open another Sequencer area and notice the drop in playback rate.
(Only Sequencer areas will have this effect, but not Sequencer Preview)

As seen in this gif:

Operating system: Windows-10-10.0.17763 64 Bits
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-14 14:25, hash: 38cc53a168

Opening more sequencer timeline areas will cause bad playback rate, but in preview mode it doesn't. Have a Video Editor area open with a Sequencer and Preview and notice the playback rate. Open another Sequencer area and notice the drop in playback rate. (Only Sequencer areas will have this effect, but not Sequencer Preview) As seen in this gif: ![SequencerTimelineInstances2.gif](https://archive.blender.org/developer/F7750370/SequencerTimelineInstances2.gif) Operating system: Windows-10-10.0.17763 64 Bits Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-14 14:25, hash: `38cc53a168`

tintwotin commented

2019-09-16 09:10:27 +02:00

Added subscriber: @tintwotin

tintwotin changed title from ~~Vide Editor: Opening several Sequencer(timeline) instances will cause bad playback rate~~ to Video Editor: Opening several Sequencer area instances will cause bad playback rate

2019-09-16 09:11:18 +02:00

Jacques Lucke commented

2019-09-17 16:40:45 +02:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-09-17 16:40:45 +02:00

I cannot reproduce it in my simple test case. Can you reproduce this with any video? A test file would probably be helpful.

tintwotin commented

2019-09-17 21:12:41 +02:00

@JacquesLucke It is properly dependent on how powerful your computer is. Mine is not very powerful, so I'm just using a 720p clip for the gif above, where the effect is quite visible. Maybe you could try with some 4k footage and keep adding sequencer areas while the video is playing(uncached) timeline in an area with sequencer+preview.

If you need some 4k footage, maybe some of this would work: https://www.pexels.com/free-4k-footage/

@JacquesLucke It is properly dependent on how powerful your computer is. Mine is not very powerful, so I'm just using a 720p clip for the gif above, where the effect is quite visible. Maybe you could try with some 4k footage and keep adding sequencer areas while the video is playing(uncached) timeline in an area with sequencer+preview. If you need some 4k footage, maybe some of this would work: https://www.pexels.com/free-4k-footage/

ChristopherAnderssarian commented

2019-09-18 00:48:21 +02:00

Added subscriber: @ChristopherAnderssarian

ChristopherAnderssarian commented

2019-09-18 00:48:21 +02:00

TBO Timelines have always been a resource hog.
And what's also demonstrated in your gif is moving the mouse over different elements causes the UI to draw at different frame rates...
ref: #60336#596645

In #68433#751669
Which editors are refreshed depends on where you start the playback. This is by design, and starting playback over the 3D viewport will generally be fastest.

Optimizations to animation playback of other editors are possible, but not considered a bug.

Not sure if this applies here, if on a per workspace or a per editor type...

TBO Timelines have always been a resource hog. And what's also demonstrated in your gif is moving the mouse over different elements causes the UI to draw at different frame rates... ref: #60336#596645 > In #68433#751669 > Which editors are refreshed depends on where you start the playback. This is by design, and starting playback over the 3D viewport will generally be fastest. > > Optimizations to animation playback of other editors are possible, but not considered a bug. Not sure if this applies here, if on a per workspace or a per editor type...

Richard Antalik commented

2019-09-22 04:40:35 +02:00

Added subscriber: @iss

Richard Antalik commented

2019-09-22 04:40:35 +02:00

Changed status from 'Open' to: 'Archived'

Richard Antalik closed this issue

2019-09-22 04:40:35 +02:00

Richard Antalik self-assigned this 2019-09-22 04:40:35 +02:00

Richard Antalik commented

2019-09-22 04:40:35 +02:00

I can confirm, performance decrease with each timeline opened.

Obviously, resources are needed to draw each timeline area.
Overall I think, that VSE UI drawing code is in quite good condition with no obvious performance sinks.

Unless I am proven wrong here, I have to say, that you have either to upgrade hardware, or keep conservative editing layout.

I can confirm, performance decrease with each timeline opened. Obviously, resources are needed to draw each timeline area. Overall I think, that VSE UI drawing code is in quite good condition with no obvious performance sinks. Unless I am proven wrong here, I have to say, that you have either to upgrade hardware, or keep conservative editing layout.

tintwotin commented

2019-09-22 08:38:55 +02:00

This is actually a regression. In 2.79 this does not happen, as seen in this gif.
In 2.80 the fps is halved each time a new sequencer-timeline is opened.
In 2.79 the fps maybe drops at little(0.5 fps) or maybe not at all.

2.80:

Another thing to notice is that in 2.79 this same clip(720p) played at almost 24 fps(correct) and in 2.80 it played at 21-22 fps(not correct) with only one instance of sequencer-timeline.

This is actually a regression. In 2.79 this does not happen, as seen in this gif. In 2.80 the fps is halved each time a new sequencer-timeline is opened. In 2.79 the fps maybe drops at little(0.5 fps) or maybe not at all. ![Multi_seq_areas.gif](https://archive.blender.org/developer/F7767732/Multi_seq_areas.gif) 2.80: ![SequencerTimelineInstances2.gif](https://archive.blender.org/developer/F7750370/SequencerTimelineInstances2.gif) Another thing to notice is that in 2.79 this same clip(720p) played at almost 24 fps(correct) and in 2.80 it played at 21-22 fps(not correct) with only one instance of sequencer-timeline.

Richard Antalik commented

2019-09-22 22:24:01 +02:00

Try disable cache bar on the bottom if that helps (no regression when I did that.)

That cache viewing thing is a bit resource intensive, but it was written with performance in mind.

Perhaps I can optimize iterating even more, but this will make code a bit more complex. Will have to think about this a bit.

Try disable cache bar on the bottom if that helps (no regression when I did that.) That cache viewing thing is a bit resource intensive, but it was written with performance in mind. Perhaps I can optimize iterating even more, but this will make code a bit more complex. Will have to think about this a bit.

Richard Antalik commented

2019-09-22 22:33:01 +02:00

Changed status from 'Archived' to: 'Open'

Richard Antalik reopened this issue

2019-09-22 22:33:01 +02:00

Richard Antalik commented

2019-09-30 00:26:18 +02:00

Closed as duplicate of #70229

Richard Antalik closed this issue

2019-09-30 00:26:18 +02:00

Sign in to join this conversation.