midi-communications-windows 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d7c6d6e900a9daa9c9a95c48a2c5b68b97bf02cd35694a0a5110cbe5ac9f1f9b
-  data.tar.gz: b2135a883c9648f77e6dbe99a5f1b25941c595f39c28dba3a5968d85f6b4d598
+  metadata.gz: 8fc6b5ad53dfa328b84bf63dcdb0660a2c5d6e00b18faec4eb5549a8f4baa116
+  data.tar.gz: 664db0add4987b5f180481b26e6d85e3ea66b7b645b59bda5a930bb6fe59eb6d
 SHA512:
-  metadata.gz: 294cfb3185f4fb694d5769fb43643260632772e9e7eea8be47691b5be92f65a64e51bf5f31b087a85a7e780d98532eca59a7311dec5d1b477cbc375b4836c884
-  data.tar.gz: bd6e9bc0bf14f7607d7d014f45e833311c874f56e58082c16bc7191030d050f8a33b4e7817b80dc8c92baa161f9c45754969b2ae837f2d37170a0a44193a2f8e
+  metadata.gz: 2bfafc2e6f554e568b37a2e53d4261734d858da411d42a8a04a0d3cc3ccbb7bb5fe7d62b7e243c9ca62a0a3804cbf451f02372c86b4b9fb88899a1c872c0e52b
+  data.tar.gz: 1718a6d1111ab6ff8e4cdbb79d6bc2c3de18aed3478cd5d997283e8c437657d4b3c91670edebaddd661ff8d4b08b7d12ac4541cd3e38284c65811a219eab90ff

data/.github/workflows/notify-plugin.yml

@@ -0,0 +1,17 @@
+name: Notify Plugin Rebuild
+
+on:
+  push:
+    branches: [master]
+
+jobs:
+  notify:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger nota-plugin rebuild
+        uses: peter-evans/repository-dispatch@v3
+        with:
+          token: ${{ secrets.PLUGIN_REBUILD_PAT }}
+          repository: javier-sy/nota-plugin
+          event-type: source-updated
+          client-payload: '{"repo": "${{ github.repository }}", "sha": "${{ github.sha }}"}'

data/.yardoc/checksums

@@ -4,5 +4,5 @@ lib/midi-communications-windows/input.rb 36e58891d1c604dd4b2f333382a4010660d4786
 lib/midi-communications-windows/device.rb 9f151193d144c298c064592ee21d44111f968d01
 lib/midi-communications-windows/output.rb 3069d46892268c529d999363bd05fac891e5f4fc
 lib/midi-communications-windows/message.rb 2390946620b244ec12a6b373e003304ef9c29e4d
-lib/midi-communications-windows/version.rb 3dbf5650d0b320f6164b3791f859d2551162dc0a
+lib/midi-communications-windows/version.rb 4804d6731ca80a4f6f679dd5585ed1b2c7517513
 lib/midi-communications-windows/type_conversion.rb dae7dc5109d955f4693920fa173f5c143dcb7bf1

data/.yardopts

@@ -4,5 +4,3 @@
 --no-private
 --embed-mixins
 lib/**/*.rb
--
-docs/testing-on-windows.md

data/README.md

@@ -30,14 +30,11 @@ enough to make `Output`'s System Exclusive wait mean something, and a port
 appearing or disappearing while the program runs.
 
 The version stays in the 0.0.x series because that was a virtual machine with no
-MIDI hardware in it, not because anything is known to be missing. It will not be
-published to RubyGems until a physical MIDI interface has closed the items
-[`docs/testing-on-windows.md`](docs/testing-on-windows.md) lists as untestable
-without one.
-
-That document is also how to rebuild the test environment: it is the procedure
-these measurements were taken with, including how to make two ports collide in
-WinMM's 31 characters of name.
+MIDI hardware in it, not because anything is known to be missing.
+
+How those measurements were taken, and what a session with real hardware still
+has to close, is written down in
+[`dev/testing-on-windows.md`](dev/testing-on-windows.md).
 
 ### One thing worth knowing before you use it
 

data/doc/MIDICommunicationsWindows/API/MIDIHdr.html

@@ -134,7 +134,7 @@ WinMM there expects.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/API/MIDIInCaps.html

@@ -132,7 +132,7 @@ declared as <code>:uint16</code> so that reading it cannot split a character in
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/API/MIDIOutCaps.html

@@ -130,7 +130,7 @@
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/API/MSG.html

@@ -133,7 +133,7 @@ is 48 bytes on 64-bit Windows, which is what the queue functions expect.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/API.html

@@ -971,7 +971,7 @@ than showing a replacement character.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Device/ClassMethods.html

@@ -355,7 +355,7 @@ back as the same object as before; see <span class='object_link'><a href="../Dev
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Device/InstanceMethods.html

@@ -1086,7 +1086,7 @@ may already hold.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Device.html

@@ -978,7 +978,7 @@ the reserved id <code>-1</code> and does not count among its devices.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Error.html

@@ -428,7 +428,7 @@ for instance</p></div>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Input.html

@@ -1544,7 +1544,7 @@ may already hold.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Message.html

@@ -690,7 +690,7 @@ byte calls for</p></div>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/Output.html

@@ -1687,7 +1687,7 @@ else, and this is where the two part company.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:53 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows/TypeConversion.html

@@ -359,7 +359,7 @@
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/MIDICommunicationsWindows.html

@@ -184,7 +184,7 @@ RubyGems is where installations break; there is nothing here to break.</p>
 
 </div>
         </dt>
-        <dd><pre class="code"><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>0.0.3</span><span class='tstring_end'>&#39;</span></span><span class='period'>.</span><span class='id identifier rubyid_freeze'>freeze</span></pre></dd>
+        <dd><pre class="code"><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>0.0.4</span><span class='tstring_end'>&#39;</span></span><span class='period'>.</span><span class='id identifier rubyid_freeze'>freeze</span></pre></dd>
       
     </dl>
   
@@ -200,7 +200,7 @@ RubyGems is where installations break; there is nothing here to break.</p>
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/_index.html

@@ -65,9 +65,6 @@
     <li class="r1"><a href="index.html" title="README">README</a></li>
     
   
-    <li class="r2"><a href="file.testing-on-windows.html" title="testing-on-windows">testing-on-windows</a></li>
-    
-  
   </ul>
 
 <div class="clear"></div>
@@ -252,7 +249,7 @@
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:17 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/file.README.html

@@ -112,13 +112,10 @@ not been exercised is anything needing real hardware — a physical interface sl
 enough to make <code>Output</code>'s System Exclusive wait mean something, and a port
 appearing or disappearing while the program runs.</p>
 <p>The version stays in the 0.0.x series because that was a virtual machine with no
-MIDI hardware in it, not because anything is known to be missing. It will not be
-published to RubyGems until a physical MIDI interface has closed the items
-<a href="docs/testing-on-windows.md"><code>docs/testing-on-windows.md</code></a> lists as untestable
-without one.</p>
-<p>That document is also how to rebuild the test environment: it is the procedure
-these measurements were taken with, including how to make two ports collide in
-WinMM's 31 characters of name.</p>
+MIDI hardware in it, not because anything is known to be missing.</p>
+<p>How those measurements were taken, and what a session with real hardware still
+has to close, is written down in
+<a href="dev/testing-on-windows.md"><code>dev/testing-on-windows.md</code></a>.</p>
 <h3 id="One_thing_worth_knowing_before_you_use_it">One thing worth knowing before you use it</h3>
 <p><code>Input#gets</code> <strong>waits</strong>. It does not return an empty array when nothing has
 arrived; it blocks until something does, and then returns everything that
@@ -230,7 +227,7 @@ Both are addressed here by construction; see the notes in
 <p><a href="https://github.com/javier-sy/midi-communications-windows">MIDI Communications Windows Layer</a> Copyright (c) 2026 <a href="https://yeste.studio">Javier Sánchez Yeste</a>, licensed under LGPL 3.0 License</p></div></div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/file_list.html

@@ -52,11 +52,6 @@
   </li>
   
 
-  <li id="object_testing-on-windows" class="even">
-    <div class="item"><span class="object_link"><a href="file.testing-on-windows.html" title="testing-on-windows">testing-on-windows</a></span></div>
-  </li>
-  
-
 
       </ul>
     </div>

data/doc/index.html

@@ -112,13 +112,10 @@ not been exercised is anything needing real hardware — a physical interface sl
 enough to make <code>Output</code>'s System Exclusive wait mean something, and a port
 appearing or disappearing while the program runs.</p>
 <p>The version stays in the 0.0.x series because that was a virtual machine with no
-MIDI hardware in it, not because anything is known to be missing. It will not be
-published to RubyGems until a physical MIDI interface has closed the items
-<a href="docs/testing-on-windows.md"><code>docs/testing-on-windows.md</code></a> lists as untestable
-without one.</p>
-<p>That document is also how to rebuild the test environment: it is the procedure
-these measurements were taken with, including how to make two ports collide in
-WinMM's 31 characters of name.</p>
+MIDI hardware in it, not because anything is known to be missing.</p>
+<p>How those measurements were taken, and what a session with real hardware still
+has to close, is written down in
+<a href="dev/testing-on-windows.md"><code>dev/testing-on-windows.md</code></a>.</p>
 <h3 id="One_thing_worth_knowing_before_you_use_it">One thing worth knowing before you use it</h3>
 <p><code>Input#gets</code> <strong>waits</strong>. It does not return an empty array when nothing has
 arrived; it blocks until something does, and then returns everything that
@@ -230,7 +227,7 @@ Both are addressed here by construction; see the notes in
 <p><a href="https://github.com/javier-sy/midi-communications-windows">MIDI Communications Windows Layer</a> Copyright (c) 2026 <a href="https://yeste.studio">Javier Sánchez Yeste</a>, licensed under LGPL 3.0 License</p></div></div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/doc/top-level-namespace.html

@@ -102,7 +102,7 @@
 </div>
 
       <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
+  Generated on Mon Sep  7 00:14:18 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.45 (ruby-3.4.7).
 </div>

data/lib/midi-communications-windows/version.rb

@@ -1,4 +1,4 @@
 module MIDICommunicationsWindows
   # Current version of the midi-communications-windows gem.
-  VERSION = '0.0.3'.freeze
+  VERSION = '0.0.4'.freeze
 end

data/midi-communications-windows.gemspec

@@ -3,12 +3,15 @@ require_relative 'lib/midi-communications-windows/version'
 Gem::Specification.new do |s|
   s.name        = 'midi-communications-windows'
   s.version     = MIDICommunicationsWindows::VERSION
-  s.date        = '2026-09-06'
+  s.date        = '2026-09-07'
   s.summary     = 'Realtime MIDI IO with Ruby for Windows'
   s.description = 'Access the Windows Multimedia (WinMM) MIDI API with Ruby.'
   s.authors     = ['Javier Sánchez Yeste']
   s.email       = ['javier.sy@gmail.com']
-  s.files       = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  # dev/ is how the library was measured, not how it is used: it describes
+  # installing preview software on a machine with no MIDI hardware, and has no
+  # business in every user's gem directory.
+  s.files       = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features|dev)/}) }
   s.homepage    = 'https://github.com/javier-sy/midi-communications-windows'
   s.license     = 'LGPL-3.0-or-later'
 

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: midi-communications-windows
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Javier Sánchez Yeste
 bindir: bin
 cert_chain: []
-date: 2026-09-06 00:00:00.000000000 Z
+date: 2026-09-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ffi
@@ -138,6 +138,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/workflows/notify-plugin.yml"
 - ".gitignore"
 - ".version"
 - ".yardoc/checksums"
@@ -170,7 +171,6 @@ files:
 - doc/css/full_list.css
 - doc/css/style.css
 - doc/file.README.html
-- doc/file.testing-on-windows.html
 - doc/file_list.html
 - doc/frames.html
 - doc/index.html
@@ -179,7 +179,6 @@ files:
 - doc/js/jquery.js
 - doc/method_list.html
 - doc/top-level-namespace.html
-- docs/testing-on-windows.md
 - examples/input.rb
 - examples/list_ports.rb
 - examples/output.rb

data/doc/file.testing-on-windows.html

@@ -1,253 +0,0 @@
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="UTF-8">
-<meta name="viewport" content="width=device-width, initial-scale=1.0">
-<title>
-  File: testing-on-windows
-  
-    &mdash; MIDI Communications Windows API
-  
-</title>
-
-  <link rel="stylesheet" href="css/style.css" type="text/css">
-
-  <link rel="stylesheet" href="css/common.css" type="text/css">
-
-<script type="text/javascript">
-  pathId = "testing-on-windows";
-  relpath = '';
-</script>
-
-
-  <script type="text/javascript" charset="utf-8" src="js/jquery.js"></script>
-
-  <script type="text/javascript" charset="utf-8" src="js/app.js"></script>
-
-
-  </head>
-  <body>
-    <div id="main_progress" aria-hidden="true"></div>
-
-    <div class="nav_wrap">
-      <iframe id="nav" src="file_list.html?1"></iframe>
-      <div id="resizer"></div>
-    </div>
-
-    <div id="main" tabindex="-1">
-      <div id="header">
-        <div id="menu">
-  
-    <a href="_index.html">Index</a> &raquo; 
-    <span class="title">File: testing-on-windows</span>
-  
-</div>
-
-        <div id="search">
-  
-    <a class="full_list_link" id="class_list_link"
-        href="class_list.html">
-
-        <svg width="24" height="24">
-          <rect x="0" y="4" width="24" height="4" rx="1" ry="1"></rect>
-          <rect x="0" y="12" width="24" height="4" rx="1" ry="1"></rect>
-          <rect x="0" y="20" width="24" height="4" rx="1" ry="1"></rect>
-        </svg>
-    </a>
-  
-</div>
-        <div class="clear"></div>
-      </div>
-
-      <div id="content"><div id='filecontents'><h1 id="Testing_this_gem_on_Windows_without_MIDI_hardware">Testing this gem on Windows without MIDI hardware</h1>
-<p><em>Written 2026-09-06. Section 1 is the part with a shelf life: it describes
-software that was in preview at the time, which Microsoft's release notes said
-was headed for Windows 11 25H2 and later during the last week of November 2026.
-If that has happened, most of section 1 collapses into &quot;nothing to install&quot; and
-the rest still applies.</em></p>
-<p>This is <strong>the procedure the library was measured with</strong>, not a promise that it
-works on another machine. All of it ran once, on one particular installation.
-Where something was checked, it says so; where it was not, it says that too.</p>
-<p>The machine was:</p>
-<p>| | |
-|---|---|
-| Windows | 11 25H2, build <strong>26200.9278</strong> |
-| CPU | ARM64 — a VMware VM on Apple silicon |
-| Ruby | 3.4.10 <code>x64-mingw-ucrt</code>, <strong>emulated</strong> under Prism (no ARM64 Ruby present) |
-| ffi | 1.17.4 <code>x64-mingw-ucrt</code>, precompiled binary |
-| MIDI hardware | <strong>none</strong> — no USB device passed through to the guest |</p>
-<p>That last row is why this document exists: with no hardware, a loopback pair is
-the only way to exercise input and output at the same time.</p>
-<p>Nothing measured on this setup says anything about <strong>timing</strong>. Emulation inside
-a virtual machine; latency and jitter need real hardware and a native Ruby.</p>
-<hr />
-<h2 id="1__What_has_to_be_installed">1. What has to be installed</h2>
-<p>Windows 11 25H2 ships <strong>Windows MIDI Services</strong> in the box: the <code>midisrv</code>
-service (<code>C:\Windows\System32\midisrv.exe</code>) and the <code>wdmaud2.drv</code> shim,
-registered as <code>midi1</code> under
-<code>HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32</code>. That shim is what
-makes endpoints from the new stack <strong>visible to WinMM</strong> without this gem doing
-anything special, and therefore what makes this setup able to test a gem that
-speaks only WinMM.</p>
-<p>What is <em>not</em> in the box are the MIDI 1.0 loopback transport and the tools. Those
-come from the [<code>microsoft/MIDI</code>] repository, release <code>inbox-dev-preview-6</code>:</p>
-<ul>
-<li><code>Windows.MIDI.Services.Basic.MIDI.1.0.Loopback.Preview.1.0.18-preview.3-arm64.exe</code></li>
-<li><code>Windows.MIDI.Services.Tools.0.99.64-devpreview.6-arm64.exe</code></li>
-</ul>
-<p>There are <code>-x64</code> variants of both. The measuring machine used the <strong>native ARM64</strong>
-ones (PE header <code>0xAA64</code>) even though the Ruby was emulated x64: the gem talks to
-<code>winmm.dll</code>, and Windows handles the crossing.</p>
-<p>The Network and Bluetooth transports from the same release are not needed.</p>
-<h3 id="Warnings_that_are_not_optional">Warnings that are not optional</h3>
-<ul>
-<li><strong>These are unsigned preview binaries.</strong> The release notes require Windows
-<strong>Developer Mode</strong>, and are explicit: <em>&quot;There are almost certainly bugs and
-missing/incomplete features.&quot;</em> This is not production software.</li>
-<li><strong>Do not redistribute them.</strong> The release's permitted-use table forbids it. A
-repository should link to the release and never host the installers.</li>
-<li>Minimum system version declared: <strong>Windows 11 25H2</strong>.</li>
-<li>Downloaded through a browser they carry Mark of the Web and SmartScreen will
-object; <code>Unblock-File</code> clears it. Fetched with <code>Invoke-WebRequest</code> they do not.</li>
-</ul>
-<h2 id="2__Installing">2. Installing</h2>
-<p>Both installers are <strong>WiX bundles</strong>, so they accept <code>/quiet</code>, <code>/norestart</code> and
-<code>/log</code>. Both need <strong>elevation</strong>, and Developer Mode writes to <code>HKLM</code>, so it is
-worth doing the whole thing in one elevated script and getting one UAC prompt.</p>
-<p>The release notes fix the order: <strong>loopback transport first, tools second.</strong></p>
-<pre class="code powershell"><code class="powershell"># --- 1. Developer Mode (the key may not exist)
-$k = &#39;HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock&#39;
-if (-not (Test-Path $k)) { New-Item $k -Force | Out-Null }
-Set-ItemProperty $k -Name AllowDevelopmentWithoutDevLicense -Value 1 -Type DWord
-Set-ItemProperty $k -Name AllowAllTrustedApps -Value 1 -Type DWord
-
-# --- 2. installers, in this order
-Start-Process -Wait -FilePath &#39;&lt;...&gt;Basic.MIDI.1.0.Loopback.Preview...-arm64.exe&#39; `
-  -ArgumentList &#39;/quiet&#39;,&#39;/norestart&#39;,&#39;/log&#39;,&#39;loopback.log&#39;
-Start-Process -Wait -FilePath &#39;&lt;...&gt;Tools.0.99.64-devpreview.6-arm64.exe&#39; `
-  -ArgumentList &#39;/quiet&#39;,&#39;/norestart&#39;,&#39;/log&#39;,&#39;tools.log&#39;
-</code></pre>
-<p><strong>Both return exit <code>3010</code></strong>, which is <code>ERROR_SUCCESS_REBOOT_REQUIRED</code>: installed
-correctly, reboot pending. The measuring machine <strong>was not rebooted</strong>, and every
-measurement was taken that way. If something behaves oddly, that reboot is the
-first suspect.</p>
-<p>To check the transport registered:</p>
-<pre class="code powershell"><code class="powershell">Get-ChildItem &#39;HKLM:\SOFTWARE\Microsoft\Windows MIDI Services\Transport Plugins&#39;
-# Midi2BasicLoopbackMidiTransport should appear, with Enabled = 1
-</code></pre>
-<h3 id="_midi_exe__and_the_PATH"><code>midi.exe</code> and the PATH</h3>
-<p>The console lands at:</p>
-<pre class="code ruby"><code class="ruby">C:\Program Files\Windows MIDI Services\Tools\Console\midi.exe
-</code></pre>
-<p>The installer <strong>does</strong> add it to the machine PATH, but <strong>a shell opened before
-installing still has the old environment</strong> and will say <code>midi</code> does not exist. In
-a fresh shell, <code>midi</code> is enough; in the installing shell, use the full path. This
-detail cost time and produced one wrong report before it was noticed.</p>
-<h2 id="3__Creating_the_loopback_pair">3. Creating the loopback pair</h2>
-<pre class="code powershell"><code class="powershell">$midi = &#39;C:\Program Files\Windows MIDI Services\Tools\Console\midi.exe&#39;
-
-&amp; $midi basic-loopback create --name &quot;Reloj Bitwig ñ prueba de longitud&quot;
-&amp; $midi basic-loopback list
-</code></pre>
-<p>Options for <code>create</code>:</p>
-<table>
-<thead>
-<tr>
-<th>option</th>
-<th>what it does</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><code>-n</code>, <code>--name</code></td>
-<td>the endpoint's name</td>
-</tr>
-<tr>
-<td><code>-u</code>, <code>--unique-identifier</code></td>
-<td>an identifier of your own</td>
-</tr>
-<tr>
-<td><code>-s</code>, <code>--save-to-config</code></td>
-<td><strong>persists it in the system configuration</strong></td>
-</tr>
-</tbody>
-</table>
-<p><strong>Without <code>--save-to-config</code> a loopback is temporary</strong>: it disappears when
-<code>midisrv</code> or the machine restarts, and nothing is written to disk. Every
-measurement was taken that way, deliberately. <code>--save-to-config</code> does modify the
-user's system configuration — ask before using it.</p>
-<p>A <code>create</code> returns an <strong>Association Id</strong>, a GUID. Keep it: it is the only thing
-that will remove the loopback again.</p>
-<h3 id="Checking_through_WinMM__which_is_what_the_gem_sees">Checking through WinMM, which is what the gem sees</h3>
-<pre class="code ruby"><code class="ruby">ruby -Ilib examples/list_ports.rb
-</code></pre>
-<p>One loopback shows up as <strong>one input and one output with the same name, byte for
-byte</strong>. With two loopbacks created, enumeration gives 2 inputs and 3 outputs —
-the third being the <em>Microsoft GS Wavetable Synth</em>, which is always there.</p>
-<h2 id="4__The_name_collision_recipe">4. The name-collision recipe</h2>
-<p>WinMM stores <strong>31 characters</strong> of a name (<code>MAXPNAMELEN</code> is 32, less the NUL) and
-drops the rest <strong>silently</strong>. To reproduce the case where two distinct ports are
-indistinguishable, create two loopbacks whose <strong>first 31 characters match</strong>:</p>
-<pre class="code powershell"><code class="powershell">&amp; $midi basic-loopback create --name &quot;Reloj Bitwig ñ prueba de longitud&quot;
-&amp; $midi basic-loopback create --name &quot;Reloj Bitwig ñ prueba de longitud DOS&quot;
-</code></pre>
-<p>The first is 33 characters, the second 37; both truncate to
-<code>Reloj Bitwig ñ prueba de longit</code>. In <code>MIDIINCAPSW</code>/<code>MIDIOUTCAPSW</code> they come back
-<strong>identical field by field</strong>: same name, same <code>wMid</code> (1), same <code>wPid</code> (25 for
-inputs, 26 for outputs), same <code>vDriverVersion</code>, same <code>wTechnology</code>. Only the
-index separates them.</p>
-<p>If you change the names, keep the character counts working — the recipe depends
-on one being longer than 31 and both agreeing up to that point.</p>
-<p>The truncation happens <strong>upstream of WinMM</strong>: <code>midi enumerate midi-services-endpoints</code> shows the service already holding the 31-character name.
-Whether the console or the service truncates was not determined; for the gem it
-makes no difference.</p>
-<p>The <code>ñ</code> survives intact (<code>U+00F1</code> in the UTF-16LE dump), which is what validates
-the <strong>W</strong> entry points against a genuinely non-ASCII character.</p>
-<h2 id="5__Removing">5. Removing</h2>
-<pre class="code powershell"><code class="powershell">&amp; $midi basic-loopback remove --association-id &quot;{bfba125e-3aca-446c-9b94-692a70153034}&quot;
-</code></pre>
-<p><strong>The braces around the GUID are required.</strong> <code>list</code> prints the id without them;
-they have to be added.</p>
-<p>Afterwards, check the machine is back where it started — with <code>list</code>, and better
-still by enumerating through WinMM: with no loopbacks there should be <strong>0 inputs
-and 1 output</strong>.</p>
-<h2 id="6__What_this_setup_can_test__and_what_it_cannot">6. What this setup can test, and what it cannot</h2>
-<p>Exercised with it, and working: enumeration with colliding names, short messages
-in all three lengths (3, 2 and 1 bytes), accumulation in <code>gets</code>, System Exclusive
-both ways at 200, 3000 and 5000 bytes, buffer recycling, closing and reopening,
-and the propagation of an error from opening a port.</p>
-<p><strong>Not testable with this setup</strong>, and therefore still untested:</p>
-<ul>
-<li><strong><code>SYSEX_TIMEOUT</code> / <code>Output#wait_until_sent</code>.</strong> The only real output device is
-the <em>GS Wavetable Synth</em>, a software synthesiser that marks <code>MHDR_DONE</code> in
-under a millisecond because there is no wire. This needs a physical interface.</li>
-<li><strong><code>RESET_TIMEOUT</code> / <code>Input#await_returned_buffers</code>.</strong> It never came close:
-closes took between 4 and 21 ms against a one-second bound. The
-device-went-away path needs something to unplug.</li>
-<li><strong>Renumbering in <code>Device.enumerate</code>.</strong> Needs a port to actually appear or go.</li>
-<li><strong><code>MM_MIM_LONGERROR</code>.</strong> None could be provoked, not even with a System
-Exclusive message larger than the entire buffer queue. The code handling it is
-unexercised — its presence has been shown harmless, which is not the same
-thing.</li>
-<li><strong>That an input and an output of the same device share a name.</strong> Established
-for a loopback, where they are literally the same device. Not for a real USB
-interface.</li>
-<li><strong>Any measurement of time.</strong></li>
-</ul>
-<p>Those are the items a session with real hardware should close.</p>
-<h2 id="7__One_finding_from_here_worth_not_forgetting">7. One finding from here worth not forgetting</h2>
-<p>Multi-client access <strong>follows the endpoint, not the API</strong>. Two WinMM clients on
-the same BLOOP input both work and <strong>both receive every message</strong>. The <em>GS
-Wavetable Synth</em>, which belongs to the classic <code>wdmaud</code> stack, refuses the second
-open with <em>&quot;The specified device is already in use.&quot;</em> So on one machine, through
-one API, shareable ports and exclusive ports coexist.</p></div></div>
-
-      <div id="footer">
-  Generated on Sun Sep  6 21:20:52 2026 by
-  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.45 (ruby-3.4.7).
-</div>
-
-    </div>
-  </body>
-</html>

data/docs/testing-on-windows.md

@@ -1,222 +0,0 @@
-# Testing this gem on Windows without MIDI hardware
-
-*Written 2026-09-06. Section 1 is the part with a shelf life: it describes
-software that was in preview at the time, which Microsoft's release notes said
-was headed for Windows 11 25H2 and later during the last week of November 2026.
-If that has happened, most of section 1 collapses into "nothing to install" and
-the rest still applies.*
-
-This is **the procedure the library was measured with**, not a promise that it
-works on another machine. All of it ran once, on one particular installation.
-Where something was checked, it says so; where it was not, it says that too.
-
-The machine was:
-
-| | |
-|---|---|
-| Windows | 11 25H2, build **26200.9278** |
-| CPU | ARM64 — a VMware VM on Apple silicon |
-| Ruby | 3.4.10 `x64-mingw-ucrt`, **emulated** under Prism (no ARM64 Ruby present) |
-| ffi | 1.17.4 `x64-mingw-ucrt`, precompiled binary |
-| MIDI hardware | **none** — no USB device passed through to the guest |
-
-That last row is why this document exists: with no hardware, a loopback pair is
-the only way to exercise input and output at the same time.
-
-Nothing measured on this setup says anything about **timing**. Emulation inside
-a virtual machine; latency and jitter need real hardware and a native Ruby.
-
----
-
-## 1. What has to be installed
-
-Windows 11 25H2 ships **Windows MIDI Services** in the box: the `midisrv`
-service (`C:\Windows\System32\midisrv.exe`) and the `wdmaud2.drv` shim,
-registered as `midi1` under
-`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32`. That shim is what
-makes endpoints from the new stack **visible to WinMM** without this gem doing
-anything special, and therefore what makes this setup able to test a gem that
-speaks only WinMM.
-
-What is *not* in the box are the MIDI 1.0 loopback transport and the tools. Those
-come from the [`microsoft/MIDI`] repository, release `inbox-dev-preview-6`:
-
-- `Windows.MIDI.Services.Basic.MIDI.1.0.Loopback.Preview.1.0.18-preview.3-arm64.exe`
-- `Windows.MIDI.Services.Tools.0.99.64-devpreview.6-arm64.exe`
-
-There are `-x64` variants of both. The measuring machine used the **native ARM64**
-ones (PE header `0xAA64`) even though the Ruby was emulated x64: the gem talks to
-`winmm.dll`, and Windows handles the crossing.
-
-The Network and Bluetooth transports from the same release are not needed.
-
-[`microsoft/MIDI`]: https://github.com/microsoft/MIDI/releases
-
-### Warnings that are not optional
-
-- **These are unsigned preview binaries.** The release notes require Windows
-  **Developer Mode**, and are explicit: *"There are almost certainly bugs and
-  missing/incomplete features."* This is not production software.
-- **Do not redistribute them.** The release's permitted-use table forbids it. A
-  repository should link to the release and never host the installers.
-- Minimum system version declared: **Windows 11 25H2**.
-- Downloaded through a browser they carry Mark of the Web and SmartScreen will
-  object; `Unblock-File` clears it. Fetched with `Invoke-WebRequest` they do not.
-
-## 2. Installing
-
-Both installers are **WiX bundles**, so they accept `/quiet`, `/norestart` and
-`/log`. Both need **elevation**, and Developer Mode writes to `HKLM`, so it is
-worth doing the whole thing in one elevated script and getting one UAC prompt.
-
-The release notes fix the order: **loopback transport first, tools second.**
-
-```powershell
-# --- 1. Developer Mode (the key may not exist)
-$k = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock'
-if (-not (Test-Path $k)) { New-Item $k -Force | Out-Null }
-Set-ItemProperty $k -Name AllowDevelopmentWithoutDevLicense -Value 1 -Type DWord
-Set-ItemProperty $k -Name AllowAllTrustedApps -Value 1 -Type DWord
-
-# --- 2. installers, in this order
-Start-Process -Wait -FilePath '<...>Basic.MIDI.1.0.Loopback.Preview...-arm64.exe' `
-  -ArgumentList '/quiet','/norestart','/log','loopback.log'
-Start-Process -Wait -FilePath '<...>Tools.0.99.64-devpreview.6-arm64.exe' `
-  -ArgumentList '/quiet','/norestart','/log','tools.log'
-```
-
-**Both return exit `3010`**, which is `ERROR_SUCCESS_REBOOT_REQUIRED`: installed
-correctly, reboot pending. The measuring machine **was not rebooted**, and every
-measurement was taken that way. If something behaves oddly, that reboot is the
-first suspect.
-
-To check the transport registered:
-
-```powershell
-Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\Windows MIDI Services\Transport Plugins'
-# Midi2BasicLoopbackMidiTransport should appear, with Enabled = 1
-```
-
-### `midi.exe` and the PATH
-
-The console lands at:
-
-```
-C:\Program Files\Windows MIDI Services\Tools\Console\midi.exe
-```
-
-The installer **does** add it to the machine PATH, but **a shell opened before
-installing still has the old environment** and will say `midi` does not exist. In
-a fresh shell, `midi` is enough; in the installing shell, use the full path. This
-detail cost time and produced one wrong report before it was noticed.
-
-## 3. Creating the loopback pair
-
-```powershell
-$midi = 'C:\Program Files\Windows MIDI Services\Tools\Console\midi.exe'
-
-& $midi basic-loopback create --name "Reloj Bitwig ñ prueba de longitud"
-& $midi basic-loopback list
-```
-
-Options for `create`:
-
-| option | what it does |
-|---|---|
-| `-n`, `--name` | the endpoint's name |
-| `-u`, `--unique-identifier` | an identifier of your own |
-| `-s`, `--save-to-config` | **persists it in the system configuration** |
-
-**Without `--save-to-config` a loopback is temporary**: it disappears when
-`midisrv` or the machine restarts, and nothing is written to disk. Every
-measurement was taken that way, deliberately. `--save-to-config` does modify the
-user's system configuration — ask before using it.
-
-A `create` returns an **Association Id**, a GUID. Keep it: it is the only thing
-that will remove the loopback again.
-
-### Checking through WinMM, which is what the gem sees
-
-```
-ruby -Ilib examples/list_ports.rb
-```
-
-One loopback shows up as **one input and one output with the same name, byte for
-byte**. With two loopbacks created, enumeration gives 2 inputs and 3 outputs —
-the third being the *Microsoft GS Wavetable Synth*, which is always there.
-
-## 4. The name-collision recipe
-
-WinMM stores **31 characters** of a name (`MAXPNAMELEN` is 32, less the NUL) and
-drops the rest **silently**. To reproduce the case where two distinct ports are
-indistinguishable, create two loopbacks whose **first 31 characters match**:
-
-```powershell
-& $midi basic-loopback create --name "Reloj Bitwig ñ prueba de longitud"
-& $midi basic-loopback create --name "Reloj Bitwig ñ prueba de longitud DOS"
-```
-
-The first is 33 characters, the second 37; both truncate to
-`Reloj Bitwig ñ prueba de longit`. In `MIDIINCAPSW`/`MIDIOUTCAPSW` they come back
-**identical field by field**: same name, same `wMid` (1), same `wPid` (25 for
-inputs, 26 for outputs), same `vDriverVersion`, same `wTechnology`. Only the
-index separates them.
-
-If you change the names, keep the character counts working — the recipe depends
-on one being longer than 31 and both agreeing up to that point.
-
-The truncation happens **upstream of WinMM**: `midi enumerate
-midi-services-endpoints` shows the service already holding the 31-character name.
-Whether the console or the service truncates was not determined; for the gem it
-makes no difference.
-
-The `ñ` survives intact (`U+00F1` in the UTF-16LE dump), which is what validates
-the **W** entry points against a genuinely non-ASCII character.
-
-## 5. Removing
-
-```powershell
-& $midi basic-loopback remove --association-id "{bfba125e-3aca-446c-9b94-692a70153034}"
-```
-
-**The braces around the GUID are required.** `list` prints the id without them;
-they have to be added.
-
-Afterwards, check the machine is back where it started — with `list`, and better
-still by enumerating through WinMM: with no loopbacks there should be **0 inputs
-and 1 output**.
-
-## 6. What this setup can test, and what it cannot
-
-Exercised with it, and working: enumeration with colliding names, short messages
-in all three lengths (3, 2 and 1 bytes), accumulation in `gets`, System Exclusive
-both ways at 200, 3000 and 5000 bytes, buffer recycling, closing and reopening,
-and the propagation of an error from opening a port.
-
-**Not testable with this setup**, and therefore still untested:
-
-- **`SYSEX_TIMEOUT` / `Output#wait_until_sent`.** The only real output device is
-  the *GS Wavetable Synth*, a software synthesiser that marks `MHDR_DONE` in
-  under a millisecond because there is no wire. This needs a physical interface.
-- **`RESET_TIMEOUT` / `Input#await_returned_buffers`.** It never came close:
-  closes took between 4 and 21 ms against a one-second bound. The
-  device-went-away path needs something to unplug.
-- **Renumbering in `Device.enumerate`.** Needs a port to actually appear or go.
-- **`MM_MIM_LONGERROR`.** None could be provoked, not even with a System
-  Exclusive message larger than the entire buffer queue. The code handling it is
-  unexercised — its presence has been shown harmless, which is not the same
-  thing.
-- **That an input and an output of the same device share a name.** Established
-  for a loopback, where they are literally the same device. Not for a real USB
-  interface.
-- **Any measurement of time.**
-
-Those are the items a session with real hardware should close.
-
-## 7. One finding from here worth not forgetting
-
-Multi-client access **follows the endpoint, not the API**. Two WinMM clients on
-the same BLOOP input both work and **both receive every message**. The *GS
-Wavetable Synth*, which belongs to the classic `wdmaud` stack, refuses the second
-open with *"The specified device is already in use."* So on one machine, through
-one API, shareable ports and exclusive ports coexist.