Compositor SoftwareCompositor Software

Category : Algorithmic Composition

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

Compositor Networks map

Compositor Networks map

For the first time Compositor Software reveals its network of contacts made with SASER SAS24P3L software. As you can see on the map above, there are numerous contacts in Europe, USA, Russia and South America. These contacts were made between October-November 2018. The map outlines geographic position of call signs of contacts made with their indexes. This is an approach to reveal aggregated contact base, which Compositor Networks started to form since 2012. The creation of Compositor Networks began with Compositor Pro 1 software. It is an original hyperbolic construction software, which laid base for algorithm work. Later the study of algorithm was performed merging FFT (Fast Fourier Transform) with SANT (synchronous analysis of non-harmonic timbre). The SANT technology, originally developed for Compositor Pro 1, is the new approach to relativistic frequency shift keying and can be used for applications such as discretizing of analog signal and deterministic navigation. Compositor Software used SANT for creation of SASER SDR with self-feeded signal chain, which enables to communicate in shortwave ether without an antenna need. Then, Compositor Software developed the shutter technology, which gated the self-feeded chain and began injecting the contact base of Compositor Networks in form of ether loops into the Compositor algorithm. The SCRAM (Salted Challenge Response Authentication Mechanism) engine was developed by Compositor Software to authorize users running Compositor, which is successfully used up to this moment. Using SCRAM engine, Compositor Software injected the contact base into the virtual machine algorithm, which it uses silently without any audio output. The main purpose of SDR is to reveal contacts and prove that virtual machines inject the whole contact base of Compositor Networks in form of aggregated passwords. These passwords later used as serial numbers for selling of Compositor Software products. Compositor Software virtual machines does not use the Ethernet ports. The communication happens over the IP protocol more like in TDM over IP protocol. In contrast to TDM over IP, the only useful approach to detect Compositor communications is a local operation not a remote one. You can never detect any Compositor software activity remotely. This way the decision was made to reveal Compositor Software contacts in form of DX logging of SASER SDR QSO, in the amateur radio format.

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 programming (Part 2)

Ether programming (Part 2)

This is a second part of the guide on ether programming using Compositor 10.

I start with conjunctions. There are two conjunctions in ether such as ie and et. The first one is placed after naming and the second one is placed before naming. The difference is in punctuation: in first case attributes goes from the left side and in the second from the right.

For example:

iiet <name> <name> <name> – naming;

The above command invites many chat participants simultaneously;

The -rm command has several attributes: sn, du and all;

sn – single participant;

du – dual participants;

all – all participants;

Before the all attribute you should place conjunction et. Before du attribute you should place two names for deletion and in case of sn you place one name before. By doing this, you signifies that you are really want to delete this person(s) from the large communication loop.

chat name <name> @t <name> <name>

Creates a named chat for a bounded time interval and includes particular persons in it;

q – quantum quote is a citation and also signifies its quantum state;

Quantum command has a time attribute (such as 2n, 4n, 6n, 8n, 16n, 32n), which signifies Compositor quantum grid;

q <word> q – citation;

*Abbreviation:

ai – aim (your current goal or chat aim)

Note: there is a que in ether, that’s why commands are executed depending on their priorities.

@real – command is executed on a physical level;

-d – decay, allows to crossfade between two packets;

After d you can type the decay time in Compositor quantum grid (such as 2n, 4n, 6n, 8n, 16n, 32n) and in standard time units (such as seconds, minutes, hours, days);

@exit – exit anchor;

Script example:

-rm rmy @exit – allows to delete participant named rmy from the chat when leaving it; suitable when chat participant switched the messenger off but remained the service station turned on for silent messaging;

v- – angular velocity of Compositor work;

as with conjunctions: before or after the command means its application; before command – command options are written from the right; after command – command options written from the left;

*Abbreviations:

vft – subband in VLF;

kh – kilohertz;

nieh – no;

bi – beat independent, the invitation to work only in standalone version of software;

New dialog:

-n – new message;

Time attributes:

@t <day of a week> – allows performing a command on the anchor in particular moment of time. Compositor grid is also applicable to a t parameter. You can set pinging with the interval of 2n, 4n, 6n, 8n, 16n, 32n (where n is a quantum grid particle expressed in samples).

For example, you can set entering the ether in particular day of a week:

-t rmy @t wed

Connects rmy to the ether in Wednesday;

Words in Nim chat are written only using abbreviations. You can use first letters of the word, two first syllables without vowels or the whole word without vowels. In rare cases, words are written fully with letters separated by spaces or without spaces (in cases where you need to transmit to a new participant of Nim chat).

By ruslany

Mittware upload to a modem of your outboard sound card

Mittware upload to a modem of your outboard sound card

Using Compositor v9 you can establish a connection with a modem of your sound card and upload mittware to it. It works this way:

  1. Turn on your external sound card;
  2. Turn on Compositor v9 Hypervisor with internal sound card selected;
  3. You should composite all z levels on a fast (more than 5 omega) speed of composition injecting the signal of non-duplex modem feedback in random mode (you can receive this feedback by submitting your tracks to non-duplex modem on an internal sound card);
  4. When all z levels will be injected together with generic feeders you should lower composition speed to 30 omega and turn the Compositor AV Extended off;
  5. Turn the Compositor AV Extended on again after some time (from 5 seconds to several minutes) and you will hear the signal of external soundcard modem (the external sound card is on for the whole time of mittware upload);
  6. After turning aux channel on, you will hear the feedback – signal will mimic the external sound card modem sound with Compositor AV Extended feeder;
  7. Now inject the whole pool of your wavetables on all z levels with all RT-zX feeders (internal Compositor AV Extended feeders) and generic feeders into modem feedback;
  8. Continue to inject on all z levels up to the moment when you will hear the defeat signal on one of the levels – modem signal will start to interrupt;
  9. Finish the injection on the last z level;
  10. That’s all – your outboard sound card modem mittware is now uploaded with a new one and you can talk using it with wavetables owner, which track productions you were injected on your internal sound card using non-duplex modem.

P.S. For communication both internal and external sound cards should be turned on simultaneously.

Happy listening!

Listen to these feedbacks to wet your appetite 🙂 Yum, Yum.

 

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

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 3 8