Designing for other people is a lot harder than designing for yourself, which makes this project harder than almost all of my previous ones - the aim is to get DrumKid into the hands of as many musicians as possible, which means I actually have to listen to constructive criticism. I've tried to elicit feedback throughout the project, but this has ramped up recently as I approach my self-imposed deadline of making the first batch of finished DrumKids by November.
I've now received comments from all three musicians who are currently using the latest prototype of DrumKid, so I thought this was a good point to share the feedback I've had throughout the project and how I've adapted the design based on it (or plan to in the near future).
My main sources of feedback/criticism have been:
- Informal feedback from friends (usually when I bring the latest prototype to the pub)
- YouTube comments (I'm one of the few creators whose comments are nearly always nice)
- Hackaday (comments, chat, and mentoring session)
- E-mail (usually unsolicited but very helpful!)
- Feedback from musicians who are currently using DrumKid
Overall, spread over these various mediums, I've had a lot of helpful comments throughout the project! I thought it would be helpful to document them here, roughly in chronological order.
Source | Comment | Response |
---|---|---|
Early feedback from friends | Too much high-frequency noise | Improved the filter circuit |
Early feedback from friends | Output is too quiet (this was with the volume on max in a noisy pub - the filter was reducing the output too much) | Added an amplifier chip to boost the signal |
Early feedback from friends | The early single-knob design was too confusing and difficult to play | I agreed with this comment and redesigned DrumKid to feature four knobs instead of one |
Email and YouTube comments | DrumKid should be compatible with Eurorack synthesizers, and the different parameters should be controllable via external control voltages | Creating a DrumKid Eurorack module would be a separate, complex project, but there seems to be a lot of demand for it, so I've started making notes about a potential future design, maybe using a Teensy |
Email and YouTube comments | DrumKid should be able to synchronise its tempo with other instruments | This has come up quite a lot, often enough that I'm considering adding this feature to the final design, although it might delay the release by a couple of weeks |
YouTube comment | It would be good to be able to load custom sample sets (different kicks, snares, etc) | Although it would be hard to make this part of the core, supported features of DrumKid, switching the samples is such an obvious customisation that I'd like to document a way for people to do it. This has made me realise that I should write a secondary "hackers' manual" for DrumKid to help people who want to customise their instrument |
Tester | There should be more different styles of basic drumbeat, such as drum 'n' bass, reggae, waltz, etc | I agree with this, and will spend some time adding more beats for the next version |
Tester | The volume knob seems to be mounted backwards | This is true - either the KiCad footprint is wrong or I did something stupid, but I will fix this in the next version of the PCB |
Tester | There should be more than six slots to save beats in | This is probably fair. There is plenty of space in the EEPROM to save more beats, but I wanted to keep the user interface nice and simple (six buttons, six save slots) - I'm considering increasing this to six banks of six (36 slots) |
Tester | The loading process is unreliable and confusing | I hadn't noticed this before, but I think there is a bug in the code, so I will investigate |
Tester | The LEDs are too bright | I noticed this, too, and had already planned to reduce the brightness for the next version, which should also have the benefit of increasing battery life |
Tester | Beats in non-standard time signatures have strange emphases | My previous, slightly lazy approach to non-4/4 time signatures was to simply truncate or repeat a 4/4 pattern, but this is musically bad. I should either have various versions of each beat for different time signatures or perhaps just have a greater range of preset patterns, including "good" 3/4, 5/4, and 7/4 patterns |
Tester | For some parameters, the left position is a neutral, unchanged sound and the right position is a "crazier" sound, but sometimes it's the other way round, which is unintuitive | This is a fair point. I never had a good, uniform justification for why some parameters go left-to-right and others right-to-left, so I will standardise this behaviour |
Tester | Replacing the batteries would be difficult | This is perhaps a weakness of the current design - to replace the batteries you need to undo six screws. It only takes about a minute if you have a screwdriver, but not everyone does! I'm going to see if it's possible to source some knurled thumbscrews so that the batteries can be replaced without a screwdriver |
Tester | It's hard to start messing around with DrumKid without consulting the manual - it would be good to have the parameters written underneath the knobs | This was mentioned by two different testers, so I should probably add explanatory text on the next PCB. I rather like the minimalism of the current design, but even I kept forgetting which knob controlled which parameters, so I'll try and find an aesthetically pleasing way to include this text |
Tester | The pitch control for the drone is difficult to use | I agree with this, but it's also hard to think of a better way to do it. I'll take this on board and try to come up with a better implementation |
Tester | An LCD to display the BPM (tempo) would be really useful | I agree that it would be good to see the exact current tempo. I could perhaps try and display it using the LEDs somehow, or even consider replacing the row of LEDs with a seven-segment display, but that would be quite a radical change |
Tester | It would be good to have either stereo or multiple outputs, so that different drums could be recorded separately | I think this is beyond the scope of a low-cost drum machine, but I'm considering this feature for the Eurorack version |
Tester | It would be great if the "zoom" parameter (which controls whether the random extra hits are quarter-notes, eighth-notes, sixteenth-notes, etc) could do triplets | I also found myself wanting this feature while playing DrumKid, but could never figure out a good, unambiguous way to implement it. Now that I know it's a more universally-wanted feature, I'll keep trying! |
It's important to note that I have only included the negative comments in the table above! I've also had lots of positive comments, but there wouldn't be a lot of point listing them all here, besides feeding my ego. I'm likely to get a few more comments from my prototype testers over the next few days, but for now I've got plenty of food for thought.
It's a big relief that no-one pointed out any obvious, fundamental weaknesses in the design. I think I can address pretty much all of the above comments by updating the code and PCB layout (and maybe changing the type of screw that secures the back panel, which isn't a big deal).
Overall, I'm really happy with how DrumKid has been received so far, both online and in real life, and I'm excited to get started on what I hope will be the final revision of the design.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.