Show Audio Tags 📋

Show Audio Tags 📋 is the debugging node of the comfy-audio-tagger pack, and its sibling Read Audio Tags 🔍 is the polite version. Where the reader extracts 17 specific fields into tidy named outputs, this one opens the file and dumps every tag it can find into a single formatted text block - including the frames the reader doesn't bother surfacing. You want it exactly when something about a file's metadata is wrong and you need to see the raw truth.

The one input, the one output

Just file_path in (a plain string - wire it from any save node's file_path output, or paste a path), and one tags_summary string out. That's the entire node. The output is a formatted block that starts with the filename and detected container type, then lists every metadata key and its value on its own line, with a footer telling you whether cover art is embedded.

Two structural details shape how you use it. First, it's not an output node - no popup on execution, no UI box. The string comes out on the tags_summary output, so you wire it into something that shows text: a text-display node, a "show text" utility, or straight into an LLM node if you want the raw tags parsed by something smart. Second, it works on any file mutagen can open - MP3, FLAC, M4A, OGG, AIFF - so it doubles as a general "what tags does this arbitrary audio file carry?" inspector, not just a checker for files this pack saved.

Why you'd actually reach for it

Read Audio Tags gives you nice, typed fields but only for the tags it knows to look for. Show Audio Tags gives you everything. The difference matters in two situations:

• A tag isn't reading back the way you expect. The M4A node in this pack, for instance, merges the license into the comment atom - open that file here and you'll see the concatenated License: ... | ... string laid bare, exactly as stored. That's the moment the raw dump beats the curated reader.
• You're inspecting files you didn't create. Sample packs, splices, downloads - the reader guesses at fields, the inspector shows what's really there. "No tags found or unsupported format" or "File not found" come back as plain text in the output, so even a broken input tells you its story instead of silently failing.

The honest framing: this is a tool you use a few times to debug, not a permanent fixture of your music workflow. It sits on your canvas, you check a file, you remove it. That's fine - that's what a debug node is for.

Install

Same as the rest of the pack - it's one small repo with a single dependency:

cd ComfyUI/custom_nodes
git clone https://github.com/lakeconstance78/comfy-audio-tagger
cd comfy-audio-tagger
pip install -r requirements.txt   # Windows portable: ..\..\..\python_embeded\python.exe -m pip install -r requirements.txt

or search "ComfyUI Audio Tagger" in ComfyUI Manager, then restart.

It's the least glamorous node in the pack and the one that will rescue you the first time a tag doesn't come back the way you expected. Keep it in your back pocket; you'll know when you need it.