Everything works so well.
But I have a problem when I read a sound from disk, do a quickie mod, and write it back.
The result is a zero-length sound.
If I write it to another filename it works great.
I assume that the file management overhead intrinsic to windows is busy and cannot comply…
So: Is there a way to tell if this has happened, maybe by the return value of the (s-save ~~~ ~~~) command?
And would it be better to just retry until success is seen in that return value,
Is there a way to busy that "windows file handling stuff" with something that requires an answer like (listdir ~~~ )? Perhaps that will force the "windows stuff" to be ready for a new action, like saving to a file just opened for reading? Thanks for your help! ~ Dalagar