1 |
.TH "gigdump" "1" "08 May 2018" "libgig @VERSION@" "libgig tools" |
2 |
.SH NAME |
3 |
gigdump \- List information 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 |
information about their properties and settings. |
11 |
.SH OPTIONS |
12 |
.TP |
13 |
.B \ GIGFILE |
14 |
filename of the Gigasampler file |
15 |
.TP |
16 |
.B \ --instrument-names |
17 |
Only list instrument names and their index number. |
18 |
.TP |
19 |
.B \ --rebuild-checksums |
20 |
Rebuild checksum table for all samples. Read description of |
21 |
.B \ --verify |
22 |
option for more details about sample checksums in general. Usually you only |
23 |
need to use |
24 |
.B \ --rebuild-checksums |
25 |
in case the samples' CRC checksum table itself was damaged. The |
26 |
.B \ --verify |
27 |
option will tell you if that is really the case and will suggest to you to use |
28 |
.B \ --rebuild-checksums |
29 |
to repair the table in such cases. If only individual samples were damaged, you |
30 |
rather might want to replace only those damaged samples with |
31 |
.BR gigedit (1) |
32 |
for example. Read description of |
33 |
.B \ --verify |
34 |
for reasons to do so. When using |
35 |
.B \ --rebuild-checksums |
36 |
all checksums of all samples will be regenerated. Hence you should manually |
37 |
check all samples once after using this option. That is by using your ears, |
38 |
or by exporting the samples, but not by using the |
39 |
.B \ --verify |
40 |
option. Because the latter cannot identifiy damaged samples that have been |
41 |
damaged before the entire checksum table had been regenerated. |
42 |
.TP |
43 |
.B \ -v |
44 |
Print version and exit. |
45 |
.TP |
46 |
.B \ --verify |
47 |
Check raw wave data integrity of all samples and print result of this check. |
48 |
For all samples of a gig file a correspondig CRC32 checksum is stored along |
49 |
to its raw wave form data whenever a conscious change to the wave form data |
50 |
was performed. By calling gigdump with this option all samples are scanned |
51 |
and compared with their existing checksums to detect any damage to |
52 |
individual samples. The individual damaged samples are listed by gigdump |
53 |
in this case. Since essentially the entire file has to be read, this can |
54 |
take a long time and hence this check is not by default performed i.e. |
55 |
each time a gig file is loaded for regular use for example. Accordingly you |
56 |
may use |
57 |
.B \ --verify |
58 |
from time to time to check explicitly whether your gig files have been |
59 |
damaged for some reason, i.e. after modifying them with an instrument editor |
60 |
like |
61 |
.BR gigedit (1). |
62 |
In case damaged samples were found, you may replace those damaged samples with |
63 |
.BR gigedit (1). |
64 |
By doing this, only the replaced samples' checksums will be |
65 |
updated. All other checksums remain untouched. That's why this approach is |
66 |
recommended over using |
67 |
.B \ --rebuild-checksums |
68 |
in such cases. |
69 |
|
70 |
.SH "SEE ALSO" |
71 |
.BR gigextract(1), |
72 |
.BR gigmerge(1), |
73 |
.BR gig2mono(1), |
74 |
.BR gig2stereo(1), |
75 |
.BR dlsdump(1), |
76 |
.BR rifftree(1), |
77 |
.BR akaidump(1), |
78 |
.BR sf2dump(1), |
79 |
.BR korgdump(1) |
80 |
|
81 |
.SH "BUGS" |
82 |
Check and report bugs at http://bugs.linuxsampler.org |
83 |
.SH "Author" |
84 |
Application and manual page written by Christian Schoenebeck <cuse@users.sf.net> |