Opened at 2011-12-17T20:33:33Z

Last modified at 2011-12-17T20:39:05Z

#873 accepted todo

trigger segment cleanup

Reported by: Ichthyostega Owned by: Ichthyostega
Priority: lesser Milestone: 0integration
Component: lumieraSteam Keywords: builder design data sanity
Sub Tickets: #872 Parent Tickets: #725, #869

Description

design how to handle the clean-up of segments superseded by the results of a new build process.

Change history (2)

comment:1 by Ichthyostega, at 2011-12-17T20:39:05Z

blocking: 869, 725 → 725, 869
Status: new → accepted

Designing the Fixture and Segmentation datastructure is blocked by the uncertainty regarding this issue, because of the yet limited knowledge about render processes and scheduling in general....

  • how do we join/link an aborted/changed rendering process to his successor, without creating a jerk in the output?
  • is it even possible to continue a process when parts of the covered time-range are affected by a build?
  • or would it be the better choice to taint every directly related process and chain-up an updated version of the processes?

comment:2 by Undercover Agent, at 2025-12-25T00:00:00Z

blockedby: 872
blocking: 725, 869
Parent Tickets: → 725, 869
Sub Tickets: → 872

Migration MasterTickets ⟼ Subtickets-plugin

Note: See TracTickets for help on using tickets.