AVS 9.10.4

Source

VedSearch

Recording covers

one verse · AVS 9.10.4

Matched to this passage

Confirmed. The text the source says this recording recites matches this corpus's text for this passage.

The line behind the control

An accent trace: one turn for each of the 3 accent marks printed in this verse, a mark above the letter turning the line up and a mark below turning it down. It is derived from the text on this page and from nothing else. It is not measured pitch, not a reconstructed melody, and not a timing of the recording: the playhead moves across it because both run left to right, and no syllable is claimed to align with any moment of the audio.

Recitation tradition

Not stated by the source

Reciter

Not stated by the source

How it was matched

Re-mapped after correcting the source's Atharvaveda hymn division, which the original coordinate transform did not model. kanda 9: the source splits our 62-verse paryaya hymn 9.6 across source suktas 9.6 to 9.11 and renumbers its verses from 1 in each, so our sukta number runs 5 behind the source's from our 9.7 onward (our 9.10 is the source's 9.15). Our key 9.10.4 therefore corresponds to the source's 9.15.4, not to its 9.10.4. the source verse at 9.15.4 recites text letter-identical to this mantra; more than one source verse does, and this is the only one that falls inside the source-order window fixed by this mantra's nearest mapped neighbours. The whole hymn's verses map into one source chapter in preserved order, which is the structural corroboration that the correspondence is the edition's and not this row's.

Attribution

Recitation courtesy VedSearch (vedsearch.org).

One file per verse. The source serves audio as base64 inside JSON, so the media_url is not a media URL and must be fetched and decoded by the product's own streaming route. Replaces no existing record: the source verse 9.15.4 was not claimed by any of the 4,680 catalogued AV rows. Admitted 2026-09-19 under OWNER_DECISION_AUDIO_TWO_TIER_PUBLICATION as SOURCE_MAPPED_UNREVIEWED. Media re-fetched that day and confirmed to resolve: JSON document of 59233 bytes. Staging evidence retained: patha_type=SAMHITA; text_similarity=1.0; quality_class=COMMUNITY_ARCHIVE; evidence_layer=DETERMINISTIC_DERIVED.