62 pointsby mayerwin4 hours ago10 comments
  • brudgers2 hours ago
    For what it is worth, Microsoft is in the process of rolling out Windows Midi Services for Windows 11.

    https://microsoft.github.io/MIDI/

    • embedding-shape28 minutes ago
      Why on earth is the "Windows MIDI Services is Here" thing a slider/carousel with one element in it? Why are the buttons completely misplaced with no margin between them? Has a human seen and tried this before they just deployed everything and went live?
    • moominan hour ago
      A few more years and we might be able to approach Atari ST levels of MIDI performance…
      • bitwizea few seconds ago
        Never gonna happen. The architecture of modern hardware and operating systems won't allow for that kind of low latency and jitter.
  • cladopa40 minutes ago
    Wow. That looks really painful. I have multiple pianos, always used cable because I wanted it to work without problems in Linux and Mac. Also I can't stand delays.

    I have created 20 utils or so with the help of Claude, in order to practice multiple things like reading sheet music, or rhythms, or different scales. I never expected it to be that useful as my new Yamaha was bought before Claude existed, and having a cable that just works is so great.

    I have spent way less effort doing all my utils than this man into just connecting its machine.

    Before using it with Claude I used them a lot with Synthesia and GarageBand, but with Claude is like having a personal trainer.

  • BonerWiener3 hours ago
    Wow very cool project! I will test it out later today - i have always been using cabled connection for my midi keyboard
  • QuantumNomad_4 hours ago
    > Windows only natively exposes BLE-MIDI through the WinRT API, which almost no DAW polls.

    I haven’t used Windows for ages. Does this mean that almost every Windows user with any Bluetooth MIDI keyboard is unable to use it out of the box with their DAW without installing additional third-party software?

    Does it apply even to latest version of the very widely used DAWs like Ableton, Pro Tools, FL Studio, Reason, and Reaper?

    • maksut2 hours ago
      That wouldn't surprise me.

      Surprisingly Windows audio stack is a mess. I have a mini keyboard with Bluetooth and it was an adventure to get it working in Windows. In Linux it was pretty much plug and play.

      Low latency audio drviers are also messy in Windows when not using an audio interface with well written ASIO drivers. Pipewire in Linux is much easier to configure. Looks like MacOS also does not have this driver problem.

      It is surprising. Because most audio plugins and DAWs support only Windows and MacOS.

    • harrouet2 hours ago
      If you use a Mac, you'd be amazed at how many things can't be done on Windows without 3rd-party software.

      Do you know how to spot a Windows user ? They print-and-scan to merge their PDFs.

      • thrtythreeforty44 minutes ago
        This is a weird comment because I feel the same about getting macOS to a useable place.

        I probably have 5 or 6 things installed on my Mac like Scroll Reverse and Rectangle, just trying to beat the window manager into something that resembles useable.

  • monikalodhian hour ago
    This is really interesting. Windows device handling can be tricky sometimes, especially when things work at one layer but fail silently at another. The channel detection approach is clever.
  • team_zlvox4 hours ago
    Thanks! Totally understand – the tool’s core audience is definitely Windows users facing MIDI driver headaches. Appreciate you stopping by though!
  • throw_m2393392 hours ago
    Tried with the Yamaha Seqtrak on Windows 10, didn't work.
  • givinguflac4 hours ago
    Impressive work! Alas I don’t use windows but if I did I would certainly check this out.
  • farhadx3 hours ago
    [dead]
  • mockbolt3 hours ago
    [dead]