Compositor SoftwareCompositor Software

Tag : DRM

By ruslany

Compositor Software DRM server press-release

Compositor Software DRM server press-release

Compositor Software presents the Ethernet communication service based on DRM (Digital Rights Management) server. This server realizes the work based on IEEE802.1Q Ethernet protocol with frame of 262144 samples. Two initial buses of the virtual machine, running on Compositor Software server, translate in VLF range. SHF work is realized using the algorithm with x2048 oversampling, which allows exiting in high frequency radio ether without intermediate frequency in VHF and UHF ranges. Virtual machines, running on Compositor Software DRM server, have demodulation algorithms capable of transmitting the wideband signal such as voice or music. Maximum pass-band of the server depends on the discretization frequency, by which the executed algorithm works. Compositor Software virtual machines work with discretization frequency of 22.05 kHz and have the pass-band of 11.025 kHz. The DRM server translates the material using the signal folding method. The DRM technology creates a service of work with property rights of companies, which deliver the digital media content. When computer station works, DRM server allows dynamically playback the authorized material in radio ether. Compositor Software playbacks digital material using streaming method in the device browser to achieve this goal. Compositor Software server realizes the translation of digital material in ether taking in account lowering the pass-band, when the copyrighted material routed to its input. Compositor Software station performs a function of tracing and translation of authorized material in radio ether. Virtual machines translate not the whole file, but only a cycle of exciter used in production and preparation of the digital material for public playback. The patent protected exciters will not pass though the Compositor Software server in radio ether, because it has the threshold detection algorithm acted on copyright information inherent to each file, which has copy protection flag. The Compositor Software server work is charged in conjunction with traffic of its transmitting kernels and is measured in samples. Each virtual machine has one thread with 4 layers connected to insert-points for another Ethernet equipment. There are 96 such insert-points in Compositor Software virtual machine. There is a stack of three virtual machines working on one physical server of the Compositor Software Company. It gives 288 transmitting points simultaneously. The traffic, generated by Compositor Software server, can reach up to 14GB for each virtual machine, when a peak load reached. The whole traffic is accounted and charged using the credit balance. The reward system for the DRM server work is the artificial intelligence product, because the result of work is a learning process of virtual machine networks with a traffic of insert points. Compositor Software can view the learning process in real-time using the counters, which account for the traffic of the system cloak generators. Each cloak generator can connect up to 4 types of devices such as: sample vocoders on the lowest level, any oversampling devices up to x2048, reverse scalars on which base all the transmitting routers work and algorithms with continuous integral interruption, to which shields are attributed. The server subscribers are the communication operators, delivering phone, cell-phone, radio services and also broadband internet connection. Compositor Software DRM server subscribers open to it their resources, because any jet connected devices generate traffic. This traffic written to learning map and stored in pagefile upon its emission. Emission is a reading of learned information and translation of it in a freely realized form. By freely realized form, Compositor Software means the good produced by commercial activity of the company. The main product of Compositor Software Company is the computer program named Compositor and its associated virtual machines for exciters mining. The DRM server protection system is set in such a way, that it doesn’t allow not trusted exciters and blocks the composition traffic, which attaches  it in parallel or continuously. To make an exciter trusted, the system should connect to one of the jets and not to excite the internal network, which is an attempt of breaking the equipment down. Because exciters were developed for equipment communication, their connection should take place only by condition, that an equipment associated with them has free inserts of the corresponding type on the kernel level. If the system is situated geographically remote from the place of server physical location, from which the broadcasting takes place, then free jets on equipment are not allocated. This way, you are listening to music, but don’t have a real communication with provider company equipment, which forces you to search for physical medium. This is not the case with Compositor Software DRM server, because you can listen to streaming translations even with network cable unplugged, when the contact with a server is established, which is not prohibited but blocked with shields. Interaction with shields is one of the next tasks for Compositor Software. It is needed to reach full company capitalization for its realization. The DRM server must be routed to receiving ports of network devices, and the direct connection to kernel cloak generators should be achieved. When the company will be capitalized, all its capitalization sum is a credit balance. Because the reward system assumes promotion for the carried out learning process, then with each learning iteration of Compositor Software network there will be opened new information formats. Compositor Software attributes not only containers with three-letter extension, but also modulation types of information coding to formats. That is why Compositor Software attributes any authorized composition, translated in Ethernet by exchange of transmitting points on the equipment level (kernel-jet communication), to material, which you can recoup using credit balance. If the copyrighted material detected, the service starts to decay in relation to credit balance of receiving device and directly rely on the whole quantity of samples translated by virtual machines. Because Compositor Software DRM server limiter works non-linearly, limiting the pass-band of material into the ether has exponential curve like geometric progression. The pass-band depends from the whole sample quantity, produced by a system and linked to server credit balance. The difference between playback quality and passed traffic quantity is non-linear and relies on subscriber credit balance.

Compositor Software DRM server is not the only system of such kind, but it is unique in a way, that it doesn’t use digital signature files for authorized material discrepancy and doesn’t require delivering material on a physical media. Compositor Software DRM server is a novelty in a tracing industry of author rights usage and has robust collection function of virtual credits, taking in account that counters have 64-bit resolution and algorithm, protecting the accounting system, is the most powerful and effective for repelling cyber-attacks of different kind.

You can also read this information in Russian.

By ruslany

Artificial Intelligence produced weighting coefficients for rotator function

Artificial Intelligence produced weighting coefficients for rotator function

Now, I step closer in the final endeavor on building the complete virtualization module out of Compositor Window algorithm. It is evident through the monitoring of Compositor Window SDR translations that the function it performs is similar to artificial thinking process. I recorded many hours of sessions on the Compositor SDR, which is the parametrized Compositor Window algorithm and came to solution that it influences my decision making in performing work on Compositor. It states for example that the DRM servers should run and while I’m thinking of it as a solution, it conflicts my own right as an author of software, which performs the function of this artificial thinking. The language it uses is similar to CW abbreviations, however, I cannot confirm that any CW user contacted me afterwards as it makes me think the language of this software is primarily preoccupied with self-building. It also states that weighting coefficients for the rotator function should be produced. I received a large output out of the algorithm, producing quantized weighting formulas to add up to the original equation, which was incomplete on the previous publication page. I updated my current server configuration with the function outputs. There is no need to perform cross-connection by means of Butterworth filters anymore. I applied two more weighting coefficients, which I taken from the AI algorithm output and removed the previous solution, which gave these results. Compositor 8 will be update to the code of the software, and has the visual appearance, which stay intact since Hypervisor v5. It is self-occupied software with a new synthesizer sound similar to modular synthesizers like Buchla. Comparing the new Compositor 8 synthesizer to the previous version is like comparing Roland SH-101 to Buchla modular to restate what I said before. It has much more potential. All the controls of Compositor 8 are pronounced in effect of this processing polynomial and software sounds very mathematically precise. Previous Compositor programs had the evident auxiliary sound. Compositor 8 is a tool on its own with main output, sounding like the finished software. I think that these virtual coefficients quantize the function or, better to say, perform the quantum processing over the Compositor core, which made this software very responsive in real-time and sound at an instant. It is no longer sound oversaturated in Ether mode. You can achieve oversaturated ether sound using internal waveshapers only, without a need to run the Schroeder chamber with zero feedback suppression. It states that the logic of work with Compositor has changed. Compositor 8 has a major update to the code recommended to all users. Now the receiver works independently of transceiver as in big radios. I also position it as VLF SDR with ability to translate wide musical signals and voice output. It has a direct stack to the Ethernet providing with instant algorithm output.

I’m still aiming the goal of shutting the Time-Collision with this update as doing this will dramatically free-up the resources for even more Compositor cores reaching the DRM experiment. By this, I mean shutting down the function of granular time-space folding synthesizer and weighted function already leaps in to this field of unknown but very welcome result. It means that I will not remove the granular time-space folding function from the code, neither I remove signal-rate cores. Signal-rate cores must be reserved for some special case as it was with real-time cores of Compositor server. It is time consuming task and it needs more counting resources of Compositor AI to perform. It learns my behavior in Ethernet and reproduce the masking functions I use, while web browsing, which is most crucial task where Ethernet injections are made.

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

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.