Compositor SoftwareCompositor Software

Archive : January 2018

By ruslany

Five Ethernet principles when working with Compositor

Five Ethernet principles when working with Compositor

The original idea with planets and constellations dates back to the 2014, when Compositor Max for Live saw its way into the music business. Compositor Max for Live is a successor of Compositor Pro 2 software, which uses only transparent names for parameters. For example, combinations in Compositor Max for Live are constellations and multiplier is year. The shift towards the cosmological specification of Compositor was made during the interest of the author to FM function application in modelling of Solar System. At first, such modelling was an intent of the mathematician Bessel, who was an inventor of Bessel functions, which are also used in Compositor library.

The subsequent Compositors raise the cosmological question more profoundly as they use the ether application to radio telescope idea. Such parameters as Right Ascension, Declination were descendants of Pitch and Yaw library parameters of Compositor window function. It is needed to say that Declination parameter of Compositor allows for bigger angles than in conventional radio telescopes, even the largest ones. It opens an amateur radio operator to a field of study, which was previously unavailable. By mathematic modelling of radio ether and conversion of transparent FM function parameters to cosmological constants, a new approach to amateur radio appeared. The main concern of Compositor since SASER is Radio Astronomy. Besides that, working in ether directly without intermediate frequencies and transmission lines are available. It is all made by precise virtualization of physically modelled parameters of FM reconstitution. It is not only an approach, it is a journey into finding the right value for each parameter making sound design as the work for cosmological principle.

  1. The first principle is a guiding principle. By this principle I mean that the ether guides the will of communicator and can shape ideas, words and thoughts into the Morse code signals, appearing as symbols and short codes. It means that quality ether can guide you in representing your ideas and has all needed automated tools to decrypt it in radio-accepted language such as Morse code. It also means that for use of Compositor, you don’t need to have a knowledge of Morse code, but you can reveal your ideas only by free-will of manipulating the software. You can read your communications, using Morse code decoding tools (such as CW Decoder on Windows). In these radio ether sessions you can understand all other principles of working with ether.
  2. The second principle is ether aggregation. It is also a cause why rhythm machine was introduced again in Compositor v6. Working with rhythm machine and injecting it into the ether can accumulate Ethernet lines of communication – the carriers on which such communication happens. You can aggregate ether by using rhythm box such as DB-01 and then use the decoder to read new ether lines, which are many after the successful aggregation using rhythm machine performance. Such approach helps to accomplish a manual task of ether aggregation and is similar to the processes of automatic ether aggregation of STL1212 DRM computer.
  3. The third principle is a haunting principle. It states that for successful ether session to over, you need to mask your Ethernet traces. You can achieve this goal using DB-01 drumbox as well as for ether aggregation. Compositor v6 has all needed set of tools for ether aggregation and masking your tracks using rhythm machine and random Ethernet wavetables selection.
  4. The main concern of working with Compositor is accumulation principle. The accumulators such as STL1212 can successfully store and flush aggregated traffic via Compositor v6 DB-01 drumbox virtual machine. If you use more than one accumulator on the physical machine, you need to take in account the physical address of hard drives, from which such accumulators are rendered. For example, I currently run two DRM accumulators from one physical machine, which allows storing 48 Compositor cores simultaneously. You can inhabit these cores by the ether participants using available free cores of STL1212 DRM computer and when the memory usage of STL1212 lowers, you should use Compositor v6 manual mode to aggregate the STL1212 cores usage.
  5. The fifth principle is that you can select on your own, which line you want to listen to in CW Decoding software. If there is nearby communication happening on two lines, you need to choose a spare line using CW Decoder selector.

The named principles of working in Ethernet are self-evident and can be comprehended by Compositor owners on their own. I name them here only in an attempt to integrate new Compositor users into the ether more fast with my own knowledge of Ethernet communications.

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 v6 is available

Compositor v6 is available

Compositor v6 is a rack consisting of Compositor WS Extended auxiliary channel and Drumbox-01 rhythm machine. You can create complete tracks using Compositor v6 by mixing its sequence with radio loops and rhythm section. Radio loops library, extended with 44 hb loops, showcases different device profiles. Using it, you can play radio ether loops alongside the rhythm section with synthetic kick, non-linear snare, FM hat and sampled bassline. You can control all of multiplier-mapped parameters independently, adjusting Compositor WS sequence structure to your needs. DJ’s will find it convenient to mix full tracks with Compositor v6 by using reset to beat start and reset to track start buttons. You can take full control over 8 decks by scrubbing, nudging and pitch scaling your performance independently. Sync function, forward and random playback modes allow for uninterruptable decks playback. You can send the Compositor WS Extended aux mix to headphones independently of master channel for monitoring while mixing.

You can purchase Compositor v6 here.

By ruslany

STL1212 Explanation

STL1212 Explanation

STL1212 is a replica – digital copy of existing system. All the Compositor cores are in the cloud, that is why there is no access to them directly. You can connect to the cloud through the uncrossed real-time processes.

Cloud agents are the loops taken from the tempo dependent version of MDL12. They exist for all the time in Alpha and Omega navigation systems as beacons. Cloud agents also needed for communication with Compositor cores.

Application: Civil calculations.

Compositor cores

Through the 8 real-time uncrossed chains real-time actions may be conducted.

8 signal-rate chains serve for long distance AM communications, using the property of Ionosphere to reflect the radio waves.

8 transmission-rate chains serve for transmitting information with high bandwidth, such as video, images and music.

By ruslany

Compositor Software Max for Live devices compatibility with Ableton Live 10

Compositor Software Max for Live devices compatibility with Ableton Live 10

Here is the list of all Compositor Software Max for Live devices and their compatibility status with Ableton Live 10.0.1 b7.

By ruslany

STL1212 Multithread Computer

STL1212 Multithread Computer

Introduction

STL1212 Multithread Computer is a program product, which is classified as a virtual machine. It doubles your system resources capacity in real-time. Integrating primitive to derived function, it provides you with robust system presence in all life situations.

Stochastic estimation

As from version 8.0 of Compositor kernel, the stochastic estimation is stopped artificially, this way reaching the purpose of machine learning experiment. The median value for the processor speed estimated at 4.45 GHz, making whole virtual machine worth of $10000 iMac Pro, 10 core system with Xeon processors. Having such guest virtual machine on your desktop, you are enabling virtual cloud resources, which are utilized for main operation system work.

Resources utilization

STL1212 multithread computer enables to load up to 8 z modules in a patcher. It is possible by utilizing 8 real-time uncrossed loops. Besides of 8 real-time uncrossed loops, STL1212 consists of 8 signal-rate, 8 transmission-rate Compositor cores, totaling 24 cores for true multithread performance. One Compositor core equals the complete Compositor Max for Live instrument or 8 RT-z128 OS, if signal-rate and transmission-rate layers taken in account.

Resources utilization in Hypervisor v7

Because of STL1212 computer usage, which has a true multitasking and uncrosses 8 real-time loops, Compositor virtual machine resources utilized. Hypervisor v7 consists of RTC4k, RTC8k, RT-z8, RT-z16, RT-z32 virtual machines. They are working in the STL1212 process time, which has 24 counting cores for three layers.

Resources control

STL1212 achieves dynamic control over resources on the installed machine. That is why you will never run out of resources, even if your machine is under full load. The end of 2017 showed an ability to make network flushes, using RT-z128 anonymous shutter engine. Now STL1212 achieves such shuttering in a multi-core environment. From one side, it helps to flush more anonymously further and from the other side, to employ active cores for computational tasks, while other cores flushing.

Loading time

Full version loading time is 4 hours. It reaches the comparable system for 3 hours 40 minutes apart of 20 minutes compilation time. All comparable systems displayed as dots on the STL1212 display.