diff --git a/doc/devel/rfc_pending/EngineInterfaceOverview.txt b/doc/devel/rfc_pending/EngineInterfaceOverview.txt index 4966339fc..9e242a27f 100644 --- a/doc/devel/rfc_pending/EngineInterfaceOverview.txt +++ b/doc/devel/rfc_pending/EngineInterfaceOverview.txt @@ -41,8 +41,8 @@ _corresponds to a single data stream_ to be rendered. Thus, when the play in _playing_ or _paused_ state, typically multiple corresponding render processes exist. -* there is an displayer- or output slot, which got allocated on creation of the - process +* there is an displayer- or output slot, which got allocated on creation + of the process * the process disposes calculated data frames "into" this slot * the process can be paused/started and stopped (aborted, halted). * some processes allow for changing parameters dynamically (e.g. speed, @@ -52,23 +52,31 @@ processes exist. .Process parameters A process is linked to a single stream data format (a -> -link:StreamTypeSystem.html[stream implementation type]). + It is configured -with _frame quantisation_ and _timings_, and a _model port_ identifier and -_channel selector_. +link:StreamTypeSystem.html[stream implementation type]). + +It is configured with _frame quantisation_ and _timings_, and a _model port_ +identifier and _channel selector_. + + quantisation:: + translates time values into frame numbers. (In the most general + case this is a function, connected to the session) + + timings:: + a definition to translate global model time units in real clock time, + including _alignment_ to an external time grid. + + model port:: + a point in the (high level) model where output can be produced. + + This might be a global pipe in one of the model's timelines, or + it might be a _probe point_. + + channel:: + within the session and high level model, details of the stream + implementation are abstracted. Typically, a global pipe (master bus + or subgroup) corresponds to a multichannel stream, and each of these + channels might be hooked up to an individual render process + (we have to work out if that's _always the case_ or just under + _some circumstances_) - quantisation:: translates time values into frame numbers. (In the most general - case this is a function, connected to the session) timings:: a definition to - translate global model time units in real clock time, including _alignment_ to - an external time grid. model port:: a point in the (high level) model where - output can be produced. + - This might be a global pipe in one of the model's timelines, or - it might be a _probe point_. - channel:: within the session and high level model, details of the stream - implementation are abstracted. Typically, - a global pipe (master bus or subgroup) corresponds to a multichannel - stream, and each of these channels might be hooked up to an - individual render process (we have to work out if that's _always the - case_ or just under _some circumstances_) [NOTE] =================== diff --git a/doc/devel/rfc_pending/NormalizedDeviceCoordinates.txt b/doc/devel/rfc_pending/NormalizedDeviceCoordinates.txt index 4272b1816..87496b4e8 100644 --- a/doc/devel/rfc_pending/NormalizedDeviceCoordinates.txt +++ b/doc/devel/rfc_pending/NormalizedDeviceCoordinates.txt @@ -58,6 +58,11 @@ Tasks ^^^^^ + + +Discussion +~~~~~~~~~~ + Pros ^^^^ @@ -75,7 +80,7 @@ Alternatives Rationale ~~~~~~~~~ - +TBD diff --git a/doc/devel/rfc_pending/ProcPlacementMetaphor.txt b/doc/devel/rfc_pending/ProcPlacementMetaphor.txt index f12f33004..d6ba41545 100644 --- a/doc/devel/rfc_pending/ProcPlacementMetaphor.txt +++ b/doc/devel/rfc_pending/ProcPlacementMetaphor.txt @@ -109,6 +109,11 @@ Tasks + + +Discussion +~~~~~~~~~~ + Pros ^^^^ * with just one concept, we get a lot of issues right, which many conventional diff --git a/doc/devel/rfc_pending/RenderOptimizer.txt b/doc/devel/rfc_pending/RenderOptimizer.txt index c10f7027d..ce2c57b7c 100644 --- a/doc/devel/rfc_pending/RenderOptimizer.txt +++ b/doc/devel/rfc_pending/RenderOptimizer.txt @@ -32,6 +32,11 @@ Tasks ^^^^^ + + +Discussion +~~~~~~~~~~ + Pros ^^^^ diff --git a/doc/devel/rfc_pending/ResourceManagementBudgeting.txt b/doc/devel/rfc_pending/ResourceManagementBudgeting.txt index 0ff21933e..ffa488e5c 100644 --- a/doc/devel/rfc_pending/ResourceManagementBudgeting.txt +++ b/doc/devel/rfc_pending/ResourceManagementBudgeting.txt @@ -73,6 +73,11 @@ Tasks // * item ... + + +Discussion +~~~~~~~~~~ + Pros ^^^^ // add just a fact list/enumeration which make this suitable: @@ -88,7 +93,7 @@ Cons Alternatives ------------- +^^^^^^^^^^^^ //alternatives: if possible explain/link alternatives and tell why they are not viable: diff --git a/doc/devel/rfc_pending/ResourceManagementProfiling.txt b/doc/devel/rfc_pending/ResourceManagementProfiling.txt index 7022d861c..bfd1b2731 100644 --- a/doc/devel/rfc_pending/ResourceManagementProfiling.txt +++ b/doc/devel/rfc_pending/ResourceManagementProfiling.txt @@ -134,6 +134,11 @@ Tasks // * item ... + + +Discussion +~~~~~~~~~~ + Pros ^^^^ // add just a fact list/enumeration which make this suitable: @@ -149,7 +154,7 @@ Cons Alternatives ------------- +^^^^^^^^^^^^ //alternatives: if possible explain/link alternatives and tell why they are not viable: diff --git a/doc/devel/rfc_pending/Roadmap-first.txt b/doc/devel/rfc_pending/Roadmap-first.txt index cdba0f267..a8a38d50a 100644 --- a/doc/devel/rfc_pending/Roadmap-first.txt +++ b/doc/devel/rfc_pending/Roadmap-first.txt @@ -136,6 +136,11 @@ Please review and discuss this proposal, consider if it's of any use setting it up this way... + + +Discussion +~~~~~~~~~~ + Pros ^^^^ * doesn't hinder us diff --git a/doc/devel/rfc_pending/StreamTypeSystem.txt b/doc/devel/rfc_pending/StreamTypeSystem.txt index 077d1aed9..4a81eaf9b 100644 --- a/doc/devel/rfc_pending/StreamTypeSystem.txt +++ b/doc/devel/rfc_pending/StreamTypeSystem.txt @@ -10,8 +10,7 @@ Stream Type System ------------------ Especially in the Proc-Layer, we need a framework to deal with different -"kinds" of media streams. - + +"kinds" of media streams. + This is the foundation to be able to define what can be connected and to separate out generic parts and isolate specific parts. @@ -69,7 +68,7 @@ or selection regarding each of these levels. conversions. Examples for Prototypes are: stereoscopic (3D) video versus the common flat video lacking depth information, spatial audio systems (Ambisonics, Wave Field Synthesis), panorama simulating sound systems (5.1, - 7.1,...), stereophonic and monaural audio. + 7.1,...), binaural, stereophonic and monaural audio. * Besides the distinction by prototypes, there are the various *media implementation types*. This classification is not necessarily hierarchically related to the prototype classification, while in practice commonly there diff --git a/doc/devel/rfc_pending/ThreadsSignalsAndImportantManagementTasks.txt b/doc/devel/rfc_pending/ThreadsSignalsAndImportantManagementTasks.txt index e218e8e9e..69ca53595 100644 --- a/doc/devel/rfc_pending/ThreadsSignalsAndImportantManagementTasks.txt +++ b/doc/devel/rfc_pending/ThreadsSignalsAndImportantManagementTasks.txt @@ -113,6 +113,11 @@ We have appstate::maybeWait() which already does such a loop. It needs to be extended by the proposed things above. + +Discussion +~~~~~~~~~~ + + Pros ^^^^ // add just a fact list/enumeration which make this suitable: @@ -127,7 +132,7 @@ Cons Alternatives ------------- +^^^^^^^^^^^^ //alternatives: if possible explain/link alternatives and tell why they are not diff --git a/doc/devel/rfc_pending/WebsiteNavigation.txt b/doc/devel/rfc_pending/WebsiteNavigation.txt index 965897144..172b6543f 100644 --- a/doc/devel/rfc_pending/WebsiteNavigation.txt +++ b/doc/devel/rfc_pending/WebsiteNavigation.txt @@ -114,6 +114,10 @@ Tasks // * item ... + +Discussion +~~~~~~~~~~ + Pros ^^^^ // add just a fact list/enumeration which make this suitable: @@ -129,7 +133,7 @@ Cons Alternatives ------------- +^^^^^^^^^^^^ //alternatives: explain alternatives and tell why they are not viable: