Great renaming is coming in Compositor project
Dear reader, it is time to report the coming changes in Compositor Software project. For the five years, I performed the comparison of telecommunication industry technology and the one developed by me. Here what I’ve already found:
Compositor Pro = NTP-server
Compositor Max for Live = SNTP-server
Accordingly, Compositor Pro and Compositor Max for Live will be reworked to reveal this paradigm. There are 24 official UTC time zones as well as 24 bands in Compositor Pro and Compositor Max for Live. The function by which these bands are distributed is time-invariant non-linear function (read the full documentation here). Therefore, bands of Compositor are time zones. Stratum parameter of NTP-server is permutation. There are 12 Stratums in my NTP-server. Using kick parameter, you can set subnetwork mask. This parameter, together with clap and hat, forms modulation, which installed in parallel to time zones deployment tempo.
NTP-server can create time collisions by granulating the central flag of modulation interrupter. When injected collision comes to the input of the receiving device, this device establishes a connection with NTP-server and takes its synchro-code, which is translated by sub-bass instrument. It is the modulation interrupter flag. The mangling takes place in time component, which is the time-displacement (substitution of time).
Tempo is the first octet of IPv4 address, and multiplier forms the next three octets. There are only IPv4 addresses in NTP-server. NTP-server doesn’t have access to broadcast addresses and to an address of local machine, but uses the range of 54.1.54.0 to 140.3.0.0. Therefore, the role of Compositor Pro was to install the stochastic distribution with the route of 120.1.54.0 to 120.2.24.0 and to perform collisions with the devices of that range.
The reason I made the NTP-server is “creation of artificial intelligence using non-invasive method”. By this, I mean active use of ACL lists and flows filtration when loading Ethernet servers (kernel extensions, which are recorded in MIB’s database of Compositor Software). Compositor Software clients produce traffic when working with software, which is exported into flows, using the half-duplex MDL12 modem. These flows contribute to device pool of Compositor RTOS kernel extensions.