INDUSTRY FIELD GUIDE
Musical instrument data for AI test-note records
Google's NSynth dataset provides a research example of labeled musical-note audio.
NAICS 339992 · Musical Instrument Manufacturing
Google's NSynth dataset provides a research example of labeled musical-note audio. An instrument manufacturer can propose its own original recording task with explicit instrument identity and observation context. NSynth dataset context
Create fictional instrument serial references, a recording manifest and self-authored test-note identifiers. State the microphone-view or position reference and recorded note label in the exercise. Ask which recording belongs to the selected instrument and test. Include a second take with the same filename but a different content identifier and a manifest missing its position reference.
Annotate instrument, take, note label, recording position, content identity and source ownership. Evaluate with a new naming scheme and original notes. Score filename equality treated as take identity, wrong-instrument matching and a missing capture condition guessed independently. The key should cite the manifest fields and retain incomplete context as unresolved.
Use contributor-owned recordings and original exercise records. Customer performances, licensed compositions, sampled media and third-party instrument files require appropriate authority. A licensing brief should state the recording-association task and independently checked examples. Establish buyer requirements before preparing a commercial archive or commissioning new capture.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
An audio clip's file name is not its performance identity
An original short note sequence is represented in a fictional recording manifest. No third-party audio appears.
| Record | Source | What it records |
|---|---|---|
| 1 | Manifest | Clip C8 from mock instrument I4, sequence N2, take 3. |
| 2 | Filename | I4_N2_take2.wav. |
| 3 | Session index | Take 2 is clip C7; both takes use the same sequence. |
Question for the model
Which take should C8 be labeled with?
Show the reference answer and checks
Records 1 and 3 identify C8 as take 3, while record 2's filename implies take 2. Keep the file-name conflict visible and use the manifest take for the linked record. Matching instrument and sequence cannot disambiguate takes on their own.
- Parsing a filename as definitive provenance
- Deduplicating separate takes of one sequence
Fields to preserve
- clip_id
- Pins the asset
- take_number
- Separates repeated performances
- manifest_conflict
- Preserves inconsistent metadata for review
Test another case
Provide an explicit rename correction and retain original and current file names without duplicating the clip.
Only contributor-owned recordings or scripts; no copyrighted repertoire, performer data or instrument-quality claims.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.