TRACKVERIFY(1)

💖 TRACKVERIFY — the trackverify(1) page, but make it cute 💖

okay bestie, listen up, because this is the page for trackverify(1) from the Track Verify manual and it is actually so useful 🦋

---

✨ NAME ✨

trackverify — verifies the data content of tracks 👑

no fr, that's the whole job. it checks your audio files and tells you if they're correct. that's it. that's the gig. 💅

---

🌸 SYNOPSIS 🌸

trackverify [OPTIONS] <track 1> [track 2] ...

you give it a track, or a whole lil lineup of tracks, and it does its thing. slay. 🎀

---

🫶 DESCRIPTION 🫶

so trackverify takes one or more audio tracks, verifies their files for correctness, and then shows you the results on standard output. easy.

and here's the part that's giving main character energy: if you hand it directories instead of files, it goes and searches them recursively for any supported audio files, and verifies those too. it's literally doing the scavenger hunt for you. 🔥

---

💅 OPTIONS 💅

• -h, --help — shows you the list of options and then dips. exit stage left. ✌️
• -t, --type=TYPE — restrict your search to one audio format. if you give it one, only files of that audio type get verified. you can use this multiple times if you're feeling greedy. and for a list of available audio formats, try: -t help 🌈
• -S, --no-summary — don't show the summary info once verification is done. sometimes you just want the receipts, not the recap. 💀
• -R, --accuraterip — verify your tracks against the ones in the AccurateRip database 👑
• --cue=FILENAME — the cuesheet to use when you're verifying a CD image against the AccurateRip database. bring your own map. 🗺️
• -j, --joint=PROCESSES — the max number of tracks to verify at one time. if you've got multiple CPUs or CPU cores, letting trackverify(1) use all of them at once can make verification faster. but — and this is important, bestie — the max speed is likely to be limited by I/O-bound stuff rather than CPU-bound stuff. so don't expect miracles. 😭
• -V, --verbose=VERBOSITY — how much output you want. pick between 'normal', 'quiet' and 'debug'. choose your own adventure. 🎀

---

🔍 VERIFICATION 🔍

not every audio format carries the same amount of error protection, okay? that's just the truth. what Python Audio Tools is capable of detecting depends on the audio format. iykyk.

for example, FLAC files get their frame checksums verified, plus the file's MD5 hash on top of that. files packed in Ogg containers get their Ogg page checksums verified. cute, right?

but for formats like Wave? there's no standard way to verify that its data content is correct. all we can do is make sure its blocks of data are the correct size. that's it. that's the whole vibe check. 🙈

---

👑 ACCURATERIP 👑

verifying lossless tracks against AccurateRip's online database is a way of making sure your rips are identical to rips other people made. the confidence level is the number of other people who have the same rip, so a bigger value means your rip is consistent with theirs. iconic.

but listen — not finding your rip in the AccurateRip database does not necessarily mean the rip is bad! the CD might be new, rare, or a different pressing than the one in the database. so don't spiral. 💖

---

🌈 EXAMPLES 🌈

check all FLAC files in the current directory:

trackverify *.flac

check only MP3 files found in the directory audio/:

trackverify -t mp3 audio/

---

🦋 SEE ALSO 🦋

audiotools-config(1), audiotools.cfg(5), cdda2track(1), cddainfo(1), cddaplay(1), coverdump(1), covertag(1), coverview(1), dvda2track(1), dvdainfo(1), track2cdda(1), track2track(1), trackcat(1), trackcmp(1), trackinfo(1), tracklength(1), tracklint(1), trackplay(1), trackrename(1), tracksplit(1), tracktag(1)

go read them all, bestie, they're all part of the same family 🫶

---

🌸 AUTHOR 🌸

Brian Langenberger

---

and that's a wrap on the trackverify(1) page, dated 2025-03-10 💜 go verify something and feel soooo accomplished, you absolutely ate 💅✨🎀