Blackmagic Camera 10.0 Brings Ten Minute Pre Record to PYXIS and URSA Broadcast G2

Blackmagic Design’s Camera 10.0 firmware brings a practical set of broadcast-focused capabilities to the PYXIS line and URSA Broadcast G2—most notably a configurable pre‑record buffer of up to 10 minutes, plus 4‑channel audio, mono headphone monitoring, dynamic fan control for the PYXIS 12K, and a handful of workflow and API enhancements that change how these cameras can be used on news, documentary, and live productions.

Background / Overview​

Blackmagic Camera 10.0 is a firmware/software refresh targeted at Blackmagic’s PYXIS 6K and 12K cinema cameras and the URSA Broadcast G2. The headline feature — pre‑record — is a long‑standing broadcast and ENG capability that many professional crews rely on to avoid missing unpredictable action. This update also adds multi‑channel audio improvements, monitoring options, new Camera Control REST API commands, and several camera‑specific refinements such as dynamic fan control on the PYXIS 12K and improved B4 lens compatibility for the URSA Broadcast G2. Multiple industry outlets corroborate the feature set released in this update. The release is being rolled out through Blackmagic’s normal Camera Setup / firmware distribution channels and is published as a free update for supported models. Independent trade coverage and Blackmagic’s own posts confirm availability and summarize the change log.

---

What “pre‑record” means — and why it matters​

The concept in plain language​

Pre‑record is a continuous circular buffer that writes recent footage to storage or temporary cache while the camera is powered on, but only saves the pre‑configured amount of footage when the operator presses record (or triggers an event). The new Blackmagic implementation lets operators pick durations from a few seconds up to 10 minutes, offering a very wide buffer for fast‑moving or unpredictable coverage.

Why 10 minutes is consequential​

• For live news and ENG, reporters often have seconds to react; a 10‑minute pre‑record covers extended lead times between a cue and the visual moment.
• For documentary and wildlife work, the “moment” can unfold over minutes; a longer buffer reduces the risk of missing the beginning of an interaction.
• For sports and event coverage, a 10‑minute buffer lets operators retrospectively capture plays or incidents that began before the operator could react.

Multiple industry writeups position the 10‑minute ceiling as a pragmatic limit that balances capture flexibility with the reality of media throughput and storage management.

---

How Blackmagic’s pre‑record appears to work (practical mechanics)​

Buffer behavior and saving strategy​

According to the vendor messaging and press coverage, the pre‑record buffer continuously writes to the installed media card and then, when record is engaged, the specified pre‑record window (for example, the last 30 seconds, 2 minutes, or up to 10 minutes) is appended to the start of the newly created clip. The approach is described as “only saving what’s needed,” which helps manage storage by avoiding full continuous rolling capture.

Key practical implications (what to expect)​

• The buffer is configurable from short durations (seconds) up to the full 10 minutes, giving teams flexibility to balance storage and protection.
• The camera continuously writes data to the media card even when not “recording” in the traditional sense; however, only the pre‑record span is retained when a new clip is created.
• Because the buffer writes to media, card speed and sustained write performance are critical: slow or low‑end cards can create dropped frames or fail to support long pre‑record durations reliably.

These points are emphasized by multiple reviews and the vendor’s messaging; production teams should treat card selection and format settings as primary considerations before relying on long pre‑record windows.

---

Audio, monitoring, and proxy features: more than just pre‑record​

4‑channel audio recording​

The 10.0 update adds 4‑channel audio recording to the PYXIS 6K, PYXIS 12K, and URSA Broadcast G2. This doubles the previous internal track count and lets operators record separate mics or ambient channels directly into the camera’s media, keeping everything in sync for editorial. For ENG, interviews, and multi‑mic shoots this simplifies capture and post workflows. Practical benefits include:

• Recording a primary talent mic plus a backup or ambient track without a separate recorder.
• Saving scratch tracks for post that are frame‑accurate to the footage.
• Easier multicam editorial when each camera already contains multiple, usable audio tracks.

Mono headphone monitoring​

The update also introduces mono headphone monitoring, which offers a simple but useful monitoring option for users who only need a single channel in the headphones (common in ENG or single‑operator situations). This reduces complexity when operators have limited monitoring hardware or prefer summed monitoring for quick checks.

Inhibiting proxy recording​

Camera 10.0 includes support for inhibiting proxy recording, giving operators control over whether or not the camera writes lower‑resolution proxies alongside main footage. This is useful when preserving media bandwidth or card throughput is a higher priority, or when proxies are not needed for a given workflow.

---

PYXIS 12K: dynamic fan control and thermal considerations​

A targeted improvement for the PYXIS 12K is dynamic fan control, which adjusts cooling behavior automatically while recording. This helps manage thermal load during heavy recording sessions and can reduce unnecessary fan noise when the camera is operating in lower thermal states. Dynamic thermal control is a practical improvement for long takes and high‑heat scenarios such as fully loaded RAW capture. Operational notes:

• Dynamic control reduces operator intervention, but teams should still monitor temperature behavior during extended 12K RAW captures.
• Noise profiles and fan curves may change; testing on location is recommended when audio is critical.
• If thermal throttling or overheating is a potential issue in specific environments, performing controlled tests with the intended codecs and media is essential before relying on extended recording windows.

---

REST API, Blackmagic Cloud, and lens compatibility improvements​

Camera Control REST API commands​

Camera 10.0 expands the Camera Control REST API, enabling deeper remote control and automation for URSA Broadcast G2 and PYXIS cameras. This will matter to broadcast facilities, OB vans, and automated deployments where integration with device management systems or custom software is used. The new commands offer greater integration possibilities for pre‑record control, proxy management, and other automated workflows.

Blackmagic Cloud improvements​

Improvements to Blackmagic Cloud functionality are included for the URSA Broadcast G2, building on Blackmagic’s cloud workflow efforts. The update is described as an incremental improvement rather than a wholesale change, but it indicates continued investment in cloud‑adjacent camera workflows.

B4 lens compatibility (URSA Broadcast G2)​

The URSA Broadcast G2 receives improved B4 lens compatibility, which is important for broadcast operations that rely on studio and ENG lens ecosystems. These compatibility updates help ensure functionality with a wider range of B4 glass and streamline field operations that mix traditional broadcast lenses with modern camera bodies.

---

Real‑world workflows and recommended practices​

Media selection and configuration (critical)​

1. Use high‑end, high‑sustained‑write media from reputable brands for any pre‑record use, especially at higher frame rates or when using Blackmagic RAW at high data rates. Cards and SSDs that cannot sustain long bursts will be the weak link.
2. Prefer fast UHS‑II / CFast / CFexpress media, or NVMe recorders as recommended by Blackmagic for high bitrate formats and long pre‑record durations.
3. Format cards in camera and run real‑world stress tests (long takes, continuous pre‑record) before a live job; this verifies sustained throughput and thermal behavior.

Codec and resolution choices​

• When enabling long pre‑record buffers, consider using less demanding codecs (when acceptable) to reduce media stress. For critical editorial workflows that require RAW, validate that the selected RAW profile plus the card can sustain continuous pre‑record writes.

Power, boot state, and reliability​

• Pre‑record is effective only while the camera is powered and properly initialized. If the camera is powered off or reboots, the buffer will not retain prior footage.
• For long field stints, ensure stable power and monitor camera firmware and media health. Unexpected reboots can invalidate pre‑record protection.

Multi‑camera shoots​

• For multi‑cam environments, pre‑record reduces reliance on perfectly simultaneous “record” triggers and increases the odds editors have usable starting frames across sources.
• Maintain timecode discipline (external LTC or camera timecode) to support multi‑cam assemblies even when pre‑record buffers differ slightly between units.

---

Testing checklist before deploying pre‑record in production​

1. Verify firmware version on each camera and read the vendor release notes for known caveats.
2. Format and test intended media with extended writes: run a continuous recording with pre‑record enabled for longer than the planned buffer.
3. Verify audio channel routing, headphone monitoring behavior, and that all four audio channels are properly captured and visible in the NLE/DAW.
4. Test API commands in the expected control environment if remote or automated control will be used.
5. Conduct thermal and noise tests for PYXIS 12K to confirm dynamic fan control meets the production’s audio and cooling requirements.
6. Validate proxy/inhibit proxy settings to avoid surprises when proxies are or aren’t generated on set.

---

Risks, tradeoffs, and caveats (what to watch for)​

• Media wear — constant background writing increases write cycles and sustained media stress. While modern media is robust, prolonged continuous writes across many events will consume card life faster than intermittent recording.
• Throughput failures — if media cannot sustain the required continuous write rate, the buffer will fail to function reliably; this can show up as dropped frames or buffer corruption.
• Power interruption — pre‑record buffers do not survive power loss; a camera reboot generally discards the transient cache.
• Heat and noise — longer pre‑record operation increases device thermal load and may cause fans to ramp; the PYXIS 12K’s dynamic fan control mitigates this but does not eliminate all thermal risk.
• Implementation specifics not in public view — vendor posts and press articles describe behavior (writes to media card, configurable durations), but low‑level implementation details (exact buffering architecture, whether a portion of buffer uses volatile RAM before a committed write, how the camera handles power loss mid‑buffer) are not fully documented in those summaries. Until release notes or technical support documentation provide deeper explanations, teams should assume the buffer is media‑backed and test accordingly. This is a cautionary point where independent lab verification is recommended.

---

Integration: NLE, audio, and post workflows​

• Four internal audio tracks simplify editorial: editors can import footage with multiple discrete tracks already synced, reduce multicam audio wrangling, and preserve ambient or backup channels for safety tracks. Confirm how the NLE channels map on ingest to avoid surprises—some systems auto‑sum or reorder audio channels on import.
• Proxy inhibition matters for cloud or nearline ingest strategies—if proxies are disabled, ensure the editorial pipeline can ingest high‑res media fast enough, or enable an alternate proxy creation step in ingest workflows.

---

Upgrade and rollout guidance for rental houses, newsrooms, and production teams​

1. Stage the update on a test camera before fleet rollout.
2. Export camera presets, user LUTs, and custom profiles before upgrading; firmware updates sometimes reset user settings.
3. Prepare new media kits (cards/SSDs), labelled and stress‑tested for pre‑record use.
4. Update camera control and automation software stacks to use the new REST API commands only after confirming command behavior in a sandbox.
5. Update the operator checklist and run a rehearsal to bake the new capabilities into the crew’s standard operating procedures.

---

Cross‑checking the facts​

Multiple independent outlets that tested or reviewed the 10.0 release report the same headline facts: pre‑record up to 10 minutes, 4‑channel audio, mono headphone monitoring, dynamic fan control for PYXIS 12K, and REST API additions. Blackmagic Design’s own announcement (via its official channels) and trade coverage corroborate the release notes—this convergence provides a strong signal that the features listed are part of the official release. Nevertheless, teams that will rely on the features in critical live workflows should verify specifics against the official Blackmagic release notes and run hands‑on tests before depending on the features in mission‑critical production.

---

Conclusion — practical takeaways​

Blackmagic Camera 10.0 is a substantive firmware step that brings broadcast‑style safeguards and workflow options to PYXIS and URSA Broadcast G2 users. The ability to pre‑record up to 10 minutes closes a major gap between cinema‑style rolling‑record habits and broadcast/ENG needs, while 4‑channel audio, mono headphone monitoring, and backend improvements (REST API, proxy control, Cloud refinements) make these cameras more flexible in newsroom and live environments. The PYXIS 12K’s dynamic fan control addresses a real operational pain point for long, high‑data‑rate RAW shoots. Before deploying these features in production:

• Validate media performance and sustained write capability.
• Perform full power/thermal/long duration tests on the actual camera units and media to confirm behavior.
• Update operational checklists, and train operators on pre‑record usage and limitations.

This update brings meaningful, usable upgrades to both single‑operator and multi‑camera teams—but the new capabilities also come with the usual tradeoffs of heavier media usage and dependency on proven media and power regimes. Teams that treat the rollout with the standard engineering discipline—test, verify, document—will realize immediate practical benefits without surprises.

---

Source: No Film School Pre-Record For Up to 10 Minutes With the PYXIS and Other Blackmagic Cameras With Latest Update