Suggestion: Save thd file with audio output

[QuantumCabbage]

Hey Jonathan,
love the interface you've built for CDP! So much fun to just try things and see what happens without any command line jockeying.
While browsing the files in the output after a while of fiddling around, it occured to me that it would be really useful if SoundThread were to save the current state of the thd file next to the output with the same date/time stamp. They're tiny anyway, and that would make it possible to go back to a specific point of experimentation later on.
Thanks for the great work!

[j-p-higgins]

This is something I am considering for a future update but haven't quite settled on the implementation of yet.

One thing I am considering is just embedding the thread file into the wav file as meta data and adding a custom file browser to SoundThread that can let you browse through your output folder, preview sounds and reload the thread used. The other option I was considering was exactly what you suggested. Either way (or something else) I will probable make it a toggleable option in the settings so those who want to keep things as lightweight as possible can.

Not sure on when I will add something like this, it need a bit of thinking about to get it done in a way that doesn't end up more complicated to navigate. Very open to suggestions and thoughts from anyone, this is also something we have discussed a bit on the discord.

[QuantumCabbage]

Thanks for the quick reply, those are interesting considerations!
If it were my tool, I'd probably make saving in the metadata the default, it offers the benefit of being able to reload the node tree without creating extra clutter. It could be implemented so that upon opening a wav file containing the metadata, a dialog pops up that asks whether the node tree should be created again or not.
A setting for saving the thd as a sidecar would offer the benefit of immediately being able to tell whether the creation process is being saved, at the expense of a bit of overhead in terms of files being created.
Looking forward to where the development is progressing!

[j-p-higgins]

Toggleable in the settings between either option or neither could be nice, I'll have a think. In terms of overhead, I don't think there would be a noticable difference in either option, I will have to modify the wav file to add the meta data after it has been made by cdp so I think it would probably take pretty much the exact same amount of time (if not a tiny bit longer) as making a file. As it is, saving the file is so quick that when implementing save or save as on quiting SoundThread I ended up adding a 100ms delay after saving before actually quiting otherwise it saved and closed so fast it felt like it hadn't done anything and stressed test users out that it hadn't saved haha

I have created a feature ticket for this here where I will post updates: #206

I havent put a specific version on this yet as I need to explore how difficult the custom file browser will be to implement before deciding when I will prioritise it