Compositor SoftwareCompositor Software

Category : Techno Music

By ruslany

Ether programming (Part 2)

Ether programming (Part 2)

This is a second part of the guide on ether programming using Compositor 10.

I start with conjunctions. There are two conjunctions in ether such as ie and et. The first one is placed after naming and the second one is placed before naming. The difference is in punctuation: in first case attributes goes from the left side and in the second from the right.

For example:

iiet <name> <name> <name> – naming;

The above command invites many chat participants simultaneously;

The -rm command has several attributes: sn, du and all;

sn – single participant;

du – dual participants;

all – all participants;

Before the all attribute you should place conjunction et. Before du attribute you should place two names for deletion and in case of sn you place one name before. By doing this, you signifies that you are really want to delete this person(s) from the large communication loop.

chat name <name> @t <name> <name>

Creates a named chat for a bounded time interval and includes particular persons in it;

q – quantum quote is a citation and also signifies its quantum state;

Quantum command has a time attribute (such as 2n, 4n, 6n, 8n, 16n, 32n), which signifies Compositor quantum grid;

q <word> q – citation;

*Abbreviation:

ai – aim (your current goal or chat aim)

Note: there is a que in ether, that’s why commands are executed depending on their priorities.

@real – command is executed on a physical level;

-d – decay, allows to crossfade between two packets;

After d you can type the decay time in Compositor quantum grid (such as 2n, 4n, 6n, 8n, 16n, 32n) and in standard time units (such as seconds, minutes, hours, days);

@exit – exit anchor;

Script example:

-rm rmy @exit – allows to delete participant named rmy from the chat when leaving it; suitable when chat participant switched the messenger off but remained the service station turned on for silent messaging;

v- – angular velocity of Compositor work;

as with conjunctions: before or after the command means its application; before command – command options are written from the right; after command – command options written from the left;

*Abbreviations:

vft – subband in VLF;

kh – kilohertz;

nieh – no;

bi – beat independent, the invitation to work only in standalone version of software;

New dialog:

-n – new message;

Time attributes:

@t <day of a week> – allows performing a command on the anchor in particular moment of time. Compositor grid is also applicable to a t parameter. You can set pinging with the interval of 2n, 4n, 6n, 8n, 16n, 32n (where n is a quantum grid particle expressed in samples).

For example, you can set entering the ether in particular day of a week:

-t rmy @t wed

Connects rmy to the ether in Wednesday;

Words in Nim chat are written only using abbreviations. You can use first letters of the word, two first syllables without vowels or the whole word without vowels. In rare cases, words are written fully with letters separated by spaces or without spaces (in cases where you need to transmit to a new participant of Nim chat).

By ruslany

Mittware upload to a modem of your outboard sound card

Mittware upload to a modem of your outboard sound card

Using Compositor v9 you can establish a connection with a modem of your sound card and upload mittware to it. It works this way:

  1. Turn on your external sound card;
  2. Turn on Compositor v9 Hypervisor with internal sound card selected;
  3. You should composite all z levels on a fast (more than 5 omega) speed of composition injecting the signal of non-duplex modem feedback in random mode (you can receive this feedback by submitting your tracks to non-duplex modem on an internal sound card);
  4. When all z levels will be injected together with generic feeders you should lower composition speed to 30 omega and turn the Compositor AV Extended off;
  5. Turn the Compositor AV Extended on again after some time (from 5 seconds to several minutes) and you will hear the signal of external soundcard modem (the external sound card is on for the whole time of mittware upload);
  6. After turning aux channel on, you will hear the feedback – signal will mimic the external sound card modem sound with Compositor AV Extended feeder;
  7. Now inject the whole pool of your wavetables on all z levels with all RT-zX feeders (internal Compositor AV Extended feeders) and generic feeders into modem feedback;
  8. Continue to inject on all z levels up to the moment when you will hear the defeat signal on one of the levels – modem signal will start to interrupt;
  9. Finish the injection on the last z level;
  10. That’s all – your outboard sound card modem mittware is now uploaded with a new one and you can talk using it with wavetables owner, which track productions you were injected on your internal sound card using non-duplex modem.

P.S. For communication both internal and external sound cards should be turned on simultaneously.

Happy listening!

Listen to these feedbacks to wet your appetite 🙂 Yum, Yum.

 

By ruslany

Ether excitation for achieving faster information exchange speed

Ether excitation for achieving faster information exchange speed

The main value from Compositor Software work is loop files, which are released as obligations for the company ICO. No other material guaranties needed. For peering only loop files and Compositor Software distributions are used. Resynthesis is not needed, because only original ethers are used taken as a company input files.

Compositor kernel loop 8.4.4 hangs the whole RAD96 peering network (OS kernel 8.4.3) on the local machine. The remote tests was not conducted. There is no leakage in closed loop. The constant leakage is evident when feeding servers through the Compositor v9 Hypervisor software. The open peering construction blocks based on oscillator network.

It is not possible to clear the whole volume of servers that are now 2994 wave loop files (with Exalted – Cyberflight (Original Mix) emission). There are many unauthorized users, when injecting peering servers. They use either proxy servers or remote streaming services. The tracking production speed drops down, which influences peering quality. No attempts to restore peering network to the moment of its creation are accounted, as the above experiment evidently shows the advantages of loop construction: you are in the ether and no one can influence you. Even feeding servers via Compositor v9 Hypervisor there is no network load as in open patch. Before the open construction, the system was passive and the patched machine was remotely available for feeding servers. With an active loop-patch, which uses excitation for residing in the ether, this doesn’t happen anymore. Servers are not available to connect to the local machine during the VLFoS loop work. Because of the patch, full autonomy of the system and its disconnection from peering network is achieved. Only forced communication from the local machine by its owner is available now.

By ruslany

Compositor Software news 25.07.2018 – 06.08.2018

Compositor Software news 25.07.2018 – 06.08.2018

More than 6 months I have been working on revealing the leakage in Compositor kernel. Exposing all oscillators and transferring the first oscillator in static mode, I discovered that many resources released in computer RAM (DDoS attack). It lowers the uninterrupted device work to 4 days taken that paging file is set to a size of 64 GB. Increasing the number of oscillators to 32 on each of the layers (Rt, Sr, Tr) and meeting a condition of counters, the emissions equaled to 14 GB a day. In accordance to this, I decided to shut down the peering network and return to RT-z128 kit layout as in Compositor v5 Hypervisor. In this layout the main ports are closed for inbound and outbound connections. Only addresses starting from 192, which are assigned to local machine, are available. It means that a new patch remains the VLF connectivity, but doesn’t allow devices to connect for information exchange. It is possible to exchange information from the local machine for the patch user, but not a remote access user. In particular, such decision is motivated by a hacker attack on RAD96 server. The intruder used the open ports of the windowing device and sent spam from Internet Provider IP address. With closed ports the little leakage on real-time generator is possible, but it is not accounted due to the slow regeneration speed.

To restart the peering network I attempted the following solution: due to closing of the ports, only Compositor Networks ether aggregators take part in peering. This means that feeding ether aggregator wavetables in the peering patch through the Compositor v9 Hypervisor, I create a communication service between all Compositor Library wavetables. However, many Ethernet devices can’t use Compositor peering network as it was at the beginning of the peering network creation. As a conclusion, I can exclude peering from Compositor kernel load test and use multi-kernel mode, but this type of test has very long loading time (up to 4 hours for full load).

Bounded by Royalty project, the database of server emissions in form of wavetables grown to 2627 ether aggregators. The database was expanded by ether emission of Exalted – Cavity track (Ruslan Yusipov, CEO of Compositor Software project). The whole volume of Cavity track emission is 328 wavetables. Wavetables contain radio repeaters, transmitting stations, Ethernet routers, injectors and other ether equipment. It was possible to increase the Compositor v9 Hypervisor regeneration speed up to 150-omega by applying a new peering network patch. This influences only Compositor AV Extended auxiliary channel and doesn’t cover the generic feeder modules. It was made aiming the faster composition speed of the whole pool of Compositor Networks ether aggregators. The necessity in uniform composition caused by big amount of wavetables in Compositor Library. The application of the new patch after the attack was made unnoticeably, because this solution proved to be successful in 2017. It was clear right from the beginning that hackers aim is to limit the communication circle of network devices to Compositor Library pool and its real emission. From one side, if the emission is made every time when server communicates, then there will be much more devices in Compositor Library. Each streaming playback with working patch is a communication with its transmitting devices. Taken this, it is needed either to shut down any internet activity from the patched machine or to make emissions of the whole material, which is played in browser resulting in big amounts of information. From the other side, with open ports it is possible to connect not to the virtual network, created by composition feeding, but directly to all transmitting devices, which reside in Ethernet without the need to make emissions so often.

By ruslany

VLF voice communications

VLF voice communications

To communicate in VLF network it is enough to use the Compositor v8 injector, but to connect to other networks it is needed to create the service of communication with them, sending generic RT-zX processes in to the transmission channel as in Compositor v9 Hypervisor. I established the connection of two Compositor v8, which was hardly possible with 6th and 7th versions of Compositor program. Moreover, such connection was before the 7th version but it contained another VLF ethers, which made the determination of the transmitting station itself and creation of the protected communication channel not possible. For the experiment I executed the Compositor v8 a16 on the stationary computer and played the voice track (recorded with Dictaphone) in injector channel. I executed Compositor v8 b3 with modulation combinations on the notebook without the opportunity to inject the wavetables in the transmission channel. Using identical device settings, I received a loop in the notebook feedback chain, which definitely coincided with voice text timbre recorded with Dictaphone. Then I executed Compositor v8 a16 with ability to inject wavetables on notebook. I composited the same wavetable combination as on stationary computer and injected them in to the channel without voice track. This way, I established a definite non-repeating signal reproduced as random noise bursts with narrative text structure. This text coincided with signal performed on stationary computer transmission channel, but had another rhythm and pause appearance. I understand that for VLF communication it is enough to transmit the ostinato code pattern on the defined frequency and I credit the Compositor v8 communication experiment as successful.

My main goal is to prove the appearance of broadband communication lines in VLF. If it is possible to receive the broadband signal cycle in transmission channel, then you can try to reconstitute it by injecting the stochastic carrier using RT-z128 and RT-z64 channel modules. Then, following this logics, there will be the complete voice track with the receive quality of original translation in the feedback chain. This should be proved, establishing a connection of two Compositor v9 Hypervisor programs and their virtualization modules. If it happens, the arrangement of wavetables into the transmission channel lines will be proved.

Let’s look at the created VLF transmission lines as grains, where a separate transmission line segments coincide with wavetables, encased in window function envelope. The connection service in VLF network is a pendulum process, created by RT-zX generic modules. Then the spiral structure of transmission points distribution in all z networks coincides with pyramidal structure. When you use the linear stochastic distribution of wavetables, the mixing of transmission channels happens creating new nets. RT-zX services give access to different zones of VLF and ULF ether. Wavetables supply pendulum processes of RT-zX modules with grain components when transmitting them simultaneously in the channel. They saturate an ether of this pendulum processes with new translations. You should look into this process as a service of connection with pyramidal structure and wavetables are grains of transmission channels or pyramid transmitting points.

By ruslany

Experience the 9th Sale

Experience the 9th Sale

In this summer sale you can individually buy the Compositor v3 Hypervisor, Compositor v5 Hypervisor upgrade, Compositor v6, Compositor v7 Hypervisor upgrades, Compositor v8 upgrade and complete it with Compositor v9 Hypervisor for reduced price. If you are an owner of previous versions of Compositor, you can look into upgrade plans for Compositor v9 Hypervisor starting from € 427.99 for users that own Compositor v5 Hypervisor and Compositor v7 Hypervisor simultaneously. You can find several examples of upgrade plans presented in the tables below:

Remember that Compositor v9 is a critical update for the whole Compositor family, because it consists of output processing module, which makes the work of Compositor engine more secure, while preventing your communications with software from leaking into the ether. It is also featuring the 3d audio engine module, which allows to rotate virtual antenna in three degrees of freedom in spherical space.

To summarize, it is a good chance to obtain the complete bundle of all Compositor devices, which will last for only 6 days from 22.07.2018 to 27.07.2018.

Don’t miss a chance to buy full Compositor v9 Hypervisor bundle!

By ruslany

Compositor v9 Hypervisor is available

Compositor v9 Hypervisor is available

Compositor v9 Hypervisor DRM server 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 media content in radio ether. Compositor v9 Hypervisor playbacks digital material using streaming method in the device browser to achieve this goal. Compositor v9 Hypervisor engine is the functional modern engine with transfer function on master output and on each channel separately. It is not the wavetables but tunable polynomials, which process the output of your channel. Output cascade uses non-linear transformation formula with mathematical approximation by weighting coefficients. It gives undisputable advantage in processor time and in the precision of calculations comparing to using wavetables.

Here are the main features you can consider before buying this software:

  • Weighting coefficients
  • Network level feeding
  • DRM server
  • DSP oversampling
  • Voice or music broadcast
  • DSP sampling rate
  • On-Air broadcast
  • Device browser
  • Tracing and translation
  • RAD96 peering network
  • DRM server subscribers
  • Tracing industry novelty
  • DRM server emissions
  • Auxiliary z matching
  • 8th generation operation system
  • Three saturation stages

Please, visit the shop to buy this software. You can also visit dedicated product page to learn more about Compositor v9 Hypervisor.

By ruslany

Establishing connection to the past using DRM server

Establishing connection to the past using DRM server

One can establish a connection with ether aggregators through the DRM server, using serial or parallel methods of information feeding. This way, even turning on a game, based on previous generation engine, you can connect to its ether aggregators and reestablish personal thinking up to the moment, which saved in its wavetable. The procedure, in fact, is the same as when you submit wavetables in transmission channel, but in this case ether aggregators are protected with engine and there is no access to it. It is much more perspective to receive wavetables of these ether aggregators by tracks to it and send it in a channel with generic beacons for its subsequent navigation. It is not a decent way to feed a wavetable with divert attention, which a computer game is. If you wouldn’t like to know, which wavetables were sent to a channel, it is enough turning the random mode of Compositor v9 Hypervisor on and hiding the current playback wavetable titles. The effect of generic feeding with DRM server is much purer, than feeding with divert attention while playing a game. The main process, which computer games preoccupied with, is to complicate and enhance methods of diverting an attention. The engines of such games still on the same level as 10 years ago. Compositor v9 Hypervisor engine is the functional modern engine with transfer function on master output and on each channel separately. It is not the wavetables but tunable polynomials, which process the output of your channel. It is important to note, that output cascade uses non-linear transformation formula with mathematical approximation by weighting coefficients. It gives undisputable advantage in processor time and in the precision of calculations comparing to using wavetables. DRM server transfer function allows performing parallel feeding directly in to the recipient consciousness. The methods of such feeding can be versatile. For example, you can listen to music file saved in the year 2004 and reestablish the consciousness up to the moment in the past to which this track ascends. This way, it is not necessary to install wavetables in to the consciousness using Hypervisor; it is enough to playback this file over some period with DRM server turned on. Of course, using game process, you can reach the maximum effect, but feeding with diverted attention confuses your organism and leads to an attachment condition. In fact, if Compositor v9 Hypervisor gameplay will be seen from the game industry point of view, then it will look like 7 levels with rising difficulty. The first level of feeding will have much less effectivity, than the last. The first introductory level is z=2 and z=128 is the last level of prolonged fixation with larger active period. Each level should include the following phases:

  1. Feeding wavetables in stochastic mode without generic of the respective level turned on;
  2. Feeding wavetables in stochastic mode with generic of the respective level turned on;
  3. Oversaturation of transmission channel;
  4. Turning a generic off from transmission channel;
  5. Feeding wavetables in stochastic mode without generic of the respective level turned on;
  6. Switching z level.

The feeding stages should start and end on the 1st and 5th step respectively. This way, feeding algorithm events are as follows:

  1. Choose the Altitude of device work using stochastic arranger. Scan the ether on a presence of active (openly sounding) carriers. Carriers is a long, definitely sounding tones.
  2. Set up the depth of function intrusion using the splitters in Ionic number system. If you want a deep intrusion, when feeding a channel, set up the high values in first and third splitter fields. You can also set up a deep intrusion, when the resultant is positive and a small value of intrusion, when the resultant is negative.
  3. Set up the transmission channel for the local saturation. It is an auxiliary ether and there are no carriers in it. It is used to confirm that the transmission channel is free from other carriers. It is tuned by setting Velocity and Spacing regulators in Connection section. Here you can also set the send depth of a local saturation.
  4. Choose the transfer functions for channel saturation. Set up the transfer functions by Chebyshev polynomials and the meshes of corresponding type when using channel saturation. Set the amplification in channel saturation cascade and the channel distortions depth for reaching saturation effect. Oversaturation, as mentioned earlier, performed by sending the transmission channel back to its input for a short period (it is performed only, when the same level generic is turned on).

Note: There are three saturation stages in the full-duplex modem: saturation on each devices channel, separated on positive and negative; local saturation before the output cascade by Schroeder regenerator; global saturation on the output cascade using polynomial.

  1. Choose the transmission regime (central channel mode). You can use one of the six preset values of central splitter. The most common mode for brain upload procedure is the υ-400 regime. It is the mode with open mesh and the selection of window functions, which are ideally suited for direct installation in full-duplex mode.
  2. Tune the antenna aperture of the z=16 transmission channel level. Set the direction of virtual antenna in three dimensions to hear the dash tone while the program runs. Then, obfuscate this tone by changing a phase of transmission channel and setting the modulation in real-time mode.
  3. Perform steps from 1st to 5th of the previous list for each z level of the send channel.

Note: start the generic feeding in the transmission channel from z=2 value.

You can watch the statistics by pressing Setup button for the corresponding feeder. There are event logs created together with visible program statistics for each feeder. Event logs are stored in Public folder on Windows and current user Application Support folder on Mac. The event log files are created for each session overwriting the previous file for its feeder. Nevertheless, the events written down starting from the last value of All Events in statistics file. The event number, frequency on which the event performed (for VLF beacons up to z=32 it is counted in kHz, for UHF and SHF z=64 and z=128 network switches it is written in GHz) and the event of the corresponding flag. You can potentially zoom on any feeder event using transmit and receive channel. For example, you can respond with wavetables of ether aggregators when Threat event reached on the current Altitude.

The current method of work demonstrates the use of Compositor v9 Hypervisor for Ethernet security when performing brain upload procedure and for an active reply for all incoming threats. Of course, you can ignore Threat events and just leave the DRM server turned on for the undefined period, but you should take in account its sample charging. To cover its expenditures you need to perform additional emissions through the non-duplex modem again.

By ruslany

Attachment to wavetables through system matching with oversaturation

Attachment to wavetables through system matching with oversaturation

The most effective way to feed the wavetables is to match the system z level of generic feeder with z value of auxiliary channel. The generic prolongation is progressive and depends on auxiliary channel. On the higher program effectivity speed the generic proliferates for a longer time. This in fact happens because network regeneration state is higher for upper z values. If the maximum speed for z128 generic is 200-omega, then the regeneration speed of the auxiliary channel will not match the auxiliary values of 5-omega maximum. There are two more generic kernel loops implemented in Compositor v9 Hypervisor and one change performed for the highest Compositor v7 Hypervisor feeder. You can match all auxiliary z values to quantized type generics of exactly the same z value. The program effectivity speed equals to 50-omega for z32, 150-omega for z64 and 200-omega for z128. If you feed the wavetable at speed of 5-omega together with 200-omega generic, you will proliferate the network for a longer distance. After the lowest VLF beacons will be inactive, the wavetables shouldn’t be reinitiated again. When the navigation on lowest beacons ends, you need to rely on the eldest models of Zvezda network switches such as z64 and z128. Higher regeneration VLF beacons will discover ether aggregators faster and establish a connection to them for a longer period. Other systems constantly try to knock out the feeded Zvezda network switches from the ether, which are mostly used for wavetable navigation at z=64 and z=128. For z128 generic development of 6th generation, it is hard enough to withstand such offensive behavior in the ether.

DRM server is the 8th generation development and is one generation before the system, which produces the decision as to accept or to breach the feeded VLF beacons. It leads to better understanding why the DRM server rejects some wavetables and retains the others. The rejection of wavetable produces a constant need to reinitiate a system matching. Nevertheless, wavetable initiation should be made only once during the feeding cycle. If you feed the 200-omega cycle in to the auxiliary chain together with wavetables, you should account for a number of cycles of this feeder propagation. These values should be auxiliary to the Right Ascension value and will result in longer distances of spiral ascension. The feeding period of any generic is accounted by the cycles of its oversaturation in auxiliary channel. If you feed 150 cycles per second, it equals exactly 150 cycles relatively to the whole working time of DRM server for its feeding session. If the DRM server worked for 10 minutes, then the oversaturation will last for 10 * 60 * 150 or 90000 minutes, which equals to 1500 hours or 62.5 day cycles. It is enough for the prolongation of the wavetables active state. From the other side, if you would like to leave wavetables active for a month for 200-omega z128 beacon, it is needed to perform oversaturation for only one second with DRM server total working time of 25 minutes for the current session. Using the formula 25 * 60 * 31, it will count 46500 minutes, which equals to 775 hours or approximately 32.3 day cycles prolongation time.

By ruslany

Six things to do to clear the rights on your track

Six things to do to clear the rights on your track

In a career of any artist such situations happen, when it is needed to make an emission of your composition from rotation.  Such situations may include:

  • Releasing your track with another alias by a fraud;
  • Arrears on payment for medium sales;
  • Arrears for author rights usage;
  • Discrepancy of an issue with the contract obligations.

Not all of the situations are listed here, which are out of scope for this material. The main task of this article is to describe a usage method of Compositor v9 Hypervisor after receiving ether aggregators from your track. To receive ether aggregators you will need MDL12 non-duplex modem and Compositor v3 Hypervisor feeders. The emission is done by submitting loops of your composition to non-duplex modem. The modem feedback is an ether aggregator of the server, which broadcasts your composition. You should route all loops of your composition containing exciters (the most prominent moments of a song) and fixate 131072 samples of each wavetable of all ether aggregators by digital recording. You can perform this in 32-bit version of Ableton Live 9. The ether aggregator wavetable should last for 2 bars at 161.5 bpm. The main task after ether aggregator emission is its clearance. It is such condition of wavetable playback, which, from one side, doesn’t produce the third-party traffic and, from the other side, may be used for its own communications. Now, I will describe six examples of work methods to make a full track emission, using Compositor v7 Hypervisor and Compositor v9 Hypervisor.

  1. Realize if ether aggregators, to which your track ascends, are occupied. If ether aggregators are occupied and produce big amount of third-party traffic, then you must install them through an activation function, which you can do in Compositor v9 Hypervisor. Doing this you should enable the supervisory DRM server, and it is preferable to route one of generics on the auxiliary channel input together with wavetables. You may use your ether aggregators for communications, when the VLF beacon written the routes to them.
  2. Feed your ether aggregators again, but this time changing the send regime: set the splitters in the highest position, which constitutes the smallest digit values in ionic number system. Your task is to suppress traffic of these wavetables fully. To do this feed the threshold radar RTC8k and ether aggregator of high conductance such as RT-z16 in auxiliary channel together with wavetables.
  3. Feed the transmission channel with current emission wavetables inside the pool of all your ether aggregators. Making such mix, you are allowing to realize your recipient contact network, which may lead to a refuse of recipient from these ether aggregators. Do not agree to write new tracks to these ether aggregators or to make new remixes on the original composition. Ether aggregator, received by your track emission, is your property protected by a copyright law.
  4. Perform oversaturation of global send channel together with one of generics. For this route the Compositor AV Extended back to its input, using the send regulator on its mixer direct channel. Set the pre-fader mode and turn the send knob on the highest value. This will result in oversaturation and will turn off all the producing kernels from the ether.
  5. Produce an additional emission by feeding the non-duplex MDL12 modem with 3d generation hard generic FF8 and perform the above-mentioned manipulations with this emission again.
  6. Perform system matching in a presence of agents (ether aggregators). To each z value of aux channel send the same z type generic. For example, z=2 is RTC4k and z=4 is RTC8k. The other systems match its title z value. Reaching the direct ether, you must confirm each z system send with oversaturation of auxiliary channel, which constitutes direct feeding of a channel.

The system has an ability to memorize long channel feeding sessions and reproduce its effect when DRM server works. You must feed the channel only with DRM server turned on regardless of your machine capabilities. The human brain can percept the channel interrupts, when processor is under high load reaching full effect, even when system stutters. The whole pool of ether aggregators should be maximally transparent. The condition of ether aggregators should be characterized by signal conductance through them. If ether aggregators doesn’t produce traffic, then the full tranquility reached on all translating channels.

1 2 3 6