How eitomurakami/raytone works
Project type and purpose
• RayTone is a standalone Unity application (Assets/, ProjectSettings/, Packages/), not a web/server app.
• It’s a node-based audiovisual sequencer, integrating the ChucK audio language and GLSL shaders into Unity as native plugins.
File structure
• Top‐level:
– RayTone/Assets – contains all Unity assets: Scripts (“/Scripts”), Prefabs, Materials, Models, Graphics/Shaders, Plugins, StreamingAssets, Scenes, Settings.
– RayTone/Packages & RayTone/ProjectSettings – manifest and pipeline configuration for the Universal Render Pipeline (URP), audio, input, build targets.
– RayToneShaderRenderer/ – native C++ OpenGL plugin source for accelerated shader rendering.
• Under Assets:
– Assets/Chunity – native bundles per platform and C# wrappers for embedding a ChucK VM.
– Assets/Plugins/RtMidi – C# wrappers for MIDI I/O.
– Assets/Plugins/SimpleFileBrowser – drop-in file-browser UI module.
– Assets/RayTone – core C# node graph:
· Scripts/Controllers – engine glue (NodeGraph manager, event dispatch, singleton access).
· Scripts/Units – class hierarchies for ControlUnits (e.g., Add, Lerp), GraphicsUnits (shader effects) and VoiceUnits.
· Graphics/Shaders & Plugins – GLSL templates and native bundles driving OpenGL calls.
· StreamingAssets – ChucK (.ck) tutorials, templates, user scripts and fragment shader templates.
• Key indicators of architecture:
– “Plugins” directories hold native bridges, showing a plugin-based modular approach.
– “Scripts/Units” and “Scripts/Controllers” map to an MVC‐style separation between model (node data), view (UI/Renderer), and controller (runtime logic).
README for additional insight
• Confirms: Node-based, programmable audio (ChucK) and graphics (GLSL).
• Emphasis on “playful” patching—so the core is a live node‐graph runtime engine.