reaproj

Parse and edit REAPER .RPP project files in Python: tracks, items, markers, regions, and render settings as objects, instead of hand-editing chunk text.

Typical uses: add regions to a project programmatically, batch-change render settings (output directory, $region naming, format) before a headless -renderproject render, read item positions and source files for analysis, or save versioned copies of a session.

Built on rpp (the tokenizer/emitter); reaproj adds the object model on top.

Install

pip install reaproj

Read a project

from reaproj import Project

project = Project.load("Session.RPP")

for track in project.tracks:
    for item in track.items:
        print(item.position, item.length, item.soffs, item.source_path)

for region in project.regions:
    print(region.name, region.start, region.end)

Add regions

project.add_region(12.5, 95.0, "Take 1")   # id and GUID handled for you

Configure rendering

from reaproj import RenderBounds

project.render.directory = "Takes"
project.render.pattern = "$region"
project.render.bounds = RenderBounds.ALL_REGIONS
project.render.stems = 0                    # master mix
project.render.normalize_enabled = False
project.render.format = "wav24"             # or "mp3", or a raw RENDER_CFG base64 payload

Save

project.save()                  # in place
project.save("Other.RPP")       # elsewhere
project.save_next_version()     # "Session v2.RPP", "Session v3.RPP", ...

Then render headlessly:

REAPER -renderproject "Session v2.RPP"

Alternatives

• rpp: the underlying low-level parser/emitter; gives you an ElementTree-like view of raw chunks. Use it directly when you need something reaproj doesn't model yet.
• reathon: constructs new REAPER projects from scratch; not aimed at editing existing ones.
• rppxml: RPP parsing via the WDL implementation.
• reapy: controls a running REAPER instance through the ReaScript API; requires REAPER to be open. reaproj works on the files themselves, no REAPER required.

Fidelity

reaproj never touches content it doesn't understand; everything round-trips through the element tree, and numeric values are preserved as strings, never reformatted. Verified on real REAPER 7 projects:

• Emission is idempotent, and the only differences from REAPER's own formatting are cosmetic quoting (quotes dropped on space-free strings; both forms appear in REAPER-authored files).
• REAPER itself loads and headlessly renders reaproj-emitted projects: in an A/B against the original project file, all rendered regions matched in name, count, and byte-identical file size, and the audio difference between the two renders was the same as between two renders of the untouched original (i.e. REAPER's own render-to-render variance from modulated plugins, not a file difference).

License

MIT