Opened at 2022-08-27T15:03:07Z
Last modified at 2026-04-16T23:14:25Z
#1223 new todo
Create foundation for precise frame-caching
| Reported by: | Ichthyostega | Owned by: | |
|---|---|---|---|
| Priority: | lesser | Milestone: | |
| Component: | lumieraSteam | Keywords: | cache render performance roadmap topic |
| Sub Tickets: | #826, #1293, #1372, #1377, #1391, #1392 | Parent Tickets: | #22, #55, #502 |
Description
As Lumiera Architect,
I want a systematic and coherent organisation of processing activities,
as foundation for precise operational control and efficient caching.
Principles
- Processing is governed by an unique and abstract scheme
- Processing steps must be tagged by semantic criteria
- Rigorous handling of versioning and compatibility
Change history (4)
comment:1 by , at 2024-11-03T00:31:31Z
| blockedby: | → 826, 1293, 1372, 1377 |
|---|---|
| blocking: | 22, 502 → 22, 55, 502 |
comment:2 by , at 2025-01-11T15:01:49Z
| blockedby: | 826, 1293, 1372, 1377 → 826, 1293, 1372, 1377, 1391 |
|---|---|
| Keywords: | cache render performance roadmap topic added |
comment:3 by , at 2025-02-03T20:58:46Z
| blockedby: | 826, 1293, 1372, 1377, 1391 → 826, 1293, 1372, 1377, 1391, 1392 |
|---|
comment:4 by , at 2025-12-25T00:00:00Z
| blockedby: | 826, 1293, 1372, 1377, 1391, 1392 |
|---|---|
| blocking: | 22, 55, 502 |
| Parent Tickets: | → 22, 55, 502 |
| Sub Tickets: | → 826, 1293, 1372, 1377, 1391, 1392 |
Migration MasterTickets ⟼ Subtickets-plugin
Note:
See TracTickets
for help on using tickets.
As part of the »Playback Vertical Slice« #1221, a prototype for the node invocation is developed, thereby re-organising existing code from the initial (and unsuccessful) attempts several years ago. This effort leads to a changed attitude towards structure and organisation of media processing steps; Lumiera will deliberately provide no exhaustive internal classification of media types, processing functionality and connectivity. The onus is shifted towards adapter plug-ins for individual media-processing libraries rather, where chances are better to capture aspects of equivalence and compatibility. A a registration API will require tagging of operations based on user-visible semantics, which is passed through the model and the builder to allow attribution of render nodes to be used to form stable frame cache keys