As mentioned above, I've abandoned this patch, I'm out of time and motivation, so someone else will have to deal with incredible weak UI/UX.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

This patch didn't make it into 2.93. As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this patch for now.

An alternative approach would be to utilize ffmpeg's fine frame rate conversion. So in import, if a mismatch between the source and the project fps is found, an offer is made, that the user can either change the project frame rate to match the source, or render an intermediate(high-quality) file with the corrected fps(including corrected audio(which also is a problem in Blender)) and utilize that. This functionality could also be used for variable frame rate source files.

Not sure why the status is set to "Needs info from user", since the bug is still valid?

Rebase.

Enough of this. I'll let text in Text strips suck...

In D10775#274119, @Campbell Barton (campbellbarton) wrote:

• For use case of one strip per line:
  
  The generated content will need a lot of manual re-timing (as timing information isn't included in the text file).
  
  Further, any edits will then need to be made in the sequencer, as reloading the text will loose all timing information.
  
  Wouldn't it be more useful to have an importer for subtitle .srt files? (we already have an exporter).
  
  Then the strips can always be deleted and re-imported without loosing timing.

• For displaying large blocks of text, we could have the strip reference a text block directly, as having to manually sync the text isn't very practical.

All tool operators exposed in the vse headers was removed with this patch: https://developer.blender.org/rBbd7969159997b8802d54e79a002350a7fb97944d by @Campbell Barton (campbellbarton) This must be a mistake?

Add option to convert paragraph to strip too.

Nice design. Question is, when implementing this, how to avoid generating inconsistency with all of the other editors(ex. animation editors), which also could need a mini-map, and keep Blender consistent?

I think the renaming in the code should be okay, but that DNA stuff looks way over my understanding of I'm doing. If you can find the time I would appreciate it if you could help me out here.

Add 'Distance' values to auto-aligning list.

Updated according to comments.

Fix rna.

https://developer.blender.org/T85868

Remove empty line.

Remove extra line.

The box margin range change has been abandoned, so it's back to 0->1.

@Brecht Van Lommel (brecht) A week ago some kids proudly premiered their lock-down film produced in Blender on Blendernation. This film was greyed out because of the filmic setting. If you look at animations and tutorials on Youtube, you can easily see which one where edited in the VSE, because they're all greyed out. This has been going on for years. A solution should have been planned and implemented right when Filmic was set up as default View Transform, or that setting shouldn't have been changed. That would what a responsible developer would have done, not sweeping it under the rug, or trying to end the conversation with asking Troy if he thinks anything is more important than what's on Troy's mind...

I'll refrain from trying to come up with a solution, since you guys surely can come up with something better.

Tagging @Brecht Van Lommel (brecht) as he seemed to be in charge of the Filmic implementation.

How does the encoding times compare between this, the previous and the built-in solutions?

In D10362#271855, @Richard Antalik (ISS) wrote:

In D10362#271854, @Peter Fog (tintwotin) wrote:

I wonder what the use is, for the Preview Setting(Proxy unchecked), since it is by large only degrading the quality without improvement in performance(75% and 50%) is worse than 100%?

Are you guys sure the unchecked 'Use Proxy' actually is useful for anything? If it isn't it might as well be removed.

It's useful when you don't want proxies to be used. I sometimes uncheck it just to see if I want to be sure that original image looks as I want it to look.

I wonder what the use is, for the Preview Setting(Proxy unchecked), since it is by large only degrading the quality without improvement in performance(75% and 50%) is worse than 100%?

The scrubbing area is up under the header. If you close the header, you'll see it. The scrollbars disappear under the sidebars and you can't right click on the header(no tool header open), to get the header menu(it properly wasn't adjusted for the tool header).