musa-dsl 0.42.7 → 0.43.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '08cad9ebc734d1e470cbf691738f1f08b9042796a4cf01adadb0bb2d126ef121'
-  data.tar.gz: f5b9a5ec33e63d511507fa27f42f64b7b126e9104c0d14c747c95445f953dc13
+  metadata.gz: d4255273d1d071bd791ad11b5da8cd3e452442c2ec5bc78aed0f594968589a79
+  data.tar.gz: 8814fbd0fa803dd30f1aaad76a0b4843f008065db1533bef87872fccf1cf8e9c
 SHA512:
-  metadata.gz: 6ca2b3741c4d4d83bf3318efe27a30b4730a9a2664ec3a5a8ad8d64f54a71697ee3b119d6ecbbfc61b2f2f4a800d516c5f857d55a012611afa4ab6f120f0ca7a
-  data.tar.gz: e0956d3b3593c171e22ebf448182655f3e754bef2af495e96fbff4a096c8c0511d937cc5732f6d57d1ec7b0ea9d3bbd01c79bf1732c7ed06dd3d8965361f300f
+  metadata.gz: 61b3eb793d334844822636e2d8597c86dee2f353170d215328bf6dfc1be4aa24fdbe96c830584de377d99472d2259ef75a804f3c564fa5785f2430a14c1805a2
+  data.tar.gz: 7616c2dd4e24bf46714a64d48690d81989fa8ed41d99972f7c0aa2164607c8e72bf7fcd57b20963eed38d56420e889cd3421135d79df11d35464f2b2b1637005

data/README.md

@@ -41,39 +41,6 @@ Musa-DSL is a programming language DSL (Domain-Specific Language) based on Ruby
 
 VSCode with the Ruby LSP extension also works well, though Ruby autocomplete and hover documentation are less complete.
 
-### AI Composition Assistant: Claude Code Plugin
-
-The fastest way to learn and compose with MusaDSL is through **[Nota](https://github.com/javier-sy/nota-plugin-for-claude)** — a plugin for [Claude Code](https://claude.ai/code) that provides:
-
-- **`/nota:explain`** — Ask any question about MusaDSL and get sourced answers with working code examples
-- **`/nota:think`** — Creative ideation across multiple musical dimensions
-- **`/nota:code`** — Describe your musical intention in natural language and get verified MusaDSL code
-- **`/nota:analyze`** — Structured analysis of your compositions
-- **`/nota:best-practices`** — Consolidate recurring patterns into searchable best practices
-
-The plugin includes a semantic knowledge base covering all MusaDSL documentation, API reference, 22+ demo projects, and 12 built-in composition best practices. Your compositions, analyses, and practices become searchable knowledge that enriches future sessions.
-
-**Requirements:** [Ruby 3.4+](https://www.ruby-lang.org/) and a [Voyage AI](https://dash.voyageai.com/) API key (free tier is sufficient for personal use).
-
-**Install in Claude Code:**
-
-First, add the Nota marketplace:
-```
-/plugin marketplace add javier-sy/nota-plugin-for-claude
-```
-
-Then install the plugin:
-```
-/plugin install nota@yeste.studio
-```
-
-Then add your Voyage AI API key to your shell profile:
-```
-export VOYAGE_API_KEY="your-key-here"
-```
-
-Run `/nota:setup` to verify the installation.
-
 ### Framework Installation
 
 Add to your Gemfile:
@@ -126,19 +93,12 @@ MusaDSL is a comprehensive ecosystem consisting of a core framework (musa-dsl) a
 **Core Framework:**
 - [**musa-dsl**](https://github.com/javier-sy/musa-dsl) - Main DSL framework for algorithmic composition and musical thinking
 
-**MIDI Communication Stack:**
+**MIDI Communication Stack** (used internally by musa-dsl for MIDI I/O):
 - [**midi-events**](https://github.com/javier-sy/midi-events) - Low-level MIDI event definitions and protocols
 - [**midi-parser**](https://github.com/javier-sy/midi-parser) - MIDI file parsing and analysis
 - [**midi-communications**](https://github.com/javier-sy/midi-communications) - Cross-platform MIDI I/O abstraction layer
 - [**midi-communications-macos**](https://github.com/javier-sy/midi-communications-macos) - macOS-specific MIDI native implementation
 
-**Live Coding Environment (MusaLCE):**
-- [**musalce-server**](https://github.com/javier-sy/musalce-server) - Live coding evaluation server with hot-reload capabilities
-- [**MusaLCEClientForVSCode**](https://github.com/javier-sy/MusaLCEClientForVSCode) - Visual Studio Code extension for live coding
-- [**MusaLCEClientForAtom**](https://github.com/javier-sy/MusaLCEClientForAtom) - Atom editor plugin for live coding
-- [**MusaLCEforBitwig**](https://github.com/javier-sy/MusaLCEforBitwig) - Bitwig Studio integration for live coding
-- [**MusaLCEforLive**](https://github.com/javier-sy/MusaLCEforLive) - Ableton Live integration for live coding
-
 ### musa-dsl Internal Architecture
 
 The musa-dsl framework is organized in modular layers:
@@ -273,7 +233,7 @@ Comprehensive MusicXML score generation with hierarchical structure, multiple vo
 
 ### REPL - Live Coding Infrastructure
 
-TCP-based server for live coding with MusaLCE clients (VSCode, Atom, Bitwig, Live), real-time code evaluation and error handling.
+TCP-based server for live coding — real-time code evaluation and error handling. Consumed by external REPL clients (editor extensions, custom evaluators).
 
 **📖 [Complete Documentation](docs/subsystems/repl.md)**
 
@@ -283,6 +243,16 @@ Ruby refinements and metaprogramming utilities: Arrayfy, Hashify, ExplodeRanges,
 
 **📖 [Complete Documentation](docs/subsystems/core-extensions.md)**
 
+## More from the MusaDSL ecosystem
+
+- [MusaDSL](https://musadsl.yeste.studio) — Ruby framework for algorithmic sound and musical composition.
+- [MusaLCE](https://musalce.yeste.studio) — live coding environment for Ableton Live and Bitwig Studio.
+- [Nota](https://nota.yeste.studio) — Claude Code plugin for AI-assisted MusaDSL composition.
+- **Pulso** — Stream Deck plugin for MusaLCE Surface controls *(upcoming)*.
+- **VST3 plugins** — collection of audio plugins for mixing and mastering *(upcoming)*.
+
+For the full map — descriptions, how they relate, which one to pick for what — see [musa-ecosystem.yeste.studio](https://musa-ecosystem.yeste.studio).
+
 ## Author
 
 * [Javier Sánchez Yeste](https://github.com/javier-sy)

data/docs/subsystems/repl.md

@@ -9,11 +9,40 @@ Editor → MusaLCE Client → TCP (port 1327) → REPL Server → DSL Context
                                              Results/Errors
 ```
 
-**Available MusaLCE Clients:**
-- **MusaLCEClientForVSCode**: Visual Studio Code extension
-- **MusaLCEClientForAtom**: Atom editor plugin
-- **MusaLCEforBitwig**: Bitwig Studio integration
-- **MusaLCEforLive**: Ableton Live integration
+The REPL is **only** the TCP eval channel between editor and server. Anything else a live-coding session needs (DAW transport, MIDI routing, OSC surface relay, etc.) lives outside this subsystem.
+
+## Two scenarios
+
+### Case 1 — Standalone live coding (you bring your own REPL)
+
+This is the scenario this document covers. You build your own `main.rb` (sequencer, voices, clock, transport, your own helpers) and start `Musa::REPL::REPL.new(binding)` inside the sequencer's DSL context. Your editor connects to it on `localhost:1327` and you send Ruby fragments live.
+
+Maximum control. Useful when:
+
+- You drive non-DAW targets — SuperCollider, Max/MSP, OSC apps, OS voice synthesis, custom hardware.
+- You're prototyping a personal live-coding DSL (helpers, Tidal-Cycles-style API).
+- You want to keep the dependency footprint to musa-dsl alone.
+
+A complete worked example with a Tidal-Cycles-style `d(n)` / `hush` / `solo` API: [`musadsl-demo/_demo-13-live-coding`](https://github.com/javier-sy/musadsl-demo).
+
+### Case 2 — Suite workflow (musalce-server handles everything)
+
+When the target is **Ableton Live** or **Bitwig Studio**, the [musalce-server](https://github.com/javier-sy/musalce-server) gem packages this REPL plus a sequencer, a clock, a transport, a DAW handler (OSC over UDP to the per-DAW extension) and a surface for Stream Deck integration via Pulso. Internally case 2 is a **specialization** of case 1 — `musalce-server` opens `Musa::REPL::REPL.new(binding)` after pre-building all the boilerplate, and exposes a `daw.*` API in the DSL context.
+
+Documented separately in the suite's architecture reference: [musalce-server/docs/architecture.md](https://github.com/javier-sy/musalce-server/blob/master/docs/architecture.md).
+
+## Components
+
+**REPL clients** (talk to the REPL server over TCP 1327 — same shape in both scenarios):
+
+- [MusaLCEClientForVSCode](https://github.com/javier-sy/MusaLCEClientForVSCode) — Visual Studio Code extension
+- [MusaLCEClientForAtom](https://github.com/javier-sy/MusaLCEClientForAtom) — Atom editor plugin (discontinued, December 2022)
+
+**Suite-only components** (only used in case 2 — see musalce-server architecture doc):
+
+- [musalce-server](https://github.com/javier-sy/musalce-server) — packages REPL + sequencer + DAW handler + surface
+- [MusaLCEforBitwig](https://github.com/javier-sy/MusaLCEforBitwig) — Bitwig Studio controller extension (Java)
+- [MusaLCEforLive](https://github.com/javier-sy/MusaLCEforLive) — Ableton Live MIDI Remote Script (Python)
 
 ## Communication Protocol
 
@@ -55,34 +84,41 @@ Server → Client:
   Starting composition...
 ```
 
-## Server Setup
-
-**Basic REPL Server:**
+## Server Setup (Case 1 — canonical pattern)
 
 ```ruby
 require 'musa-dsl'
+require 'midi-communications'    # or any other MIDI/OSC layer you prefer
+
 include Musa::All
 
-# Create sequencer and transport
+# 1. MIDI output of your choice
+output = MIDICommunications::Output.gets
+
+# 2. Clock + transport
 clock = TimerClock.new(bpm: 120, ticks_per_beat: 24)
 transport = Transport.new(clock, 4, 24)
 
-# Start REPL server bound to sequencer context
-# The REPL will execute code in the sequencer's DSL context
+# 3. Sequencer DSL context — anything you define inside `with` becomes
+#    available in the REPL (instance methods, accessors, helpers).
 transport.sequencer.with do
-  # DSL methods available in REPL
-  def note(pitch:, duration:)
-    puts "Playing pitch #{pitch} for #{duration} bars"
+  voices = MIDIVoices.new(sequencer: transport.sequencer, output: output, channels: [0, 1])
+
+  # Define whatever DSL surface you want exposed to the REPL.
+  def my_note(pitch:, duration:)
+    voices.voices[0].note(pitch, duration: duration)
   end
 
-  # Create REPL server (port 1327 by default)
+  # 4. Start the REPL server (binds to TCP/1327 in this DSL context)
   @repl = Musa::REPL::REPL.new(binding)
 end
 
-# Start playback (REPL runs in background thread)
+# 5. Start playback (REPL runs in background thread)
 transport.start
 ```
 
+If you instead want the **suite workflow** (case 2 — Bitwig or Live with DAW handler + Stream Deck surface), don't write the above by hand: install [musalce-server](https://github.com/javier-sy/musalce-server) and run `musalce-server bitwig|live`. It opens this same REPL with a richer DSL context (`daw.*`, `surface[:event]`, …).
+
 **File Path Injection:**
 
 When a client sends a file path via `#path`, the REPL injects it as `@user_pathname` (Pathname object). This enables relative requires based on the editor's current file location:

data/lib/musa-dsl/sequencer/base-sequencer-implementation-every.rb

@@ -201,7 +201,5 @@ module Musa::Sequencer
         @do_after << { bars: bars.rationalize, block: block }
       end
     end
-
-    private_constant :EveryControl
   end
 end

data/lib/musa-dsl/sequencer/base-sequencer-implementation-move.rb

@@ -597,7 +597,5 @@ module Musa::Sequencer
         @stop
       end
     end
-
-    private_constant :MoveControl
   end
 end

data/lib/musa-dsl/sequencer/base-sequencer-implementation-play-timed.rb

@@ -198,8 +198,6 @@ module Musa::Sequencer
         @do_after << { bars: bars.rationalize, block: block }
       end
     end
-
-    private_constant :PlayTimedControl
   end
 end
 

data/lib/musa-dsl/sequencer/base-sequencer-implementation-play.rb

@@ -359,7 +359,5 @@ module Musa::Sequencer
         @do_after << { bars: bars.rationalize, block: block }
       end
     end
-
-    private_constant :PlayControl
   end
 end

data/lib/musa-dsl/sequencer/base-sequencer-implementation.rb

@@ -490,7 +490,5 @@ module Musa::Sequencer
 
       alias to_s inspect
     end
-
-    private_constant :EventHandler
   end
 end

data/lib/musa-dsl/version.rb

@@ -1,3 +1,3 @@
 module Musa
-  VERSION = '0.42.7'.freeze
+  VERSION = '0.43.1'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: musa-dsl
 version: !ruby/object:Gem::Version
-  version: 0.42.7
+  version: 0.43.1
 platform: ruby
 authors:
 - Javier Sánchez Yeste