Every edit — renaming, deleting, adding, reordering, changing a track's type — is held in memory until you choose File → Save or Save As. Close without saving and the pod on disk is untouched, to the byte.
This is the one behaviour C-POD changed on purpose. The original applied some operations straight to the archive and deferred others, with nothing on screen to tell you which was which. That is how a track got converted to Rumble without anyone asking for it.
Add, delete, rename and reorder are list operations in memory, so they are instant whatever the archive weighs. The old tool rewrote the entire pod — and a backup copy of it — on every single one of those operations. That is why renaming one file in a 154 MB pod used to take minutes.
Saving is not always a rewrite. C-POD looks at what you changed and does the smallest thing that is correct:
| What you changed | What gets written |
| The comment | 80 bytes |
| Names | the directory region |
| The order of files | the directory region |
| A file, for one the same size | just that region |
| Added, removed or resized anything | a full rewrite |
Reordering is the surprising one. It does not move any content: POD1 addresses every file by an explicit offset, so the directory rows can be rewritten in a new order while every byte of payload stays exactly where it is. Moving one line in a 154 MB archive writes a few kilobytes.
Saving keeps the previous version as name.pod.bak unless you turn
that off in Preferences. It costs nothing when the archive is being rebuilt
anyway, and one file copy when the save was small enough to patch in place.
