# Cavendish skin uses APIs deprecated in 1.42; keep those warnings out of the error log $wgDeprecationReleaseLimit = "1.41"; $wgEnableSidebarCache = true; $wgParserCacheType = CACHE_DB; LTP: Difference between revisions - wiki.openlighting.org
Personal tools
The Open Lighting Project has moved!

We've launched our new site at www.openlighting.org. This wiki will remain and be updated with more technical information.

LTP: Difference between revisions

From wiki.openlighting.org

Jump to: navigation, search
No edit summary
No edit summary
 
Line 1: Line 1:
LTP stands for "latest takes precedence" and is a method of merging [[DMX]] data from multiple sources.
LTP stands for "latest takes precedence" and is a method of merging [[DMX]] data from multiple sources. LTP is cheaper in terms of memory to implement that [[HTP]] because it only requires two buffers.


LTP is cheaper in terms of memory to implement that [[HTP]] because it only requires two buffers.
'''Example''' (using an 8 channel output buffer).


Example
{| border="1" cellspacing="0" cellpadding="4"
 
!
{| border="1"
! Source A Data
! Source B Data
! Output Buffer
|-
| Initial State
|
|
| 0 0 0 0 0 0 0 0
|-
| First frame from Source A
| 4 7 9 10
|
|
| 4 7 9 10 0 0 0 0
|-
|-
| Time 1 | foo
| Frame from Source B
|
| 1 3
| 1 3 9 10 0 0 0 0
|-
|-
| Second frame from Source A
| 1 2 3 4 5 6
|
| 1 2 3 4 5 6 0 0
|}
|}


See also:


* [[HTP]]
'''See also''':
* [[HTP]]


[[Category:Definitions]]
[[Category:Definitions]]

Latest revision as of 02:12, 11 July 2009

LTP stands for "latest takes precedence" and is a method of merging DMX data from multiple sources. LTP is cheaper in terms of memory to implement that HTP because it only requires two buffers.

Example (using an 8 channel output buffer).

Source A Data Source B Data Output Buffer
Initial State 0 0 0 0 0 0 0 0
First frame from Source A 4 7 9 10 4 7 9 10 0 0 0 0
Frame from Source B 1 3 1 3 9 10 0 0 0 0
Second frame from Source A 1 2 3 4 5 6 1 2 3 4 5 6 0 0


See also: