How to Check a Chinese Instrument Recording’s Source and Credits

Read the description before trusting the instrument tag

A recording title or search tag is a starting claim, not a complete instrument identification. Read the original file description, identify who supplied the label, and distinguish a solo, an ensemble, a practice sample, a loop and a software-produced example. Record the exact source before writing a listening caption.

This guide audits five publicly accessible Freesound file pages as checked on 7 November 2026. We read their metadata and uploader descriptions; we did not audition, download, measure or independently authenticate the audio. The worked results therefore show what those descriptions support, what they leave unknown, and where an instrument label must be corrected.

The site’s audio license notes explain its publication policy. This worksheet answers a different reader task: how to inspect a specific source record and avoid assigning an ensemble, a software patch or an unnamed performer to the wrong claim.

Keep identity, dates and permission in separate fields

1. Source identity: stable original URL, exact file title and account name.
2. Instrument claim: what the description actually says, including solo, ensemble, software or uncertainty.
3. People and work: named performer, ensemble, composer and composition, if supplied. The uploader is not automatically the performer.
4. Dates: recording date and upload date separately. Leave a missing recording date blank.
5. Extent: full performance, selected passage, sample or loop, with the source’s duration.
6. Reuse: the file’s displayed licence and link, credit requirements, and any separate permission evidence.

Then write one restrained caption and one remaining question. A file description can support an uploader-described identification without proving acoustic provenance, a complete performer list or every instrument heard. A tag may help discovery while giving less context than the description.

Case 1: a pipa-related file is an ensemble rehearsal

The file Pekin-Univ-Orchestra-4.wav, uploaded by xserra, describes a rehearsal of the Chinese Orchestra of Pekin University: a dizi solo with pipa accompaniment. It says the rehearsal was recorded with a Sony PCM D50 on 3 June 2012. The upload date is 31 July 2012, and the displayed duration is 1:06.744.

A useful caption is: “Uploader-described Chinese-orchestra rehearsal, with dizi solo and pipa accompaniment; recorded 3 June 2012, uploaded 31 July 2012.” Calling it an isolated pipa tone would erase the stated lead instrument and ensemble context.

The record does not name individual performers or a composition. It does not supply a time at which we independently isolated a pipa. Keep those fields unresolved. A tag mentioning another instrument cannot establish which player produces a particular audible event without further evidence.

Source: [2].

Case 2: “guzheng solo” names an iPad GarageBand example

The file guzheng solo, uploaded by neolein on 25 May 2019, explicitly describes “solo guzheng from ipad garageband.” It gives a minor-pentatonic description and a displayed duration of 1:25.090.

A suitable caption is: “Guzheng-labelled iPad GarageBand software example, as described by the uploader.” The page is not evidence of a yangqin performance. Nor does the word “solo” certify that an acoustic guzheng was recorded in a room, establish a microphone setup, or measure the real instrument’s volume.

If you are comparing actual yangqin and guzheng sound production, this file cannot settle the difference. You need an identified acoustic performance or demonstration of the appropriate instrument, with its source and passage clear. Correct the identification before adding a more elaborate listening exercise.

This source shows why reading one short sentence can be more useful than accepting a familiar instrument tag. Software examples can be useful for their own purposes when labelled honestly; they answer a different question from an acoustic instrument recording.

Source: [4].

Case 3: another file by the same account is a mixed plugin scene

The separate file blossom valley in paradise by neolein names Chinese YangQin, guzheng and other plugins. It is classified as multiple instruments, shows 6 June 2020 and duration 1:02.997, and displays CC0.

A useful caption is “Uploader-described mixed YangQin/guzheng plugin scene.” This record does name YangQin; the problem is treating its software ensemble context as an isolated acoustic instrument demonstration. It does not establish the physical model, playing action or practice-room volume of a real yangqin.

Do not confuse it with guzheng solo, file 472707. The uploader is the same, but the file IDs, titles, descriptions, durations and dates differ. Read the actual URL behind a player before deciding that its source is wrongly attributed. The two source records support different bounded captions.

Source: [5] [4].

Cases 4 and 5: a practice sample and a short loop

If columns extend beyond the screen, swipe or scroll inside the table to read them.

The erhu description supports a practice-sample context. It does not establish the account owner as the named performer. The dizi description reports recording equipment and reuse of recordings, but the resulting four-second loop does not represent a whole performance or every regional playing style.

If your question needs phrasing across a long passage, a very short loop may be the wrong extent. If it needs a measured tempo, the filename is insufficient. Record the limit and find the source or analysis that answers the actual question.

Source: [1] [3].

Permission and instrument identification are two checks

The observed erhu and both neolein file pages display CC0. The rehearsal and dizi-loop pages display Attribution 4.0. These labels describe the licences supplied on those records; they do not identify an instrument or authenticate a performer.

The official CC BY 4.0 deed summarises sharing and adaptation with appropriate credit, a licence link and indication of changes. It also says not to imply endorsement and not to add legal or technological restrictions that prevent permitted uses. Preserve the source title and supplied creator/account details, distinguish an edit from the source file, and consult the linked terms for the intended reuse.

The official CC0 deed summarises a waiver to the extent permitted by law and reuse without permission, including commercial use. Its limits include rights such as privacy, publicity and trademarks. A waiver label does not independently prove that an uploader owns every right.

These are human-readable deed summaries, not a full legal-code review. This article links the source records and does not republish their audio. A correctly credited wrong instrument is still a wrong identification; a correctly identified recording still needs the applicable reuse check before you copy it.

Source: [6] [7] [1] [2] [3] [4] [5].

Make the caption match the evidence

Work in two passes. In the first, read the file title, description, creator fields and dates without adding listening adjectives. In the second, if you can access a suitable recording, observe a specific passage and mark its start and end. Keep what the source says separate from what you actually heard or saw.

For an ensemble, a clear programme, score or visible identified performer can help connect a part to an event. For a software example, retain the software label. For an anonymous clip, a resemblance to “bright,” “mellow” or “Chinese” does not supply missing provenance.

Do not invent a timestamp to make a source card look complete. The cases above have file durations, not our auditioned passage timings. Copy only supplied dates and names. An upload date is not a recording date, and a creator account is not an automatically verified performer credit.

When a site caption and original description disagree, preserve the original URL and the exact mismatch, correct or remove the unsupported label, and check other pages that use the same data record. A single shared audio object may populate an instrument page, a comparison desk and a licence list.

Five questions to use on the next file

For the ensemble context, continue to the orchestra section guide. For visible flute construction, use the dizi, xiao and xun comparison.

Keep the source with your next question

Use this blank record with one actual file or score. Leave unsupported dates, people and relationships unknown; a precise unresolved question is more useful than a filled-in guess.

RECORDING SOURCE AND CREDIT NOTE

Exact original URL / file ID / title:
Uploader account / separately named creator:
Stated instrument and acoustic / ensemble / practice / loop / software context:
Named performer / ensemble / work, or unknown:
Stated recording date, or unknown:
Upload date separately:
Displayed duration:
Passage start / end ONLY if actually auditioned:
Displayed licence / licence URL:
Credit supplied / changes made / proposed use:
Supported caption:
Missing fact / next source needed:

Blank reader worksheet. This article checked metadata; it did not audition or measure audio.

Download the blank recording source and credit note (TXT). Keep any personal lesson or performer details in your own copy.