/[svn]/libgig/trunk/man/gigdump.1.in
ViewVC logotype

Contents of /libgig/trunk/man/gigdump.1.in

Parent Directory Parent Directory | Revision Log Revision Log


Revision 2985 - (show annotations) (download)
Tue Sep 20 22:13:37 2016 UTC (7 years, 5 months ago) by schoenebeck
File size: 2127 byte(s)
* gig.cpp/gig.h: Added new method Sample::VerifyWaveData() which
  allows to check whether a sample had been damaged for some
  reason.
* gigdump tool: added and implemented new parameter "--verify"
  which allows to check the raw wave form data integrity of all
  samples.
* gigdump tool: added and implemented new parameter
  "--rebuild-checksums" which allows to recalculate the CRC32
  checksum of all samples' raw wave data and rebuilding the gig
  file's global checksum table (i.e. in case the file's checksum
  table was damaged).
* Bumped version (4.0.0.svn8).

1 .TH "gigdump" "1" "20 Sep 2016" "libgig @VERSION@" "libgig tools"
2 .SH NAME
3 gigdump \- List informations about a Gigasampler (.gig) file.
4 .SH SYNOPSIS
5 .B gigdump
6 [OPTIONS] GIGFILE
7 .SH DESCRIPTION
8 By default it prints out a list of all available samples, real-time instrument
9 scripts and instruments within a Gigasampler (.gig) file, along with detailed
10 informations about their properties and settings.
11 .SH OPTIONS
12 .TP
13 .B \ GIGFILE
14 filename of the Gigasampler file
15 .TP
16 .B \ --rebuild-checksums
17 Rebuild checksum table for all samples. Read description of
18 .B --verify
19 option for more details about sample checksums in general. Usually you only
20 need to use
21 .B --rebuild-checksums
22 in case the samples' CRC checksum table itself was damaged. The
23 .B --verify
24 option will tell you if that is really the case and will suggest to you to use
25 .B --rebuild-checksums
26 to repair the table in such cases.
27 .TP
28 .B \ -v
29 Print version and exit.
30 .TP
31 .B \ --verify
32 Check raw wave data integrity of all samples and print result of this check.
33 For all samples of a gig file a correspondig CRC32 checksum is stored along
34 to its raw wave form data whenever a conscious change to the wave form data
35 was performed. By calling gigdump with this option all samples are scanned
36 and compared with their existing checksums to detect any damage to
37 individual samples. The individual damaged samples are listed by gigdump
38 in this case. Since essentially the entire file has to be read, this can
39 take a long time and hence this check is not by default performed i.e.
40 each time a gig file is loaded for regular use for example. Accordingly you
41 may use
42 .B --verify
43 from time to time to check explicitly whether your gig files have been
44 damaged for some reason, i.e. after modifying them with an instrument editor
45 like
46 .BR gigedit (1).
47
48 .SH "SEE ALSO"
49 .BR gigextract(1),
50 .BR gigmerge(1),
51 .BR gig2mono(1),
52 .BR gig2stereo(1),
53 .BR dlsdump(1),
54 .BR rifftree(1),
55 .BR akaidump(1),
56 .BR sf2dump(1),
57 .BR korgdump(1)
58
59 .SH "BUGS"
60 Check and report bugs at http://bugs.linuxsampler.org
61 .SH "Author"
62 Application and manual page written by Christian Schoenebeck <cuse@users.sf.net>

  ViewVC Help
Powered by ViewVC