Papers › SSAST: Self-Supervised Audio Spectrogram Transformer
SSAST: Self-Supervised Audio Spectrogram Transformer
Yuan Gong, Cheng-I Jeff Lai, Yu-An Chung, James Glass
Recently, neural networks based purely on self-attention, such as the Vision Transformer (ViT), have been shown to outperform deep learning models constructed with convolutional neural networks (CNNs) on various vision tasks, thus extending the success of Transformers, which were originally developed for language processing, to the vision domain. A recent study showed that a similar methodology can also be applied to the audio domain. Specifically, the Audio Spectrogram Transformer (AST) achieves state-of-the-art results on various audio classification benchmarks. However, pure Transformer models tend to require more training data compared to CNNs, and the success of the AST relies on supervised pretraining that requires a large amount of labeled data and a complex training pipeline, thus limiting the practical usage of AST. This paper focuses on audio and speech classification, and aims to reduce the need for large amounts of labeled data for AST by leveraging self-supervised learning using unlabeled data. Specifically, we propose to pretrain the AST model with joint discriminative and generative masked spectrogram patch modeling (MSPM) using unlabeled audio from AudioSet and Librispeech. We evaluate our pretrained models on both audio and speech classification tasks including audio event classification, keyword spotting, emotion recognition, and speaker identification. The proposed self-supervised framework significantly boosts AST performance on all tasks, with an average improvement of 60.9%, leading to similar or even better results than a supervised pretrained AST. To the best of our knowledge, it is the first patch-based self-supervised learning framework in the audio and speech domain, and also the first self-supervised learning framework for AST.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2110.09784")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2110.09784", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2110.09784")
Code
Syntology 16 code samples harvested from 2 repositories linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 6 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 1 sample from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 15 samples from 1 repository, 12 ran (6 with no instrument failure; 6 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:
- siavashshams/ssamba, community (archive-listed): harvested for another paper, listed under the repository
Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
16 samples harvested: 13 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 1 of the 16 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.
ced6bc2bfdfe0059 · report
fixture: signature n_position:int/0/int, d_hid:int/0/int · returned Tensor · level recorded 2026-09-22 571ae4f8e76e6bc8 · report
fixture: signature output:ndarray/2/float, target:ndarray/2/float · returned list · level recorded 2026-09-24 5ee11f4af0d2fc1e · report
fixture: signature I:Tensor/3/float, A:Tensor/2/float · returned Tensor · level recorded 2026-09-24 e469cef4384ff73a · report
fixture: signature auc:float/0/float · returned float64 · level recorded 2026-09-24 5ea88601f05850d6 · report
fixture: signature a_dir:str/0/str · returned list · level recorded 2026-09-24 e217fb47bef3abe4 · report
fixture: signature a_dir:str/0/str · returned list · level recorded 2026-09-24 1c75a85694e30f0b · report
fixture: signature label_csv:str/0/str · returned list · level recorded 2026-09-24 c15efdd12442aeb4 · report
fixture: signature index_list:list/1/str, label_csv:str/0/str · returned list · level recorded 2026-09-24 a8fb3f62e2a901d7 · report
fixture: signature label_csv:str/0/str · returned dict · level recorded 2026-09-24 ad2738e74fab6072 · report
fixture: returned dict · level recorded 2026-09-24 cbf115a314bcd23e · report
fixture: signature label_csv:str/0/str · returned dict · level recorded 2026-09-24 546678fcbd2854db · report
fixture: signature M:Tensor/3/float, simtype:str/0/str · returned Tensor · level recorded 2026-09-24 ecb5ae1f3a358b96 · report
fixture: signature args:Args/0/?, epoch:int/0/int · returned dict · level recorded 2026-09-24 340de5fa0cf72870 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Audio Classification | Balanced Audio Set | SSAST-PATCH | Mean AP | 31.0 | #6 of 8 | Archive leaderboard | report |
| Audio Classification | Balanced Audio Set | SSAST-FRAME | Mean AP | 29.2 | #7 of 8 | Archive leaderboard | report |
| Speaker Identification | VoxCeleb1 | SSAST-FRAME | Accuracy | 80.8 | #9 of 12 | Archive leaderboard | report |
| Speaker Identification | VoxCeleb1 | SSAST-FRAME | Top-1 (%) | 80.8 | #9 of 12 | Archive leaderboard | report |
| Speaker Identification | VoxCeleb1 | SSAST-PATCH | Accuracy | 64.2 | #11 of 12 | Archive leaderboard | report |
| Speaker Identification | VoxCeleb1 | SSAST-PATCH | Top-1 (%) | 64.2 | #11 of 12 | Archive leaderboard | report |
| Spoken Command Recognition | Speech Command v2 | SSAST-FRAME | Accuracy | 98.1 | #1 of 4 | Archive leaderboard | report |
| Spoken Command Recognition | Speech Command v2 | SSAST-PATCH | Accuracy | 98.0 | #3 of 4 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections