Ticket #244 (accepted meta)

Opened 2 years ago

Last modified 15 months ago

clarify relation of output channels, exit nodes and segments

Reported by: ichthyo Owned by: ichthyo
Priority: normal Milestone: 0integration
Component: lumieraProc Keywords: builder render design
Cc: Blocked By: #93, #95, #235, #717, #718
Blocking: #242, #243

Description

still some fuzziness in here; probably due to the fact that I discovered that it's impossible to keep the topic "multichannel" entirely out of the low-level model (the reason being compressors and spatial sound and image handling)

Change History

comment:1 Changed 2 years ago by ichthyo

  • Blocking 242 added

comment:2 Changed 20 months ago by ichthyo

  • Status changed from new to accepted
  • Blocked By

next things to to

comment:3 Changed 15 months ago by ichthyo

  • Blocked By 717 added

comment:4 Changed 15 months ago by ichthyo

  • Blocked By 718 added

(In #718) probably knowing enough now about that topic to try to nail it down.....

comment:5 Changed 15 months ago by ichthyo

  • Priority changed from grave to normal
  • Type changed from todo to meta

Actually this work is done.

The key for solving this was the introduction of the entity ModelPort.

  • a channel as such isn't relevant anymore. This will be settled by the stream type system
  • an elementary stream ends up being hooked up to a (global) Pipe
  • each pipe not connected any further yields a ModelPort. This will be detected by the builder
  • on top level, there is a partitioning by timeline; below of that is the temporal segementation
  • within each segment, for each ModelPort there is a corresponding exit node.

While the definition work is done, I'll leave this around as meta ticket to track the progress of the actual datastructure definition

Note: See TracTickets for help on using tickets.