Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
gigdump(1)			 libgig	tools			    gigdump(1)

       gigdump - List information about	a Gigasampler (.gig) file.

       gigdump [OPTIONS] GIGFILE

       By default it prints out	a list of all available	samples, real-time in-
       strument	scripts	and instruments	 within	 a  Gigasampler	 (.gig)	 file,
       along with detailed information about their properties and settings.

	      filename of the Gigasampler file

	      Only list	instrument names and their index number.

	      Rebuild  checksum	 table	for  all  samples. Read	description of
	       --verify	option for more	details	about sample checksums in gen-
	      eral.  Usually you only need to use  --rebuild-checksums in case
	      the samples' CRC checksum	table itself was damaged. The	--ver-
	      ify  option  will	 tell  you if that is really the case and will
	      suggest to you to	use  --rebuild-checksums to repair  the	 table
	      in  such	cases.	If  only  individual samples were damaged, you
	      rather might want	to replace only	 those	damaged	 samples  with
	      gigedit(1)  for  example.	Read description of  --verify for rea-
	      sons to do so. When using	 --rebuild-checksums all checksums  of
	      all samples will be regenerated. Hence you should	manually check
	      all samples once after using this	option.	That is	by using  your
	      ears,  or	by exporting the samples, but not by using the	--ver-
	      ify option. Because the latter cannot identifiy damaged  samples
	      that have	been damaged before the	entire checksum	table had been

	-v    Print version and	exit.

	      Check raw	wave data integrity of all samples and print result of
	      this  check.  For	all samples of a gig file a correspondig CRC32
	      checksum is stored along to its raw wave form  data  whenever  a
	      conscious	change to the wave form	data was performed. By calling
	      gigdump with this	option all samples are	scanned	 and  compared
	      with their existing checksums to detect any damage to individual
	      samples. The individual damaged samples are listed by gigdump in
	      this  case.  Since  essentially  the entire file has to be read,
	      this can take a long time	and hence this check is	not by default
	      performed	 i.e.	each time a gig	file is	loaded for regular use
	      for example. Accordingly you may use  --verify from time to time
	      to check explicitly whether your gig files have been damaged for
	      some reason, i.e.	after modifying	them with an instrument	editor
	      like  gigedit(1).	  In  case 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. That's why this approach  is	recom-
	      mended over using	 --rebuild-checksums in	such cases.

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

       Check and report	bugs at

       Application  and	 manual	 page	written	  by   Christian   Schoenebeck

libgig 4.2.0			  08 May 2018			    gigdump(1)


Want to link to this manual page? Use this URL:

home | help