Looking for electronic-drum testers

Offen
#27 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
58/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
macos, unity
Bereich
game-dev, testing-qa

Rechercherichtung

Read #14 for the reproducibility requirements and acceptance checklist, then run HitTheKit on macOS with the electronic drum kit or MIDI percussion controller. Check discovery, guided setup, mappings, gameplay, and disconnect/reconnect behavior. Done means submitting the results through the Hardware compatibility issue form with the device model, OS version, connection type, and concise failure details while removing private identifiers.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

good first issue hardware help wanted

Help test HitTheKit with real electronic drums

HitTheKit needs reproducible compatibility reports from people who own an electronic drum kit, drum module, or MIDI pad controller.

You do not need to be a developer. A short, carefully documented smoke test is useful whether the device works perfectly, works partially, or is not detected.

Who we are looking for

Testers with:

  • an electronic drum kit, drum module, or MIDI percussion controller;
  • macOS on Apple Silicon for the current CoreMIDI runtime path;
  • any experience level, including complete beginners.

Keyboard gameplay is cross-platform, but production MIDI device support is currently focused on macOS CoreMIDI. Windows and Linux MIDI backends are future work.

What to test

  1. Does HitTheKit discover the device?
  2. Can you select it and start guided kit setup?
  3. Are kick, snare, hi-hat, toms, crash, and ride detected correctly?
  4. Does a short gameplay input smoke test work without disconnects or duplicated hits?
  5. If you disconnect and reconnect the device, does the application recover cleanly?

How to report a result

Please open a report using the Hardware compatibility issue form:

https://github.com/Codewriter90x/HitTheKit/issues/new?template=hardware_compatibility.yml

The reproducibility requirements and acceptance checklist live in #14. This issue is the public call for testers; individual device results should be submitted through the form so they remain searchable.

Useful information includes:

  • operating system version and architecture;
  • drum module or controller model;
  • USB MIDI, MIDI interface, or other connection type;
  • discovery, mapping, gameplay, disconnect, and reconnect results;
  • concise error text when something fails.

Privacy and content boundary

Before submitting, remove:

  • serial numbers and device identifiers;
  • usernames, email addresses, hostnames, and home-directory paths;
  • full raw logs or unfiltered MIDI captures;
  • commercial audio, charts, MIDI files, lyrics, or artwork.

Never upload credentials, tokens, private keys, Apple account details, or Unity license data.

Not ready to test yet?

You can still help by:

  • commenting with the drum module you would like HitTheKit to support;
  • sharing this issue with electronic-drum players;
  • reacting with 👍 so we can estimate interest.

Thank you for helping build a transparent compatibility matrix for real kits.

Vorherrschende Sprache
C#
Sterne
0
Forks
0
Ø Merge
16 Std. 9 Min.
Gemergte PRs (30 T.)
7

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Codewriter90x/HitTheKit

Alle Issues in Codewriter90x/HitTheKit

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.