korg2gig(1)

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

✨ korg2gig — the libgig tools glow-up ✨

okay so bestie, buckle up, because this is korg2gig(1) from the libgig tools family and she is literally a whole conversion queen 💅

🌸 NAME 🌸

korg2gig — Convert sound files from KORG to GigaStudio format. 🎹➡️💖

🎀 SYNOPSIS 🎀

korg2gig [-v] [-f] [--interpret-names] FILE1 [ FILE2 ... ] NEWFILE

🦋 DESCRIPTION 🦋

okay so picture this: you've got a pile of KORG sound files, the ones your KORG synthesizer keyboards use — think Trinity, Triton, OASYS, M3 or Kronos 👑 — and this little tool takes that whole list and converts them into a Gigasampler/GigaStudio (.gig) file. Every single input KORG file gets merged into one single (.gig) output file. one file. all of it. slay.

For each KORG "multi-sample" (.KMP) file, a separate GigaStudio instrument gets created in the output (.gig) file. And the KORG Sample (.KSF) files that those multi-sample (.KMP) files reference? They get automatically detected, loaded, and written to the output (.gig) file too, no extra work from you bestie ✨ Assignments of samples to keyboard regions, sample loops, and other minor articulation info get converted as well. 🫶

But note — and this is important, no cap — the multi-sample (.KMP) form is very primitive. It does NOT save the detailed articulation information of your KORG keyboard, like envelopes, LFO and filter settings. That info lives in a separate program (.PCG) file. 😭

Unfortunately there is no support for KORG's program/combinations/bank (.PCG) files yet. Have a look at option --interpret-names for a workaround 👀 And because of this lack of support for .PCG files, you still have to adjust the articulation settings in the output (.gig) file afterwards with an instrument editor application like gigedit(1). that's just the vibe rn.

If you are explicitly passing KORG sample (.KSF) files as well, and they are not referenced by any "multi-sample" (.KMP) file you might have passed, then those orphaned samples get added to the output (.gig) file in a separate sample group called "Not referenced" 💜 That way you can easily tell apart the samples in the output (.gig) file that are actually used by one of the instruments, and the samples that are not used yet. iconically organized, honestly.

NOTE: This tool might need quite a lot of RAM at the moment. Approximately, it will allocate as much RAM as the expected output .gig file will be in size. So make sure you have enough free RAM and/or swap space, otherwise this tool might crash if it cannot allocate the required RAM space. 💀 please check your RAM first bestie, I'm begging.

💖 OPTIONS 💖

  • FILE1 [ FILE2 ... ] — A list of input KORG sound (.KMP or .KSF) files. You must supply at least one KORG file. KORG sample (.KSF) files referenced in the so called "multi-sample" (.KMP) file(s) are automatically detected and loaded, so in most cases you'd just pass .KMP file(s) as your input file argument(s). easy ✨
  • NEWFILE — Output file in Gigasampler/GigaStudio (.gig) format. If this output file already exists, korg2gig will abort with an error message unless you specify -f as argument as well. 🙈
  • -v — print version and exit
  • -f — Overwrite output file if it already exists.
  • --interpret-names — Try to guess left/right sample pairs and velocity splits. This is a nasty workaround for the fact that there is no support for reading KORG .PCG files yet. If you manually named the multi-samples (.KMP files) on your keyboard in a scheme like "PIANO 003-120 -R", it will interpret the two hints as a) velocity split range (in this example from velocity 3 to 120) and b) stereo sample pairs (in this case the multi-sample contains the right channel). Of course you can also omit one or both hints if you don't want to have a velocity split or stereo sample pair for certain instruments or regions. 🧚 the way that naming scheme is doing double duty... obsessed.

🌈 SEE ALSO 🌈

korgdump(1), wav2gig(1), gigedit(1), rifftree(1), akaidump(1), gigdump(1), sf2dump(1), dlsdump(1)

the whole friend group, fr fr 💕

🍓 BUGS 🍓

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

(not me asking you to snitch on the bugs but like... do it, they wanna know 🫶)

👑 Author 👑

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

and that's the page bestie!! this one is from libgig 4.5.2, dated 10 May 2014 🌸 go convert something iconic, ily, periodt 💅✨

📦 where this page comes from