The dumps future workstations can only read
We are get used to 8-bit SysEx dumps, many of us even listened to their audio presentations. However, how the dump of modern embedded real-time operation system sounds? Let’s start with the fact that modern operation system is 64-bit, which gives almost 8 times more dynamic range, than 8-bit dump. Moreover, RTOS dumps are written with 192 kHz sample rate. In this post I will sum up two dumps, which were made with MIB 4795 and MIB 5007, which allows saying about their origin only one thing: these dumps are the music productions on their own.
In essence, we are dealing with routing tables, reproduced on the high regeneration speed. But, my task is to find the source of these routing tables, the hardware and software system, which can read these dumps and respond not only with sequence of events, but with sound generators tuning, sound synthesis parameters and effects. This station should include 64-bit operation system itself, working with 192 kHz sample rate, which is critical to CPU working frequency.
Such DAW should allow reading dumps with a large dynamic range and perform settings in accordance to the loaded network map. I would like to achieve panning and equalization in virtual environment without human intervention, in addition it should be performed not by a topology of some algorithm, but to exist inextricably with routing path filed in the current moment.
I remind you that 8 routing tables mixture is sufficient for a complete routing path. Taking in account 8×32 matrix for such routing tables, they are aired on 32 destinations. This tells us about high load of RTOS channel in a moment of dump creation. The high load on output channels creates tasks on input channels, because communication is a kernel-loop relationship and performed in a cycle with consistent calls and answers. To receive the answer the calling system should set in a que, because only 8 input streams available in RTOS. That is why there is a constant insufficiency in RTOS, it can’t be covered even with high console port regeneration speeds, and because to upload routing tables into the buffers the time is needed where high regeneration speed doesn’t play any role.
That is why the whole MIB should be loaded using autoload with aliases for the full base without forced thrust. I repeat, that forced thrust creates a big que and events processed only using generic feeder interrupters that is why you should constantly monitor filed system statuses. Because, there are no injections in filed systems on such high regeneration speeds as 192 kHz, then it is needed an additional time to receive an answer. If you need to receive an answer immediately, you should run RTOS on discretization frequencies lower, than 192 kHz, where the injections happen all the time, but the quality of the answer will be lower.