--- title: "Idea Capture MIDI Recorder" date: "2026-07-20" canonical: "https://raytally.com/en/ideas/2026-07-20-what-i-learned-selling-2-500-midi-recorders-hardware-is-not/" generator: "RayTally · dev-prompt-v4" signal: query: "What I learned selling 2,500 MIDI recorders: Hardware is not so hard" observed_at: "2026-07-20T00:33:14.313Z" sources: - url: "https://chipweinberger.com/articles/20260719-hardware-is-not-so-hard" boundary: "Published at 2026-07-19T00:00:00.000Z. Observed at 2026-07-20T00:33:14.313Z." - url: "https://news.ycombinator.com/item?id=48966713" boundary: "Published at 2026-07-19T00:00:00.000Z. Observed at 2026-07-20T00:33:14.313Z." - url: "https://help.ableton.com/hc/en-us/articles/360000776450-Capture-MIDI" boundary: "No publication timestamp is present in the source record." - url: "https://www.musicradar.com/music-tech/no-menus-to-dive-through-no-modes-to-get-stuck-in-just-play-loop-and-explore-your-musical-ideas-auxy-unveils-svensson-a-minimalist-keyboard-built-for-instant-music-making" boundary: "Published at 2026-04-30T00:00:00.000Z." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-20-what-i-learned-selling-2-500-midi-recorders-hardware-is-not/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Idea Capture MIDI Recorder When inspiration strikes, one press saves a MIDI passage with synchronized audio, editable playback, and an index of its melodies. ## Product concept When a musician hums a phrase, improvises on a keyboard, or plays a drum machine, one press preserves both the performance and its audio. Recordings are arranged chronologically, with repeated motifs and bars worth developing flagged automatically. On the next session, the musician can reopen any fragment and continue writing from it. The product is built for the instant an idea arrives, rather than for sorting through a pile of untitled files afterward. ## Why now (backed by facts) On July 19, 2026, an article about starting a MIDI recording-hardware company ranked third in a Hacker News snapshot, with 388 points and 195 comments; the same article disclosed that Jamcorder had sold 2,500 units. That concentrated discussion moved “automatically preserve a performance when inspiration strikes” from a personal workflow issue into a public conversation about hardware startups and product tradeoffs, making this a timely moment to test the device category. ## Direction (model inference, not independently verified) Target user: Independent musicians writing songs, practicing keys, or making electronic music, especially those who improvise at a keyboard, drum machine, or microphone but do not want to open a DAW, set up tracks, and organize files every time. They use it when an idea has just appeared and they do not yet know whether it is worth developing. Minimal entry point: Start with a lightweight Ableton Live companion that continuously listens to connected MIDI input. Pressing the device button saves the most recent passage and links its audio recording to the MIDI clip. Version one should cover timeline playback, clip trimming, and export, while recurring-motif indexing can initially be limited to single-track keyboard performances. Ableton has confirmed that Capture MIDI continuously listens and can recover material played moments earlier, providing a familiar reference workflow for users. The strongest case against: The strongest counterargument is that users can already recover what they just played with Ableton Live’s Capture MIDI, buy Move, or use newer keyboards with instant loopers. If recurring-motif detection is not reliable enough, the device may amount to a more expensive record button. Supporting sung audio, free timing, pedal control, MIDI clock, and multiple hardware connections at once would also substantially increase synchronization, latency, storage, and support complexity. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Create a series of short demonstrations around the real moment of forgetting to press Record but wanting to retrieve the last phrase. Use the same keyboard, vocal, or drum-machine performance to show how a button press enables playback, recurring-motif navigation, and continued writing. The initial launch can draw directly on the original author’s Hacker News discussion of a hardware startup, offer a downloadable desktop trial in music-production and Ableton communities, then use preorders or a waitlist to validate demand for hardware. ## Competitors & gaps (model inference) - Ableton Live Capture MIDI: Ableton Live already offers Capture MIDI, which can recover MIDI played moments earlier, but it depends on an open project, armed or monitored tracks, and a computer-based workflow. It does not preserve audio and MIDI together at the device level or provide a time-based index for ideas. - Ableton Move: Ableton Move combines portable creation, microphone recording, MIDI connectivity, and continued editing, but it is a music-making device with sounds and a sequencer rather than a tool focused on automatically saving every performance and retrieving it by recurring motifs. - Auxy Svensson 49: Auxy’s Svensson 49 also offers a multitrack MIDI looper that begins recording when a player starts and lets them revisit what they just played. It is currently positioned as a full home keyboard, however, and reporting indicates that it cannot yet export audio or MIDI to other devices. ## How it makes money (model inference) Sell the hardware as a one-time purchase, with basic recording, playback, and clip export included. Offer cross-device sync, automatic indexing, and more advanced editing as an optional subscription. ## Source context Theme: MIDI recorder hardware startup Trigger Hacker News post (original English): What I learned selling 2,500 MIDI recorders: Hardware is not so hard Heat at capture: ~388 points, 195 comments (point-in-time values) Points and comments are a historical snapshot from the moment of capture and drift over time. They only explain “why now”; do not present them as precise market numbers. ## Sources - What I learned selling 2500 MIDI recorders, part 1: Hardware is not so hard (https://chipweinberger.com/articles/20260719-hardware-is-not-so-hard) - What I learned selling 2,500 MIDI recorders: Hardware is not so hard (https://news.ycombinator.com/item?id=48966713) - Capture MIDI (https://help.ableton.com/hc/en-us/articles/360000776450-Capture-MIDI) - Auxy unveils Svensson, a minimalist keyboard built for instant music-making (https://www.musicradar.com/music-tech/no-menus-to-dive-through-no-modes-to-get-stuck-in-just-play-loop-and-explore-your-musical-ideas-auxy-unveils-svensson-a-minimalist-keyboard-built-for-instant-music-making) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.