bazmonk / digigurdy-baz

DigiGurdy Teensy Code
MIT License
16 stars 10 forks source link
arduino hurdy-gurdy midi teensy teensy35 teensy41

digigurdy-baz

See the wiki here for more documentation.

See the code documentation here.

Check out version 3.0.0! (NEW)

Other "testing" branch changes since v1.0:

About

This is the software repository for the digigurdy code (https://digigurdy.com).

I tried it and I don't like it. Now what?

This repository includes (in the other folder) a recent version of John Dingley's original digigurdy code, as well as a version of it I modified with a different tuning setup. Follow the same installation instructions above to put the old code back, and thanks for trying it out!

If there's something particular about it that annoys you, feel free to open an issue (see the top of this page) for me to suggest what you'd like me to change, and I'll see if I can accommodate it.

I found a bug.

Please open an issue (top of the page here) and describe it for me. If it's a build problem, I'd like to see the output of Teensyduino (from the bottom panel) when it fails.

Big bonus points (I'll make a credits screen for you all) if you can reproduce it and tell me how so I can fix it. Git issues here generate emails for me so it's the preferred way to document them (versus facebook or some other method).

I want it to do something it doesn't do.

Feel free to open an issue. I'll see what I can do. This is all in my spare time so responsiveness is what it is, but I will see your issue pretty quick.

Part of rewriting this was with maintainability and extendability in mind. The code is well-formatted, I've abstracted the strings, MIDI interaction, buttons, keybox, crank, etc. into easy-to-use classes. I put a lot of effort into using readable variables, commenting the crap out of the code, and not doing anything needlessly "clever"... I tried to make it easy for you to explore adding to it yourself.

I haven't really thought of how I'll handle a bunch of competing pull requests because I'm not expecting it, but feel free to clone the repo, make improvements, and submit a pull request. I'm open to them.

Acknowledgements

HUGE credit to John Dingley, his amazing creation (the DigiGurdy itself), and the original codebase that he wrote. He worked out the display, the way the original crank worked, the interaction with the MIDI subsystem... I'm standing on his shoulders.