M4 Mac Studio optimisation — ProRes, proxies, multi-format delivery, and a repeatable professional workflow
Focus: Optimising DaVinci Resolve on the M4 Mac Studio — performance, storage, and project organisation.
M4 Mac Studio — the Resolve workflow advantagesThe M4 Mac Studio's unified memory architecture means CPU, GPU, and RAM share the same memory pool — eliminating the bandwidth bottleneck between separate CPU RAM and GPU VRAM that affects Intel/AMD systems. For Resolve: 4K ProRes 422 HQ footage plays natively without proxies. 4K H.265 S-Log3 footage may need optimised media for smooth real-time playback. 4K HDR footage in Rec.2020 space plays smoothly. The M4's hardware ProRes encode/decode engine makes ProRes exports and optimised media generation significantly faster than software encoding.
Storage strategy — fast, redundant, and organisedYour M4 Mac Studio has an internal SSD rated at approximately 3,000–7,000 MB/s read (depending on configuration). For active projects: store your project folder on the fastest available SSD — either the internal drive or a Thunderbolt 4 external SSD (OWC Envoy Pro FX, Samsung T7 Shield, or similar rated at 1,000–2,000 MB/s). For backup: use a separate external drive (or NAS) that is never the primary editing drive. For archive: use HDDs (cheaper per TB) for long-term cold storage of completed projects.
Resolve project organisation — the Power Bins strategyPower Bins in Resolve persist across all projects — anything you put in a Power Bin is available in every project without re-importing. Use Power Bins for: your standard LUTs, motion graphic templates (ProRes 4444 from Cavalry), music libraries, commonly used sound effects, your base grade stills (.drx files), and your delivery presets. Set up your Power Bins once — properly — and they will save you 15–30 minutes of setup time per project across your career.
Optimised media and proxy workflowIn Resolve: right-click clips in the media pool → Generate Optimised Media. Resolve creates lower-complexity versions for editing (H.265 → ProRes 422 proxy) and seamlessly switches to originals for export. For 4K H.265 footage from the a6700 in a complex multi-clip timeline: optimised media is often necessary for smooth real-time playback. Set the optimised media format in Preferences → Media → Optimised Media and Render Cache — ProRes 422 at the resolution of your timeline is the standard setting.
The render cache — Resolve's hidden performance toolResolve's Render Cache stores processed versions of clips in memory — once a clip is cached (shown by a blue or red bar above it in the timeline), it plays back at full quality without the computer re-processing it in real time. Set the Render Cache to Smart mode (Playback → Render Cache → Smart) — Resolve will automatically cache complex clips (those with colour grades, Fusion effects, or heavy noise reduction) while leaving simple clips uncached. The cache is stored on your fast SSD — ensure you have sufficient free space (10–20% of the drive is a minimum).
Drill 1
Resolve performance benchmark
Create a test timeline with 10 minutes of 4K H.265 S-Log3 footage from the FX30. Play back without optimised media — note the playback frame rate (shown in the viewer). Generate optimised media for all clips. Play back again. Generate optimised media at half resolution. Compare all three playback experiences. Document the results and determine the minimum optimised media resolution that gives smooth playback on your specific M4 configuration.
Drill 2
Storage speed test
Using the Disk Speed Test app (free on the Mac App Store), test the read and write speeds of: your internal M4 Mac Studio SSD, and any external SSDs you use for editing. Compare the results against the speed requirements for smooth 4K ProRes 422 HQ playback (approximately 500 MB/s minimum for a single stream, 1,500 MB/s for a 3-camera multi-cam timeline). Identify any storage bottlenecks in your current setup.
Drill 3
Power Bins setup
In Resolve, set up your definitive Power Bins structure: (1) LUTs — your creative grade LUTs and S-Log3 monitoring LUTs, (2) Stills — your best grade stills as .drx files, (3) Graphics — your Cavalry motion graphics as ProRes 4444 files, (4) Music — your most-used licensed tracks, (5) SFX — your most-used sound effects. Populate each bin. Test by creating a new project and confirming all Power Bin assets are immediately available.
Drill 4
Render cache optimisation
On a complex timeline (with colour grades, Fairlight audio, and at least one Fusion composition), enable Smart render cache. Let Resolve cache all complex clips. Measure the timeline playback frame rate before and after caching. Monitor the cache folder size in Preferences. Establish how much disk space your typical project's cache requires and plan your SSD allocation accordingly.
Week 1 Assignment
"Optimised Resolve workflow documentation"
Produce a 1-page workflow reference document for your personal M4 Mac Studio Resolve setup: storage configuration (which drive holds what), Resolve Preferences settings (optimised media format, render cache settings, GPU settings), Power Bins structure, and your standard project setup checklist. This document is a professional reference you would hand to an assistant editor.
Storage configuration is clearly diagrammed or described
All relevant Resolve Preferences settings are specified
Power Bins structure is complete and populated
Project setup checklist covers all steps from blank project to ready-to-edit
DaVinci ResolveM4 Mac Studio
Focus: Codec strategy — understanding ProRes, H.264, H.265, and when to use each.
Codec fundamentals — what a codec actually doesA codec (compressor-decompressor) is an algorithm that reduces the size of video data by discarding information the human eye is unlikely to notice. The key trade-offs: quality (how much information is preserved), file size (how much the data is compressed), and processing demand (how much computing power is needed to encode and decode). In post-production, high-quality codecs (ProRes, DNxHD) are used because they are fast to decode and minimally compressed — important for colour grading and effects work. For delivery, efficient codecs (H.264, H.265) are used because they produce small files at acceptable quality — important for streaming and distribution.
ProRes — the production codecApple ProRes is a family of intraframe (each frame is complete in itself — no delta frames) codecs designed for post-production. The variants: ProRes 4444 XQ (highest quality, largest files — 500–700 MB/min at 4K), ProRes 4444 (with alpha channel — for motion graphics), ProRes 422 HQ (high quality — the standard for camera originals and master deliverables), ProRes 422 (medium quality — proxy and optimised media), and ProRes 422 LT / Proxy (smaller files for remote review). On the M4 Mac Studio, ProRes encode and decode is hardware-accelerated — ProRes exports are dramatically faster than on Intel machines.
H.264 and H.265 — the delivery codecsH.264 (AVC) is the universal delivery codec — plays on virtually every device without compatibility issues. At 4K, H.264 files are typically 15–35 Mbps for consumer use and 35–68 Mbps for high-quality delivery. H.265 (HEVC) offers roughly 50% better compression than H.264 at the same quality — a 4K H.265 file is approximately half the size of an equivalent H.264 file. The trade-off: H.265 requires more processing power to encode and decode, and some older devices and platforms do not support it. Use H.264 for maximum compatibility (email links, client previews, older platforms). Use H.265 for YouTube, Vimeo, and modern platforms where file size matters.
The ProRes master workflowThe recommended professional workflow: record in H.265 or H.264 (small files on card) → edit in ProRes (generate optimised media on the M4, which converts H.265 to ProRes for editing) → grade in ProRes → export a ProRes 422 HQ master (the archive quality version) → transcode the master to H.264/H.265 for delivery. The ProRes master is your insurance policy: if a platform changes its compression standards, or a client needs a different format, you transcode from the master rather than from a compressed delivery file.
Frame rate and codec compatibilityAlways match your delivery frame rate to your production frame rate. Mismatched frame rates cause speed errors: H.265 footage shot at 25fps in a 30fps Resolve timeline plays too fast (as if time-accelerated). In Resolve's Deliver page, always confirm the Output frame rate matches your timeline frame rate before rendering. For slow motion footage (shot at 50fps or 120fps), the timeline is typically 25fps — the footage is conformed to 25fps and plays at 50% or 20% speed.
Drill 1
Codec quality and size comparison
Export the same 60-second timeline in six codec variants: ProRes 4444, ProRes 422 HQ, ProRes 422, H.264 at 68 Mbps, H.264 at 20 Mbps, and H.265 at 35 Mbps. Record the file size of each. Open all six in QuickTime Player and compare quality at 100% zoom. Note where you first see quality loss compared to ProRes 4444. This comparison makes codec selection decisions concrete and informed rather than theoretical.
Drill 2
Export speed benchmark
Export the same 10-minute ProRes 422 HQ timeline in three ways: from the Deliver page using hardware ProRes encoding, from the Deliver page using software ProRes encoding (disable hardware acceleration in Preferences), and as H.265 using hardware encoding. Time all three. Compare the export speeds. The M4's hardware ProRes encoder should produce significantly faster results than the software encoder.
Drill 3
Delivery format matrix
Create a definitive personal delivery format matrix: for each of your five most common delivery destinations (YouTube, Vimeo, Instagram Reels, Instagram Feed, broadcast/client master), document: the exact Resolve Deliver settings you use (codec, resolution, frame rate, audio codec, audio bitrate). Save each as a named Deliver preset. Test each by exporting a 30-second test clip and uploading to the relevant platform.
Drill 4
H.265 compatibility audit
Test your H.265 delivery files on three different devices: your Mac Studio (native playback), an iPhone, and any TV or streaming device you own. Confirm smooth playback on all three. If any device struggles with H.265, note it as a client communication point — some clients' in-house review systems may not support H.265 smoothly.
Week 2 Assignment
"Codec strategy reference guide"
Produce a 1-page codec strategy reference guide for your production workflow: when you use each codec and why, your standard ProRes master export settings, your five delivery format presets (with exact settings), and your recommended client preview format. This document should be practical enough to use as a quick reference during a client delivery session.
Reference guide covers all production and delivery codecs
Standard ProRes master export settings are specified and correct
Five delivery format presets are documented with exact settings
Client preview format recommendation is justified
Document is formatted clearly enough to use as a real reference
DaVinci ResolveM4 Mac Studio
Focus: Multi-format delivery — preparing and delivering content for multiple platforms simultaneously.
Aspect ratio strategy — designing for multi-formatModern video content often needs to exist in multiple aspect ratios simultaneously: 16:9 for YouTube and Vimeo, 9:16 for Instagram Reels and TikTok, 1:1 for Instagram feed, and 4:5 as a portrait alternative to 9:16. Shooting strategy: if you know multi-format delivery is required, frame your 16:9 shots with important subject matter in the central third of the frame — the 'safe zone' that will survive all crop ratios. Use your camera's 4:5 or 9:16 guide overlay (available in the a6700 and FX30) while shooting 16:9 to confirm the key subject matter is within the crop boundary.
Resolve's multi-format delivery workflowIn Resolve's Deliver page, you can add multiple render jobs simultaneously. Create a job for each delivery format and queue them all — Resolve renders each sequentially. Use a 16:9 master timeline, then create additional timelines for 9:16 and 1:1 versions with adjusted framing (use the Transform controls in the Inspector to reposition each clip). Some operators prefer to create separate timelines for each aspect ratio; others use Resolve's Smart Reframe feature (which uses AI to automatically reframe clips for different aspect ratios — useful as a starting point, always requires manual refinement).
Audio loudness across multiple platformsDifferent platforms have different loudness standards. In a single Resolve session delivering to multiple platforms: create a Fairlight bus for the full mix output. Use the Loudness Meter to measure integrated LUFS. For YouTube delivery (-14 LUFS), the full mix level is your primary target. For broadcast delivery (-23 LUFS), reduce the master fader by approximately 9 dB from your YouTube level, export, and reset. Note: do not simply turn down the export level — recalibrate the Fairlight mix for each delivery standard to ensure the dynamic range and balance remain correct at the target loudness.
Subtitles and captions for accessibilitySubtitles and captions significantly increase watch time on YouTube and social media and are legally required in some broadcasting contexts. In Resolve: create a Subtitle track in the Edit page (Timeline → Add Subtitle Track). Add subtitle clips by clicking in the subtitle track. Set the font, size, and position in the Inspector. Export the subtitles as: burnt-in (embedded into the video), sidecar .srt file (for uploading to YouTube separately), or SRT-embedded in an MKV container. For a professional client delivery, providing a .srt file alongside the video file is considered standard practice.
Delivery naming conventions and metadataWhen delivering multiple versions of the same content, naming is critical. Convention: ProjectName_ClientName_Version_Format_Date.ext. Example: RestaurantBrand_CafeNoma_v03_YT16x9_20260615.mp4. For the same project with multiple aspect ratios: RestaurantBrand_CafeNoma_v03_IG9x16_20260615.mp4. Metadata embedded in the file (via Resolve's Deliver page → Metadata) should include: project name, copyright, frame rate, and codec. Consistent naming and metadata makes files findable and identifiable years after delivery.
Drill 1
Multi-format delivery workflow — timed
Take a 90-second finished edit. Create three delivery timelines: 16:9 (YouTube), 9:16 (Instagram Reels), and 1:1 (Instagram Feed). Reframe the 9:16 and 1:1 versions manually in Resolve using the Transform controls. Queue all three render jobs in the Deliver page. Time the complete render for all three formats. Review the results on your phone to confirm mobile compatibility.
Drill 2
Smart Reframe test
Take the same 90-second edit. Apply Resolve's Smart Reframe feature to create a 9:16 version automatically. Compare the Smart Reframe result against your manual reframe from Drill 1. Note: where does the AI make good decisions? Where does it make obviously wrong ones? How much manual correction does the Smart Reframe result require? This comparison tells you when to use Smart Reframe vs manual.
Drill 3
Subtitle workflow
Take a 2-minute interview segment. Create a complete subtitle track in Resolve for the entire interview — every spoken line must be subtitled accurately. Export the video with burnt-in subtitles (a single file), and separately export the video with a sidecar .srt file. Upload the .srt version to a private YouTube video and confirm the subtitle upload works correctly.
Drill 4
Complete multi-platform delivery package
Take a finished commercial project from Module 20. Produce the complete multi-platform delivery package: YouTube 4K 16:9, Instagram Reels 1080p 9:16, Instagram Feed 1080p 1:1, and a ProRes 422 HQ master. Name all files according to your naming convention. Deliver as a Dropbox or Google Drive folder share link. This is the format in which you will deliver all future commercial projects.
Week 3 Assignment
"Multi-format delivery package"
Produce a complete multi-format delivery package for a 60–90 second piece: YouTube 4K 16:9 (H.264), Instagram Reels 1080p 9:16 (H.264), Instagram Feed 1080p 1:1 (H.264), and a ProRes 422 HQ master. Include a .srt subtitle file. Name all files according to your standard convention. Deliver as a shared folder link.
All four format deliverables are present and play correctly
9:16 and 1:1 versions have been manually reframed — important elements are not cropped
Subtitle file is correct and plays synchronised with the video
All files are correctly named according to the standard convention
DaVinci ResolveM4 Mac Studio
Focus: Building a repeatable, efficient post-production workflow — from ingest to delivery in a consistent, professional system.
The complete post-production timeline — setting realistic expectationsFor a 2-minute commercial film, a realistic post-production timeline is: Day 1 — ingest, sync, rough assembly. Day 2 — rough cut. Day 3 — first cut delivery. Client feedback (allow 3–5 days). Day 8 — revisions and second cut. Day 9 — colour grade. Day 10 — audio mix. Day 11 — final approvals and export. Day 12 — delivery. Total: 12 working days, or approximately 3 weeks including client feedback time. Build this realistic timeline into your client agreements — it prevents the pressure that leads to quality compromises.
Automation and efficiency tools — keyboard shortcuts and macrosThe difference between a 2-hour post-production session and a 4-hour session on the same material is often not skill — it is automation. Invest time in: learning every Resolve keyboard shortcut relevant to your workflow (J/K/L for playback, I/O for marking, F9/F10 for placement), creating custom keyboard shortcuts (Resolve allows full remapping), using Fusion macros for common compositing operations, and building Smart Bins that auto-organise your media. Every 30-second shortcut that saves you 5 minutes per use pays back in the first week.
Template projects — starting every new project from a known good stateYour project template (built in Module 6 and refined throughout the course) should be the starting point for every new client project. Open the template, import it as a new project, rename it, and immediately update: the bin structure with this project's specific content, the timeline settings if the delivery spec differs from the standard, and the Power Bins to confirm all required LUTs and graphics are available. This 10-minute project setup prevents the 2-hour 'find the LUT' emergency mid-grade.
Quality control — the final check before deliveryBefore delivering any file to a client, run a final quality control (QC) check: (1) watch the entire film without stopping and without any editing tools in front of you — just watch it as the client will, (2) check the audio on three different listening systems (ATH-M40X, laptop speakers, earbuds), (3) check the video on two different screens (your calibrated monitor and your phone), (4) verify the file plays correctly in a web browser or the target platform, (5) confirm the file name and delivery format match the client specification. Only then deliver. A QC issue discovered after delivery requires a re-delivery conversation — a QC issue discovered before delivery is a private technical problem.
Continuous improvement — the retrospectiveAfter every delivered project, spend 30 minutes writing a retrospective: what went well in the production, what went well in the post-production, what went poorly, and specifically what you would change on the next similar project. These retrospectives, accumulated over time, become your most valuable professional development resource — a personal record of your growth and the specific lessons that produced it.
Drill 1
Post-production timeline creation
For your fictional restaurant project from Module 20, create a complete post-production timeline: specific calendar dates from ingest through to final delivery. Include: ingest and rough assembly, rough cut, first cut delivery, client feedback window, revisions, colour grade, audio mix, final approval, and delivery. Build in realistic time for each stage based on your actual experience from the course.
Drill 2
Keyboard shortcut audit
In Resolve's keyboard shortcut customisation page (Resolve → Keyboard Customisation), review all shortcuts relevant to your workflow. Identify any function you regularly perform with the mouse that has an available keyboard shortcut. Add at least 5 keyboard shortcuts to your workflow this week. After one week, assess how much time those shortcuts have saved.
Drill 3
Project template update — final version
Using everything you have learned in Phases 3 and 4, update your DaVinci Resolve project template to its final, most sophisticated version: RCM colour management, group grade structure, Fairlight bus structure with stem routing, all Power Bins populated, and all delivery presets saved. Export as a .dra archive and save it in a 'Master Templates' folder. This is your definitive working template — replace all previous versions.
Drill 4
Complete project retrospective
Write a retrospective on the most complex project you have completed in this course. Use the format: (1) what went well in production, (2) what went poorly in production, (3) what went well in post, (4) what went poorly in post, (5) three specific changes you would make if you were to do this project again. This retrospective should be 400–600 words and honest — it is a private professional development document.
Week 4 Assignment
"Complete post-production workflow documentation"
Produce a complete personal post-production workflow guide: your standard post-production timeline (specific stages and realistic time allocations), your definitive Resolve project template (.dra archive), your codec strategy reference guide (from Week 2), and a project retrospective for any completed course project. Together these four documents constitute a professional post-production operations manual.
Post-production timeline has specific stages and realistic time allocations
Resolve project template is complete and exports as a working .dra archive
Codec strategy reference guide is accurate and usable
Project retrospective is honest, specific, and actionable
DaVinci ResolveM4 Mac Studio
Editing directly from the camera card
Editing directly from an SD or CFexpress card means if the card is removed or fails, the entire project is lost. Camera cards are not designed for the repeated random-access reads of editing.
Fix: Always copy all footage to your primary editing SSD before importing into Resolve. Make a backup copy to a second drive. Only format the card once both copies are verified.
Using H.265 for everything including master files
H.265 is compressed delivery codec — not ideal as a master or archive format. Each time you encode from H.265 to another format, generation loss accumulates — reducing quality with each transcode.
Fix: Keep your master files as ProRes 422 HQ or higher. Use H.265 and H.264 only for delivery files. Your ProRes master is the definitive version from which all delivery formats are transcoded.
Delivering without a final QC check
Delivering a file with a colour-grading error, an audio sync problem, or a metadata issue after it has been sent to a client creates a re-delivery conversation that damages confidence in your professionalism.
Fix: Always run the complete 5-point QC check before every delivery: watch the full film without stopping, check audio on three systems, check video on two screens, verify playback in a browser, and confirm the file name matches the client spec.
The Resolve Smart Cache is your best free performance upgrade
Enable Render Cache → Smart mode on every project. Resolve will cache complex clips automatically in the background as you work — by the time you have reviewed a sequence and are ready to play it back, it is already cached and plays at full quality. The cache lives on your fast SSD and costs no extra time — it runs in the background while you are doing other work.
SW:DaVinci Resolve · M4 Mac Studio
Export your ProRes master first, then transcode
Always export the ProRes 422 HQ master first. Then use Resolve's Deliver page or FFMPEG to transcode the master to your delivery formats. This is faster and safer than rendering multiple lossy formats from the timeline — and gives you a permanent high-quality archive of every delivered project.
SW:DaVinci Resolve · M4 Mac Studio
Build your delivery preset library before you need it
Creating a new Resolve delivery preset under deadline pressure is how configuration mistakes happen. Build and test all your delivery presets (YouTube, Vimeo, Instagram Reels, Instagram Feed, ProRes master, broadcast) when you are not under pressure. Test each preset with a 30-second clip uploaded to the relevant platform. Save the presets. Then never rebuild them under deadline again.