trackerboy
DaisySP
trackerboy | DaisySP | |
---|---|---|
4 | 31 | |
93 | 803 | |
- | 2.2% | |
0.0 | 7.3 | |
about 1 year ago | 15 days ago | |
C++ | C++ | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
trackerboy
DaisySP
-
Ask HN: Manufacturing somewhat novel MIDI controller
You are about to bite off a lot. Ignore all the other advice in this thread, I do this for a living.
You have some software experience, this is good. Assuming you have embedded software experience (which is essential for what you are doing and not at all like web programming) you have a foothold to finish this project without going completely insane.
Hardware is a completely different beast. With software everything happens in your head and when you get stuck you can usually think your way out of it. With hardware, you really do need to learn to do things meticulously and step by step. There are many things that can go wrong. You will learn a lot on this journey.
Don't be afraid to ask for help. Finding a hardware community will be essential to do this as you learn the skills you need. You're going to make a lot of mistakes, best to go in embracing it
A good place to start is to join an open source community for MIDI. Two off the top of my head is http://www.ucapps.de/ for MIDI specific hardware and https://www.electro-smith.com/daisy
A large amount of the work you will find yourself doing at the beginning is just figuring out where and who to ask questions about things like the keybed and other hardware issues. None of this is terribly 'hard' but none of it is easy. Most of it comes from experience.
It is almost always best to use someone else's product when you are designing your first. Roger Linn (https://www.rogerlinndesign.com/) gave me some fantastic advice a couple years ago when I was trying to design switch caps: "Do you want to be a company that designs switch caps or one that designs synthesizers?" and that stuck. I don't want to design switch caps, so I bought them off the shelf, contracted someone to design my own, and moved on.
So to that end... just buy a couple keybeds from Fatar or someone else, or just grab a synth you already have or buy one off ebay and harvest the keybed from that (often times much cheaper than buying direct!)
Don't be afraid to spend money on tools. If you find something difficult, like soldering, I have not once regretted spending money on better tools. They grow with you and save you hundreds if not thousands of hours of unnecessary frustration. When you know you need a tool, find a way to get it.
Maybe I should make a blog post about this... hmm
Hope that helps!
- Is there a programmable module for audio (like EuroPi but w/ bipolar output)?
- Where is a good place to get started with DSP coding?
- Porting C++ DSP code to gen~
-
how to make an “experimenter”?
Check out Daisy DSP from ElectroSmith. They have an entire platform you can build your own synth upon. Many new EuroRack modules being released over the last ~1.5 years are built upon the Daisy SDK.
-
First pedal in five years - pedal pcb terrarium
Here is the GitHub https://github.com/electro-smith/DaisySP
- Oh that looks cool! Too bad it's $500..seems a bit much
-
Rendering audio blocks in a digital oscillator (hardware)?
For an excellent implementation of C++ embedded audio DSP, checkout the DaisySP project and associated hardware. The libDaisy audio drivers abstract this block processing well.
- Electronic music icon Korg makes music with Raspberry Pi
-
A Chord Synthesizer From Another Dimension
There is a github page for this that has downloadable firmware and a link to the firmware programmer which suggests that it’s running on a Daisy. Although it would be ethically super questionable at best, it probably wouldn’t be that hard to reverse engineer.
What are some alternatives?
hUGETracker - The music composition suite for the Nintendo Game Boy
MeeBleeps-Freaq-FM-Synth
Qv2ray - :star: Linux / Windows / macOS 跨平台 V2Ray 客户端 | 支持 VMess / VLESS / SSR / Trojan / Trojan-Go / NaiveProxy / HTTP / HTTPS / SOCKS5 | 使用 C++ / Qt 开发 | 可拓展插件式设计 :star:
supercollider - An audio server, programming language, and IDE for sound synthesis and algorithmic composition.
hUGEDriver - An easy-to-use, fast, tracker-based, public domain sound driver for Game Boy homebrew
Rack - The virtual Eurorack studio
devkitSMS - development kit and libraries for SEGA Master System / SEGA Game Gear / SEGA SG-1000 / SEGA SC-3000 homebrew programming using C language (and the SDCC compiler)
fv1-pedal-platform - Schematics, code, and pcb layouts for an FV-1 guitar effects pedal
PS - Single file synth + demo song
nts-1-customizations - Official repository for hardware customizations of the Nu:Tekt NTS-1 digital kit
miniaudio - Audio playback and capture library written in C, in a single source file.
curv - a language for making art using mathematics