On Mittwoch, 1. November 2017 13:16:58 CET Jaime T wrote:
> Tascam BG (Biggagigga/Purgatory Creek) Rhodes (md5sum: 0fa5...):
> Verifying sample checksum table ... DAMAGED
>
> Could anyone please give me an idea of what is causing this? I can
> provide any diagnostic info required and/or I can upload these to
> cloud-storage if needed.
If the integrity check for a sample failed, gigdump prints you both the
expected checksum, as well as the actual checksum it calculated. Compare the
two checksums printed on the screen. If they simply look mirrored like:
"aabbccdd" vs "ddccbbaa"
then simply ignore this error. That was a bug in libgig before and your
samples are fine. And in that case you can simply run
gigdump --rebuild-checksums foo.gig
to get rid of this false error in the file.
If however the two printed checksums look completely different, then your
samples "may be" damaged. But again, there was a bug in libgig before where
not all sample checksums were updated after making certain modifications with
libgig (i.e. using gigedit) before. So in that case you might need to check
the individual samples manually (i.e. with your ear), because there might be
potentially noise, clicks or something like that. And again if all sounds fine
run
gigdump --rebuild-checksums foo.gig
See also
man gigdump
About one year ago, when I accidentally damaged one of my gig files and
actually started using this feature, I actually found out that there were
several bugs regarding those checksums, editing and integrity check for many
years without anybody noticing it. I fixed them, so it should work fine now.
CU
Christian
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
