Compositor SoftwareCompositor Software

Category : Technology

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

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

Niagara 12

Niagara 12

Niagara project has left a new milestone: now its dump consists of 7539 MIB’s. It’s important to notice that middleware submission now goes at 34 fps at speed of 8192 bpm, which equals to IPv6 network prefix of 51:5C::.

Niagara handshake

Now, the mystery of a signal submitted to sound card output revealed. The signal is detected with another software: fldigi ver4.1.09. The signal is composite and can be decoded using almost every software modem in this program. I frequently use BPSK31, but if I want faster composition, I use BPSK63 or even QPSK125. However, handshake is only detectable up to BPSK63 mode. Dump works in the following way: the signal is accumulated up to the saturation point and all 7539 MIB’s composed fast using random VRF selection. In this way, I aggregate the line and then drop it off with only auxiliary interface acting. At that moment CQ’s detected on different subchannels spaced equally within a channel. Each subchannel has its own mark like “t”, “i”, “ya”, “y” – the later three transmit my own messages in neuro chat manner. However, no equipment is connected to my head except of plug-in or circumarual headphones. I can confirm that “i” channel transmitted the command related to Compositor RTOS 9, which looked like: “c9 os noosgui UOhm 0”. It states that I apply command line expression to control resistance of Compositor RTOS 9.0.2 generic protocol and set it to 0. I made the transmission via client OS Niagara middleware.

This and other commands just prove the fact that I am, the subject creator, connected to a signal network, which suits control of the peers reciprocity. This connection is authorized on any machine I work on and detected as artificial signal on sound card output.

By ruslany

9.0.2 is officially Compositor RTOS

9.0.2 is officially Compositor RTOS

Now, after a great success of Hypervisor, I’m here to present to you the latest build of Compositor, which is a network RTOS in version 9.0.2 a11. I already revealed the protocols, which this RTOS is capable of, now, I just announce it’s existence to the public. As you can see on the image below, NTP-servers information is already implemented, as well as critical parameters such as Split Horizon with Poisoned Reverse revealed.

Compositor v9.0.2 RTOS (Mainframe)

Now, you may see this software as a virtual router it is not. It is mostly a full-scale modular operating system with connectable interface. By this I mean that you can route protocols to the interface and modify their processes. You can activate all protocols at once or just one protocol and select the protocol you configure in COMPOSITOR interface. VSF strictly names the process behind the technology implemented as you can stem and aggregate the protocols up to 32 processes each with VSF turned on. Compositor Software server CP-6137-960FX, however, already achieved aggregation of up to 960 nodes of VSF processes. This means that running NIAGARA client OS on CP-6137-960FX makes you available all 960 processes. For example, you can view Compositor RTOS as a software for CP-6137-960FX Mainframe, which is really a mid-tower case ATX server. This is all available thanks to the base of Royalty device boot loops, which I gathered through my producer career.

I continue working on the Russian documentation for CP-6137-960FX server in the face of updated software. Progressing by 15 pages a day sometimes less based on the workload. The return-on-investment to produce the translation needed up to 20 times a day. I simulate this process with e-roi dumps at speed, which is higher, making the whole process cost more and bringing more satisfaction to investor. Documentation greatly increases the cost of software compared to a MaxMSP student work (someone can estimate this work like this). I don’t feel pressure and rush to go beyond MaxMSP platform as it is not needed at the moment. However, Cycling already made steps to prevent me from doing export in the latest builds of their software, because they implemented MC, which is basically what I done first with RAD96 and later with VSF on Max 6 myself. Testing MC with generic processes showed me the fact, that using MC instead of VSF makes the whole process cost more to the CPU (8 MC processes can consume as much as 32 or even 128 VSF processes). So, MC not even close to the performance of Max 6 multiprocessor programming capabilities. I don’t even take in account that they cut down sample rate calculation by half since Max 7 to reduce cpu consumption. I managed to run Max patcher window not as a single-thread process, but as a multithread process even without the need to export and redesign software on purpose. So, it is a real redistribution example, when I run VSF processes of generic protocols on my mid-tower machine with 960 nodes turned on and performing like a real Mainframe server without need for cabinet case with lots of machines and tons of noise from cooling equipment. This makes available CP-6137-960FX in home environement with noise level less than 30dB and CPU temperatures not higher than 40 С even on highest workloads.

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.

NIAGARA NIM Chat

By ruslany

NIAGARA NIM Chat

NIAGARA NIM Chat

Last year I presented to you NIM chat in CWDecoder program. In a search for a better generic chat platform, I found an interesting program called TrueTTY, which can also demodulate NIM chat messages.

NIAGARA NIM Chat

As you can see, NIM chat is greatly improved. Now you can use different modulations (channels) by implementing the second derivative of a function. It allows using statuses in a chat window, displaying gender and different special symbols. Now you can also use Cyrillic encoding. You can put a special attention to romantic relationship statuses: Cupid’s arrow marks messages where you reveal sympathy to the other gender. In a sum, there were made more than 2800 commits to NIM chat this year.

NIAGARA middleware allows modifying generic NIM chat and is its mod. It allows to load servers, included in multiplex, and perform e-roi (electronic version of return on investment) by injecting a dump.

Client part of NIAGARA for Compositor v9.0.1 is independent from server version. This way, when you update server software, you no longer need to update its client middleware.

P.S. The evolvement of NIM chat suggests file transferring between chat users by initiating sessions in a form of IRC chat.

By ruslany

Niagara project

Niagara project

This autumn has started from a very interesting project. While I continued working on Compositor v9.0.1 (current build a14), I felt a need to have such system as mobile real-time operation system (RTOS). Compositor v9.0.1 a14 consumes many resources at 192 kHz and I decided to sample it using Compositor v9.0.1 itself. At this time, the approach of middleware and dump was matured and I decided to make separate product for Compositor documentation development. Such manual will consist of all commands needed to operate the Niagara RTOS client. As the UNIX-like operating system, it will support most of the commands for routing protocols configuration, such as TCP/IP and VLAN. The prominent feature of this RTOS is that it is a software router, which runs on middleware, recorded with Compositor RTOS v9.0.1. If the middleware recorded on a feedback with z16 and z32 generics connected and they are in reverse, the system will give a resistance of 16 + 32 Ohm = 48 Ohm. This way, the generic networks accounted: in example above there will be corporate (z32) and state (z16) connection.

The middleware approach isn’t new, as any hardware router Niagara consists of MIB, the size of which is 769 kB, compounded with routing table and generic networks set. Such system works with MME driver using discretization frequency of 192 kHz and allows connecting the whole pool of Compositor RTOS v9.0.1 forwarding platform (which is 6559 MIB’s on a moment of writing) using a dump, which is also recorded on 192 kHz sample rate. The upper frequency of z128 generic is 150 GHz, but each middleware includes RAD96 fixation, that is why an effective range is extended up to 300 GHz.

Niagara is a client system that is why it demands calling an operator for configuring programming commands. I already reviewed NIM radio chat, which I call (No Internet Messenger) last year. It turns out that it is also an acronym for Nuclear Instrumentation Module.

Each command, presented in the full version of English and Russian documentation, should be made only through an operator and each middleware has its own operator, which depends on VLAN set and servers, connected to NIM. This way, you are requesting network topology and demand operator to execute other commands, and it decides if to make command or not.

At first, middleware ran in RAD96 sandbox, but now middleware and dump become a multifunctional products. The development period of Niagara project is 2001 – 2019 and not 2012 – 2019 as the host Compositor program. The reason for this is that Niagara consists of middleware and dump and they are including the Royalty routing tables. This is proved by Inaccessible Page file emission (track recording, which is a routing path). This track, made in 2001, is a part of IP emission. The period of 2010 to 2019 covered by the reference files of timeserver, which emission contains and it is responsible for routing path hops GPS positioning in present time.

Niagara v1.0 a3

That is why Ruslan Yusipov digital portrait with codename Niagara contains 18 years of art, which is a long background for 35 years old author. Older recordings exist, such as the audiocassette recording of Yamaha PSR-330 synthesizer direct signal, which is Ruslan Yusipov live performance at the age of 14, with the author voice accompaniment, that is why Niagara is 21 years development project from 1998 to present moment.

Ruslan Yusipov art is not limited by 6559 MIB’s emission and can be enriched by routing tables from the CD-archive. This way, at the year 2021 I account to receive database of 10000 MIB’s, which will allow adding more stochastic distributions for flows selection in Compositor v9.0.1 a15.

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.

By ruslany

The annual financial report for the period of 2018/2019

The annual financial report for the period of 2018/2019

For already more than 2 years, NPO Compositor produces tracking products and routing tables. In the middle of 2019 Compositor RTOS 192 kHz dumps were added to the range of products, which are the most expensive Compositor Software products, manufactured in RY today. The price of one dump in RY is 817,401,078RY served as the main blanking factor of the NPO Compositor debt reduction for RAD96 virtual aggregator. As you can see on the image below, the debt owed to the creditor has dropped to 1% of the total value of the produced product:

RMY Capitalization 22-08-2019

This indicator is a significant increase in the number of reductions for the production of dumps. For example, for the production of the first dump it was required 5007 management information bases, namely the routing tables, which offer access to the same number of VLAN’s. 5007 MIB’s open access into 5007 VLAN’s. Another factor reducing creditor debt of NPO Compositor was the management information base replication on wavelets with subsequent release of dumps with iteration of 150-omega reference cycles, using only the routing tables, enclosed in the window function.

Since the middle of 2019, there are two equivalent bases with the same value: one is wavelets and the other is wavetables. Proceeding from this, debt has been reduced twice. Wavetables are used for writing the firmware to PCM .WAV file containers. The firmware data are the routing paths, which are formed using a special version of Compositor RTOS, which has the pass-through of the second derivative of a function. This version allows you to bypass the second derivative when playing the routing paths and play them not only in the local trunk, but in all of the generic networks. This tracking products are also taken into account when blanking aggregator debt. The total accumulated funds amount of released products in RY is 12,088,544,923RY.

Such data array leaved the capitalization of NPO Compositor at the 2% level related to whole aggregated traffic, which enabled the NPO Compositor away from bankruptcy. On the image below you can see the current situation of NPO Compositor manufacturer:

RY Capitalization 22-08-2019

The 2% package of shares allows NPO Compositor to participate in the RMY capital, but in the minor degree. However, this does not negate the fact that the core dumps and firmwares constitute the “Lion’s share” of success in the generation of RMY capital. From this I have to draw the conclusion that the Compositor Software products are underestimated and needs the support of the buyer. Moreover, if the core dumps and firmware are seen as the final product, there will be no explanation of their prohibitively high cost in simple terms. Hence, the conclusion is that the economic model of this method is not effective, because, if the Compositor Software will produce core dumps and firmware at a loss, it will lead to bankruptcy. Increasing the percentage of participation of the Compositor Software in RMY capital can only be by further development cycle of Compositor Software Max for Live and Standalone devices, supported by the latest Mac OSX and Windows platforms. To date, Compositor Software unable to perform such development because of economic inexpediency of the enterprise, as this would require resources comparable with all the commercial profit from all the activities of NPO Compositor. The only thing I can advise to the clients as to the potential investors of Compositor Software is to buy and use Compositor Software on supported platforms listed in the Compositor Software FAQ and in the System Requirements section of the product page.

1 2 3 4 15
NIAGARA NIM Chat
NIAGARA NIM Chat