Ouch. Thing is, if it renamed automatically, it'd break package.trg and Eden preset files.

Actually it does currently automatically rename from .WAV to .wav (which bit me on the trg maker!)

Well, if a sample doesn't copy at all, wouldn't it also break the package.trg and Eden presets? Would it be a big thing to coordinate the TRG maker's approach to filenames with Nanosync's approach (if such an approach is on the horizon)?

Sorry, if I ask stupid questions, I've actually never used TRG banks because I rarely use the same setup twice.

Oh, I wasn't suggesting it shouldn't do renames. Just noting that there's potentially more to it than renaming individual files. I've not run into your problem but it should at least throw an error, no doubt.

Ok, I see what you mean. I ran into the problem when I was sampling a cd. I tend to keep the original track names so I have a sense who I've stolen from, and the 70's track names were quite a bit longer than they are now.

Now that I'm aware of the problem I can circumvent it by batch renaming the files in Adobe Bridge but there should definitely be a warning.

There was a short of discussion and a short of... official statement? :P about it here.
http://forums.blipinteractive.co.uk/node/2260?page=2
Ends up that at the moment, you have to carefully name nsp's before you compile them. ;)

Thanks, Zupi, I'd forgotten about that. And Syrupcore is right saying, that it's not as simple a problem as I thought. But actually the solution I suggested would not make the situation any worse ;)