Compositor SoftwareCompositor Software

Archive : December 2017

By ruslany

Compositor Software: Happy New Year!

Compositor Software: Happy New Year!

The 2017 was a very busy and productive year for Compositor Software. Three versions of software were released this year. They all cover the aim of autonomous stochastic performance and artificial listening.

Top 3 key achievements of 2017:

  1. Compositor v5 Hypervisor released
  2. Compositor v4 released
  3. Compositor v3 Hypervisor released

Top plans for 2018:

  1. Compositor v6 Mini-rack
  2. Compositor v7 Hypervisor
  3. Compositor STL1212 Multithread Computer module
  4. Compositor WS Extended

Winter Sale is under way, where you can buy among all:

  1. Compositor Pro 2
  2. Compositor 3 Feeders
  3. Compositor 3 Hypervisor
  4. Compositor 4
  5. Compositor 4 Max for Live
  6. Compositor 4 Extension 1

We wish you Happy New Year 2018!

By ruslany

Compositor Software Winter Sale

Compositor Software Winter Sale

Huge sale comes on Winter Holidays of 2017/2018 at Compositor Software Web Shop! Now you can buy the exclusive algorithmic composition software for reduced price. Almost every version of the software goes with big discount, including the bundled versions.

Here is the list of all products, which are on sale now:

Discount Price
Compositor Pro 2 30% € 74,42
Compositor 4 65% € 102,90
Compositor 4 Max for Live 20% € 36,00
Compositor 4 Extension 1 70% € 77,70
Compositor 3 Feeders 30% € 112,00
Compositor 3 Hypervisor 30% € 180,03

 

The sale lasts from 24.12.2017 14:00 GMT to 03.01.2018 20:00 GMT

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

Playing Flanker 2.0 with Compositor 5.0

Playing Flanker 2.0 with Compositor 5.0

Playing Flanker 2.0 with Compositor 5.0 is rather interesting experience. Being a seasoned keyboard player of Flanker 2.0 back in 2000’s, I use the Compositor 5.0 artificial intelligence to return to the skill of playing this simulator after 17 years breakdown. The first impression about Compositor 5.0 is that the system always stays online, and no external radio sources present in the Ether as stated in my goals. Compositor 5.0 always informs you about the right or false behavior in navigating the Su-27 plane by changing the Ether tuning or creating an emptiness in the Ether translation to bring attention to current maneuver. Rendering the 3D graphics with textures and vector animations result in slower system flushes, than watching video with separate audio tracks, making a headroom for further improvements in expense of more cpu and memory usage.

Compositor 5.0 preview. Auxiliary channel setup: carriers tuning, working with feeders, listening to radio ether.

There are many situations in game plan, when the intruder or foe tries to attack your plane. At these moments Compositor 5.0 RT-z128 OS module reacts and makes the threshold even lower because of a feedback loop compression mechanism implied by a shutter system. This is evident by pauses in Ether translation and rapid tuning changes. Together with hearable timecode, it constitutes the real-time simulation for the game process or any other current task you are involved in. The timecode can’t be demodulated due to synthesizer leakage breakthrough fix applied with shutter. It brings me to the idea that big planes in a simulator could be controlled with Compositor 5.0 AI as well as smaller ones like Su-27 in Flanker 2.0. It is evident that the solution under the War Ships (WS) work group settled the important update for all Compositor users. As I test Compositor 5.0, I become more confident that buffer capacity is enough to play even modern games, but can result in more flushing time after the game session ends.

By ruslany

Compositor WS kernel eight channel synchronization experiment

Compositor WS kernel eight channel synchronization experiment

The main idea in multithread kernel is to create a truly independent calculation for several streams apart of kernel protection functions. The experiment with 8 decks was conducted and different types of material submitted to Compositor WS kernel. At first, loops were introduced in one-threaded operation and the shutter issue raised. Second, the multi-thread operation was aimed by submitting complete tracks into the kernel, directly injecting them. The experiment evidently shows the need to synchronize the material, because 8 real-time generators are independent. Under these conditions, no threat was qualified to the kernel, which means it could be used for multithread operations such as DJ software for music mixing.

Here is a video I shot after this experiment and it showcases Compositor 5.0 assistment in Flanker 2.0 manual landing with keyboard.

By ruslany

Direct generic injection experiment with Compositor WS kernel 7.6.7

Direct generic injection experiment with Compositor WS kernel 7.6.7

Under pressure of generic injection Compositor WS kernel 7.6.7 system doesn’t show signs of life. When you are passing its own channel back into the Compositor WS channel, oversaturation is emerging. On the middle values of oversaturation there is a proximity effect. Switching to sigma 200 translation regime and increasing the transmitter power to 0.2, the channel saturation is imitated. This way the direct generic injection effect is achieved. Shutter also stands here hard with ideal integration time of 300 ms. It catches the feedback and delivers the loop fast, flushing it. This way there is no effect of generic injection after several seconds of applying it, and the system returns back to ordinary state.

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.