gig2stereo(1)

📦
version 4.5.2 · 4 versions
, in nixos 26.05, ubuntu resolute, ubuntu stonking

✨ gig2stereo — the libgig tools era ✨

okay bestie, sit down, because this one is a glow up for your .gig files 💅 (it lives in the libgig tools manual, section 1, iykyk)

🎀 NAME 🎀

gig2stereo — literally converts Gigasampler (.gig) files from mono pairs into true stereo. no cap.

🌸 SYNOPSIS 🌸

gig2stereo [ OPTIONS ] FILE_OR_DIR1 [ FILE_OR_DIR2 ... ]

🦋 DESCRIPTION 🦋

so the vibe is: you hand this girl a list of Gigasampler (.gig) files and/or directories as argument(s), and she converts the individual Gigasampler files from two separate mono sample pairs into true stereo interleaved format. any directories you pass get scanned for .gig files, bestie. 🫶

important: the Gigasampler files are directly modified, not copied. it is giving commit-and-pray, so back up first, fr fr.

and since at this point the Gigasampler format only defines mono and stereo samples, this program currently also assumes all samples in the .gig files you give it are either mono or stereo. that's the whole menu. 🌈

the lore (background): the Gigasampler/GigaStudio format lets you create stereo instruments in two ways — either by referencing true stereo (interleaved) samples in the instruments, or by referencing a pair of (two) mono samples. unfortunately LinuxSampler does not support the latter at the moment 😭, so if a gig instrument uses mono sample pairs, you will still hear it in mono. this tool was created to circumvent this issue by letting you convert gig files to use real stereo (interlaved) samples instead. and even if LinuxSampler would add support for mono sample pairs, it would be less efficient than using real stereo samples — both concerning disk streaming and DSP processing after streaming input. so like, it's a win-win. 👑

after conversion, you will find all newly created true stereo samples in separate new sample group(s), which will be postfixed with " STEREO" in their group names. so you should easily be able to distinguish the newly created true stereo samples (i.e. when editing the .gig file with gigedit(1)) from old samples. 💖

also, if the original (now replaced) mono samples were postfixed with a channel indicator in their sample names (i.e. "Spiccato D3 -L"), the new stereo samples will have a similar sample name, but without such an audio channel indicator at the end of their names. thus in the mentioned example, the newly created stereo sample would be named "Spiccato D3" instead. iconic behaviour honestly. ✨

💅 OPTIONS 💅

  • FILE_OR_DIR1 — Gigasampler (.gig) filename or directory 🍓
  • FILE_OR_DIR2 — Gigasampler (.gig) filename or directory 🍓 (yes bestie, you can keep stacking them, the synopsis literally says ...)
  • --force-replace — force replacing any found old mono sample reference by the new true stereo samples. by default certain references of the old mono samples are not replaced by new true stereo samples, usually because the respective old mono reference is been used in an instrument context that seems to be entirely a mono use case, not stereo, and thus replacing the mono sample reference by stereo ones might not be intended for the respective instrument. because there might indeed be instruments in the same .gig file which are designed as explicit mono variant (i.e. to allow the musician to save resources while playing, or for live mix-down reasons, which are usually mono on live venues). by using --force-replace all those old mono sample references in question will also be replaced by the new stereo sample references. 🔥
  • --incompatible — also match incompatible mono samples as pairs. by default, when searching for potential mono samples that could be combined to true stereo samples, some sanity checks are performed. thus if two mono samples have completely different characterstics (i.e. different fine tune setting, different loop types) then they are by default considered to be incompatible and will not be merged to a true stereo sample, to avoid undesired audible errors in the modified file. under certain circumstances you might want to circumvent this sanity check, for instance when you think that few cents fine tuning difference in the mono samples are no reason for you to not merge them into a stereo sample. in this case you can use this option to force the conversion. however certain fundamental incompatibilities are still not ignored, even if you use --incompatible — for example if the two mono samples have different bit depth, sample rate or loop start and loop end points. in such cases those mono samples will still not be merged to stereo samples, because the actual result of the merge under that condition will certainly not be desired. 🫣
  • --keep — keep old mono samples. by default old converted mono samples, if they are not referenced by any instrument anymore, will automatically be deleted after conversion. by using this argument it will preserve all of the old mono samples. 🧚
  • -r — recurse through subdirectories. 🌸
  • -v — print version and exit. ⭐
  • --verbose [LEVEL] — be verbose and print additional information while converting. the additional numeric argument is optional, it allows one to define the verbosity level (1 .. 2, default: 1). 💜

👑 SEE ALSO 👑

gig2mono(1), gigextract(1), gigdump(1), gigmerge(1), wav2gig(1)

the whole friend group, honestly. go say hi. 🌈

💀 BUGS 💀

check and report bugs at http://bugs.linuxsampler.org

(not me telling you to go file a bug report, but like, do it, they wanna hear from you 🙈)

🌸 Author 🌸

application and manual page written by Christian Schoenebeck <cuse@users.sf.net>

okay that's the whole page bestie, ily, go convert something 💖

this was libgig 4.5.2, dated 06 Jan 2015 — yes she's an elder but she still ate, periodt. ✨🦋💅

📦 where this page comes from