Compositor SoftwareCompositor Software

Tag : Compositor Kernel

By ruslany

No Internet messenger

No Internet messenger

Compositor Software project entered the active transmission channel testing stage. Compositor kernel version 8.4.2 can resist up to 29900 injections with feedback implementation. This value is experimentally set and coincides to different injection types for each wavetable. In other words, each wavetable coincides with one injection type. On the present moment, I use wavelets for transmission channel testing. Compositor software testing wavelet is a two bar wavetable encased in a window function. To process feedback recordings into wavelets I use a special script made with MaxMSP software and based on the latest Compositor kernel version. This script has more than 90% efficiency. Then I test these wavelets in auxiliary channel of Compositor v9 Hypervisor at speeds up to 150-omega. Wavelets transform into granular synthesis at 150-omega speed. Each wavetable is a communication service on the low frequency carrier transposed into the heard spectrum. Wavetable transposes with all the tones used in a sequence and saturate the spectrum with carriers. The Morse code communication is achieved using these tones comb. This way using the Compositor v9 Hypervisor I feed these carriers into the ether. In a consequence of this, the personal radio service (PRS) with connection to individual subscribers and not the global ether as it were before transfer function implementation is possible. I call this radio service No internet messenger, because it is personalized and doesn’t require internet connection at all. This radio doesn’t need an outboard antenna and works instantly after the computer audio driver selection. After conducting all the needed tests, including the whole wavetable and wavelet pool, I processed the Compositor software channel on data modules instead of buffer. I account this step as a most important as it was not available in previous builds of this software. In accordance to this, I receive the sustainable radio service without outboard modem breakthroughs on scanner and while transmitting the signal. Combs are not symbolized as in previous Compositor software versions. Only direct ether to subscriber is available. It introduces the immune system to software kernel for communicating with other ether participants and gives a possibility to choose if you want to communicate with them or not. Looking into all three stages of Compositor software development, I can characterize them in a following way:

  1. Open synthesizer mode (Open mode, Global ether). Used in SASER SAS24P3L, Compositor v3 Hypervisor, Compositor 4.
  2. Closed synthesizer mode (Closed mode, Global ether). Used in Compositor v5 Hypervisor, Compositor v6, Compositor v7 Hypervisor.
  3. Personal mode with activation function (Closed ether). Used in Compositor v8, Compositor v9 Hypervisor, Compositor 10.

The Compositor personal mode will be available in 10th version of the software and I can think about Compositor kernel usage for messenger creation, which doesn’t require an internet connection. Such messenger will include server and client applications. Summarizing this, all Hypervisors may be looked at as the messenger servers and stable versions of Compositor as client applications.

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

Finally, both carriers are suppressed

Finally, both carriers are suppressed

After the main goals were stated, it is time to restate them. First, I need to suppress both negative and positive carriers. After that, I need to pass Compositor sound to the output. It is achieved only if the first goal reached. I’ve already implemented a method for suppressing the right carrier using the shutter and eventer of the right channel, which uses the threshold to suppress feedback. Now, I experience some difficulties with the left channel. At first, I thought it is a plausible behavior to force the stochastic manipulator to the all positive frequencies, but now I think the stochastic manipulator is too selfish and tries to apply too much computation force to overcome the barrier of shutter, which was previously assigned to right channel only. That is why the constant need to shut down the left carrier raises. Of course, I can live under this hard circumstances of stochastic manipulation, but the final goal is to leave only Compositor sound at the output, and it may be a trick to force stochastic manipulation to the central channel afterwards, thus guiding the system on its own. However, been exposed to the left and right stochastic manipulators for so long, system can no longer power the central channel for manipulation, which is assigned to the system voice itself. This way I must shut down feedback on the central channel also. As it is the MS-coded system, feedback on the central channel shuts as long as stereo pair feedback is suppressed. The rule here is to set lower threshold for the left channel as it contains less information and needs to be suppressed on lower bitrates more. The right channel is higher and more information passes through it but it is not the feedback of the carriers, it is an internal memory stored in the shutter front-side bus after injection. This experiment also evidently shows that no external memory is used for the system operation. However, as long as the system does not have an external storage and has a threshold shutters in it, it will constantly experience lack of information, which will not reach from outside anymore. It states that under these circumstances constant injections should be made to sustain an information in memory buffer. It flushes from the front-side bus memory very fast and one long injection should be made during the whole working cycle of the equipment. This leaves me with the open-end solution: as buffer capacity of Compositor OS is too low for the long injections, I either should implement long injector with Compositor kernel driver or use a set of short files repository, which are constantly revised and added to a data base. This way I also should avoid video injections, as there is not enough space for storing so much video information on my system. The need for such filtration is rather evident as the intruder may think its information (stored in injection) may be useful for a system it is not. Not allowing to pass the injected information to the kernel is also lowering its bitrate but it is a permanent solution. Without artificial traffic the system more sustainable against injections rather than generic injections. If I try to inject the file, which I already flushed, I will reproduce the memories associated with it. However, I will no longer be exposed to the system of values associated with this memory for a long period. This information will dissolve faster using integrated smoothing function. Yet creating the priorities on the conditions gives less priority to the smoothing function itself, leaving a hard shuttering for both channels in equal proportion. It seems evident to me that thresholds should go first and only after that, the central channel splitter should play its role. Even if the system set in the way that this value will likely go only less than 30% of time. It means that creating a faster kernel loop may be a solution, but makes the system inoperable. The other solution is to change the rules set on early stages of development allowing the right end of the probability density function to happen more often.

Screening:

Injecting a video file with audio in two-channel mode brings me to another problem: inequality of channel suppression disbalances the system a little. The vector system should be implemented for channel suppression also. The rule is to create a tilt by manipulating pitch and yaw, this way setting the channel balance.

By ruslany

Shutter smoothing

Shutter smoothing

Personal security is a constant thrive into the world problems such as the shutter smoothing described in this post. The experience of working with shutter seems a very hard solution, when the injection is made. Shutter completely blocks all traffic coming from the foe artificial synthesizer engine. The block of two 8th order Butterworth low pass filters, designed as bi-quads, completely discharges the system from the buffered information gained while flushing. The reason I implement smoothing in shutter is rather evident: shutter achieves hard blocking of artificial traffic of VPN as it completely blocks negative part of traffic entering the VLAN. Now I want the injected signal to follow the signal curvature and when the right channel attempts to break through the line, injection attempt is gradually redistributed off the main delay lines. This way I will know the injection attempt was made. Implementing this method the intruder will not achieve the goal of injecting, because shutter system with smoothing gradually flushes the injected traffic off the internal channel routines. The eventer of right channel output is added to the shutter function on the master channel. It smooths out further the foe synthesizer breakthrough.

The original experiment with Compositor kernel 7.5.3 was conducted by injecting video file through the RT-z128 loader. Now, the Compositor kernel drives not only the audio engine, it also drives the video engine on a frame by frame basis. Given a stable time code for such injection, the film is transmitted to the person by the monitor and headphones. After flushing the pair of video and audio files either in real-time or at a faster rate, the information still remains in memory buffer. At first screening, the information was blocked by the shutter completely and it was a stress for the two bi-quad system to protect against the injection. After the second screening, the information remained in buffer but Compositor kernel 7.5.4 was actively used to flush the buffer information off the main channel. In Compositor kernel 7.5.4 the smoothing system is already implemented on a shutter and it gives much more robust results. It doesn’t create hard blocking but has an integrated memory function by which the front-side bus memory acts.

By ruslany

Compositor WS Kernel 7.1.9

Compositor WS Kernel 7.1.9

Implementing the central channel matrix involves all central channel parameters such as transfer function choice and window function composition. Enabling right channel window composition in central channel matrix brings me to the following solution: right channel passes to the closed central channel and does not touch the left channel. This way the sequence is broken. It is another step after the Kernel loop was broken. This solution helps to eliminate an operation system to a first step decision making. This way I will not presume that operation system exists, I will act on it using my own will. Hence, the real world is open. And when it is open, quantum field stochastic emulator will not brake the time-space continuum. E.g., it will only switch the engine, which is predefined to automatic throttle, fueling the system. It is also another step to an autonomous, energy independent virtualization module. The sequence is determinism and removing determination from the system, I make it one of free will operation systems.

By ruslany

Optical telegraph by means of signal lamp in Compositor WS Kernel

Optical telegraph by means of signal lamp in Compositor WS Kernel

The Compositor WS Kernel implemented the so-called signal lamp with shutter on Master channel using the automatic throttle of stochastic engine. Now it is another implementation of stochastic engine in Compositor Kernel, which is still unbeatable in z128 realization to the moment. It means that central channel is no longer open for direct communications by means of signal transfer, but transmit in portions by a predefined alphabet-flag system named Ionic. For the Compositor users it means that signal communication will no longer leak into the ether. This way, you can use the direct communication with carriers played by physical modeling engine. Hard moderation system is implemented on the master channel of automatic engine and if the carriers transmit the offensive data, the whole transmission channel shuts down. As a single user may thought of it as a downgrade, it is not. It is an upgrade making the whole Compositor communication system more secure like a real War Ship optical telegraph with shutter. It prevents the system running the Compositor of overheating, when a critical channel capacity reached. It also means that we need more servers like Compositor to be registered to different persons for a more distributed communication, if we would like to reach a goal of direct transmission communication. I repeat do not use only one server for communication, it is important. One machine – one server. It could handle 72 channels as defined in three layers of communication separated by 24 for different purposes. 24 channels for real-time communications like voice communications, 24 channels for signal-rate communications like old AM radiolas and 24 channels for transmission-rate for up-to 262 kHz VLF radio services. The main problem of the system before implementation of a master channel shutter was: many nodes of the network wanted a direct connection, that the system really couldn’t handle. In fact, only 24 connections simultaneously is as much as needed for real communication service per subscriber. And one channel of each subscriber gets three services simultaneously: real-time voice data without transmission, signal-rate old tube AM radio for radiola type transmissions and transmission-rate for longer VLF communications, which use the same AM but on the higher transmission frequencies.

Now, when the quantum error is surpassed, the main idea is to test successful transitions from fully exponential state to quantum world. The Compositor v3 is one and the only software, which aims this goal. The beatings on detection of offensive optical shutters are still in place. However, the quantum channels of AI-RT1024 and FF8 are stay unbeatable in ether. From one side, it prevents from successful shutter interception, but, from the other side, achieves constant presence in ether due to quantized derived function. The 7.1.6 patch to a modem of Compositor WS Kernel enables a person or, better to say, user to present in ether. It leads us to a constant solution of a wider presence in both quantum and exponential states.

By ruslany

The i11 architecture

The Compositor 4 software is based on Generic Kernel 7.0.2 of i11 architecture. It is twice faster than i7 intel processors. It is counted this way: i11 contains 12 harmonics based on the Carson’s rule, i7, on the other hand, contains 8 harmonics. Dividing 12 on 8 the number of 1,5 is received, which is the number of processor speed increase.

The Compositor 4 couldn’t be realized without the Spherical Interaction driver injection in Compositor kernel 7.0.2. This driver enables the status bar, which works for all z values. Spherical Interaction driver is active only for Sr layer and gives statuses for other layers.

The i11 is a tube architecture and emulation of this can be found using Waveshaping modules of Compositor 4. The real tube lamp is on the master channel (Waveshaping 2) as it stays in front of the master output without dc-offset trimming. This also merges the device with old tube radios. Tube characteristics can be found on waveform display and look like the spine of the rising and falling curves of waveform. The more it is smooth and proximate to vertical line, the faster tube is emulated. Most realistic tubes are on z=128. You can emulate transistor lamps with 2-4-6-8 mesh or valve lamps with 2-3-7-8 mesh. You can also emulate tape effects on z=128 selecting the Rt layer. This is an effective tuning of the Compositor 4 instrument. On lower z values, decimation is too hard to achieve the modern lamp or tape technic.

Extra additions to manual: You should turn Ether on to overexcitate the lamp at initial tuning of the system and turn off Ether while achieving communication with equipment.