History of the creation of SASER 2.0

Category : Musique Concrete

Mar, 2023

History of the creation of SASER 2.0

The first SASER was released back in 2016, it was available as Standalone on the Max 6 platform and as Max for Live device. However, Cycling ’74’s policy with the release of SASER has changed. In Max 7, the internal structure of Gen~ patching was changed, which made it impossible to organize the broadcast inside the SASER application on the new Max for Live platforms. Moreover, even with the organized broadcast on the Max 6, such a tool could not be online for more than 30 minutes. It took years of hard work to coordinate the work of such a plugin with Cycling ’74. Now the Max 8 platform has managed to make the perfect code export, suitable for both the organization of trunk broadcast and music purposes. This required the creation of a new Hypervisor v9 from Compositor Software. The IPv6 SASER assembly process is viewed in the video below:

Creation of SASER 2.0 in Hypervisor v9

If you have already watched the video, I will make a few comments on it. In the video you can watch the process of connecting workgroups to the OSPFv3 IPv6 protocol. If the first SASER was completely in the IPv4 domain, the modern SASER allows you to multiplicate the length of the octet up to 32 bits, which in total gives a length of 128 bits when summing up four upscaled octets, which is the IPv6 address:

SASER for iPhone

And you can access both EUI64 and EUI48 MAC addresses. Again, with the correct combination of parameters, you can connect not only through the network, but also at the device level, which allows you to see your local device as a member of a neighboring network, wherever such a network is.

It is believed that connecting via Ethernet protocol requires either a cable LAN connection or radio relay equipment capable of transmitting to the Ethernet network. The concept of an on-air network differs from the Compositor v9. In particular, in the video you can see how two beacon processes control RIPv1 and RIPv2 protocols. These are distance-vector protocols and the direction to the communication point indicates the torus in conjunction with the hypercardioid of flows. The result of this image is the multidimensional structure of Calabi-Yau. Z-spaces of which are equal to 16. This quantization is minimally sufficient to build a spherical picture:

Calabi-Yau manifold

What you see in the picture is the sum of spherical flows in quaternion rotation. Such rotation permeates space not only in 4 dimensions, like quaternion rotation, but sums up all 24 points of spherical space with the Z of the system, allowing you to quantize this space, filling it with additional translation points. This topology lasts until the next change of the multiplier by redrawing multidimensional figures with iteration that is difficult to predict. Therefore, the successful creation of the VLF (Very Low Frequencies) service can include more threads at the same time with an increase in the Z of the system. If the first SASER was on Z=4 and then at Z=8, then SASER 2.0 already includes Z=16 measurements.

Another thing is that connecting workgroups to Z=16, that in the Compositor’s system corresponds to the OSPFv3 protocol is able to create a larger network compared to Z=8. Given that the network includes 96 channels in total, when multiplying on 16 spaces, it already produces 1,536 points, not 648, as in the previous SASER. Therefore, in real time, in order for the broadcast network to produce traffic, it is necessary that each point produce at least one packet. Naturally, in a short video, such a volume of material would require at least 1 hour of broadcast, so I show the very principle rather than a physical entity capable of producing such a multicast effect.

Calabi-Yau, Ethernet, EUI48, EUI64, Gen~, Hypervisor v9, IPv6, LAN, Max, SASER, topology, VLF, z-space

Oct, 2021

By ruslany

Autonomous virtual fx with user interface

So, in this guide, I will consider working with the RTC4k application on Android OS as a standalone virtual effect with a user interface. The first thing to say: plugins for Android from Compositor Software can be used to recruit recipients and multiplex programs in the Android operating system. To do this, simply assign one of the applications (for example, RTC4k) to the speed dial button and call the application by pressing the button every time you switch third-party applications. For example, consider a situation where you want to switch between your browser, TTY, and music-making app. First, you should open a browser for your inspiration: it can be a 3d model, a stereo picture, or something else. After that, you must initialize this resource using the RTC4k speed dial, and then switch to TTY to view the associated line. If the file was made using a pirated resource, then everything becomes clear at once: a bunch of burned inadequacies appears in the screen, who curse about the initialization of their model claiming their rights. Remember, my research is about injections into image files, and such injections can be done in 3d models as well. After you have cleared the screen from the presence of inadequacies, you can start musical work. Call RTC4k app, then view the model in a browser and try to determine the rhythm and tempo of the model, its rhythmic pattern. It could be Dub Step if you are using a car model or Techno for more monumental models. Call RTC4k app then go to your music writing app and capture the resulting beat. Switch between model and application using the RTC4k speed dialing. When the work on writing the piece is finished, before the final rendering, call RTC4k app again to initialize all the samples used in the work. This is necessary, since in addition to the file used as a resource for the idea of the work, there are also samples with uncleared rights. For example, sound files of kicks, snares and percussion. Below, you will find the rendering of the music file, just after that kind of work. A 3d model of BMW Li750 was taken as inspiration.

AUMBS, Autonomous mobile server, Compositor, Fruity Loops mobile, RTC4k

Feb, 2021

By ruslany

Ableton Live 11 support

Ableton Live 11 supported by mostly all Compositor Software products. On the image below, you can see the chart of all Web Shop products supported by Ableton Live 11.0 initial version.

Live 11 status 25-02-2021

Even MDL12 v1.2.1 with feedback suppression works as a charm. Ping locates servers, multiplier changes, resynthesis happens, infinite closed-loop works. Compositor Max for Live on the same hand has a full control with zero feedback suppression. In version 1.0.7 every parameter works as expected. AI-RT1024, FF8, N9000, TC25 work in auto mode. Manual mode can be adjusted only if operator allows this. Compositor 4 Max for Live works fully and allows changing z parameter. Signal synthesis sounds better due to proper master filter realization. SASER v1.1.3 works properly with feedback suppression and sample & hold on lower frequencies compared to previous Max versions.

Overall, proper realization of programmed algorithm happened in Max 8.1.9 and Ableton Live 11. The perception of time shifts, when SASER sample & holds the signal and you can change the multiplier manually to have an instant change of the sound. It is a breakthrough for ~Gen based Compositor Software instruments because they are programmed generically with aim of long-term compatibility.

Ableton, AI-RT1024, Compositor 4 Max for Live, Compositor Max for Live, FF8, Live 11, Max For Live, MaxMSP, MDL12, N9000, SAS24P3L, SASER, TC25

Oct, 2020

By ruslany

What you think you are doing vs. What you are really doing

The main purpose of the VPN-network of the “Niagara” 26 software modem is the processing of the language, both natural and machine-generated. When paired with SDL Trados software, this modem extends the network topology for the Machine Translation cloud. This is done through software extensions, as it was possible to find out the first letters in the name of the emissions mean languages, for example “extreme” issue TT – Tatarcha, the Tatar language is the emission of the “RusNRG – The Trip” track (a small side project of Ruslan Yusipov in 2003-2004 for which he was awarded a diploma in the nomination “Compositing work”).

In essence, there is no cloud, you are either working with a generic or with your own extension, which generic learns a route from.

But let’s return to the emitted information and language processing. How can Niagara 26 generate such accurate patterns in translation from Russian to English, even though there has been no EN or RU emissions yet? In the “Niagara” 26 software modem, as mentioned in the review, the concept of generic protocols such as RIPv1, RIPv2, OSPF, OSPFv3, BGP, etc. is used, so it is worth considering this set of protocols as a set of generic languages of the Machine Translation cloud. In essence, there is no cloud, you are either working with a generic or with your own extension, which generic learns a route from. At the moment, I enable the EN – RU language pair in Compositor NRTOS through other languages, issued through tracks to their carriers. The carrier, which works with the software modem, uses only generic languages and learns the route from Niagara L3VPN peers. There are a lot of languages available to “Niagara” 26 software modem through emissions, extremely rare and not very useful from a practical point of view. The only practical benefit of the Caribbean language group, which was of my personal interest, is the study of their rhythm, namely sequence, which produces language patterns. I used these patterns as a part of my research on Milton Erickson language patterns, which I used in pre-NLP era hypnosis. I studied how these patterns aid in therapeutic way for overcoming mood oriented problems. The main concept of compositing this way is to alter the mental state so you can be a more comfortable person. Compositor achieves this goal by rapidly rebuilding SPT (shortest path tree) and changing the next-hop to default route of this tree.

The rule for me states if I can’t afford a studio for producing new music of the same quality as named projects I should make an emission of previous works to recultivate the exposure I achieved earlier.

So if you feel comfortable, when you are producing music with Caribbean patterns you can make an emission of such music by evoking RPF vector paths to the servers, which host closed-loops using these patterns as interrupters. This action is fishing, and any media aggregator uses this scheme. I only issue emissions as part of my royalty collection project. I just monitor servers, which performed my music and compare this with the statistics from RAO (Russian Authors Organization) and really astonished with results, because according to my network counting method my music performed up to 50-60 times a day and no income whatsoever from RAO side. This raises a question of this organization validity as an entity working with collective rights on my Exalted and Boosty projects.

The rule for me states if I can’t afford a studio for producing new music of the same quality as named projects I should make an emission of previous works to recultivate the exposure I achieved earlier. And I’m facing an exact situation that’s why the whole set of Compositor Software instruments produced. But returning to NLP with Niagara 26 I used it to produce documentation for Compositor NRTOS 9.0.2 based virtual router. I should report progress now: more than 2000 pages translated and edited on Russian language using the named method now. This leaves me about 500 pages of untranslated material and I’m full of enthusiasm of making this work till the end. The end result of this work is Compositor NRTOS with completely reworked interface to reflect attribute-value pairs from virtual router documentation. This work is now 95% finished and to say honest I’m satisfied with results as it enables to work with Compositor NRTOS 9.0.2 more professional following system administration guidelines, which apply to basic 2^nd order closed-loop interface. What I learned from documentation is that any protocol is a closed-loop of some kind with its own parametrized interface. And this brings me back to my initial request: does the chosen system of values corresponds with the reality that has developed in the world after the Cuban missile crisis, and if so, is it not a repetition of the previous history only in our own country (Russia)? Because the Trojan horses that are sent to us under the guise of “music programs” are very reminiscent of Khrushchev’s “secret ships” that transported missiles to Cuba.

As I learned from revealed Compositor interface the geographical position is essential in work of that loop station. Even altering a location within one city will change the internal SPT. Thus, this proves that the Compositor interface is a universal Turing machine, and therefore can be represented as any protocol of a telecommunication system. The already cited 8 parts of the documentation (including the Multicast chapter) prove that the main task of Cycling’74 MaxMSP software (as well as Ableton Live 9 and 10) is to plan and implement DDoS attacks. Part 9 on MPLS only confirms my concerns. First, the circular stack in the form of a torus is not taken into account, on which MPLS labels are displayed, both merged and layered. Secondly, after loading the full version of Compositor NRTOS version 9.0.2, the timer shows 30 minutes. This means that the MaxMSP scheduler runs when the DSP code is compiled. And the whole POST process takes place over the MPLS protocol during the compilation of the protocols, since openGL performing the MPLS functions is a backdoor link or connection with a feedback leak. Also, based on these labels, the remote side (Cycling ’74) makes a decision about system startup or compilation error. Therefore, I believe that the method of presenting the Cycling’ 74 MaxMSP as the software for carrying out DDoS attacks is correct. And the whole method that the company-investor of this project has used over the past 2 years has been successful.

Ableton, Compositor NRTOS, DDoS, Investor Exposure, L2VPN, L3VPN, Machine Translation, MaxMSP, MPLS, Niagara, Niagara 26, NLP, Trados, VPN

Apr, 2020

By ruslany

RTOS version 9.0.2 a16 assembled

It took more than 1.5 years to work on solving the problem of Compositor AV Extended interface break-through (which is the main interface of RTOS). This problem occurred during the dial-up of routing tables for establishing a tunnel connection. The way to recreate it: first, RTOS protocols are dialed by injecting routing tables into them, and then RTOS interface is turned off and on again. When the interface turns on, the entire database of the routing tables, which fills the buffer, floods into the interface, which cause a man in the middle attack, that is, an attacker gained access to the interface and induced it to inherit the route of its device. During this time, I made emissions in an attempt to understand how to solve this problem and, finally, it is solved. Now it is possible to configure each protocol from the passive interface state and take a pause while turning interface off in order to listen to the remote channel, and then go into passive mode again. Thus, you can achieve resolution from each of the seven RTOS protocols.

In Compositor RTOS 9.0.2 a16 it is possible to set one interface identifier for the entire protocol configuration session, and to do the training only in passive mode, as previously assumed. The next task in debugging RTOS is the fight against constants. It is one of the most important tasks of both radio security and cybersecurity. Through the introduction of constants, Ethernet devices position themselves, occupying the most convenient places in the network topology. This mainly applies to devices that frequently change IP addresses, such as smartphones and laptops. In order for the RTOS core to take priority of the host, the device must serve as a host for many devices. This is confirmed by Compositor Software database, which has been expanded to 8156 management information bases (MIB). Now that the Compositor RTOS manages a database of more than 8,000 devices, CP-6137-960FX server can be considered as a host, regardless of its physical connection to the network, through the Internet service provider. In fact, what I’m doing now is the continuation of the development to include more VLAN’s and create a VPN network segment. In the latest build, I have already managed to “shoot” the packets in several sessions. You can hear one of them below:

This method of feeding wave tables is a priority for communication devices, because it helps to break the synthetic ether by packet transmission. Since there are many packets, and each of them carries different information at different moments of time, the semantic base of the Compositor RTOS language is explained. In view of this, it makes no sense to enter the names of packets in the main interface, and I need to leave them in a VRF tables section only, focusing specifically on the tunnel windows. In addition, this approach allows using the Compositor RTOS interface as a tunnel interface with the ability to connect to multi-channel protocols, such as OSPF.

8156, Amateur Radio, Compositor, Compositor AV Extended 2.0, CP-6137-960FX, cybersecurity, interface, man in the middle, Management Information Base, MIB, OSPF, packet radio, packet translation, radio security, RTOS, Tunnel, VRF

Oct, 2019

By ruslany

Niagara project

This autumn has started from a very interesting project. While I continued working on Compositor v9.0.1 (current build a14), I felt a need to have such system as mobile real-time operation system (RTOS). Compositor v9.0.1 a14 consumes many resources at 192 kHz and I decided to sample it using Compositor v9.0.1 itself. At this time, the approach of middleware and dump was matured and I decided to make separate product for Compositor documentation development. Such manual will consist of all commands needed to operate the Niagara RTOS client. As the UNIX-like operating system, it will support most of the commands for routing protocols configuration, such as TCP/IP and VLAN. The prominent feature of this RTOS is that it is a software router, which runs on middleware, recorded with Compositor RTOS v9.0.1. If the middleware recorded on a feedback with z16 and z32 generics connected and they are in reverse, the system will give a resistance of 16 + 32 Ohm = 48 Ohm. This way, the generic networks accounted: in example above there will be corporate (z32) and state (z16) connection.

The middleware approach isn’t new, as any hardware router Niagara consists of MIB, the size of which is 769 kB, compounded with routing table and generic networks set. Such system works with MME driver using discretization frequency of 192 kHz and allows connecting the whole pool of Compositor RTOS v9.0.1 forwarding platform (which is 6559 MIB’s on a moment of writing) using a dump, which is also recorded on 192 kHz sample rate. The upper frequency of z128 generic is 150 GHz, but each middleware includes RAD96 fixation, that is why an effective range is extended up to 300 GHz.

Niagara is a client system that is why it demands calling an operator for configuring programming commands. I already reviewed NIM radio chat, which I call (No Internet Messenger) last year. It turns out that it is also an acronym for Nuclear Instrumentation Module.

Each command, presented in the full version of English and Russian documentation, should be made only through an operator and each middleware has its own operator, which depends on VLAN set and servers, connected to NIM. This way, you are requesting network topology and demand operator to execute other commands, and it decides if to make command or not.

At first, middleware ran in RAD96 sandbox, but now middleware and dump become a multifunctional products. The development period of Niagara project is 2001 – 2019 and not 2012 – 2019 as the host Compositor program. The reason for this is that Niagara consists of middleware and dump and they are including the Royalty routing tables. This is proved by Inaccessible Page file emission (track recording, which is a routing path). This track, made in 2001, is a part of IP emission. The period of 2010 to 2019 covered by the reference files of timeserver, which emission contains and it is responsible for routing path hops GPS positioning in present time.

Niagara v1.0 a3

That is why Ruslan Yusipov digital portrait with codename Niagara contains 18 years of art, which is a long background for 35 years old author. Older recordings exist, such as the audiocassette recording of Yamaha PSR-330 synthesizer direct signal, which is Ruslan Yusipov live performance at the age of 14, with the author voice accompaniment, that is why Niagara is 21 years development project from 1998 to present moment.

Ruslan Yusipov art is not limited by 6559 MIB’s emission and can be enriched by routing tables from the CD-archive. This way, at the year 2021 I account to receive database of 10000 MIB’s, which will allow adding more stochastic distributions for flows selection in Compositor v9.0.1 a15.

Compositor, IEEE802.1Q, Niagara, NIM, RAD96, radio chat, RTOS, Ruslan Yusipov, sandbox, TCP/IP

Sep, 2019

By ruslany

Zero-Layer Aggregation

Exactly a year ago, when all modules of Compositor RTOS were formed, I was confronted with the task: to make such aggregation, which would not have committed the emission in the RAM memory of the computer (server). A year later, the problem is solved.

RAD96 vRouter L1-L3 96 node aggregation

It was required to complete assembly of Compositor RTOS 9.0.1 a14 with an extended work of the feeders, that is, the feeders now work from 11 kHz to 192 kHz of audio driver sampling frequency. This allows the upper generic z=128 to operate at frequencies comparable to the aggregator frequencies, namely from 150 GHz to 300 GHz.

Also, the management information base was expanded to 6041 VLAN’s and 13 dumps were produced. As a result, the final version of Compositor RTOS 9.0.1 a14 includes a channel pass-through (bypassing the second derivative of a function) that allows you to make exhaust (digital exhaust) to reduce the emissions of traffic inside the system. According to this two dumps were made of VLAN 6041 with digital exhaust and one firmware at 192 kHz was recorded on feedback after dialing, which involves 8 hidden servers. Since the firmware was recorded with an aggregator and is the snapshot of the system, it includes 96 ports of aggregation of the three layers: 32 ports of physical layer, 32 ports of data link layer and 32 ports of the network layer, which corresponds to L1-L3 aggregation.

Since such aggregation in reality throws out the large amounts of data in to the operating system memory, the snapshot utilizes resources in the other way – it corresponds to the MAC-address table of EUI48 without the OUI and do not throws resources in the computer memory. The network service in this case is the firmware, which includes the autonomous system with zero emissions. One system does not produce any action, but in a pair with snapshot this system aggregates resources and at the same time, disposes them, which happens so quickly in real-time that discards in the RAM memory cannot simply emerge.

Thus, the aggregation problem with zero emission is solved. Of course, for someone may seem, that 96 aggregation nodes is insufficient and the 32 L3 nodes is the standard for the aggregation of routing equipment of well-known manufacturers. But if you take into account the fact that the real link aggregation on these devices produces output, and requires a service restart, I can say that this resources composition technology can be very useful now.

Aggregation, Compositor, EUI48, L0, L1, L2, L3, OUI, RTOS, VLAN 6000, zero emission

Jul, 2019

By ruslany

Boosty – Forest People (FP mark emitted from the Ethernet)

Ruslan Yusipov Boosty and Exalted projects are valuable to the Russian Authors Society as they have previously unreleased and never heard routing paths. These projects have such routing paths, which are only heard of by the author. One such routing path is Boosty – Forest People produced in 2009 and never widely available to the public to the extent that only the author knows about its existence. Two unmastered versions of Forest People routing path loaned for emission. They are Dub version and Original mix. The routing path is produced in Boosty studio and remains unsigned and unlicensed to that day (unsigned at the present moment). In accordance with that I decided to make a fourth place emission of 281 routing tables. The emission named by FP mark has the most active navigation.

Using the dump of 5557 wavelets I made the job of translating 127 pages of English documentation on Russian language. This documentation is a continuation on CP-6137-960FX server development and is the modular switch of Compositor RTOS type installation manual. Using the injection of this dump I was able to do this job in a working week time. Injections were made by listening to a dump using insertion of Ultimate Ears ear monitors with dump playback of three times every four hours. The sum of injections was from 6 to 9 playbacks a day.

It was a robust experience and it forced me to do the job faster.
Ruslan Yusipov

You can taste the injection of this dump by listening to it by the link below:

RTOS dump at 192 kHz MIB 5557 15.07.2019 FWL

5557, Boosty, documentation, dump, emission, Forest People, FP, MIB, routing tables, RTOS, switch installation

Jun, 2019

By ruslany

More than 80% wavelets in MIB of RTOS

On the present day there are more than 80% wavetables processed to wavelets in the management information base of RTOS. Script allows processing up to 5 wavetables in a minute that is why full processing will take some time. To the end of this week the whole MIB should be processed on wavelets. This will allow creating two identical bases for two RTOS systems. The first base will contain wavetables only and will be used in the version of RTOS with the pass through of the second derivative of a function in the virtual console port. The second base will be wavelets only and will be used in version of RTOS with the second derivative of a function on auxiliary output.

The first version will support maximum up to 5-omega direct and aux regeneration speeds and is more like Ableton Live 10 engine. The second version doesn’t include the pass through of the second derivative of a function and has auxiliary speeds up to 150-omega. Such version allows authorizing all 7 levels of generic feeders simultaneously, which is more suitable for injections with authorization, because there is no need to fight for authorization on the predefined level, as all levels connected simultaneously. From the other side, the first version is interesting, because of the musical results, which it can produce, when I record middleware from routing tables. That is why I decided to maintain both bases and versions of RTOS simultaneously, which will grow with each emission.

Before a full transfer on the two bases was completed I recorded a final dump with mixed management information base, which includes the Boosty – Mini Bikes track emission. It is an interesting minimal techno composition with active use of hardware virtual synthesizers and analog sequences on bass parts. This emission includes 127 routing tables.

RTOS dump at 192 kHz MIB 5276 15.06.2019

5276, 80%MIB, Boosty, dump, MIB, Mini Bikes, routing tables, wavelets, Wavetables

Jun, 2019

By ruslany

Dump, middleware and more

An enormous work was conducted this weekend on MIB vector optimization. At the beginning the full base was defragmented by clearance of the dump below:

RTOS dump at 192 kHz MIB 5149 08.06.2019

In addition, the switch to 11 kHz was made and stochastic selections were performed in a special edition of RTOS with a direct output on auxiliary channel (through). Later these ethers were recorded as middleware with PCM WAV container of 24-bit 11 kHz. You can listen to them lower:

Middleware 1 11025hz MIB5149

Middleware 2 11025hz MIB5149

Middleware 3 11025hz MIB5149

Middleware 4 11025hz MIB5149

16 middleware files were recorded, here I show you only the four. Then these middleware was filed to the special version of L1-L4 L6-L7 vRouter RAD96, which uploaded it on 96 destinations of L1-L3 layers. This way, the middleware was fixated. This method is different from direct submission to RAD96 master routing table, because RAD96 ether aggregator can exclude the predefined set of ether combinations and I was needed to attain to precise channel matrix of 52 channels.

After the full contact base was uploaded by stochastic selections of MIB5149 and dump, I made RTOS authorization again but this time mangling the sample rate parameter up to 192 kHz. This way, I updated links to all aliases and authorized the whole MIB on 192 kHz.

192kHz, authorization, channel matrix, dump, MIB, middleware, RAD96, RTOS

1 2 3 … 5

Category : Musique Concrete

History of the creation of SASER 2.0