Show HN: Guitoro, a virtual guitar you strum with your keyboard
A browser-based “virtual guitar” that you strum with a computer keyboard is impressing many musicians and non‑musicians with its playability, sound quality and polished UI, especially on mobile. Users highlight its value as both a creative instrument and a learning tool, praising features like key-based chord layouts, solo mode and built‑in songs, while requesting refinements such as more intuitive default fretboard orientation, custom tunings, multitouch, left‑handed options and MIDI support. Several comments also note its potential for accessibility and education, from assisting disabled players to serving as a lightweight alternative to traditional instruments and DAWs.
Overall Reception
- Strongly positive reaction: many found it “incredible,” “surprisingly playable,” and spent 10–30+ minutes just experimenting.
- Praised for UI/UX polish, smooth performance (including on older phones), and surprisingly convincing guitar feel for a browser app.
- Some see it as a powerful creative/learning tool; others frame it more as a fun toy/novelty rather than a serious practice/replacement for a real guitar.
Guitar Orientation & Views
- Major confusion around the default “Player view,” which initially showed a left-handed-looking orientation and low string at the top.
- Many guitarists said this clashes with how chords/tab are usually presented and with their playing muscle memory.
- “Tab” / “Audience” views (low string at bottom) are widely preferred; multiple users requested these as default.
- The creator later pushed an update improving the tab orientation and was encouraged to keep the old version as an explicit left-handed option and add a clear left-hand mode.
Interaction, Playability & Sound
- Strumming mechanics generally feel good, but users noted:
- Strings that stay the same across chord changes should keep ringing.
- Option needed to avoid auto‑strum on chord change.
- “Let ring” toggle and “arp” mode behaved buggy for some.
- Requests for more expressiveness: per-string picking within chords, fingerpicking, string bends, palm muting, dynamic volume tied to strum speed, simple ADSR/filters, body‑tap percussion zone.
- Built‑in amp/FX with overdrive/distortion/fuzz are appreciated, though some still hear a “MIDI-ish” character and want more realistic samples.
Keyboard Mapping & UX Suggestions
- Current layout: A-row = main chords in the key, Q-row = 7ths, Z-row = color chords.
- Several users find chord labels vs physical key positions confusing. Proposed alternatives:
- Numbers 1–7 for I–VII chords.
- Modifier keys (Shift/Alt/Ctrl) for up/down strum and major/minor/7th variations.
- Solo mode sparked interest in “musical typing”: treating the QWERTY keyboard itself as an instrument, even using AI to map songs to keystrokes.
- Suggestions for flipped keyboard mappings so players can hold a wireless keyboard like a guitar.
Learning, Accessibility & Use Cases
- Viewed as a strong learning/teaching aid; at least one music teacher plans to use it in class.
- Non‑guitarists reported feeling empowered to explore chords and composition.
- One story described a stroke survivor, unable to hold a guitar, engaging with the app enthusiastically.
- Users value:
- Built‑in songs and band accompaniments.
- Ability to paste chord/lyric sheets into “my songs.”
- There is demand for structured beginner lessons and tutorials, which are reportedly planned.
Feature Requests & Future Directions
- Frequently requested:
- Custom tunings (including C standard and arbitrary tunings).
- Ukulele mode.
- Left‑hand mode with correct headstock orientation.
- Multi‑touch on tablets/phones for picking multiple strings instead of zoom.
- Tap‑tempo input, MIDI I/O, and a VST or standalone/offline version.
- Some want a FAQ/about section describing how it was built and the role of AI.
Technical & Cross‑Platform Issues
- Mostly smooth on desktop and mobile, but reported problems include:
- Choppy audio on Brave.
- Broken layout on Firefox (Linux).
- Distorted sound after app switching on Android Chrome.
- Occasional issues with the “arp” toggle state.
- Users encouraged broader browser testing and fixes, as the core experience is otherwise highly praised.