--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README	Fri Oct 17 19:01:34 2025 -0400
@@ -0,0 +1,19 @@
+This is a "playground" for reversing the Vegas Pro ".veg" file format.
+
+What I've figured out so far:
+  - The .veg file format has a Wave64-style RIFF structure.
+  - Each file has one big "riff" chunk; it contains the GUID of the
+    "riff" chunk, a 64-bit little endian size, and another GUID
+    defining what the type of the data is. In fact, this exactly
+    explains WHY my little 'msvpvf' tool was able to get away with
+    simply overwriting the bytes at 0x18, since that's the GUID
+    stating whether it is a .vf or a .veg.
+  - That one big "riff" chunk contains many sub-chunks, which
+    contain other data. The first of these sub-chunks is a
+    chunk containing generic header data, for example project
+    resample settings. All of the others are "list" chunks,
+    which follow the same format as the "riff" chunk.
+  - The GUIDs seem to be totally random besides the "riff" and
+    "list" chunks.
+  - Any and all strings are stored as UTF-16 little endian
+    (Windows NT style).