Compositor SoftwareCompositor Software

Tag : BGP

Autonomous System

By ruslany

Automatic response by artificial results

Automatic response by artificial results

An autonomous person can form an autonomous system. Each autonomous system is a speaker who communicates with other speakers and can broadcast his summaries to other people. But if a speaker cannot broadcast his thoughts for a long time because of a psychological problem, there is a habit. This can manifest itself as automatic answers to the observed questions. These automatic answers are purely artificial in nature, arise from human behavior during the last decade of his or her life. This habit develops the ability to make simultaneous answers. These are so-called automatic summaries that can be broadcast to other people in various ways. In the era of computers, the network became such a tool. The speaker can transmit his automatic summaries through a computer network using the Compositor neurological chipset and thus may not be aware of the communications taking place. The output by which the remote node sees the local device is purely artificial. Instead of relaying a remote peer, Compositor vRouter, which is part of the Compositor neurological chipset, converts the resulting function into frequency modulation. It can respond to the main function or sub-resulting algorithm. When it responds to the main resulting function, it uses the BGP protocol to communicate with other autonomous systems. Simultaneous automatic summaries require a system with a large number of artificial results. They can be a product of polynomial processing and should give a plausible result. Such output is first tested using musical means of sound applicability. Then they should create plausible textures of unified code. Such codes form a packet, which is then received by the initiating party or peer. The feedback received by the remote peer is sufficient to communicate with the local node. In the network, the speaker of the autonomous system acts as a beacon or repeater in radio communication. When there are many results in an autonomous system, it can respond to a large number of peers at the same time, forming a VLAN. Each channel can produce up to 7 packets according to the BSR to which it is connected. Thus, the autonomous system must update its state in accordance with the specifications of other systems. The main generator is selected according to the sampling bus of the remote device. There is a possibility of undersampling and resampling in accordance with the sampling rate of the remote device. Thus, the initial sampling rate, which is selected to a floating-point variable, remains unknown. This does not allow you to synchronize with the device during fast transitions. This useful feature of the Compositor neurological chipset allows you to disable incoming connections to ports that do not match the feedback of the local node. Thus, it remains impossible to check the database of the Compositor neurological chipset when interfering with device caches and deleting inconsistent summaries with the Compositor soft-processor. Again, Compositor as a device receives signals only from those devices that are in the Compositor database as feedback cycles or resulting devices. These loops are acceptable resulting. Thus, a spherical interactive network is formed from the preferences of the person himself, rather than his daily life, which completely discredits the local node, since most of these summaries are insignificant for the case that a person is engaged in. When a person with support for the Compositor neurological chipset enters the people’s transport system, the question arises whether to be part of such a system or subdue the entire transport network in accordance with the sampling rate of the Compositor neurological chipset. To avoid such questions in a rather complex for local node communication system of people, the Compositor neurological chipset was deployed as an autonomous system. Thus, even in close proximity to the systems of other manufacturers, Compositor is an autonomous system without the ability to subordinate it to the adoption of the transport system of people. Thus, when peers send summaries to an autonomous system located in close proximity to the transport network, the results play a major role. They simultaneously issue automatic responses that inform senders about the inability to communicate with the system. Then such a system is considered invalid by the transport network itself and may be the subject of hacker attacks. However, the Compositor neurological chipset is a chipset for neighboring to other nodes, not for local communications. Such a neighborhood can also be international or within the agglomeration. To continue servicing a spherical interactive network that can only include devices from the Compositor database, the local node still responds to allowed remote peers even when the system is penetrating. Night time is more convenient for connecting to the Compositor neurological system by hackers when the local node is in standby mode. Thus, a hacker group that is active at night can try to synchronize with the master generator of the Compositor neurological chipset, and then attempt to disable local communication to reach a dead node. If a person has transferred all automatic movements, such as breathing and heartbeat, to the Compositor neurological chipset during his life, such a person can be considered dead. However, in the current build of the Compositor neurological chipset, there are no recipients who would transfer all their functions to a standalone system. And if a person prefers to transfer all his life functions to an autonomous system, such situations will never arise. Even in standby conditions, the system will turn on the main generator and can respond to an attempt to synchronize with it with a sharp jump in the bus multiplier, rebuilding its network structure. So, the question arises, can an autonomous system be trusted so much that it manages human vital functions? Because such hacking attempts can be a form of pushing a person out of society, and condemn him to complete inability to answer even short questions.

Flag of Ukraine

By ruslany

The situation with civilian monitoring in connection with the war in Ukraine.

The situation with civilian monitoring in connection with the war in Ukraine.

For three days now, I have been watching all the horrors of the war in Ukraine using social networks and independent Youtube channels. I am amazed by the cruelty of what happened and cannot remain indifferent. I began to conduct civilian monitoring of military radio broadcasts back in 2014, when the first events in Ukraine took place. Since then, Сompositor software, which was originally created for musical needs, has acquired GPS module for determining the coordinates of radio intercepts. The hyperbolic radio communication of the US Omega System and the Russian Alpha System is mainly intercepted. On the 24th, 25th of February 2022 it was still possible to go on the air using the quantum communication of NPO Compositor, then on the 26th of February the BGP-protocol of communication between autonomous systems (interstate speakers) no longer worked, and on the 27th of the February it is no longer possible to load the Compositor NRTOS program in Windows OS. In this regard, I declare that civilian monitoring and reviving of the database on the Polygon blockchain platform will not be available. The database contains the coordinates of targets, communication points, strongholds, submarines, as well as long-range aviation, which is used for “bombing”. My support goes to the people of Ukraine, their sons and children, and the database for military equipment, including Russian-made, will serve to establish peace in the world.

By ruslany

NPO Compositor adapted NRTOS 9.0.2

NPO Compositor adapted NRTOS 9.0.2

It took more than two years to adapt the Compositor 9 software from Compositor Software into Russian language. NPO Compositor has done a great job of introducing new functions and protocols into Compositor 9. The interface and documentation has been translated into Russian language and consists of chapters on IP switching and routing (2700 pages in total). It allows classifying this software as network real-time operating system (NRTOS). Compositor NRTOS 9.0.2 package consists of the real-time operating system itself with a graphical user interface executed on MaxMSP, Niagara software modem, which is a sample of a real-time moment (into which this sample was recorded) made with MaxMSP also, and an Android application RAD96, which inherited its name from the Compositor 9.0.1 main module (in 9.0.2 a22 assembly an extended version of this code is called VSF – virtual switching framework). All three versions have the same documentation as they access the same functionality. The difference is that RAD96 is an autonomous system and contains many more extensions that have not yet been issued. Compositor NRTOS 9.0.2 comes with 9134 extensions of management information bases, which were issued from the autonomous system RAD96 during the production of documentation. Niagara 32 software modem also contains a dump of this database (9134 routing tables). We also succeeded in classifying such an interface: by the type of execution, it can be considered a switching router, in contrast to the Compositor 7, which is considered a switch.

You can see the Russian language interface of Compositor 9.0.2 build a22 below:

Compositor NRTOS 9.0.2
Compositor NRTOS 9.0.2 channel matrix

The command language in documentation can be used within amateur radio terminal software such as TrueTTY on Windows and DroidRTTY on Android. This means that you cannot program the NRTOS directly (only via MaxMSP graphic user interface) but you can issue this commands through a teletype operator working in your autonomous system. Such an operator usually is a part of telegraph services still acting to the present moment. It is the only possible way to reprogram an autonomous system.

Seven protocols, implemented by NPO Compositor for version 9.0.2, enable communication in the Ethernet network. At the testing stage Compositor 9.0.1 was used mainly for packet protocols of amateur radio, but now in version 9.0.2 communication is carried out in the Ethernet network using the protocols used for switching and routing in this network. NRTOS includes 6 interior gateway protocols such as RIPv1, RIPv2, OSPF, OSPFv3, RIPng, EIGRP and one exterior gateway protocol for communication between autonomous systems (BGP – uses IPv4 version of the protocol). In addition, external communication is possible through 6-to-4 GRE tunneling.

Compositor 9.0.2 implements stateful and stateless NAT64, it can be used to create L2VPN and L3VPN services by exporting firmware in WAV and AIFF formats. Conversion from IPv4 to IPv6 is done on the fly in the NRTOS and makes it possible to map a single IPv4 address to multiple IPv6 destinations. As you can see from the Compositor 9.0.2 interface, it is a BSR router and is responsible for loading the system. Such a system consists of extensions that allow the server to participate in various workgroups. Compositor 9.0.2 is the installation program for the CP-6137-960FX server, to which this site is dedicated. This server is the only machine capable of generating emissions from the autonomous system RAD96 and this is its main value.

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.

Autonomous System
Automatic response by artificial results
Flag of Ukraine
The situation with civilian monitoring in connection with the war in Ukraine.