export const meta = { title: "How to Configure RED RAPTOR Media to Avoid Dropped Frames", description: "Learn how to configure RED RAPTOR media, compression, proxies, formatting, and card allocation to prevent dropped frames during demanding high-data-rate shoots.", tldr: "To avoid dropped frames on RED RAPTOR, use RED-approved CFexpress Type B media, format cards in-camera, and match resolution, frame rate, REDCODE compression, and proxy settings to the card’s sustained write capability. Test the exact highest-load recording mode before the shoot, reserve high-endurance cards for high-speed or long high-data-rate takes, and keep media roles clear across card slots and offload cycles.", slug: "how-to-configure-red-raptor-media-to-avoid-dropped-frames", publishedAt: "2026-08-29", readingTime: 9, thumbnail: "https://cdn.aspectlabs.dev/blog/how-to-configure-red-raptor-media-to-avoid-dropped-frames/cover-d4230bbf8428.png", authors: ["bright"], primaryTopic: "camera-workflows", topics: ["camera-workflows"], tags: ["red"], faq: [ { "question": "Which CFexpress cards should I use with RED RAPTOR to avoid dropped frames?", "answer": "Use RED-approved CFexpress Type B media and choose the card class based on the recording workload, not just capacity. High-endurance cards are better for repeated high-data-rate recording, high-frame-rate work, hot environments, and cards that will be cycled heavily during the day. Capacity-focused cards can be appropriate for longer standard-speed recording when the data rate is less demanding." }, { "question": "Can a CFexpress card with enough free space still drop frames?", "answer": "Yes. Free capacity doesn't guarantee sustained write performance. A card can have plenty of available space but still be a poor recording target if it's fragmented, overheated, not approved for the mode, or has been used like a general-purpose drive. For best reliability, format the card in-camera and avoid deleting individual clips or writing unrelated files from a computer." }, { "question": "What settings most affect whether RED RAPTOR media can keep up?", "answer": "The biggest factors are resolution, recording frame rate, REDCODE compression ratio, sensor format, codec or project format, and whether in-camera proxies are enabled. Higher resolution, higher frame rate, lower compression, and simultaneous proxy recording all increase the sustained write load on the card." }, { "question": "Should I lower resolution or increase REDCODE compression first if media is struggling?", "answer": "It depends on the creative and post requirements. If the production needs full resolution for reframing, VFX, stabilization, or delivery, increasing REDCODE compression may be a better first compromise than lowering resolution. If the shot doesn't need the larger sensor format or full raster, reducing resolution can also reduce media pressure. The decision should involve the DP, post supervisor, colorist, or VFX supervisor when image quality requirements are strict." }, { "question": "What should I do if the camera reports dropped frames or a media error?", "answer": "Stop treating that card and setting combination as safe. Protect the recorded material, switch to a freshly formatted approved card, and test again at the same recording mode. If the issue follows one card, quarantine that card. If it happens across multiple approved cards, reduce the data rate by changing compression, frame rate, resolution, proxy settings, take length, or cooling conditions, and confirm camera and media firmware are current." }, { "question": "Should we record in-camera proxies when the camera is close to its media write limit?", "answer": "If the recording mode is already high risk, post-generated proxies are often safer because they remove extra writes from the CFexpress card during capture. Aspect can create proxies and previews after upload, which keeps acquisition focused on the camera original while still giving editorial lightweight media for fast access and review." } ], } The safest RAPTOR media setup is simple: use RED-approved CFexpress Type B media, format it in-camera, and choose the lowest data-rate recording setting that still protects the image requirements of the job. Dropped frames usually show up when one of those three things is out of alignment: the card can't sustain the write, the selected resolution/frame rate/compression combination is too aggressive, or your team has treated the card like a general-purpose drive between shoots. V-RAPTOR-class cameras are built for high-data-rate work, including large-format R3D recording and high-speed modes, but you do need to treat the camera, media, and offload plan as one system. A card that's fine for 8K 24 fps may not be the card you want for repeated high-speed takes all day. A setting that works on a fresh card may fail after your team has filled the same card, partially deleted files on a laptop, used it for random files, and put it back in the camera. This is where most “dropped frame” prevention actually happens: before the slate. ## Start with sustained write speed, not card capacity CFexpress cards are often marketed by capacity and peak read speed. For RAPTOR recording, the more important number is sustained write performance under heat. Video capture isn't a burst workload, so the card has to accept a continuous stream of data until the take ends, and it has to keep doing that after the card warms up. RED’s current RAPTOR media options include RED CFexpress Type B options in 660 GB, 1.3 TB, 2 TB, and 4 TB capacities. RED notes that the 660 GB and 2 TB cards share the same underlying hardware, and the 1.3 TB and 4 TB cards share the same underlying hardware. The difference is how the media is configured in software and firmware. The split matters: - 2 TB and 4 TB cards prioritize capacity while maintaining durability for normal production use. - 660 GB and 1.3 TB cards are [overprovisioned to prioritize](https://docs.red.com/955-0199/955-0199_V1.3_Rev-B_RED_PS_V-RAPTOR_8K_VV_Operation_Guide/Content/D_Accessories/CFexpress.htm) extended write cycles and improved thermal performance during constant writing and rewriting. - The high-endurance options are better suited to heavy daily cycling, repeated high-speed recording, and productions that turn cards around continuously. The right card depends on how the shoot behaves. If you're doing long-form interviews at moderate settings, capacity may matter more. If you're doing automotive, tabletop, sports, plates, action, or anything with repeated high-frame-rate bursts, endurance and thermal behavior matter more than raw terabytes. For the highest-risk recording days, treat high-endurance media as the default. Capacity media is still useful, but it shouldn't be the card you discover can’t keep up after lunch. ## Understand what pushes the write load up A RAPTOR recording setting isn't one variable because the write load comes from the combination of resolution, frame rate, codec, compression, and proxy behavior. Change one and the card may still be fine, but change three and you may move from safe to marginal. The main settings that affect write load are: - Resolution: 8K writes much more data than 6K, 4K, or 2K at the same compression and frame rate. - [Recording frame rate](https://docs.red.com/955-0199/955-0199_V1.2_Rev_A_RED_PS_V-RAPTOR_Operation_Guide/Content/4_Menus/b_ProjSet/RecFrameRate.htm): doubling the capture fps roughly doubles how many frames the camera has to write. - REDCODE compression: lower compression means higher quality and higher data rate. Higher compression lowers data rate. - Project format: R3D, R3D plus proxy, and ProRes modes have different media demands. - Sensor format: lower resolutions may use a smaller area of the sensor, which can change field of view as well as data rate. - ProRes proxy recording: proxies are helpful for editorial, but they add additional writes during capture. RED’s documentation describes R3D as a [compressed RAW format](https://docs.red.com/955-0225/955-0225_V2.0+Rev-A+RED+PS,+V-RAPTOR+%5BX%5D+8K+VV+Operation+Guide/Content/4_Menus/b_ProjSet/Proj_Format.htm) that stores image settings like ISO, saturation, LUTs, and color metadata non-destructively rather than baking them into the image. That flexibility is useful, but it also means you should be deliberate about the compression ratio instead of treating it as an afterthought. A good starting rule is to decide the creative requirement first, then reduce write load in the least destructive place. If the shot truly needs 8K, keep 8K and consider a more compressed REDCODE setting. If it needs high-speed motion but not full sensor width, a lower resolution high-speed format may be the better trade. If editorial needs fast turnaround, consider whether in-camera proxies are worth the additional media load, or whether your team should generate proxies after offload. ## Match recording settings to the card before the shoot day RED cameras expose these choices through [Project Settings and the Media menu](https://docs.red.com/955-0199/955-0199_V1.3_Rev-B_RED_PS_V-RAPTOR_8K_VV_Operation_Guide/Content/4_Menus/e_Media/01_Intro_Media.htm). The exact menu labels vary a bit by model and firmware, but the workflow is consistent: set the project format, sensor format, recording frame rate, REDCODE compression, and proxy behavior before you decide that a card is “approved” for the day. For RAPTOR-class cameras, the risk tiers usually look like this: | Risk tier | Typical configuration | Why it raises or lowers media risk | Safer operating response | |---|---|---|---| | Lower risk | Standard frame rates, moderate resolution, R3D at a more compressed setting, no simultaneous proxy | Sustained write demand stays well below the most demanding camera modes | Use approved media, format in-camera, and keep normal card rotation discipline | | Medium risk | 8K at standard frame rates, lower REDCODE compression, or proxy recording alongside R3D | Resolution, compression, or extra proxy writes increase the sustained load | Test the exact card and mode before shoot day, especially for long takes | | Higher risk | 8K high frame rate, low compression, repeated long takes, hot environments, or heavily cycled media | Multiple high-load factors combine and can expose thermal or endurance limits | Prefer high-endurance media, improve cooling, or reduce one write-load variable | | Highest risk | Maximum camera modes, high ambient heat, long rolling takes, and cards selected mainly for capacity | The setup is operating close to the limits of the camera and media system | Run a stress test at the planned mode, reserve best media for these shots, and have a lower-data-rate fallback | - Lower risk: standard frame rates, moderate resolution, R3D at a more compressed setting, no simultaneous proxy. - Medium risk: 8K at standard frame rates, lower compression, or proxy recording alongside R3D. - Higher risk: 8K high frame rate, low compression, repeated long takes, hot environments, or media that your team has cycled heavily. - Highest risk: maximum camera modes, high ambient heat, long rolling takes, and cards your team selected for capacity rather than endurance. Some published production guides summarize internal CFexpress limits by mode. For example, RED [V-RAPTOR XE guidance](https://www.lensrentals.com/product-assets/ca5e2c03-b7b5-4950-a400-3711198f8055/Camera%20Production%20Guide%20-%20RED%20V-RAPTOR%20XE%208K%20VV%20.pdf) lists high-speed REDCODE RAW examples such as 8K up to 60 fps at LQ on internal CFexpress, 4K up to 120 fps, and 2K up to 240 fps at HQ. RED’s own V-RAPTOR [X] documentation also references CFexpress Type B media for high-data-rate formats [up to 800 MB/s](https://docs.red.com/955-0199/955-0199_V1.2_Rev_A_RED_PS_V-RAPTOR_Operation_Guide/Content/C_TechSpecs/Specs_V-RAPTOR.htm), including 8K 120P on supported models. Those numbers are useful, but they shouldn't replace a camera-specific test. The supported ceiling depends on the exact camera body, firmware, media firmware, sensor format, and recording configuration. If production plans to live near the ceiling, test the exact setup, not a similar one. A simple way to think about it: the camera spec tells you what is possible. Your media test tells you what is safe for this job. ## Choose compression with both post and the card in mind When a card starts dropping frames, the first reaction is often to lower resolution. That may be the wrong move because, on RED, REDCODE compression gives you another lever. Because R3D is RAW and stores many image decisions as metadata, moving to a more compressed REDCODE setting may be a better compromise than losing resolution or changing framing. For many productions, the difference between compression settings is less damaging than giving up 8K reframing, stabilization room, VFX plate resolution, or a required sensor crop. Aspect streams large R3D files to Finder or your NLE, so an editor can start cutting without waiting for a full download. That makes high resolution camera originals easier to keep, because nobody has to make a temporary local duplicate. That said, compression isn't free. Lower compression settings preserve more data but increase card load and storage footprint. Higher compression settings reduce the risk of dropped frames and reduce offload volume, but you should clear the setting with the DP, colorist, VFX supervisor, or post supervisor if the project has heavy grade, green screen, beauty work, or archival requirements. A useful conversation before camera prep sounds like this: - Which shots actually require maximum resolution? - Which shots require maximum frame rate? - Which shots require the lowest available compression? - Which shots need in-camera proxy recording? - Which shots can safely use a lighter data-rate setting? This avoids the common trap of setting the whole day to the most demanding combination because one shot needs it. RAPTOR gives you a lot of latitude, but the media only sees sustained data. ## Format cards in-camera and keep them camera-only Formatting discipline is one of the cheapest ways to avoid dropped frames. RED’s media guidance is direct: your team should [format CFexpress media in-camera](https://docs.red.com/955-0199/955-0199_V1.2_Rev_A_RED_PS_V-RAPTOR_Operation_Guide/Content/5_How_To/Media/MediaBestPractices.htm), and shouldn't delete clips from the card using a computer. The camera uses exFAT to support large files and high data rates, but your team shouldn't treat the card like a portable SSD. The behaviors that create media problems are usually boring: - Deleting selected clips on a laptop instead of formatting in-camera. - Copying non-camera files, folders, or applications onto the card. - Letting macOS use the card for Time Machine prompts or hidden system clutter. - Pulling media without ejecting it properly. - Mixing firmware states across cards. RED specifically warns against saving general files to the card. Your team should write only files like presets, firmware upgrade files, and LUTs from a computer to the card. RED also warns not to use the CFexpress card as a backup disk and not to delete clips from the card on a computer. The reason is fragmentation and data integrity, because a card can look like it has enough free space and still be a bad recording target if the free space is fragmented or the filesystem has been dirtied by non-camera writes. Secure formatting in-camera gives the camera the clean recording target it expects. Also, [don't put adhesive labels](https://docs.red.com/955-0199/955-0199_V1.0_Rev_A%20RED_PS_V-RAPTOR_Operation_Guide/Content/5_How_To/Media/MediaMgmt.htm) on CFexpress cards. RED warns that heat can weaken the adhesive, labels can detach inside the camera, and labels can reduce heat dissipation. Use cases, sleeves, color-coded wallets, or external card logs instead. ## Build a pre-flight that stresses the actual recording mode A media test is only useful if it matches the hardest thing the camera will do. Rolling 8K 24 fps for ten seconds doesn't prove that the card will survive repeated high-speed takes in a hot car rig. Before the shoot, test the exact combination that your team will use for the heaviest scene: - Camera body and firmware version. - Media model, capacity, and media firmware where applicable. - Project format and sensor format. - Recording frame rate and project time base. - REDCODE compression. - Proxy recording enabled or disabled. - Expected take length. - Expected ambient temperature and camera build, including cages, plates, and airflow restrictions. Recording frame rate deserves special attention because it's different from project time base. RED’s documentation describes recording frame rate as the number of frames captured per second, while project time base is the playback rate. A 120 fps recording in a 24 fps project is a much heavier media event than normal-speed 24 fps capture. Make sure the test is using the recording frame rate, not just the timeline base. If the camera throws a media warning, stops recording, or shows dropped-frame behavior during the test, don't try to “watch it carefully” on the day. Change one of the variables: use a faster or higher-endurance card, increase REDCODE compression, reduce frame rate, lower resolution, disable simultaneous proxy, shorten take length, improve cooling, or split that setup onto a different camera/media plan. ## Plan card allocation by slot and by workload On a single-slot RAPTOR body, allocation is simple but unforgiving: each card is either safe for the current recording mode or it isn't. Don't rotate in unknown cards because the approved cards are full. Label the card case, not the card itself, and separate media by status: blank, exposed, offloaded, verified, and cleared for format. On dual-slot RAPTOR XL-style workflows, don't treat both slots as interchangeable unless the media in both slots is identical in performance class and condition. If one slot has a high-endurance card and the other has a capacity-optimized card, the recording plan should reflect that. A sane allocation strategy is to group cards by the job they're allowed to do: - Reserve high-speed cards for maximum frame rate, low compression, or long high-data-rate takes. - Use general cards for standard frame rate dialogue, interviews, and controlled B-roll. - Use capacity cards when runtime matters more than cycling intensity. - Remove retired or suspect cards from camera rotation until tested or replaced. This is especially important when the shoot bounces between modes. A crew might shoot 8K 24 fps dialogue for most of the morning, then jump into 8K high-speed inserts for fifteen minutes. If the crew treats every card the same, the wrong card ends up in the camera at the exact moment the data rate spikes. For larger sets, make the card role visible in the media log. The loader or DIT should know whether an empty card is approved for the next setup. The assistant camera team should know when a mode change also requires a media change. ## Don’t let offload habits damage capture reliability Dropped frames are a capture problem, but offload habits can create the conditions for them. The moment a card leaves the camera, the media workflow needs to preserve both the footage and the card’s future reliability. RED’s media management guidance emphasizes ejecting media properly before removing it, and that applies both in-camera and on the computer side. If you mount the card on a workstation, reader, or offload cart, eject it cleanly before pulling it. Sudden removal can create filesystem issues that may not be obvious until the card goes back into the camera. For post, R3D files are widely supported, but RAW workflows still need some setup. In Final Cut Pro, for example, Apple notes that REDCODE RAW support requires the RED Apple Workflow Installer, and it recommends importing R3D files before generating optimized or proxy media if post will adjust RAW settings. That's a post-production detail, but it affects production planning: if post wants proxies, decide whether your team should record them in-camera or post should generate them after verified offload. In-camera proxies can speed editorial handoff, but they aren't free during acquisition. Post-generated proxies add time after offload but reduce camera-side write load. For high-risk recording modes, pushing proxy generation downstream may be the safer call. Aspect automatically generates previews and proxies for uploaded RED media, so editorial can review and organize clips without adding proxy writes in camera. That lets production keep the capture setting safer while post still gets lightweight files to work from. ## When dropped frames happen anyway If a RAPTOR reports dropped frames or media errors, treat it as a system warning. The immediate fix is to protect the take and reduce write pressure. The follow-up is to isolate whether the issue is the card, the settings, the camera firmware, or the environment. Common causes include: - Unsupported or non-approved media. - Heat buildup during long or repeated takes. - Fragmented media from deleting files on a computer. - Mixed card firmware or outdated media firmware. - Simultaneous proxy recording pushing the write load over the edge. RED’s troubleshooting guidance starts with firmware, rebooting, and testing with an alternate recently formatted CFexpress card. That's a good order of operations on set too. If a second freshly formatted approved card works at the same settings, quarantine the first card. If both cards fail, lower the data rate or investigate camera configuration, firmware, and thermal conditions. Don't put a suspect card back into rotation because it records a short easy take. Test it at the same or higher load than the failed setup. If it can't pass that, it doesn't belong in the day’s media pool. ## The setting is safe when the whole chain is safe Avoiding dropped frames on RED RAPTOR media means matching the recording mode to sustained card performance and keeping the media clean enough to deliver that performance all day. For most productions, the reliable pattern is consistent: approved CFexpress Type B media, high-endurance cards for heavy write days, in-camera formatting, no computer-side deletions, current firmware, and a real test at the highest planned data rate. Then allocate cards according to workload instead of capacity alone. That gives the camera team room to use high-resolution RAW, high-speed capture, and flexible post workflows without turning every record press into a media gamble.