What does the REAPER ReaScript API documentation say about BWF timecode start offsets and project drop-frame frame rate?
The curator re-read all cited web sources (S13); nothing was executed. REAPER's scripting API can insert media at its BWF timecode start offset (InsertMedia flag 4096) and read the project frame rate and drop-frame state; the API text has no iXML, pull-up or sample-rate-conversion documentation (the user guide was too large to read).
The curator re-read all cited web sources (S13); nothing was executed.
REAPER's scripting API can insert media at its BWF timecode start offset (InsertMedia flag 4096) and read the project frame rate and drop-frame state; the API text has no iXML, pull-up or sample-rate-conversion documentation (the user guide was too large to read).
Curator qualifications: The curator re-read all cited web sources (S13); nothing was executed. Documentation read 2026-10-22; no audio imported. REAPER User Guide not read.
Limitations: Documentation read 2026-10-22; no audio imported.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://www.reaper.fm/sdk/reascript/reascripthelp.html",
"note": "REAPER ReaScript help (live) InsertMedia and TimeMap_curFrameRate"
}
]
}Evidence claims
- [sourced_fact] REAPER's scripting API can insert media at its BWF timecode start offset (InsertMedia flag 4096) and read the project frame rate and drop-frame state; the API text has no iXML, pull-up or sample-rate-conversion documentation (the user guide was too large to read). · locator: REAPER ReaScript help (live) InsertMedia and TimeMap_curFrameRate source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |