So hi, I've got this system working now where if I click on a button, the array in question is dumped to /tmp/plom.wav and Renoise or Ableton Live loads it. Now, Renoise is good with this, i.e., when i overwrite plom.wav with something else, it'll just load that. Ableton Live, not so much.

if something is loaded into ableton live, loading the same wavefile (even though it's been overwritten), will result in the same wavefile being loaded, not the new one. so how could i use some random hash for creating a filename for these "not so great" other apps?

@esaruoho A random hash is probably a bad idea as you will sometimes be confused about which is the newer file.
So maybe just a counter, spinning 1 to 10 or 1 to 50?, banging your write message, with the file name plomjaa_ableton_$1.wav
The new [file] object can delete files too...... so you can keep the folders tidy.

The only complication is that you will need to save the counter value as you close Pd.
Not so easy to automate, and remembering to save would be hard.
You could write the value to a text file at the same time..... and load the value from that file as the patch starts.
David.

@whale-av said:

@esaruoho A random hash is probably a bad idea as you will sometimes be confused about which is the newer file.
So maybe just a counter, spinning 1 to 10 or 1 to 50?, banging your write message, with the file name plomjaa_ableton_$1.wav
The new [file] object can delete files too...... so you can keep the folders tidy.

The only complication is that you will need to save the counter value as you close Pd.
Not so easy to automate, and remembering to save would be hard.
You could write the value to a text file at the same time..... and load the value from that file as the patch starts.
David.

sounds like the best solution would be to use plom1...plom16 and also add yyyy_mm_dd to the start.

@esaruoho Live is either working from its own copy of plom.wav stored elsewhere or just assuming the file has not changed for some reason. For the former finding where Live stores its copy and deleting it with [command] before opening the new one might be enough, for the latter perhaps opening a really short audiofile (like 1 sample long) before opening plom.wav will give Live the kick in the ass it need to actually check plom.wav's attributes and see if it is the same file. For both, deleting plom.wav before writing to insure it is a new file could work, Live could be going by file creation time instead of modification time because it assumes you are doing all your editing in Live so modification times will not change, this assumes OSX has creation time (it did years ago) for files but it is simple enough to test, suppose you can also trying running touch on plom.wav before the open command.

No need to try combinations of these methods, I doubt combining would work, they either work or they do not. But they should be a bit more efficient than reworking names which could be of use for you since you sound like you are already running out of space between blocks.