Live data from Hacker News

Show HN: I built a WebMIDI sequencer to control my hardware synths

simplychris.ai

21–23 of 23 posts

Re: Show HN: I built a WebMIDI sequencer to control my hardware synths

#21

Neat - here is another one you might find helpful (chrome only) https://cdn.robrohan.com/seq/index.html And the source: https://github.com/robrohan/r2_seq

It's kind of annoying when someone shows what they're working on, and the first comment is always, "Oh yeah, here's some alternatives." It feels like less like you're trying to be helpful and more like you're just kind of cheekily crapping on them. 2 cents. Maybe it would be more helpful if you were to ask how it could be different, what it improves upon. Ask if they've seen this. Something more than, "Oh yeah, here's something in addition to what this person is trying to show."

Re: Show HN: I built a WebMIDI sequencer to control my hardware synths

#22

This does not solve the underlying problem at all, which makes today's MIDI, coming from a normal computer, almost unusable for serious sequencing. This is timing and jitter issues! So, may I asked, what is the actual use-case for this sequencer? I would like to see/hear some music you made with it. Or is this just for the sake of using AI?

PipeWire with rtkit works incredibly stably with wildly short buffer lengths (low latency). Given the short buffer size, there's not much chance for big timing issues to arise (unless there's underruns with dead air, which doesn't seem to be the case). This was a surprising assertion to hear. Maybe on some OS, doing reliable timing is a problem. But with modern audio pipelines, things feel like they are in an extreme…

Actually I am using PipeWire with rtkit on Debian. But somehow it does not solve my midi problems. "Audio pipeline" is not "midi". Nevertheless I am doing all my _audio_ (not midi) work on Debian and I am very happy with it.

Re: Show HN: I built a WebMIDI sequencer to control my hardware synths

#23

Earlier quoted context omitted.

If you have hardware synths you are going to have a decent midi and audio interface that this is not a problem. It wasn't even a problem 25 years ago. There is no reason for consumer grade audio to be able to do this because most people will never use it.

I have maybe 20 hardware synths and I do a lot of sequencing. And yes it wasn't a problem 25 years ago, that is exactly why I still use an Atari STe! :-) But today it is a problem. It is just not possible to do complex and tight sequencing today with a normal Win, Mac or Linux computer. Even with my RME PCIe card. Your argument, "it wasn't a problem decades ago, so it cannot today either" is simply not correct.

Midi from a browser suffers from slowdownw due to have javascript is just too slow, non-threaded. There afde ways around it, but those are all workarounds.

Just move put of focus, and you will see how it handles sending clock. I went to a hardware based, external clock signal, and using spp to force syncs between my tools, and use rtmidi+c

Post reply on HN