gigdump(1)

💖 gigdump(1) 💖

okay bestie, gather round — this is gigdump, one of the libgig tools, and it's literally the vibe-check machine for your Gigasampler files. 🎀

---

✨ NAME ✨

gigdump — list information about a Gigasampler (.gig) file. That's it. That's the job. She reads, she reports, she does not touch your stuff (unless you ask her to, see below 👀).

---

🌈 SYNOPSIS 🌈

gigdump [OPTIONS] GIGFILE

---

🦋 DESCRIPTION 🦋

So like, by default? She just prints out a list of all available samples, real-time instrument scripts and instruments inside your Gigasampler (.gig) file, plus the detailed info about their properties and settings. Everything you'd wanna know, handed to you, no cap. 💅

---

👑 OPTIONS 👑

• GIGFILE — the filename of the Gigasampler file. That's your main character right there. ⭐
• --instrument-names — only lists instrument names and their index number. Short, sweet, no extra lore. 🍓
• --rebuild-checksums — rebuilds the checksum table for all samples. Go read the description of the --verify option first for the whole tea on sample checksums in general, okay? 🫖

Usually you only need --rebuild-checksums if the samples' CRC checksum table itself got damaged. The --verify option will tell you whether that's actually the case, and it'll even suggest you use --rebuild-checksums to repair the table when it is. If only individual samples got damaged, you'd lowkey rather want to replace just those damaged samples with gigedit(1), for example — go read the --verify description for the reasons why. 👀

Heads up fr fr: when you use --rebuild-checksums, all checksums of all samples will be regenerated. Which means you should manually check all your samples once after using this option. And bestie, "manually check" means by using your ears, or by exporting the samples — NOT by using the --verify option. Because --verify cannot identifiy damaged samples that were damaged before the entire checksum table got regenerated. It literally can't see them. 💀

• -v — print version and exit. That's it, that's the whole thing. ✨
• --verify — checks the raw wave data integrity of all samples and prints the result of that check. 🧚

Here's the lore: for all samples of a gig file, a correspondig CRC32 checksum is stored alongside its raw wave form data whenever a conscious change to the wave form data was performed. So when you call gigdump with this option, all samples get scanned and compared against their existing checksums to detect any damage to individual samples. And the individual damaged samples? gigdump lists them for you in this case. 📋

Warning, and I mean it: since essentially the entire file has to be read, this can take a long time. That's exactly why this check is not performed by default — i.e. not every time a gig file is loaded for regular use, for example. 😭

So accordingly, you may use --verify from time to time to explicitly check whether your gig files have been damaged for some reason — i.e. after modifying them with an instrument editor like gigedit(1). 🎀

And if damaged samples were found? You may replace those damaged samples with gigedit(1). By doing this, only the replaced samples' checksums will be updated. All other checksums remain untouched. Which is exactly why this approach is recommended over using --rebuild-checksums in those cases. Iconic behaviour, honestly. 👑

---

🔥 SEE ALSO 🔥

gigextract(1), gigmerge(1), gig2mono(1), gig2stereo(1), wav2gig(1), dlsdump(1), rifftree(1), akaidump(1), sf2dump(1), korgdump(1)

iykyk — the whole libgig friend group is in the chat. 🫶

---

💀 BUGS 💀

Check and report bugs at http://bugs.linuxsampler.org — not me being dramatic, just please actually report them instead of suffering in silence bestie. 🙈

---

🌸 AUTHOR 🌸

Application and manual page written by Christian Schoenebeck <cuse@users.sf.net> — absolute legend, gave us the whole tool. 👑

---

<div>so yeah, that's the page 💖</div>

this manual came out of libgig 4.5.2, dated 08 May 2018 — yeah she's been around a while and she's still slaying. mwah 💅✨🎀🦋