How does DimPro handle bad .sfz and .wav files

I am considering upgrading to DimPro from the free sfz.

One frustrating aspect about sfz is debugging.

Whilst there IS a comment character (the "/" slash), sfz essentially ignores
everything that does not match a command, so it's kind of redundant, really.

What I would like to know is: does DimPro help the user when an unrecognized
command has been typed? Some sort of error message, error log, perhaps
a "Parse File" button?

How about file references where the .wav file is missing/incorrectly named?
This is a common error I make, esp. with the number of template
files I have accumulated.

Also, what happens if the .wav files are bad? (Length of a chunk incorrect, say).
I ask this because I wonder some problems I have with sfz are perhaps related
to a bad .wav files.

MM is right: Dimension jumps up and tells you if there is an error in an sfz. The dialog could be more advanced (e.g. line numbers to go with the errors would help a lot, some people make big sfzs René…) but it's a whole lot better than the freeware sfz that doesn't let you know when something goes wrong. Also, Dimension doesn't ignore things that it doesn't understand so that forward slash plays an important role in commenting your patchs and also commenting out sections for testing purposes.

Also, Dimension can calculate an MD5 checksum for your .wav files! Do this upon creating them then included md5= in your <region> definitions to have Dimension check for bed bugs upon loading.

What would a checksum help me do?

It's more for when you're preparing your patch for sharing with others. By including an MD5 checksum, Dimension will check to see that the waveforms being loaded are exactly as they were when you authored the patch, being sure that they didn't become corrupted somehow in the transmission process. Check René's thread for a better explanation: “Sign your samples”