Hi all.

I was just wondering about the 'stand-in' file- 'music.wav' for the 'solarq' set...

my understanding is that it's a temporary file until a real sample becomes available. If this is the case, is there not a risk (if & when the real wav becomes available) that clrMAME will not pick up on it as it will think it's already in the samples directory?

Is this correct, and is there a fail-safe mechanism to avoid this potential issue?

Another thing is: even though i keep uptodate with samples as they are dumped, the dats always seem to indicate that I am a couple dozen samples short of a complete set. MAME32's inbuilt auditing states the same.

Yet it seems impossible to find the correct samples anywhere.

There are some sites offering empty dummy files (such as solarq's wav), but what is the point in this? Can't there just be a 'no-good dump known' instruction or some like rather than stating out-right that it's missing. Surely it can only be missing if it's been sampled & dumped?

Thanks for any clarification on this guys.

> available. If this is the case, is there not a risk (if & when the real wav
> becomes available) that clrMAME will not pick up on it as it will think it's
> already in the samples directory?

You're wrong. There is no risk. The samplesdatfile will be updated with the correct sha1/cr32 hashvalues as soon as the samples are available.

> Another thing is: even though i keep uptodate with samples as they are dumped,
> the dats always seem to indicate that I am a couple dozen samples short of a
> complete set. MAME32's inbuilt auditing states the same.

MAME32's audit system..haha...forget it. The samples datfile is right and covers the samplesets which are in the official current mame build and are available at mame.net.


> Yet it seems impossible to find the correct samples anywhere.

www.mame.net. The ones which are listed with the placeholder aren't recorded yet.

> There are some sites offering empty dummy files (such as solarq's wav), but what
> is the point in this? Can't there just be a 'no-good dump known' instruction

The placeholders ARE marked as no-better-dump-known (flags baddump) in the datfile.


Resumee: There is no risk.

Roman Scherzer
ClrMamePro