Comparison of Compositor v9 Versions for MaxMSP 6 and 9
When discussing Compositor v9, it is essential to acknowledge the existence of two distinct versions for MaxMSP 6 and 9. The first version, available in MaxMSP 6, is the stable version of Compositor v9, addressing internal Cycling ’74 issues and the company’s transition to RNBO add-ons. The second version, available in MaxMSP 9, is a merged version lacking a collision-free server component.
Using the MaxMSP 9 version, progress on my tasks has been hindered due to its limitations. Additionally, Cycling ’74 has removed several features in MaxMSP 9, resulting in a significantly reduced level of productivity. For instance, when requiring the AjavaOS local build with its associated mechanics, the MaxMSP 6 version of Compositor v9 is the preferred choice, as it provides a real-time operating system (RTOS). Conversely, the MaxMSP 9 version is unable to write in 64-bit float format, which is a critical limitation given that all modern operating systems are 64-bit. Furthermore, writing in 32-bit float is also not recommended due to the absence of the OUI part in the EUI64 namespace.
At the inception of the v9 project, I articulated a goal of achieving civil control of submarines via radio ether. Each parameter was meticulously tailored to this objective. Notably, the virtual antenna dish’s pitch, roll, and yaw angles were programmed distinctly from the Max 9 version of Compositor.
Currently, the focus has shifted towards the Airplane production industry, with a gradual transition towards Space Fighters. During the Army 2023 exhibition in Russia, I created a model of an airplane. This model was a direct response to my earlier statement on human control and dispatching of drones, which I subsequently introduced to Compositor v9. Consequently, extreme angles for 3D objects are no longer feasible due to the limitations imposed by the carrier physics, which extend to the virtual dish. I conducted tests that demonstrated the model of Cyberplane crashing when a dispatcher’s position remained unoccupied for an extended period.
Regarding the upper protocols RIPng and EIGRP, which were successfully tested in the Apple App Store version of Compositor v9, the only remaining enhancement is the recording of 64-bit float data.
Returning to my previous statement regarding local machine support for AjavaOS, it is evident that in the face of restrictions imposed by the Russian government, it remains the sole viable solution for developing my operating system. Even paying for Apple services via mobile phone will be discontinued tomorrow. Nevertheless, I continue to utilize all Compositor generics in the low-level OS of this phone. Given that this chipset is ARMv8, it operates efficiently with minor glitches during peak loads. However, I do not believe that mobile services will surpass the desktop version of Compositor v9. They can assist in routing within mobile internet networks and accessing resources in Europe or the United States.
In essence, this represents a shift from submarine control to airplane control, which was my primary update for the App Store version of Compositor v9.
