Scene added to sequencer doesn't show it's sequencer output #33602

Closed
opened 2012-12-18 14:09:06 +01:00 by Ken Kornisch · 4 comments

%%%Creating a scene "source" with sequencer output and adding this scene to the sequencer of a new scene "edit" results in the sequencer output not shown in scene "edit".

This is a new behavior in Blender 2.65. Checked this on official Build r52859 and own build r52982.

Some investigation led me to Fix #33253, where Sergey stated: "Also removed Use Sequencer from scene's strip settings, it's not supported."

Not really shure if this is a bug at all, or if I'm missing some new workflows? I really loved the ability to use these nested scenes, you can see it's use in attached .blend.

Opening this .blend in Blender 2.64 will work as expected. (At least expected by me ;) )

Let me know if I can help in any way.

Best,
Ken


System is Windows 7 64bit | Blender 64 bit

%%%

%%%Creating a scene "source" with sequencer output and adding this scene to the sequencer of a new scene "edit" results in the sequencer output not shown in scene "edit". This is a new behavior in Blender 2.65. Checked this on official Build r52859 and own build r52982. Some investigation led me to Fix #33253, where Sergey stated: "Also removed Use Sequencer from scene's strip settings, it's not supported." Not really shure if this is a bug at all, or if I'm missing some new workflows? I really loved the ability to use these nested scenes, you can see it's use in attached .blend. Opening this .blend in Blender 2.64 will work as expected. (At least expected by me ;) ) Let me know if I can help in any way. Best, Ken --------------------------------------------------------------- System is Windows 7 64bit | Blender 64 bit %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Sequencer is not recursive, it can not compute sequences from scene's strip because of design limitation. It only worked in some cases and was never working reliable confusing users. Now sequencer's recursion is disabled explicitly.

New depsgraph and updated animation system would likely make it possible to re-enable recursive sequencers, but at this moment it can not be done in predictable way.%%%

%%%Sequencer is not recursive, it can not compute sequences from scene's strip because of design limitation. It only worked in some cases and was never working reliable confusing users. Now sequencer's recursion is disabled explicitly. New depsgraph and updated animation system would likely make it possible to re-enable recursive sequencers, but at this moment it can not be done in predictable way.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Author

%%%Okay thank you. So for now I will have to stick with pre 2.65 versions, as this function worked very well for my purposes.

Regarding the latest build:

The closest to what I try to produce would be to set up a "source" scene with compositor output, and then adding this scene to the "edit" sequencer, as compositing output will be displayed. This leaves me without source audio, and high latency on scrubbing, but then thats what the proxy system is made for right ;)

Thanks for your hard work and your answer :)%%%

%%%Okay thank you. So for now I will have to stick with pre 2.65 versions, as this function worked very well for my purposes. Regarding the latest build: The closest to what I try to produce would be to set up a "source" scene with compositor output, and then adding this scene to the "edit" sequencer, as compositing output will be displayed. This leaves me without source audio, and high latency on scrubbing, but then thats what the proxy system is made for right ;) Thanks for your hard work and your answer :)%%%
Sign in to join this conversation.
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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#33602
No description provided.