Tom Rees

Ok, so this issue has been intermittent, and so confusing. The patch seems to be fine, I'm not doing anything complex.

So I have recorded about 8000 samples using different variables on a snare drum (different velocity, damping, mic, snare tightness etc). And I have used simple dials to calculate which file number to choose so that it plays the right recorded sound using an sfplay~. You drop the folder of samples into a live.drop (this issue happens with dropfile too btw) which autopopulates a umenu.

These files all load and play fine, and it's all working great. But then, sometimes, the patch starts playing the wrong sounds - starts playing different files to the one displayed in the umenu - a different file even to the file path being sent to sfplay! there's no way of knowing which file is playing and it's infuriating, because it says it's playing one file but the sound is completely different.

I have made progress on figuring this out but it just gets weirder: I went on finder (MacOS) to view the folder, and certain batches of files were missing. Those missing files correspond to the ones that aren't playing properly. That's good. But then, those files will reappear in the folder randomly.... 

the files use a naming format SNARECODE_MICTYPE#001 etc with up to #256 before it repeats again. The files that go missing are #100 upwards. After they reappear, I drop the folder back in Max which still detects the files and adds them to the umenu, but playing any of the files over #100 aren't correct. This is so confusing, I was wondering if anyone knows of some sort of known issue that affects file-reading, how I've broken it perhaps.

It would be much appreciated if anyone could help, this is for my final year project at uni.

EDIT: today, I loaded it up and it is deleting all the files past 220, but there's still the same number of files, it just duplicates the earlier files to make up the numbers... and when I try and delete those duplicates I get an error saying they don't exist. wtf is going on

Max Device 5.amxd

So I have recorded about 8000 samples using different variables on a snare drum (different velocity, damping, mic, snare tightness etc). And I have used simple dials to calculate which file number to choose so that it plays the right recorded sound using an sfplay~.  You drop the folder of samples into a live.drop (this issue happens with dropfile too btw) which autopopulates a umenu.
These files all load and play fine, and it's all working great. But then, sometimes, the patch starts playing the wrong sounds - starts playing different files to the one displayed in the umenu - a different file even to the file path being sent to sfplay! there's no way of knowing which file is playing and it's infuriating, because it says it's playing one file but the sound is completely different.

I have made progress on figuring this out but it just gets weirder: I went on finder (MacOS) to view the folder, and certain batches of files were missing. Those missing files correspond to the ones that aren't playing properly. That's good. But then, those files will reappear in the folder randomly.... 
the files use a naming format SNARECODE_MICTYPE#001 etc with up to #256 before it repeats again. The files that go missing are #100 upwards. After they reappear, I drop the folder back in Max which still detects the files and adds them to the umenu, but playing any of the files over #100 aren't correct. This is so confusing, I was wondering if anyone knows of some sort of known issue that affects file-reading, how I've broken it perhaps.

Ok, so this issue has been intermittent, and so confusing. The patch seems to be fine, I'm not doing anything complex.
So I have recorded ab

file-loading-being-very-strange

"Mac SD Tom:/FYP SNARE ENRICHMENT ENGINE /6. SNARE RECORDINGS SHORTENED+NORMALISED TO 17.5 LUFS/All Snares (Stereo)/BP-B14_Audix i5#001.wav"

I would at least shorten that path a bit and also check this

there is a space and slash in the path which actually can't be.

P.S. avoid using special characters (e.g., * . ” / \ [ ] : ; | = , < ? > & $ # ! ‘( ) { })

I would at least shorten that path a bit and also check this
ENGINE /6. SNARE
there is a space and slash in the path which actually can't be.

P.S. avoid using special characters (e.g., * . ” / \ [ ] : ; | = , < ? > & $ # ! ‘( ) { })

Thanks! I didn't notice there was a space in the folder name, and that's useful to know about the special characters. Hopefully this will stop weird things from happening!

dropfile-umenu loading causes files to disappear/duplicate