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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 3046 by schoenebeck, Wed Sep 21 12:11:36 2016 UTC revision 3047 by schoenebeck, Fri Nov 25 18:17:38 2016 UTC
# Line 15  filename of the Gigasampler file Line 15  filename of the Gigasampler file
15  .TP  .TP
16  .B \ --rebuild-checksums  .B \ --rebuild-checksums
17  Rebuild checksum table for all samples. Read description of  Rebuild checksum table for all samples. Read description of
18  .B --verify  .B \ --verify
19  option for more details about sample checksums in general. Usually you only  option for more details about sample checksums in general. Usually you only
20  need to use  need to use
21  .B --rebuild-checksums  .B \ --rebuild-checksums
22  in case the samples' CRC checksum table itself was damaged. The  in case the samples' CRC checksum table itself was damaged. The
23  .B --verify  .B \ --verify
24  option will tell you if that is really the case and will suggest to you to use  option will tell you if that is really the case and will suggest to you to use
25  .B --rebuild-checksums  .B \ --rebuild-checksums
26  to repair the table in such cases. If only individual samples were damaged, you  to repair the table in such cases. If only individual samples were damaged, you
27  rather might want to replace only those damaged samples with  rather might want to replace only those damaged samples with
28  .BR gigedit (1)  .BR gigedit (1)
29  for example. Read description of  for example. Read description of
30  .B --verify  .B \ --verify
31  for reasons to do so. When using  for reasons to do so. When using
32  .B --rebuild-checksums  .B \ --rebuild-checksums
33  all checksums of all samples will be regenerated. Hence you should manually  all checksums of all samples will be regenerated. Hence you should manually
34  check all samples once after using this option. That is by using your ears,  check all samples once after using this option. That is by using your ears,
35  or by exporting the samples, but not by using the  or by exporting the samples, but not by using the
36  .B --verify  .B \ --verify
37  option. Because the latter cannot identifiy damaged samples that have been  option. Because the latter cannot identifiy damaged samples that have been
38  damaged before the entire checksum table had been regenerated.  damaged before the entire checksum table had been regenerated.
39  .TP  .TP
# Line 51  in this case. Since essentially the enti Line 51  in this case. Since essentially the enti
51  take a long time and hence this check is not by default performed i.e.  take a long time and hence this check is not by default performed i.e.
52  each time a gig file is loaded for regular use for example. Accordingly you  each time a gig file is loaded for regular use for example. Accordingly you
53  may use  may use
54  .B --verify  .B \ --verify
55  from time to time to check explicitly whether your gig files have been  from time to time to check explicitly whether your gig files have been
56  damaged for some reason, i.e. after modifying them with an instrument editor  damaged for some reason, i.e. after modifying them with an instrument editor
57  like  like
# Line 61  In case damaged samples were found, you Line 61  In case damaged samples were found, you
61  By doing this, only the replaced samples' checksums will be  By doing this, only the replaced samples' checksums will be
62  updated. All other checksums remain untouched. That's why this approach is  updated. All other checksums remain untouched. That's why this approach is
63  recommended over using  recommended over using
64  .B --rebuild-checksums  .B \ --rebuild-checksums
65  in such cases.  in such cases.
66    
67  .SH "SEE ALSO"  .SH "SEE ALSO"
Legend:
Removed from v.3046  
changed lines
  Added in v.3047
  ViewVC Help
Powered by ViewVC