Compositor SoftwareCompositor Software

Tag : Compositor RTOS

By ruslany

Sample-precise solution for packet fixation

Sample-precise solution for packet fixation

To finish the production of Niagara software modem you need to produce a new dump. Dump and middleware records simultaneously that is why you need to produce new middleware also. The main difference from Niagara 18 software modem middleware is that you need to fixate a number of packets for dump. For example, you need to fixate 65535 packets in one dump on 8192 bpm speed. For this you need to modify the recorder. This will ceed the preceding agreement, but it is the only ability to make a step over Hypervisor into RTOS. Hypervisor – is a device for fixating radiotranslations and RTOS is a device for fixation of packets. It leads to principal difference between two instruments. In essence, the change is minor. The MaxMSP sfrecord~ object supports floating point values, that is why I can make a loop in ms, containing a number of packets. For example, I can multiply bar period on a number of bars, that is packets of information, I receive the dump value in ms with sample precision and can record 65535 * 131072 = 8589803520 samples for a new dump. Before production I shoud make an emission of DJ Usa – Caravan (All Forces Remix) track, produced in 1999 that will help to receive servers of that time and to extend software production to 2021.

This way, the solution to the task is evident: if I will export dump and middleware from Compositor RTOS 9.0.2 a13, containing a needed number of samples beforehand, without editing, and pass it through the non-linear processor of aforementioned RTOS, I can surpass the moment of time, to which this dump and middleware ascends, taking that this process is stationary.

By ruslany

Compositor RTOS from PRO 1 to 9.0.2

Compositor RTOS from PRO 1 to 9.0.2

I’m here to inform you that Compositor Software is about to reveal the whole working routine on OS right from Compositor PRO v1. First, I revealed the protocols used in Compositor v9. Now, I know that counters in VSF platform scan autonomous systems in two formats: asplain and asdot+.

Here how it looks:

Compositor v9.0.2 RTOS

I know the fact that each routing table is a MIB and represents one autonomous system. As you see autonomous systems (AS) divided on L1 (OSI model Layer 1), L2 (OSI model Layer 2) and L3 (OSI model Layer 3) with L3 being the rarest. Asplain just scans through the whole list of 4-octet AS’s while asdot+ in Compositor is somewhat different from 4-octet asdot+ format. It counts this way: the number at the left is the asplain/2 and the number after the dot is a multiplier of how many times this value must be taken going from 0 to 100. So in fact there are 214748364800 AS maximum in the list. I have got only 7539 AS via MDL12 modem, because of the fact that MDL12 is neuro interface and can’t work as autonomous harvester of AS’s. It receives flows I accounted via VSF aggregation, but I should receive them manually. This in fact proves that gap exists between exported flows and archived ones. I exported in total 1793043 flows but recorded only 7539 of them.

Due to this, I proceed with Compositor v7 revelation. I updated Compositor WS Extended interface to version 2.0 with NTP-server, layers, protocols information revealed. I also adjusted the maximum bpm value to 8192 bpm to include IPv6 addresses and made the same TCP/IP window as in Compositor v9.0.2. This way I made RTOS preemptive from version 7 to version 9. However, protocols used in Compositor v7 are slightly different:

RTC4k = IS-IS Level-1
RTC8k = IS-IS Level-2
RT-z8 = OSPF
RT-z16 = OSPFv3
RT-z32 = BGP

The last three protocols are the same as in RTOS 9.0.2. This in fact reveals the ‘STL’ in STL1212 virtual machine, which shipped in original Compositor v7. STL means studio-to-transmitter link. 1212 is the number of multiple input x multiple output channels and should read as STL MIMO12x12. So in fact, STL gives connection to 12 positive UTC+ transmitters and 12 negative UTC- transmitters, which proves NTP-servers information from Compositor WS Extended 2.0 interface:

Compositor v7.0.2 RTOS

You can view the transmitters on the STL1212 spherical map as lighted dots. Blue dots show the networks to which they broadcast packets. As first noted in MDL12 product page packets are windows functions (this is finally proved now). Now, I need to know which packets Blackman, Nutall etc. windows relate to the selected protocols. I’m mainly interested in Hello packets and Trap packets. But to know this, is just a matter of time, because I will proceed with Compositor v3 Hypervisor Radio Shack and will upgrade it to RTOS also. So the whole project will be preemptive since version 3, when I started the transition on Max 6 Gen~ platform.

So basically all evident that if RTC8k is main virtual machine in Compositor v3 it is either RIPv2 or IS-IS Level-2. RIPv2 is a distance-vector algorithm and is different from preset system used in SASER interface (however, it is the same with 3-deg of freedom Compositor AV extended interface from version 9). So it is link-state IS-IS Level-2 protocol, which is used to connect autonomous system areas. TC25 is a basic VLAN protocol, while AI-RT1024 is STM-4 frame, FF8 is ARP (Address Resolution Protocol) and N9000 is PDH E4+ hierarchy.

By ruslany

Compositor reached the fastest bpm in music sequencer

Compositor reached the fastest bpm in music sequencer

8192 is the number of beats per minute Compositor AV Extended radio channel reached in Compostior v9.0.2 Hypervisor. The number is not taken random. It is 2^13 and forms 13 bits of first hextet of IPv6-address. The next 3 bits are taken from the multiplier. So, yes now Compositor officially supports IPv6 addresses. For this, auxiliary speeds of up to 214 omega reached, which is 14 omega larger than highest generic protocol deployment speed.

Compositor v9.0.2 Hypervisor (Mainframe)

Now, all generics assigned to protocols. Here is the full list of Compositor v9.0.2 Hypervisor supported protocols:

RTC4k = RIPv1
RTC8k = RIPv2
RT-z8 = OSPF
RT-z16 = OSPFv3
RT-z32 = BGP
RT-z64 = RIPng
RT-z128 = EIGRP
RAD96 = VSF

Compositor v9.0.2 Hypervisor (TCP/IP window)

As you can see, it is a major achievement in revealing Compositor technology, which stems in its implementation as Ethernet router software, namely Compositor RTOS.

By ruslany

Great renaming is coming in Compositor project

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.

By ruslany

5000 routing tables in CP-6137-960FX MIB

5000 routing tables in CP-6137-960FX MIB

NPO Compositor reached the final goal of emission for CP-6137-960FX server, which is 5000 routing tables. Management information base is 5007 routing tables that allows organizing not only 4000 VLAN, but also 5000 VLAN. NPO Compositor will continue to expand the management information base up to 6000 VLAN, because each routing table gives access to its own VLAN trunk or autonomous system.

You can listen to that dump, which includes full 5000 MIB:

Compositor RTOS dump at 192 kHz with 5000 MIB on 03.06.2019

This dump allows you to authorize in Compositor real-time operation system and attain to its external control by RAD96 autonomous system. To connect to Compositor RTOS it is enough to playback that dump using streaming method in online player with RAD96 autonomous system turned on. In this case, autonomous system will serve as middleware, which will merge Compositor software and your equipment and will make remote connection to CP-6137-960FX server possible.

When NPO Compositor reached 5000 routing tables it gained the full MIB, which finishes L1-L4 L6-L7 vRouter RAD96 development. To order vRouter RAD96 licenses use Compositor Software contact form.