target_synchronous(3)

💅 target_synchronous (3) ✨

okay bestie, welcome to the Arcan Lua API — this one's a little spicy so buckle up 🎀

---

🌸 NAME 🌸

target_synchronous — enforce synchronous transfers, no cap 💅

---

🦋 SYNOPSIS 🦋

target_synchronous( dstvid, state )

---

✨ DESCRIPTION ✨

okay so real talk: this function is potentially dangerous 😭 — there's a genuine tradeoff between responsiveness and reliable readbacks for recordtargets. here's the vibe: if the frameserver isn't ready to receive when a readback from the GPU has been completed, the frame gets discarded. gone. poof. 💀 that's the async-discard behavior, and you can alter it on a single frameserver by calling target_synchronous.

what does it change? it switches up the synchronization behavior so that processing will not continue until the frameserver is ready to receive. the way that this works means an untrusted frameserver implementation can potentially livelock the main engine 😳 and it'll also introduce additional jitter between rendered frames. so like... highkey be careful, bestie.

but wait 🫶 — if this is performed on a frameserver in decode mode, the "discard if PTS is too old" behavior gets disabled, and the last presented timestamp will be set to the frame that would've otherwise been discarded. iconic, honestly.

---

👑 switching it on and off 👑

this behavior can be switched on or off dynamically by setting state to:

• 1 / true — the default, bestie 💖 (synchronous mode, obvi)
• 0 / false — off, back to the async life 🌈

---

⚠️ friendly reminder that this is the potentially-dangerous one — livelock and jitter are absolutely on the menu if you're not careful 🙈

---

🍓 SEE ALSO 🍓

• targetcontrol 💜

---

later bestie 🫶 this page came from the Arcan Lua API, dated October 2026 — go forth and synchronize responsibly, mwah 💋✨