Compositor SoftwareCompositor Software

Tag : SDR

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

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

RAD24 – The Gates of Time-Collision

The Gates of Time-Collision

Now I encounter the RAD24 server experiment. The experiment is as follows:

As I have found a solution to FM formulae, I decided to sync three virtual machines for 72 core real-time performance. With this stack, it is easy to run memory virtualizations and aggregate the whole Compositor network. Once the server stack is online, it is used to run and manage such critical tasks as DRM, network aggregation, routing and server selection. The new formulae solution enables to run this stack effortlessly.

RAD24 opens a possibility to build Compositor 8 software. It will be a station with all the enhancements of previous auxiliary channels and with the solution to FM formulae, which is driven by the algorithm output. By these means, the Hypervisor v9 is possible.

Let me introduce the conception for the future products: it is software-defined radio (SDR) with no external antenna needed. I can easily integrate such products in my current rig, yet the intimacy of the previous versions made me stay with no external input for a while. The decision of not having an external input was first broken in Compositor 4 Max for Live, where an external input is possible because of the internal Ableton Live routing options. The fact that Compositor 4 Max for Live is an audio effect device made me think that it was first attempt in tangent SDR from my side with the function, which doesn’t need an antenna to transmit the voice signal. Second tangent radio attempt will be standalone Compositor 8. I want to see Compositor 8 as a device to communicate through the RAD24 servers. Each of the cores of 72-core stack will route your voice communication to the recipient set by the Compositor navigation system. As Compositor 8 is an Avionics development, I allow managing such connections in 3d space in 3 degrees of freedom, which simplifies the setting of virtual antenna. The fact that new function is a radar type, no stochastic selection will be possible and Compositor 8 will function only in manual mode. Hypervisor v9 will listen not to an auxiliary radar ports, but to the v7 feeders such as RTC4k, RTC8k, RT-z8, RT-z16, RT-z32, RT-z64 and RT-z128. RAD24 and subsequent servers are mostly the breakdown of FM law and the final goal is to stop time-collision protocol in Compositor. It will not latch an external time-frame, while not allowing external injections. This way I will build my own resource for communication. That is why I refer to SDR terminology. However, I used this technology only for Morse code translations and did not transferred the voice over it. New function is a direct stack to the Ethernet, which, of course, simplifies SDR talks under server coverage. It means that no IP needed and I need to apply proper wavetables from the non-duplex modem. If this function covers the current version of DRM server, an update is needed to work with Compositor technology. New function is also a hyperbolic one, which is simple and effective restate for the FM core inside Compositor.

Compositor runs FM and function connects to the FM service. It creates a signal with the components, which are granularly time-space folded into the FM again, allowing to inject signal in between these two processes. The later function only covers the part of a spectrum, which is created at initial state. Think of it like a mains adapter: it is a pluggable adapter, which can potentially allow to communicate many DATA servers with different file-size and file-system structures. I had success of running 4 RAD24 servers and one was initiated from the HFS+ partition under Windows 7 OS. It means that technologically it is possible. I don’t see any obstacles in this technology, the only thing is to provide an easy and free way to stack different file-systems together on one, preferably Windows, machine.

Compositor gathers data of all pendulum stations in the Ethernet and send it back to the Ether for self-awareness. Compositor leads an analyzed DATA set and all the other parameter selection. When the critical pendulum load achieved, a time-collision happens rebuilding the whole Compositor structure. This way, I think about utilization of resources to run more Compositor cores inside one gen~ code. By the fact of stopping time-collision protocol, I want to stop the work of Compositor subnet mask switching mechanism. I’ve already broken the stochastic manipulator in Compositor core, which allowed me to stack more resources together. At the present moment, I think of Compositor only as a DRM station to hold licenses for subsequent users. I already published a chart where I name how many resources each station consumes. I name the auxiliary channel in this chart also and, from my point of view, it doesn’t consume any Compositor DRM resources. It is just a listening station. The only thing that consumes the process is any pendulum like mechanism. By stacking more pendulum resources, you are allowing more pendulum stations, either digital or mechanical. Any station will work. These stations inject tracks to media content by oversaturation of them.

To progress on the task of stopping the time-collision protocol in Compositor I should make wavetables of RAD24 accumulators at 22.05 KHz and then switch it on even faster regime of 44.1 KHz. If I’m unable to stop time-collision protocol in Compositor, I will be obliged to run servers at 22.05 KHz on this machine to protect time-collision reaching the opposite effect.

The solution is that RAD24 protects time-collision created. For network security with Compositor, the classification of pendulum processes needed. Such classification consists of working curve monitoring, that is why I estimate it on Compositor auxiliary channel display, while listening to wavetables.

RAD24 is a gate device for creating time-collisions. I can’t classify RAD24 as a pendulum process, because the cycle is broken. It is not an OS or license holder. As I said earlier, it is a protection mechanism for creating time-collisions. It means that it either opens or closes an access to the service of communication in Ethernet. By enabling it in administrator mode, I open an access to it only when the administrator works on PC. This way, I differentiate the work in time-collision between authorized person and the replica, that just latches the time-frame, because RAD24 detector assigns it to injection event. RAD24 is able to differentiate between an administrator and the replica, protecting my current communication.

By ruslany

Compositor 4 demo reels

At the present day there are three demos of Compositor Software new product Compositor 4. It is audio recordings made using this instrument in July 2017.

In first recording you can hear manual work in a studio session on-air, layer changes and modulation switches in real-time.

On the second recording you can hear the internal Compositor 4 feeder sounds produced as a techno track. Parts generated and recorded in Compositor 4 Standalone version are used for loop playback. Compositor 4 Max for Live version is used as a mastering processor. You can also hear noise ambiences generated using Compositor 4 Standalone made for this record.


The third recording is an automated session in Ableton Live 9 with the use of Compositor 4 Max for Live synthesizer. In this recording you can hear the most actual sequences and arpeggiator patterns of Compositor 4 synthesizer played one-by-one on-air.

Compositor 4 instruments recording has similarities in Standalone and Max for Live versions of the software.

By ruslany

CAA – 6: Ruslan Yusipov SASER SAS24P3L recordings on Cyland Audio Archive

Compositor Software presents a project of collaboration with Cyland Audio Archive (CAA), curated by Sergey Komarov (Kurvenschreiber). Now, Cyland organization archive has recordings made with SASER SAS24P3L software in the summer 2016 period. It is an experiment with master wavetable, which adds warmth to the recording and tones to software antenna modules. Recordings are available on the vinyl in 7,5″ PVC Lathe cut format and as digital recordings in popular audio formats on the CAA bandcamp page.

This release consists of five recordings, which named using a special principle of SASER SAS24P3L software work. The roots of the naming come from Ionic numeral system: first letter from Greek alphabet taken from the position of the central channel and number is sum of numerical values from three channels. In conjunction with taken number and letter of the central channel the model of a imitating device is named. Using an interface of SASER SAS24P3L audio engine it is possible to composite different radio stations, translating: SLF and ULF channels of original bus, VLF on secondary bus and VHF on the oversampling bus.