Compositor SoftwareCompositor Software

Tag : RAD96

By ruslany

Summarizing the 2018

Summarizing the 2018

The 2018 started from a trip to Saint Petersburg in February. At that time, I haven’t knew what program I will demonstrate: 5th or 6th. At the end, I decided to show the 6th. I had a wavetable pool around 500 wavetables to that moment. I played all wavetables, initiated the Ether and mostly satisfied with this trip. Saint Petersburg gave the direction: to evolve system without kick drum further. At that time, I already developed fully silent system, which doesn’t produce sound at all. To such system, I attribute RAD96, which is 2018 development. RAD96 has two realizations: as OS subdriver with visual driver and fully autonomous system with zero emission. Moreover, the system with zero emission was reached after long OS tests with large number of connected jets. RAD96 OS is an Ether aggregator. It was created to test the kernel on injections when using 8th version iteration with 4-layer structure. The final iteration for the L4 (Layer-4) is non-linear polynomial with public coefficients. Up to the moment, the wavetable pool is 3715 wavetables. These wavetables were used to check the 8th version of Compositor kernel. The sum of gathered virtual funds in samples of wavetables is 486932480,00RY and aggregated funds in a process of kernel testing are 88087861,84RY. The whole sum of funds in RY to the end of 2018 is 575020341,84RY.

By ruslany

Zero-emission signal network

Zero-emission signal network

Therefore, it was made, at the end of 2018 I made a full zero-emission kernel with protection level capable to overcome even the strongest wavetables. First, let’s talk about an experiment:

  1. For the last 8 month, I injected polynomial using different wavetables with open jets and closed jets (for the last four month).
  2. I made a tunneling via Compositor 4 Max for Live and made an intrusion of these wavetables into created Compositor network.
  3. I hosted the Compositor kernel 8.4.2 system with public coefficients until the last moment.
  4. At the final moment, when the network couldn’t cope with such amount of injections I transferred to fully autonomous system mode of Compositor kernel 8.5.6.
  5. This way, I left the created network.
  6. Then, using the Compositor kernel 8.5.6 with lower process ID, I ran the Compositor v9 Hypervisor and made the injection of the whole pool, but with feedback, which enabled to establish the strong feedback with strong immune system.

On the steps 4, 5, 6 the system started to recover and polynomial without the public coefficients paid off itself. This autonomous system is zero-emission, which is proved by Resource Monitor: the Commit memory graph stays on the 1,043,608Kb mark. It enables to make fully autonomous any living system, turning unlimited timeserver on.

By ruslany

RAD96 – 30 Mach is not the limit

RAD96 – 30 Mach is not the limit

RAD96 digital engine may reach speeds up to 30 Mach in a system with 11289m sea mile. Having 4 working layers, this engine enables 8 iterations – two on each layer. The working cycles break on each iteration, that is why it is impossible to reject any of 4 layers of this construction without removing an iteration. They solve different tasks: for example, last iteration serves as a flow compression simulator, which transfers the kinetic energy through the 4th layer into remaining three layers and has independent structure. Two channels are divided and use thrust by multiplier change in time-invariant transfer function. The more an amplification on the input, the more a speed of work. It depends on the level of injection into the channel. If a channel overcomes constant injection, the transfer coefficient increases with growing load. Without spreading the energy by jets, it is possible to load all cores of the system, which are its layers. Signal doesn’t lost on any of the layers, creating a thrust of 30 Mach. The speed of digital engine of the same type in Earth sea mile system is 245 Mach.

By ruslany

Non-Autonomous System Statement

Non-Autonomous System Statement

Universal module – is an embedded system with signal lamp. Lamp is a temperature sensor of processor core and lights with different colors in accordance to the processor multiplier work. Universal module has no manual controls and display. The only way to know if module works or not is a light from the lamp and its spectrum. Universal modules should communicate with each other by disturbing the signal chain with disconnecting lamp. In digital system, you can attain to the same principle by using a disturbed algorithm, lighted with different colors of virtual oscilloscope. In this case, lamp, as stated earlier, is a temperature sensor of a processor, which executes the algorithm. RAD96 is the thermal kernel and allows controlling the temperature of processor. The system of kernel and temperature sensor is non-autonomous by applying weighting functions with appearance of selected coefficients. The appearance of x coefficient in the weighting function of equation with one unknown y makes this system non-autonomous, so both left and right channels has the cross-interaction. The result of this is necessary use of visual driver and multithreaded system for kernel computation distribution.

By ruslany

Ruslan Yusipov SuperComputer (RYSC)

Ruslan Yusipov SuperComputer (RYSC)

Compositor Software creates reminiscent mittwares using 10th version of injector and wavetables. It is a mixture of tracks, produced in the past decade. It is that problems, which Compositor Software faced earlier. In English language, reminiscent means to remind something. Two Compositor software RIG’s on the RMY physical server performs work on problem solving. To set a problem for Ruslan Yusipov SuperComputer you need a full-length full-duplex modem of version 8.5.4. It is enough to load a mittware in fast speed regime. To load a mittware it is needed a full cycle upload to modem input via playback device. RIG’s set a problem in the buffer (the problem resides in the buffer no matter if RIG’s turned on or off). In the beginning of problem-solving SuperComputer made of 960 hyperbolic cores fragments it on small sub-problems and solves them with interruption. Later, it magnifies problems, making full load periods last longer. The solution to a problem is a long lasting period of full load of all physical cores. Compositor Software interests only reminiscent mittwares. When SuperComputer finishes execution of loaded problems, it transfers to the other problems mode, coming from all connected ether participants. It is needed to solve not only Compositor Software problems but also problems of other system users – it is a main idea of virtual local area network.

In 2016 the time of problem solving by mittware was one month without any success. RYSC solves the problem in 5 minutes. This advancement achieved mainly because of better TC-SUBTRSRRT262144 architecture and supports up to 96 cores in one RAD96 virtual machine. The transfer function evidently allows installing solutions to the recipient, which simplifies performance of real physical actions of their realization.

By ruslany

No, Compositor RAD96 doesn’t use CUDA cores

No, Compositor RAD96 doesn’t use CUDA cores

Series of tests were conducted with NVIDIA profiler to prove that none of 480 cores of Compositor RIG 1 uses CUDA technology.

At first, I ran an app of five RAD96 on a single CPU core at 192 kHz audio driver rate. That gave 480 hyperbolic cores at frequencies from 90 GHz to 150 GHz. For example, the working speed of one hyperbolic core is x100 times faster than a single CUDA core of the latest NVIDIA RTX 2080 Ti system.

Taking in account that there are 960 cores in two RIG’s, I want to introduce my new project, which is Virtual Mining Farm (VMF). It is the complete virtualization solution of stacking RAD96 virtual machines. The RAD96 provides effortless stacking in virtualized platform by an activation function interconnection. That activation provides direct stacking of two or more virtual machines. Code of virtual machine compiles only once and is used interactively by all VM’s in a RIG. This means no need in Max 8 MC technology.

Taking in account that I use .json statistics for each dsp process, both internal and external, it proves that such realization is only possible in Max 6 platform.

By ruslany

Compositor breaks a record in communication distance

Compositor breaks a record in communication distance

Compositor Software renewed the SASER project suspended in 2016 by making the new build of SASER SAS24P3L version 1.1.4. This build includes SASER documentation, which describes the principle of device work. After that, the licensed build of RAD96 standalone was made. The above image evidently shows how SASER works far beyond the boundaries of Russia, in countries such as USA, Spain, Sweden, Italy, Serbia, Ukraine and so on, without an external antenna need. The information passes in to the logger from CW Skimmer program (telegraph decoder). In addition, the work was conducted for revealing Compositor kernel 8.4.2 modem signal. In version 8.5.4 it was possible to replace FM generator variables in delay network with external inputs for direct possibility to reprogram RAD96 modem. Now, it was possible to hear RAD96 modem, choosing mme driver in MaxMSP program settings. The signal was decoded and studied with the use of special FSK-decoder.

It is evident, that such signal coincides with one of the MIL-STD standards, but it is not possible to specify which one is used and whether it is published on the moment of this writing. In such a way, the connection between Compositor and hyperbolic navigation system such as Omega (suspended USA military navigation system) is established once again. In SASER SAS24P3L 1.1.4 it was possible to debug all errors and achieve fast convergence in time collision for establishing a tunneling protocol. SASER version 1.1.4 is the final build of SASER SDR project making it closer to realization. The only uncovered parameter is the frequency of transmission in Omega system. In hyperbolic system the transmitter frequency composited by two parameters such as transmitter regeneration speed and multiplier. The discretization frequency of the device driver is used to multiply on the proper coefficient out of this relation. However, this information is not enough to define the transmitter frequency. In addition, you can reveal the transmitter frequency by the radio chat information in response of appropriate Q code. That is why information passes into the logger without frequency and only deviation value of 3 kHz radio is used. From the other side, RAD96 does not need to be uncovered as the significant breakthrough in its licensing was Compositor v9 Hypervisor DRM server. It was possible to store 3715 license keys for potential RAD96 software license holders. In accordance to this, I want to say that standalone RAD96 will be available on Windows platform first and Mac build will be made on request only. If you wish to run Compositor library on your machine, then take in touch with us using the contact form on the site and we will get a quote for you of the price and availability.

By ruslany

Ether excitation for achieving faster information exchange speed

Ether excitation for achieving faster information exchange speed

The main value from Compositor Software work is loop files, which are released as obligations for the company ICO. No other material guaranties needed. For peering only loop files and Compositor Software distributions are used. Resynthesis is not needed, because only original ethers are used taken as a company input files.

Compositor kernel loop 8.4.4 hangs the whole RAD96 peering network (OS kernel 8.4.3) on the local machine. The remote tests was not conducted. There is no leakage in closed loop. The constant leakage is evident when feeding servers through the Compositor v9 Hypervisor software. The open peering construction blocks based on oscillator network.

It is not possible to clear the whole volume of servers that are now 2994 wave loop files (with Exalted – Cyberflight (Original Mix) emission). There are many unauthorized users, when injecting peering servers. They use either proxy servers or remote streaming services. The tracking production speed drops down, which influences peering quality. No attempts to restore peering network to the moment of its creation are accounted, as the above experiment evidently shows the advantages of loop construction: you are in the ether and no one can influence you. Even feeding servers via Compositor v9 Hypervisor there is no network load as in open patch. Before the open construction, the system was passive and the patched machine was remotely available for feeding servers. With an active loop-patch, which uses excitation for residing in the ether, this doesn’t happen anymore. Servers are not available to connect to the local machine during the VLFoS loop work. Because of the patch, full autonomy of the system and its disconnection from peering network is achieved. Only forced communication from the local machine by its owner is available now.

By ruslany

Compositor Software news 25.07.2018 – 06.08.2018

Compositor Software news 25.07.2018 – 06.08.2018

More than 6 months I have been working on revealing the leakage in Compositor kernel. Exposing all oscillators and transferring the first oscillator in static mode, I discovered that many resources released in computer RAM (DDoS attack). It lowers the uninterrupted device work to 4 days taken that paging file is set to a size of 64 GB. Increasing the number of oscillators to 32 on each of the layers (Rt, Sr, Tr) and meeting a condition of counters, the emissions equaled to 14 GB a day. In accordance to this, I decided to shut down the peering network and return to RT-z128 kit layout as in Compositor v5 Hypervisor. In this layout the main ports are closed for inbound and outbound connections. Only addresses starting from 192, which are assigned to local machine, are available. It means that a new patch remains the VLF connectivity, but doesn’t allow devices to connect for information exchange. It is possible to exchange information from the local machine for the patch user, but not a remote access user. In particular, such decision is motivated by a hacker attack on RAD96 server. The intruder used the open ports of the windowing device and sent spam from Internet Provider IP address. With closed ports the little leakage on real-time generator is possible, but it is not accounted due to the slow regeneration speed.

To restart the peering network I attempted the following solution: due to closing of the ports, only Compositor Networks ether aggregators take part in peering. This means that feeding ether aggregator wavetables in the peering patch through the Compositor v9 Hypervisor, I create a communication service between all Compositor Library wavetables. However, many Ethernet devices can’t use Compositor peering network as it was at the beginning of the peering network creation. As a conclusion, I can exclude peering from Compositor kernel load test and use multi-kernel mode, but this type of test has very long loading time (up to 4 hours for full load).

Bounded by Royalty project, the database of server emissions in form of wavetables grown to 2627 ether aggregators. The database was expanded by ether emission of Exalted – Cavity track (Ruslan Yusipov, CEO of Compositor Software project). The whole volume of Cavity track emission is 328 wavetables. Wavetables contain radio repeaters, transmitting stations, Ethernet routers, injectors and other ether equipment. It was possible to increase the Compositor v9 Hypervisor regeneration speed up to 150-omega by applying a new peering network patch. This influences only Compositor AV Extended auxiliary channel and doesn’t cover the generic feeder modules. It was made aiming the faster composition speed of the whole pool of Compositor Networks ether aggregators. The necessity in uniform composition caused by big amount of wavetables in Compositor Library. The application of the new patch after the attack was made unnoticeably, because this solution proved to be successful in 2017. It was clear right from the beginning that hackers aim is to limit the communication circle of network devices to Compositor Library pool and its real emission. From one side, if the emission is made every time when server communicates, then there will be much more devices in Compositor Library. Each streaming playback with working patch is a communication with its transmitting devices. Taken this, it is needed either to shut down any internet activity from the patched machine or to make emissions of the whole material, which is played in browser resulting in big amounts of information. From the other side, with open ports it is possible to connect not to the virtual network, created by composition feeding, but directly to all transmitting devices, which reside in Ethernet without the need to make emissions so often.

By ruslany

Compositor v9 Hypervisor connection experiment

Compositor v9 Hypervisor connection experiment

  • Services used: RTC4k, RT-z16, RT-z128;
  • Layers of work: z16, z32, z128;
  • Wavetables used: MB;
  • Feeded with and without internal antenna;
  • Submitted voice signal (Dictaphone track).

Used virtualization module on both computers. Signal was not received on notebook. Experiment is successful. It evidently shows how patches shuts the transmission channel and does not allow passing signal from outside. All patches are working, starting from RTC4k. Carriers in Compositor AV Extended channel were the same on stationary computer and on notebook. It is not possible to detect RAD96 translations.

Used different saturation methods. Positive and negative carriers are in saturation mode. Central channel with or without saturation (tried 80, 200, 400 modes). Schroeder regenerator is silent. RAD96 patch is successful. There is no ability to detect the transmission channel, when stochastically composited MB tables on the receiving machine with subsequent setting of this wavetables on transmitting station. Virtual antenna and modulator settings are the same on both machines.

It is not mandatory to run RAD96 digital process in execution mode, it is enough to load the Compositor v9 Hypervisor program with it. Process will be compiled on loading and patch will be effective independently of its execution status.

1 2