@Julian Eisel (Severin) Okay, could you maybe open a design issue, so C beginners will know that is is a welcome feature to work on?

Discussion about an icon to replace "Run Script" goes on here: https://devtalk.blender.org/t/new-icons-for-blender-2-8x/4651/735

So, no love for the Sequncer handles?

These settings will enable hardware acceleration -hwaccel auto and this one -tune fastdecode will allow a much faster playback in Blender(going from 20 fps to 30 fps on my low spec computer) and this one will use all threads: -threads 0 I don't know which ones are enabled in the Blender build of ffmpeg lib, but I know from testing alternative codecs for proxies, that these settings will make a difference in encoding/decoding speed(though some of them may be h.264 only).

Oh, this is great. Any chance for VSE handle selection too? Like this add-on: https://github.com/Salatfreak/VSEBoxSelectHandles

Just guessing here, but it seems to me changing the Set Proxy Size, when no proxies are generated, is still changing the resolution, properly mirroring the Resolution % in the Output options:

Well, users shouldn't have to deal with cache in the first place - is should work unnoticeable - so being able watch the cache working is imo mainly a developer/debugging tool - and therefore should be off as the default setting.

Could we have Show Cache switched off as the default setting until this is resolved?

Yes, same thing in the official 2.80.
Ex. shortcut for Play(the timeline header button) is visible in Layout Workspace, but not in ex. Animation, Compositing, Video Editor, 2D Animation, 2D Full Animation etc.

Here the panel headers are in the nuance between the level above them and the level below them - when opened. This way the headers have their own nuance, but is still a level/step down from the top level. Maybe it's too hard to notice?

You would still need the slider:

In T69684#776003, @Christopher_Anderssarian wrote:

Yet the default settings allow you to set it out of range -2 and 2. If it is set out of range, it won't pan at all.

This is for panning to more than 2 channels.
Here's my cheat sheet:

Unless this no longer works. I haven't checked the 2.8 release....

Testing the latest diff:

Thanks for the suggestion, but updating the driver doesn't change anything here.

It is actually like 2 fps faster with the node texture on(on a build I did this morning), so that doesn't explain the difference in playback rate.

Well, I spend a lot of time trying to locate reasons for the low playback rate in the VSE and posted about it here: https://developer.blender.org/T69334#782384 leading to nothing. Then I asked in the blender.chat if I should report the findings, as bugs and the reply was like "if Richard wanted it". My fault is that I guessed that it might be good to submit those findings in a way they won't be forgotten about, so I'm sorry about this. I'll try not to waste anyone's time or my own on stuff like this anymore.

I'm closing this one.

It may not be considered a bug, however there is a lot of complaining going on over the low playback rates of the VSE, so maybe it is worth addressing those elements causing the low playback rate, like this one?

This patch deals with set selection: D5881

When opening a new sequencer workspace this error shows:

Last night @Richard Antalik (ISS) and I did some tests(on the vse chat: https://blender.chat/channel/vse?msg=nMDvchLamuWnAorGZ ) concerning proxy formats, but a few elements which might lower the fps came up during that process:

Here the 50% percent resolution doesn't have an effect on the fps. It is still 24 fps in the 2.79. The Blend mode does have an effect in both 2.79 and 2.80, however the question is if the transparency setting is off on the scene-strip and Opacity is set to 1, then the Blendmode shouldn't have any effect at all.

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.

This quite annoying bug has also been reported here: T67295

There are several things which can give a poor playback rate ex. if the footage resolution doesn't match the render resolution setting or the footage fps/colorspace doesn't match the render fps/colorspace settings.
AV-sync is also causing a severe drop in fps, but if you're not just organizing or previewing stuff in the VSE, but actually editing stuff for an emotional impact, it is crucial to have the audio in sync and reliable fps at all times while editing.
Uncached material, playback while caching can also cause a drop in fps.

@Jacques Lucke (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.

In the Video Editor Workspace, the File Browser's path and search field are not useful unless you make the width of File Browser area fill half of the screen(1920x1080):

A bit of feedback:

Maybe @Andrzej Ambroz (jendrzych) could be asked to come up with an alternative icon for "Run"/"Execute", so we can avoid the not-so-nice looking text buttons in header/footers?

The Play icon is used for Run here in PyCharm - without any stop/pause 2. meaning:

I've noticed that the exposed rename function in the menu always suggest renaming the active object in the 3D View, which seems a bit peculiar when there is no 3d view in your current workspace, like file browser or VSE.

@Julian Eisel (Severin) For me it sure feels like a bug, that having only file browser and main UI window visible, and when closing the file browser pop up, the preferences suddenly becomes visible. You're thinking: hey, didn't I just close that file browser pop up, and when looking closer, you realize it's the preferences pop up!? And you're like: hey, what's happening? I didn't ask for viewing the preferences at all.

This could even be expanded, so it is not that last setting remembered, but the last setting for the file type, so ex. setting the font file browser to thumbnails, because that is the only setting where you can see the font style, doesn't affect the file browser settings for ex. add-ons(where you do not want thumbnails).

@Julian Eisel (Severin) Thank you for looking into those so quickly.

Testing this file browser in the VSE Workspace I noticed a few things:

• There is no (right)sidebar.
• There is still the extend area from below in the left sidebar - but it is empty.
• There are no file type options. Movies, sounds and images can be imported, so those options should be available(in a (right)sidebar?).
• Why not have the footer exposed? (and remove Cancel and Rename "Okay" to "Add".
• Right click on a file icon - and the only option is "Edit Source"?
• Ex. "Rename" should maybe be exposed in this case ^ And not exposed in the general Context menu.
• Increase/decrease isn't that a save option and not an import option, and therefore shouldn't be exposed in the import browser context menu?
• In Thumbnails view the filenames takes up far too much space, if less text space another line of thumbnails could be visible.
• Why no thumbnails in Vertical/Horizontal view?
• There are several operators exposed in the Context menu - but they're not exposed in the header menu, and they should.
• Would it be beneficial to have the Filebrowser area wider, so ex. import options could be exposed?
• The column width is locked.

You are properly aware of this, but the order of Okay and Cancel is in the Mac order, so for Windows users their muscle-memory will let them click Cancel when they want to Okay:

@Campbell Barton (campbellbarton)

Maybe the prefetch should be switched off during 'transform' operations, to avoid delays during those operations?

With the Import settings fully visible in the Sidebar, maybe the Sidebar could also be used for a preview of text/code files, that would be very useful for ex. the python templates, which are very hard, as a user, to understand what solutions a template actually contains when just reading the filename. If this was added maybe the hard to navigate Templates menu in the Text Editor could be removed, and instead the Menus entry could just open a file browser in the template path?

@William Reynish (billreynish) It was used for toggling the frame number/timecode on top of the playhead on/off. After the drag area was added, the frame number/timecode couldn't be toggled off anymore. In other words removing this function, means removing the option to add ex. a down-pointing arrow on top of the playhead like other softwares like Houdini or FCP X.

One more operator missing tooltip in the Text Editor, if you like?

Quite strangely everything works correctly when trying that line of code, but if I restart Blender and do the following I get the non descriptive indentation error:

Is it ok I tag you, as Text Editor module owner, on this report @Campbell Barton (campbellbarton)?

Has this been committed yet? Maybe in addition, it could be considered to give the Text Editor a typing focus, like the text entry boxes?

Yeah, it's properly part if of a larger "normalization" process, which at some point should also include Menu re-organization. Having View as first menu, is unique to Blender too. And having to use a menu called Add to import files is pretty unique too(like in the VSE).

In D5517#125961, @Campbell Barton (campbellbarton) wrote:

Would rather leave this as is.
It means documentation/tutorials cannot say "Click on the File menu" without some risk the users gets the wrong file menu.

The alignment tooltips maybe needs to be corrected too. The icons cause confusion because, the operator is not working like in a text editor, but relative to the location(as described it this patch).

Your .blend file does not contain any source files. However, in your .blend, if I change the source to an audio file on my computer, the audio is playing fine, so there is no setting in the file which might cause not to hear the audio.