The disk activity is because Podium stores the part of the 700mb that you crop away into the undo history. In order to “fix” this, I’ll need to implement a new “maximum storage size used by undo history” setting next to the existing “maximum sequence/sound undo levels” option. This would mean that if you crop away wave data beyond the set maximum size, you would not be able to undo the crop action.
I’m not able to import the full file again from the file browser, everytime I import it I only import the cropped loop (and I cannot slip edit it), but the 700 is there, because I can hear it with browser’s preview
If you try to drag in a sound file that is already imported in the project, the import is skipped. So the sound object that you cropped is still the one used, although it has not been saved to file yet.