Compositor SoftwareCompositor Software

Tag : EUI48

Calabi-Yau manifold

By ruslany

History of the creation of SASER 2.0

History of the creation of SASER 2.0

The first SASER was released back in 2016, it was available as Standalone on the Max 6 platform and as Max for Live device. However, Cycling ’74’s policy with the release of SASER has changed. In Max 7, the internal structure of Gen~ patching was changed, which made it impossible to organize the broadcast inside the SASER application on the new Max for Live platforms. Moreover, even with the organized broadcast on the Max 6, such a tool could not be online for more than 30 minutes. It took years of hard work to coordinate the work of such a plugin with Cycling ’74. Now the Max 8 platform has managed to make the perfect code export, suitable for both the organization of trunk broadcast and music purposes. This required the creation of a new Hypervisor v9 from Compositor Software. The IPv6 SASER assembly process is viewed in the video below:

Creation of SASER 2.0 in Hypervisor v9

If you have already watched the video, I will make a few comments on it. In the video you can watch the process of connecting workgroups to the OSPFv3 IPv6 protocol. If the first SASER was completely in the IPv4 domain, the modern SASER allows you to multiplicate the length of the octet up to 32 bits, which in total gives a length of 128 bits when summing up four upscaled octets, which is the IPv6 address:

SASER for iPhone

And you can access both EUI64 and EUI48 MAC addresses. Again, with the correct combination of parameters, you can connect not only through the network, but also at the device level, which allows you to see your local device as a member of a neighboring network, wherever such a network is.

It is believed that connecting via Ethernet protocol requires either a cable LAN connection or radio relay equipment capable of transmitting to the Ethernet network. The concept of an on-air network differs from the Compositor v9. In particular, in the video you can see how two beacon processes control RIPv1 and RIPv2 protocols. These are distance-vector protocols and the direction to the communication point indicates the torus in conjunction with the hypercardioid of flows. The result of this image is the multidimensional structure of Calabi-Yau. Z-spaces of which are equal to 16. This quantization is minimally sufficient to build a spherical picture:

Calabi-Yau manifold

What you see in the picture is the sum of spherical flows in quaternion rotation. Such rotation permeates space not only in 4 dimensions, like quaternion rotation, but sums up all 24 points of spherical space with the Z of the system, allowing you to quantize this space, filling it with additional translation points. This topology lasts until the next change of the multiplier by redrawing multidimensional figures with iteration that is difficult to predict. Therefore, the successful creation of the VLF (Very Low Frequencies) service can include more threads at the same time with an increase in the Z of the system. If the first SASER was on Z=4 and then at Z=8, then SASER 2.0 already includes Z=16 measurements.

Another thing is that connecting workgroups to Z=16, that in the Compositor’s system corresponds to the OSPFv3 protocol is able to create a larger network compared to Z=8. Given that the network includes 96 channels in total, when multiplying on 16 spaces, it already produces 1,536 points, not 648, as in the previous SASER. Therefore, in real time, in order for the broadcast network to produce traffic, it is necessary that each point produce at least one packet. Naturally, in a short video, such a volume of material would require at least 1 hour of broadcast, so I show the very principle rather than a physical entity capable of producing such a multicast effect.

By ruslany

Compositor v3 RTOS – analog radio interface for IPv6 Protocol

Compositor v3 RTOS – analog radio interface for IPv6 Protocol

Compositor v3 Hypervisor Radio Shack software updated to RTOS. Now, Compositor RTOS v3.0.3 supports numerous new features, such as:

  • Protocols implemented:
    • RTC8k = IS-IS Level-2
    • FF8 = ARP (Address Resolution Protocol)
    • TC25 = VLAN (IEEE 802.1aq)
  • Hierarchies added:
    • AI-RT1024 = SDH STM-x
    • N9000 = PDH E1
  • Other features:
    • TCP/IP protocols stack implemented
    • TCP/IP window added
    • EUI48 table added
    • BPM now is the network field parameter of IP-address
    • Network field includes 2^13 to define as IPv6-address
    • All modules renamed to reflect new functionality
Compositor v3.0.3 RTOS

The main reason I made the update is to reveal the FF8 (ARP) and TC25 (VLAN) protocols work. That is why the working routine in Compositor RTOS v3.0.3 looks as following:

At the beginning, I set the time to reach the destination point, where the network deployed. I make this by setting deployment time in degrees from -180 to 180, which is the range from 0 to 60 minutes. Then I set the IP-address of destination interface the following way: the part of IP-address, pointing on the interface ID is set stochastically or manually. Multiplier in IPv4 sets the second field, which is the part of network and host. That is why the highest network for Compositor RTOS in IPv4 is 255.4.0.0. When I’ve reached the destination network and I’ve got the closed feedback loop on the loop-back interface output, I define the autonomous system type, which it belongs. I do this by enabling VLAN and ARP protocols and resolving the assignment of IPv4-addresses to the network devices of this autonomous system. I look into the IPv4-addresses of next-hops and reveal the number of such next-hops before returning to the first hop. The more hops IS-IS Level-2 protocol makes, the larger a metric of the destination network (autonomous system). This way I reveal all peers of the destination network.

When I define ABR (area border router) of that network using IS-IS Level-2 protocol, I turn the VLAN and ARP protocols off and start to translate this device information into IPv6 network, by enabling TCP/IP protocols stack. This process allows merging IPv4 networks with IPv6 networks and to expand the influence of my database into IPv6 protocol.

By ruslany

Zero-Layer Aggregation

Zero-Layer Aggregation

Exactly a year ago, when all modules of Compositor RTOS were formed, I was confronted with the task: to make such aggregation, which would not have committed the emission in the RAM memory of the computer (server). A year later, the problem is solved.

RAD96 vRouter L1-L3 96 node aggregation

It was required to complete assembly of Compositor RTOS 9.0.1 a14 with an extended work of the feeders, that is, the feeders now work from 11 kHz to 192 kHz of audio driver sampling frequency. This allows the upper generic z=128 to operate at frequencies comparable to the aggregator frequencies, namely from 150 GHz to 300 GHz.

Also, the management information base was expanded to 6041 VLAN’s and 13 dumps were produced. As a result, the final version of Compositor RTOS 9.0.1 a14 includes a channel pass-through (bypassing the second derivative of a function) that allows you to make exhaust (digital exhaust) to reduce the emissions of traffic inside the system. According to this two dumps were made of VLAN 6041 with digital exhaust and one firmware at 192 kHz was recorded on feedback after dialing, which involves 8 hidden servers. Since the firmware was recorded with an aggregator and is the snapshot of the system, it includes 96 ports of aggregation of the three layers: 32 ports of physical layer, 32 ports of data link layer and 32 ports of the network layer, which corresponds to L1-L3 aggregation.

Since such aggregation in reality throws out the large amounts of data in to the operating system memory, the snapshot utilizes resources in the other way – it corresponds to the MAC-address table of EUI48 without the OUI and do not throws resources in the computer memory. The network service in this case is the firmware, which includes the autonomous system with zero emissions. One system does not produce any action, but in a pair with snapshot this system aggregates resources and at the same time, disposes them, which happens so quickly in real-time that discards in the RAM memory cannot simply emerge.

Thus, the aggregation problem with zero emission is solved. Of course, for someone may seem, that 96 aggregation nodes is insufficient and the 32 L3 nodes is the standard for the aggregation of routing equipment of well-known manufacturers. But if you take into account the fact that the real link aggregation on these devices produces output, and requires a service restart, I can say that this resources composition technology can be very useful now.

Calabi-Yau manifold
History of the creation of SASER 2.0