Scene Proxies in the Video Sequence Editor
Open, Needs TriagePublic

Description

System Information
Windows 7 Ultimate, 64-bit, 32GB, 5960x, Nvidia Quadro FX 1800 (Primary) & GeForce 9800 GTX+ (Secondary)

Blender Version
Broken: (2.79a) Official builds
Worked: (2.79) Official builds

Short description of error

To cut a long story short @Campbell Barton (campbellbarton) disabled Scene proxies in the Video Sequence Editor because:

Looked into this and for now building proxies doesn't support anything besides movie, so disabling support for this.

rB6535f668b4733e354db7073c4edc82e6e820a678

This shocked me, have I been using Blender wrong? Because I've been happily doing this for months.

I don't quite understand the rationale behind the removal of is.

The main problem for me is that I have projects (made in 2.79 and earlier) that rely on scene proxies and when opening them up in 2.79a viewing or creating them doesn't work.

Now there are issues with Scene Proxies most notably the aforementioned (T54048) one and it can be really bad:


and
Other proxy issues

  • Skipping frames whilst rendering.
  • Properties side panel scrolls up after changing proxy location in the File Explorer.
  • Overwrite don't have the same behaviour as Overwrite does in the render setting (in the properties editor)
  • and inconsistent functionality.

But I've always treated this as an incomplete feature, (same way I treat NetRender, it's somewhat stable but is inconsistent. e.g. T52502) throwing in a bug report due to just crashing (T53792) and have been fine.

But now with the update, the Proxy/Timecode Panel is still there and does nothing. and as I said in my query to @Campbell Barton (campbellbarton)'s decision to disable this:

So, @Campbell Barton (campbellbarton) does this invalidate my bug report? T53792
Also, is it a good idea to disable this considering the Proxy/Timecode Panel option still there (or are you still working on this)?

With no information or feedback in the Blender Manual or when trying to create proxies (nothing happens), you are going to get users confused on a essential feature that worked (works fine in cycles for me (not the file names the crashing)) in 2.79 and now doesn't with no apparent reason why.


...generating proxies currently only works for movies...

No... they don't. They worked for Scenes before. (and they work for images for that matter)

...cancel until other types of sequence strips are supported...

What do you mean by this? That it's officially 'supported', documented?


Now that I've been trying to research around a bit, is this an incomplete feature or has it slowly gotten broken in time?
There's T43857 which uses a scene proxy. So there must be other uses who uses this right? Or was this just an example?
I would love to use this with Eevee; having the proxies rendered in no time and my GPU not getting taxed.


What I think to be good next steps:

  1. Having the functionality back as it was before.
  2. An open task to deal with the Other proxy issues.

Exact steps for others to reproduce the error
Zipped folder with a working Blender file and proxy:
Tested in Ubuntu VM both 2.79 and 2.79a with reproducible behaviour.^
Tested on a separate laptop with both 2.79 and 2.79a with reproducible behaviour.^
(Note: In my Ubuntu VM I had to toggle Textured Solid button in the Scene Preview/Render Panel to get the proxy showing in 2.79.)
(^ Reproducible behaviour being: fully working in 2.79 and not working at all in 2.79a)

I'm sure this was just a misunderstanding.
Yours,
A passionate Blender user

Details

Type
Bug

Adding @Sergey Sharybin (sergey) & @Bastien Montagne (mont29) as after a quick search seem to be the most active on the subject of VSE Proxies.


So...
It has been well over a month since I first asked about the code change (T54048#485618) and a month since this task's submission.
I completely understand if no administrator can undertake this (code quest, moving etc..), all I ask is for this to be looked over.
And after some advice/motivation I guess I'll keep nagging about it untill something happens.
I mean this has slipped past the release of 2.79a and 2.79b so I'm writing this early in hopes this will not get missed in 2.80 or maybe in a 2.79c release.

In the interest of saving time (whatever the modern day equivalent of telephone tag is)

If it is decided to reinstate scene proxies

I can:

  1. Create tasks (from other proxy issues)
  2. Give details on the issues/behaviour/bugs
  3. Give expected behaviour
  4. Show use cases (2.80, Eevee,..etc)
  5. Give opinions on behaviour/functionality/design
  6. Give functionality (expected limitations)

Anything else? Any other information required?

If it is decided to completely remove (and not support) scene proxies

Then: feel free to
bigbadbugreport

my reports (T54259, T53792)

and please remove the Proxy/Timecode Panel from properties.

and a valid reason for the removal of this!.