1 |
.TH "gigdump" "1" "8 May 2005" "libgig @VERSION@" "libgig tools" |
.TH "gigdump" "1" "20 Sep 2016" "libgig @VERSION@" "libgig tools" |
2 |
.SH NAME |
.SH NAME |
3 |
gigdump \- List informations about a Gigasampler (.gig) file. |
gigdump \- List informations about a Gigasampler (.gig) file. |
4 |
.SH SYNOPSIS |
.SH SYNOPSIS |
5 |
.B gigdump |
.B gigdump |
6 |
[ -v ] GIGFILE |
[OPTIONS] GIGFILE |
7 |
.SH DESCRIPTION |
.SH DESCRIPTION |
8 |
Prints out a list of all available samples and instruments within a Gigasampler (.gig) file along with detailed informations about their properties and settings. |
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 |
.SH OPTIONS |
12 |
.TP |
.TP |
13 |
.B \ GIGFILE |
.B \ GIGFILE |
14 |
filename of the Gigasampler file |
filename of the Gigasampler file |
15 |
.TP |
.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 |
.B \ -v |
29 |
print version and exit |
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" |
.SH "SEE ALSO" |
49 |
.BR gigextract(1), |
.BR gigextract(1), |