Which of Pro Tools, REAPER and Resolve document keeping the bext TimeReference when a file is rendered, trimmed or sample-rate converted, and what does REAPER's history actually promise?
REAPER's version history documents preserving the source start offset on render (v7.16, adjusted for take offset), a batch-converter choice between keeping the BWF start or using item position (v5.985), clearing offset data on consolidate/glue with source metadata (v7.35), and adjusting the written position after trimming silence (v7.37). No entry or API text says how a stored sample-count start is rescaled when the sample rate changes (no pull-up/pulldown terms). Pro Tools and Resolve remain unresolved here.
REAPER's version history documents preserving the source start offset on render (v7.16, adjusted for take offset), a batch-converter choice between keeping the BWF start or using item position (v5.985), clearing offset data on consolidate/glue with source metadata (v7.35), and adjusting the written position after trimming silence (v7.37). No entry or API text says how a stored sample-count start is rescaled when the sample rate changes (no pull-up/pulldown terms). Pro Tools and Resolve remain unresolved here.
Curator qualifications: Docs read 2026-10-22; no file imported, rendered or converted. Sample-rate-conversion behaviour unknown (would need a fixture test).
Limitations: Docs read 2026-10-22; no file imported, rendered or converted.
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/whatsnew.txt",
"note": "reascripthelp.html (curator readback = pin) whole-text search; producer whatsnew.txt (= pin) L3000-3004, L7382, L2182, L2018, L5442, L5681 and whole-file search"
},
{
"url": "https://www.reaper.fm/sdk/reascript/reascripthelp.html",
"note": "reascripthelp.html (curator readback = pin) whole-text search; producer whatsnew.txt (= pin) L3000-3004, L7382, L2182, L2018, L5442, L5681 and whole-file search"
}
]
}Evidence claims
- [sourced_fact] REAPER's version history documents preserving the source start offset on render (v7.16, adjusted for take offset), a batch-converter choice between keeping the BWF start or using item position (v5.985), clearing offset data on consolidate/glue with source metadata (v7.35), and adjusting the written position after trimming silence (v7.37). No entry or API text says how a stored sample-count start is rescaled when the sample rate changes (no pull-up/pulldown terms). Pro Tools and Resolve remain unresolved here. · locator: reascripthelp.html (curator readback = pin) whole-text search; producer whatsnew.txt (= pin) L3000-3004, L7382, L2182, L2018, L5442, L5681 and whole-file search 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. |