Video Sequencer Preview should have own engine (and other settings?) #53158
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#53158
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For the end user that means they get to pick which engine to use for scene strip preview, as well other viewport settings to optimize draw time.
Right now the video sequencer Scene strip still has old "Draw Mode", and "Texture Solid". My suggestion would be to have a "ViewRender" struct in the Scene strip, and allow users to pick different viewport settings, just like we will do for workspaces.
Changed status to: 'Open'
Added subscriber: @dfelinto
Added subscriber: @Blendify
+1
Added subscriber: @ideasman42
Am wondering if it would be annoying to have to select the engine per-strip.
It could for example - use the current scene's engine, with a checkbox to allow selecting a custom engine - for the times this is needed.
Note that in the future we probably disallow a scene using its self as a strip. so scenes used for the sequencer will likely not be used for rendering 3D view too. See: #52586
@ideasman42 I like this, and this should probably be the default (imagine 20 strips and trying to tweak the volumetric sample of all of them and keep them in sync).
I wouldn't make it granular though. So you either manually set the engine and other ViewRender settings, or just use current scene (not strip scene)'s settings.
Added subscriber: @spockTheGray-4
Hi guys, just assigning this to me so other ppl know and we don't duplicate effort :)
Hey guys - ok, so it looks like right now the only engine it uses is Eevee and the settings are all out of wack atm in 2.8 (which seems like what you were saying here)... want to confirm a couple things with you in terms of requirements:
In my 2.78 testing, it looks like scene strip previews were always done using the selected scene's renderer (Blender or Cycles), not the current scene's settings. Now, we want it to be done using the current scene's engine settings by default, or allow them to select their own engine, in which case they need some preview settings available specific to whatever engines they choose. Does this jive with what you were thinking?
What other engines should optionally be available for preview??? Blender & Eevee + Cycles? Clay?
For the engines that need to be available, what settings (for each engine) do you think are appropriate to expose through the scene preview settings tab?
Yes.
Technically, all of them. Though I can see how the Game Engine shouldn't be used.
All the ViewRender settings, which at the moment means only the engine, but in the future it will include other options.
Hi @dfelinto - I dropped patches for this and #52586. Let me know if you see anything I need to change!
Finally figured out how to tie revisions to tasks and add images to diff summaries lol, so I'm going to ditch the google doc approach for just adding relevant info to revision summary and tying it to the appropriate phab task...
Cheers,
Danrae
@dfelinto to add to my (updated) comment above about adding docs to revision summaries instead of google doc - I just realized I can edit the phab task summaries directly (learning new things everyday lol), so if that's OK with you guys - maybe I can just add details / pics to the actual task summaries instead moving forward?
Just bowing out of this one for now as it's been quiet on this topic and I know the core dev team is busy w/ code quest stuff atm. Cheers!
Added subscriber: @FilipMond
Added subscriber: @PierreSchiller
I'm with @spockTheGray-4 on those points.
Definitely the VSE should be emphasized to work in a collaborative (remote/local network connected) link and append environment.
Tangent animation did the Bcon2014 on this. So it is definitely possible.
Added subscriber: @brecht
Changed status from 'Open' to: 'Resolved'
This has long been implemented now in 2.8, with a different design than originally proposed in this task.
Added subscriber: @tintwotin
Though this may be implemented, the current implementation makes playback of eevee rendered scene strips that slow, that they are not usable:
Added subscriber: @AndreaMonzini