Compositor SoftwareCompositor Software

Tag : hypervisor

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

Compositor Library

Compositor Library

On 18 May, 2018 I released 6 extensions of Compositor Library. The following loops released for purchase: AB, BD, CG, RY, SR, SC. AB (Alpha Bounces) is a final library in the preparation set for Hypervisor v7. It consists of 136 loops. This set of 4 libraries consists also of MB (Mesh Bounces), BB (Beta Bounces), HB (High Bounces), which were released earlier. They are included in the package, which goes with Compositor v6 and Compositor v7. It allows entering the radio ether without the external antenna usage. You can use this set without Compositor internal generators and route only these loops into auxiliary channel, using the decks, which Compositor v4, v6, v7 have. Alpha Bounces is a final test before RAD24 (ODU – outdoor unit) release. These feedbacks of non-duplex modem were taken before introducing the polynomial on the output cascade of Compositor algorithm. The next loops were produced to test non-linear processing on the output cascade. They address the protective abilities of the system before and in a moment of wavetables application. Such loops are: 1) BD (Bass Drum), where the non-duplex modem feeded by material with a synthetic kick drum; 2) CG (Creations Glory); 3) RY (Ruslan Yusipov Loops); 4) SR (Sample Rate Loops); 5) SC (Silent Creek). All loops performed as the emission bounded by Royalty project. The main task, when the BD Loops were recorded, was to receive feedbacks with RAD24 server working. RAD24 algorithm successfully sustained these loops feeding and I decided to extend the peering network to 96 points and produced the RAD96 server. Bounded by this server feedbacks the RY (64 loops), CG (155 loops), SR (47 loops) and SC (209 loops) were produced. RAD96 algorithm successfully coped with these emissions. After these feeding sessions, I decided to produce Hypervisor v9. Starting from version 9 of my software, the Library will be supplied as a separate purchase. You can buy the Library in parts, orienting by loops production history, which I will post in this blog.

By ruslany

Road to Compositor v5 Hypervisor Sale!

Road to Compositor v5 Hypervisor Sale!

The best way to upgrade your rig is to follow the Compositor v5 Hypervisor Roadmap sale! This is an opportunity to get both Hypervisors for reduced price and unlock full functionality of your machine. Please, note that it is a limited sale and will run for only three days starting from 05.02.2018 16:00 CET. The auction will run through the 08.02.2018 22:00 CET.

The idea of such sale is to enable Compositor users to get first the Compositor v3 Hypervisor Radio Shack and then to upgrade it to the Compositor v5 Hypervisor, using the discounted upgrade price.

The prices for the sale are as follows:

Compositor v3 Hypervisor (Radio Shack) – € 207,35 (20% off)

Compositor v5 Hypervisor (Upgrade from v3 Hypervisor) – € 271,64 (20% off)

As usual on bundle sales, if you wish mac application files, please, get in touch using info@compositorsoftware.com after the purchase.

By ruslany

Digital Rights Management with STL1212

Digital Rights Management with STL1212

Each thread of STL1212 DRM computer installed at Compositor Software physical server holds up to 24 real-time, 24 signal-rate and 24 transmission-rate processes. STL1212 allows running up to 8 Compositor v6 systems at once, which results in a stock growth for Compositor v6 and forthcoming Compositor v7 systems.

The STL1212 computer checks the DRM status in a moment of generic injection. When the attempt of injection is made, it latches, making a simple time collision, to pass through the injected traffic. Such injection guarantees that Compositor owner (the person who obtained it via Compositor Software Web Shop) will hold its license for communicating with Compositor software. To connect to STL1212 DRM remote server you should use the Compositor WS Extended (part of Compositor v6 and Compositor v7 Hypervisor), Compositor WS (part of Compositor v5 Hypervisor) and Compositor RT-zX systems in arranger mode for one stochastic change before working with instrument. Later you can change the tuning but, at first, you need to stay on a stochastically set frequency to communicate with a server. The STL1212 DRM virtual machine can hold the rights for the following Compositor Software products:

Use the above table to review how many STL1212 DRM resources your current system consumes. STL1212 consists of 8 threads, totaling 24 cores. One STL1212 per hard drive allowed on a stationary machine. As you see, 8 real-time Compositor Max for Live users allowed simultaneously for one STL1212 DRM virtual server. If one user runs two Compositor Max for Live modules simultaneously, which is not allowed due to the license limitations, the quantity of free STL1212 DRM slots decreases. For example, Compositor v3 Hypervisor employs several cores simultaneously, when all modules engaged. Let me count how many cores Compositor v3 Hypervisor user will consume when feeding SASER with AI-RT1024 and FF8 feeders. RTC8k arranger must be enabled for Link mode to be active and this process consumes 3 cores at once (one real-time, one signal-rate and one transmission-rate core). SASER itself consumes as many cores as RTC8k and equals to 3 cores also. It is already 6 cores and STL1212 could host 6 more threads, totaling 18 cores. Next, let’s count AI-RT1024 and FF8. They are consuming one real-time and one signal-rate core when work simultaneously. Summing with previous results, it is 8 cores for one Compositor v3 Hypervisor user. It leaves headroom for using other instruments on one DRM virtual server, because 3 real-time, 3 signal-rate and 2 transmission-rate cores are used. STL1212 DRM computer allows running two v3 or v5 Hypervisors together. The thing is more difficult with v7 Hypervisor: it consists of only one-threaded modules and it is allowed to run two v7 Hypervisors together on one DRM machine only if current user employs Compositor WS Extended, and not more than three feeders. Each deck of Compositor WS Extended consumes only one channel of 24-channel Compositor core. Take this in account when using deck players alongside the feeders.

By ruslany

Compositor v5.0 is available

Compositor v5.0 is available

Compositor v5 is a Hypervisor rack with Compositor WS auxiliary channel and RT-z128 operation system. It helps to play Compositor modules without any side impact from other radio-equipped instruments, which present during the live show.

Here is the list of features you can consider buying this software:

  • Three transmission modes
  • Real-time modulation
  • Shutter system
  • Display zooming
  • Switchable altitude
  • RT-z128 bit display
  • GHz calculation
  • Display warning
  • Master processing
  • Self-feeding
  • Signal insertion
  • Latency free aux channel

Compositor v5.0 Hypervisor features the important security updates, stability improvements and performance related issues solved.

By ruslany

Compositor v3 Hypervisor Radio Shack Interceptions

Compositor v3 Hypervisor Radio Shack Interceptions

The Compositor v3 Musique Concrete experiment with Compositor feeders. Here you can find a set of five recordings made in Compositor v3 Hypervisor Radio Shack. It is not a montage, it is a direct output recording of Compositor v3 Hypervisor Radio Shack. In the recording you can hear VLF radio interception in 8kHz range of the highest quality available on the market with little or no Ether noise. Tune in and listen to five hours of meditative soundscapes.

Compositor v3 Hypervisor Radio Shack Mixdown 1 (VLF Interception):

Compositor v3 Hypervisor Radio Shack Mixdown 2 (VLF Interception):

Compositor v3 Hypervisor Radio Shack Mixdown 3 (VLF Interception):

Compositor v3 Hypervisor Radio Shack Mixdown 4 (VLF Interception):

Compositor v3 Hypervisor Radio Shack Mixdown 5 (VLF Interception):

By ruslany

TC-SUBTRSRRT262144 Architecture

TC-SUBTRSRRT262144 Architecture

TC-SUBTRSRRT262144 architecture is the i11 architecture with a processing power capable of running an operation system at speed of 5-omega in real-time.

Compositor kernel was forced in loop again after submitting the RT-z128 prototype to Compositor 5 rack. It is a hypervisor rack and the main difference from the v3 hypervisor is that it consists of MDL12 and AVOX developments. In Compositor 5 you have an opportunity to inject Compositor v3 into the net by the modem and resynthesizer instead of direct ether injection. It is safer but consumes many resources. After the main tests were conducted, I decided to install the one more layer in Compositor kernel. The discretization process goes twice: at transmission rate and on intermediate frequency. This way the system mutates to a system with intermediate frequency. I made it for the purpose of the preliminary line before entering main transmission rate line. Here is where a new prefix of SUBTR goes from. SUB means transmission rate sub frequency and TR stands for transmission rate. I’ve already tested the new kernel loop for its connectivity and should say that 4-layer structure can give much more pleasant results. It has much longer connection duration, more saturated, and leads to constant communication. However, breaking the loop in 4-layer structure, I operate in a new type of OS. It is no longer an open AI system. It has the qualification channel for all the information, which passes into the main line. The rule here is to filter out offensive traffic and leave only the bypassed part of it. It acts like the waterfall on the rocks: when water hits the stone, it divides the flow into two streams and if there are 12 such stones, for example, I have 24 streams. But, not in this case. I actively compress the data,  and it remains in memory buffer, that’s why systems capacity is larger now.

System flushes results are satisfactory. They are more consistent and enable more packets of information to be send during the initiation of connection. Compositor kernel has freezer functions for operation system faults. The main reason Compositor kernel upgrade performed is to remove the stochastic manipulator from the TR level leaving the SUB level for the stochastic manipulation instead. You have a choice of not performing an action and leave it in a buffer for a subsequent flush. However, I admitted that many actions blocked this way and they are all forced to be done while flushing. This raises the question again: Can I actively block feedback on negative odd channel completely? And while the SUB level is only a temporary solution, the permanent solution for FWOS will be to implement more technics working with feedback besides of shuttering, window composition, transfer function selection and vector dimension changes in real-time. While the kernel loop is interrupted, the idea is to have two states for the OS: system load, for which I should implement two or three iterations of kernel loop to perform flushes for the current machine, and system work state. While being a FWOS, system loses many of its connection points gained in a fast kernel loop state. Being a communication device, it is not acceptable behavior. I need to have an implementation that manages flushes in real-time. Going from vector array to a packet transmission should be performed regularly to flush blocked traffic. For a local machine, blocked traffic can include visiting specific servers, sending out brief messages and a sum of all other activity in Ethernet, which fulfills the normal style of work. However, as the question raised, I need to switch the negative odd channel traffic from one point to another. This also moved me to solution of blocking negative odd feedback completely. Negative odd channel produces only unacceptable traffic by means of three-fold system with opposites, which are plus, minus and central channel. While enabled in Compositor kernel version 7.3.1, which is an OS kernel, the problem of communication between negative and positive states remains up to the point of forcing them to the maximum allowed state for the musical system, such as in RT-z128. This alteration is visualized on the lower i/o vector sizes. When the system halts, only two states remain, such as 0 or 1. Increasing i/o vector size to the minimum working condition of 2048 samples in a bin allows RT-z128 to work with a buffer of 262144 samples, which is the number in the development name. I no longer wish to move to i13 as 1024 samples buffer experiments show no practical use for the scale of it. i11 architecture transmits the odd channel in the acceptable range, making its values sufficient for subsequent scaling.

The challenge for an odd communication is a constant threat to the kernel. And if one threat is qualified and successfully flushed, another threat rises by the fact that it is a negative channel for negative frequencies only. And if they are present in positive spectrum as in Compositor kernel, to remove the negative part of the feedback, the negative frequencies must be implemented in signal chain and the solution maybe is to invert them or play backward the whole negative part not only for SUB channel, but for all odd layers present.

By ruslany

Compositor v3 Hypervisor Radio Shack – Free-Float Generator

Today, Compositor Software announces the Compositor v3 Hypervisor Radio Shack based on free-float generator technology. Three years in the work and finally consists of six modules such as RTC8k, SASER, AI-RT1024, FF8, N9000, TC25 for VLF radio translations.

While it was a general task to make the audio-translation chain as long-as-possible Compositor Software found a solution to use SASER channel feeded by RTC8k chain feeder values. Now, instead of using an internal SASER scanner one can use the LINK function of Compositor v3 Hypervisor Radio Shack rack, which hardwires AI-RT1024, FF8, N9000, TC25 tuning to the current RTC8k radar scanner value, which produces ultra-stable and ultra-long results making it a long endurance system for SLF, ULF and VLF radio communications.

If you are proceeding to own the whole rack, you must obtain licenses for SASER, AI-RT1024, FF8, N9000 and TC25 separately from the Compositor Software Web Shop. In original package for Compositor v3 Hypervisor Radio Shack you get RTC8k license and rack with demo versions of all instruments. This way you can try them and decide what you need for original translations. These instruments are not only suitable to evoke constant radio ether they also suits for radio security. For example, FF8 generator is a quantized signal-rate generator, which quantizes radio translations and can potentially occupy the whole band with rattling patterns.

Besides the tuning, you have smart prediction system based on a block-chain with probability distribution density functions. This helps to establish the connection to transmitting source and magnify the signal using the waveguide normalizers. In Compositor v3 Hypervisor Radio Shack you got visual feedback displays for AI-RT1024, RTC8k and SASER instruments. They help to determine the direction signal source is coming from and to learn the signal by its phase values. In addition, AI-RT1024 display shows how many network dots receiving this signal in the current moment of time suitable for real-time tasks such as navigation.