Live data from Hacker News

Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

github.com

21–30 of 32 posts

Re: Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

#22
post #8
post #7

god damn it. if i'd seen this yesterday i probably wouldn't have blown rent on a couple of volcas.

now i'm thinking about some kind of qmk integration that provides step indication and other status info directly on the keyboard. there's LEDs in it anyway right

I’ve thought a lot about this! I’d love to create hardware someday that plugs directly into a keyboard and turns it into a music workstation. I recently came across the Wooting keyboard line which seems like the perfect fit, since you could get pressure sensitive keypresses (currently one big downside of the Typebeat workflow).

https://wooting.io/

Re: Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

#24
post #22
post #8

Earlier quoted context omitted.

now i'm thinking about some kind of qmk integration that provides step indication and other status info directly on the keyboard. there's LEDs in it anyway right

I’ve thought a lot about this! I’d love to create hardware someday that plugs directly into a keyboard and turns it into a music workstation. I recently came across the Wooting keyboard line which seems like the perfect fit, since you could get pressure sensitive keypresses (currently one big downside of the Typebeat workflow). https://wooting.io/

pressure sensitive is alright but once you move away from the absolute baseline of common hardware it's more attractive to just spend money on a real synthesizer.

go full pi appliance. it wouldn't be too hard to make an sd image, perhaps compatible with one/some of those "pi tablet" kits, that would boot straight into this, recognize various qmk-compatible usb ids and offer to push firmware.

Re: Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

#26
post #2

Hi HN! I’ve been working on Typebeat for a year and a half, and I decided yesterday to make the code public. There’s also a website where you can download the macOS build and try an online demo: https://typebeat.kofi.sexy The project was initially conceived as “vim for music”. All of Typebeat is controlled by the 30 main character keys on the computer keyboard. The result is a workflow that’s a little tricky to learn…

Github page says, "I am not actively developing this project, but I may return to it at some point in the future". Is that still accurate?

Re: Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

#29
post #2

Hi HN! I’ve been working on Typebeat for a year and a half, and I decided yesterday to make the code public. There’s also a website where you can download the macOS build and try an online demo: https://typebeat.kofi.sexy The project was initially conceived as “vim for music”. All of Typebeat is controlled by the 30 main character keys on the computer keyboard. The result is a workflow that’s a little tricky to learn…

Github page says, "I am not actively developing this project, but I may return to it at some point in the future". Is that still accurate?

Yes, pretty much. It’s definitely cool that so many folks here have left positive feedback, but ultimately I don’t have the same bandwidth and motivation that I had when I started this project. Whenever those return, I’ll return to it. Until then, I’m just planning to chew on the core idea and take in everyone’s suggestions.

Re: Show HN: Typebeat: Keyboard-controlled music sequencer, sampler, and synth

#30
post #29

Earlier quoted context omitted.

Github page says, "I am not actively developing this project, but I may return to it at some point in the future". Is that still accurate?

Yes, pretty much. It’s definitely cool that so many folks here have left positive feedback, but ultimately I don’t have the same bandwidth and motivation that I had when I started this project. Whenever those return, I’ll return to it. Until then, I’m just planning to chew on the core idea and take in everyone’s suggestions.

I think this is a perfectly reasonable default. thanks for making something interesting and making it available for everyone to use and/or learn from.

aside: it's kind of weird to assume that all projects on GitHub are constantly being updated for free. old projects are inevitably going to outnumber new ones on any system that keeps old projects available, unless that system continues growing at an ever-increasing pace forever and ever.

Post reply on HN