For those who don’t know the tool: Fusion Studio is a node-based compositor for VFX and motion graphics, living next to DaVinci Resolve and sharing its licensing universe, minus the timeline politics.

Motion graphics gets a bigger toolbox

Fusion Studio 21 adds support for Krokodove motion graphics effects, plus over 70 new motion graphics effects and tools. A new Macro Editor arrives with an inspector view and publishing to macros, aimed at making reusable tool setups less of a scavenger hunt.

Text tools also pick up practical upgrades. Text+ and MultiText add spell checking. Font handling expands with emoji and color fonts, plus a font browser for previewing and selecting fonts. MultiText adds improvements for position, pivot, alignment, and CSV import, and it gains double and triple click selection with drag selection, which should make dense text comps less like surgery with oven mitts.

Roughly a third into testing, expect your existing templates and macros to need a quick sanity pass, because new editors tend to surface old assumptions. That is normal. Test new tools before you trust them in production.

SPEEEEEEEEEED

Fusion 21 also leans harder into retiming with the SpeedWarp node SPDw. SpeedWarp is an AI powered retiming tool that analyzes motion between existing frames to construct new intermediate frames for smooth slow motion without stuttering. It uses DaVinci’s neural network and supposed to be good at reconstructing complex motion where traditional interpolation or frame blending would typically blur or distort.

HTML and JSON graphics walk right in

Fusion Studio 21 adds native support for OGraf HTML graphics and native support for Lottie animations. That combination targets a common pain point in broadcast and social deliverables: motion packages that need to travel cleanly between teams and machines without turning into a pile of fragile renders. And since there is always one more Typo, you want it to work quickly.

We need to talk about OGraf

The OGraf Standard is a web based broadcast graphics specification from the European Broadcasting Union. It targets graphics like lower thirds and over the shoulder elements, and it aims to make them deliverable and renderable across diverse platforms instead of being trapped inside closed vendor systems. The idea is modular graphics workflows where components can be mixed and matched, so teams can create a graphic once and render it on traditional broadcast outputs, digital platforms, web streams, and even inside video editing tools.

At the spec level, OGraf defines what a compliant graphic looks like and how a renderer should interpret it, so a graphic can be created once and used in multiple compatible renderers. A graphic must include a JSON manifest ending in dot ograf dot json plus a JavaScript file that exports the graphic as a Web Component, along with any resources like images, videos, and fonts. The spec also describes a typical workflow split into editor, controller, server, and renderer, and it explicitly allows those parts to come from different vendors rather than a single all in one stack.

That is excellent news for Fusion Studio users because it adds native support for OGraf HTML graphics, which turns this from a broadcast only niche into something you can pull directly into comp land without reinventing the pipeline.

If your shop already gets OGraf packages from a broadcast graphics team, or you need to hand off the same graphic logic across multiple renderers, native OGraf support means fewer bespoke conversion steps and less glue code that breaks at the worst possible time. It also gives Fusion users a more standardized on ramp for HTML graphics workflows, which is the kind of boring interoperability that saves hours.

USD and the 3D side of comps

Fusion Studio 21 updates its USD stack with support for USD SDK 25.11, including the Hydra 2.0 API for the Storm renderer. USD support expands to 3D matte objects and textures, plus a USD Texture Projector and Catcher. The USD Loader also gains global in and out controls. On the compositing side of 3D, the 3D Renderer adds support for Cryptomatte. Fusion Studio 21 also adds native support for creating Relief Maps.

There are also workflow improvements that focus on day-to-day graph hygiene. Fusion Studio 21 lets you change common inspector properties for multi-tool selections, and it can change common inspector values across all selected multi-tool layers. That should reduce the classic Fsuion ritual of clicking twelve nodes to change the same one value.

Deep, stereo, vectors, metadata, and lens work

Fusion Studio 21 adds multilayer support for stereoscopic 3D clips and deep images. Deep images gain color correction. Vector channel support is added for multilayer workflows.

Metadata handling gets more flexible: user defined metadata variables can be used in paths, expressions and scripts. Lens Distort adds checkerboard calibration and GPU acceleration.

Fusion Studio 21 also allows keyframes and spline views to open as a floating window, which is a small quality-of-life feature that tends to matter a lot once you animate all day.

Installer scope and the extra apps

Fusion Studio 21’s installer puts the core application on your system and also adds utilities for setting up hardware control panels. It also installs Blackmagic RAW Player and Blackmagic Proxy Generator into the applications folder. On macOS, installation runs via the Fusion Studio Installer icon, and removal uses the Uninstall Resolve icon. On Windows, uninstall goes through Programs and Features, selecting Fusion Studio and running Uninstall. On Linux, uninstall comes from choosing the uninstall option after running the installer.

Minimum system requirements to actually run it

The macOS minimum requires macOS 15 Sequoia or later, an Apple Silicon based computer, and 16 GB of system memory or 32 GB for improved performance. For monitoring, it lists Desktop Video 12.9 or later.

The Windows minimum requires Windows 10 Creators Update, 16 GB of system memory or 32 GB for improved performance, and a GPU with at least 4 GB of VRAM. It lists a GPU that supports OpenCL 1.2 or CUDA 12.8, AMD and Intel official drivers from the GPU manufacturer, and an NVIDIA Studio Driver 570.65 or newer. For monitoring, it lists Desktop Video 12.9 or later.

For Windows on Arm, the minimum calls for Windows 11 for ARM on a Qualcomm Snapdragon X Elite series processor, with 16 GB of system memory or 32 GB for 4K.

On Linux, the minimum calls for Rocky Linux 8.6 and 32 GB of system memory, plus a discrete GPU with at least 4 GB of VRAM. It lists OpenCL 1.2 or CUDA 12.8 support, AMD official drivers from the GPU manufacturer, and an NVIDIA Studio driver 570.26 or newer. For monitoring, it lists Desktop Video 12.9 or later.

Pricing and licensing reality check

Fusion Studio is listed at $295. As always, new tools and innovations should be tested before use in production, preferably on a clone of the job, not the only copy of the job.

Link Citation Block

// Quoted info
https://www.blackmagicdesign.com/products/fusion
https://www.blackmagicdesign.com/products/fusion/compare
https://www.blackmagicdesign.com/support
https://www.komkomdoorn.com/krokodove/
https://ograf.ebu.io/
https://lottie.github.io/
https://openusd.org/
https://github.com/Psyop/Cryptomatte
https://www.blackmagicdesign.com/products/blackmagicraw
https://www.blackmagicdesign.com/products/blackmagicproxygenerator
https://www.apple.com/macos/
https://www.microsoft.com/windows
https://www.kernel.org/
https://www.khronos.org/opencl/
https://developer.nvidia.com/cuda-zone
https://www.nvidia.com/download/index.aspx
https://www.qualcomm.com/products/mobile/snapdragon/pcs-and-tablets/snapdragon-x-elite
https://rockylinux.org/
https://www.blackmagicdesign.com/products/davinciresolve

The post Fusion Studio 21 beta is here first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

A proper hardware device by Blackmagic Design (BM for short) and a calibrated screen has been the iron law for any professional user of DaVinci Resolve (DR for short). But for all those working under MacOS, this may have been valid for the longest time. We are looking at recent changes in DR for those without one. Spoiler: calibration still matters!

How to check

To see what’s going on when playing your movie on other devices and players you can compare your own footage, for sure. At least, if you were the colorist, you should know how it should look like. But if you are unsure (and our memory for colors can be tricked easily), there is the classic SMPTE chart in DR, which has the so-called PLUGE pulse (short for picture line-up generation equipment) in the lower right. In the wider black bar there are two narrow zones with a value just above black, the left one being the darker one (check your waveform).

If your blacks are not crushed by a false gamma interpretation, you should be able to see the right bar just faintly inside the black stripe. The middle one may only become visible if the shadows are lifted too much. Of course, it all depends on your screen too. If it’s not capable of showing black or at least near black, the rest of that whole area will not be pitch black, making it harder to judge the subtle differences. Actually, there is a third bar to the left of the two, but that is reaching down into the sub-black area and only visible if you have exported the file with “Retain sub-black and super-white data” activated. Normally it is just cut off.

Calibration options

DisplayCal is plugging into DR and sending its test patches through the grading software over any compatible I/O device to the screen you need to calibrate. The resulting LUT can be copied into DR and used as a monitoring LUT to correct deviations of the connected screen. This approach works absolutely correctly with the right settings in DisplayCal, being able to avoid any interference of the operating system, be it MacOS, Windows or Linux. Final precision is limited only by shortcomings of your monitor, like weak shadow areas, as visible below. BTW, those small spikes and minor shifts in the waveform are caused by compression in our recorder.

In our series of articles for those not able to spend a fortune on high-end solutions, we have shown how to get a proper LUT with the help of free software and second-hand hardware for Apple silicon. But now we have two solutions pretty much on par regarding calibration in the operating system by an ICC profile. So, we wanted to know if one can live without such an I/O device and that perfect calibration over the whole chain. Actually, BM has recently changed how preview windows and full screen display color and contrast. So, ICC profiles may not be insufficient any more for DR on a Mac with a screen adhering to standard!

Direct monitoring

BM has supported the use of Mac display profiles in DR’s viewers under MacOS for quite some time, even in 10-bit. But due to peculiarities carried over from older systems, they needed to use a non-standard version of Rec. 709, called 709-A. That was nothing but a crutch, and it was not only Apple’s fault that contrast and brightness were inconsistent between many players and other devices. If you are seriously bored, you can read this thread, with over 20 pages, the longest one ever in the DR user forum. You can follow some true experts and many wannabes there, discussing a ‘final’ solution. So, what’s our take on it?

The Never Ending Story: Are Apple XDR devices suitable for reference use in colour grading?

The main problem is lack of timely standardization when everything went from tubes to digital cameras and screens. The Rec. 709 standard for HDTV was defined based on analog technology, which behaved differently from modern cameras and screens. The newer addition to that standard is called BT. 1886, but it was only published by the ITU in 2011.

At that time there were already too many digital technologies in use, and most manufacturers didn’t really care much about adherence to a standard coming so late. BT.1886 defines a gamma (a contrast curve) of 2.4, which is fine for viewing TV in a rather dimly lit living room. Adjusting that curve is not really adhering to the standard, but on this model of a TV, for example, a value of +2 will get it to 2.2.

This slightly older Samsung TV, as a typical example, is offering modes like Movie, Natural, Standard, and Dynamic. Nothing says “Rec. 709” or “BT. 1886” right away, but „Natural“ is actually adhering to BT.1886, even fixed to it. „Standard“ is BT. 1886 too by default, but allows you to override that gamma in the expert settings – go figure. “Movie” is also adhering to BT.1886, but with a very warm tint – which again can be overridden, just like gamma. Recent ones have the “Filmmaker” setting, which is supposed not to change anything, and “Dynamic” is for bright rooms. Have fun with all the creative names and options of other manufacturers!

A lighter and less contrasty gamma of 2.2 might be better in a brighter environment. Mobile devices in particular are watched wherever you go. Even if some can reach very high brightness values these days, details in darker areas of the image can get lost if the content was graded as 2.4. Encoding clips for social media instead of movies for cinema buffs may profit from a gamma of 2.2, which is correctly flagged as 1-4-1 by DR. It even adheres to a standard, called BT.470 System M, as shown by MediaInfo (free). But this was a standard for analog television in some parts of the world only, and is now considered historical.

But do TVs and other devices really check such flags, which contain the information about encoding in your digital video files? They should tell the playback device which colour primaries, which colour matrix, and which gamma (called transfer characteristics here) were used. If you check with the info function for a video file on a Mac, the ones for Rec. 709 BT. 1886 are code points 1-1-1 or flags (I’ll use flag from here). They will be listed by cross-platform software such as MediaInfo as Rec. 709 for all three parameters.

In a perfect world, all playback devices and software players should respect such flags and show your video accordingly. Well, at least most of them assume your sources are 1-1-1, but often don’t care if it’s flagged as anything else, like 1-4-1 or 1-2-1. Some even force 1-1-1 on your clips, whatever they are. As we all know, YouTube is recompressing your sources, which is acceptable if the quality is good enough. But what’s absolutely unacceptable: whatever your original flagging was, YouTube will set it to 1-1-1 without even asking you! Just try to send one of your clips to YT and read it back. The free video patcher AMCDX by Alex Mogurenko will help you to correct wrong flags, but you need to remember the original encoding.

What to do?

In consequence, your results, which you encoded as gamma 2.2 for viewing in brighter environments, will actually be displayed darker and loose detail in the shadows. And if you encode from DR as Rec.709 gamma 2.4, which is offered as another option, it may too bright and lack contrast and saturation on players or a browser not respecting the flags. So, always encode as Rec. 709 (Scene) and hope for the best. It should look right on a TV with the correct settings. These can normally be found on most modern TVs or monitors if you dig deep enough into the menus, either as Rec. 709 or BT. 1886. Out of the box, many TVs are set to a very contrasty and saturated look, shouting out “Buy Me!” to the visitors of a mall for electronics.

The very popular VLC player is another example of ignoring flags, while we can recommend mpv player or its descendants for observance of flags. Of course, this says nothing yet about the quality of the screen attached to it. If that one is not calibrated, or at least set correctly in its menus, the image may still be far off. And then, there are all those image ‘enhancements’ imposed by digital TVs for viewing conditions, like bright environments or late hours. Or think of a projector meant to be visible in a not so dimly lit boardroom and optimized for (visual!) clarity of business charts.

Recommendations

Recent MacBooks and iPad Pro models have excellent blacks and offer reference modes for several standards, including HDTV (BT.709-BT. 1886). These are factory-calibrated and deactivate any image adjustments, assuming an environment properly lit for grading. Now, there is some sample variation and according to our own measurements, the nit value for white can be a tad low, like around 90 instead of 100 (some experts even suggest 120). Nevertheless, such screens come pretty close to a properly calibrated screen in the lower price range and offer much better blacks than conventional IPS panels.

If you are working for TV, we would still advise a professional, calibrated monitor via an I/O device. But, at least with the settings explained above, your viewers in DR will not look completely off when a client is looking over your shoulder. For all those working for social media, where your audience will have devices that you can’t control anyway, we suggest sticking to the only widespread norm: Rec. 709 with a gamma of 2.4. If you are concerned about visibility in bright environments, change the lighting in your room and check with an average smartphone, but avoid the setting for gamma 2.2 when rendering.

If you work for clients who want your results for social media, but are picky about how their movies look, you may need to supply them with an iPad Pro for presentations. Set it to a reference mode, block that, and try to explain to them why their average boardroom projector may look different. You may even want to take a photograph of TVs in an electronics market showing the same content next to each other.

Let’s do it on a Mac

So you’ve got a MacBook Pro (MBP for short) with Apple silicon and you’ve got a calibration probe, be it by Datacolor or Calibrite. But working just for the internet, you didn’t invest in an I/O device. We don’t care which generation of that laptop, as long as it has the nice XDR screen and reference modes. But who likes to work with DaVinci Resolve on such a small screen (even the menu bar is too short for all the little extras)? Let’s say you have a larger screen with decent color quality attached when you start grading at your home base. After all, not only Apple says that you should be grading to standards in a controlled environment – something hard to find in a hotel room or on the road. Now calibrate that external screen with your probe, and you’ll be generating just an ICC profile for the Mac in this case. More than one profile can be prepared for the correction of different monitors, which will be managed by the system.

Brightness according to BT. 1886 would be 100 nit, but 120 fits modern screens better. The steps needed for calibration are fully self-explanatory with the Spyder Pro software, and the result on a decent screen is very close to what we see on the MBP when set to reference mode. OK, DisplayCal may be a tad more precise. But it’s more complicated and taking many more measurements, resulting in excessively long lunch breaks.

You need to set the system preferences of DR to use the Mac profiles, as already shown above, and now you have to stick to Rec. 709 (Scene) on the Deliver page to get your output and its flags right. Do not use Rec. 709 Gamma 2.4, even if theoretically it should be the same!

Your timeline can be whatever you prefer: Rec. 709, ACES, or DaVinci Wide Gamut Intermediate (DWG). Of course, with manual settings your first node should get a CST (Color Space Transform) to adapt the incoming camera sources to DWG. Resolve’s automatic setting, called DaVinci YRGB Color Managed (aka RCM) set to SDR would also deliver the flags as 1-1-1, by the way. But you may need to check if the incoming footage’s color and gamma is identified correctly or needs to be set manually. That’s often the case if some difficult source has been transcoded into an intermediate codec, like ProRes, DNxHR, or Cineform.

Conclusion

In the end, you need to understand that rendering into a specific colour space and gamma is actually changing the visual content of your results. 
Tags are just metadata, which should trigger the right interpretation in players. That’s the point where chaos breaks loose, because manufacturers often don’t care for the tags and display your video based on assumptions. The only reliable approach is encoding to Rec. 709 with a gamma of 2.4 and having the tags set to 1-1-1, which is automatically done if you render into Rec.709 (scene).

The post LUTs, Tags, or ICC: Getting Colours Right in Resolve on a Mac first appeared on DIGITAL PRODUCTION and was written by Uli Plank.

Getting your bearings: Switching from Premiere Pro to DaVinci Resolve

Getting started in a new Software can be tough. I usually just want to get started with my edit without having to look for the right buttons to achieve what I have in mind. In the previous article, we looked at setting up your project, importing and organising media and generating proxies to get you ready for your first edit really fast. If you’re already set, the following will give you input on where you’ll find everything in Resolve to get your first cut done.

Get your Project settings right.

After you’ve imported and organised all your footage, you probably want to start editing right away. Still, there’s one more thing we need to do beforehand: set up the project’s framerate and resolution. Unlike Premiere Pro, DaVinci Resolve uses a single frame rate for the whole project. This will be the framerate all your Timelines will automatically be created with. When importing footage, this will be automatically played at the Timeline’s speed. If you, e.g., insert 50fps in a 25fps timeline, Resolve will drop frames to make it play in real-time. It’s important to know that after creating your first Timeline in a project, the current set project framerate will be locked. But don’t worry: although the project uses a single frame rate, it’s still possible to create timelines with different frame rates in that project. To set the project frames to the project settings, click the gearwheel icon in the bottom-right corner of the project, and the master settings will open.

A cool feature to mention is the ‘Use vertical resolution’ checkbox, which lets you switch to vertical resolution quickly without even thinking about the right numbers. This is also possible for a single Timeline instead of a project. If you tend to work with the settings a lot, click the three-dot menu in the top-left corner of projects to set your current settings as a default preset.

Now that you’ve set your project settings, you can create a Timeline by right-clicking in the media pool and selecting Create New Timeline, or pressing Ctrl / Cmd + n. If you want to have a different framerate or Resolution than what is set in the project settings before, untick the ” Use project settings checkbox to get into the small menu.

A small gearwheel icon in the Timeline’s thumbnail indicates it’s a custom timeline. It will automatically open and become visible through the playhead, turning red. If you’d like to give your Timelines different colours, you can do that by right-clicking them in the Media Pool and choosing clip colour.

Media Pool navigation on the Edit page

When working on a different page, your Media Pool is accessible via the Media Pool Panel, which you can activate in the top-left corner. It can be accessed on every page except the Deliver Page. Like in Premiere Pro, you have different view options. The three available are list, thumbnail, and metadata view. To switch between them, use the drop-down menu in the top bar.

List view gives you the most information about your clip. Using thumbnail view, it’s easy to identify the clip by a picture. A powerful feature in the thumbnail view is the live preview: when you hover over a thumbnail, you will see a preview of your clip in the source viewer. It can be deactivated in the three-dotted menu of the source viewer by deselecting live media preview.

To deactivate the sound when Live previewing, press Shift + s. If you want to adjust the thumbnail size, use the zoom function in the top bar. If you’d like a thumbnail as well as some metadata, the metadata view is for you.
When you’re looking for a particular clip, there’s a search bar in the top menu that allows you to find clips by any metadata available, including the one you set yourself when organising your clips. After you’ve found your clip, seeing the waveform can be quite helpful. By double-clicking, your clip will be loaded into the source viewer.

J, l, and K can be used like in Premiere Pro. By pressing the left or right arrow key, the clip will scrub single frames backwards or forwards.

Get through lots of footage. Fast.

By default, Resolves’ source viewer is set to Source Clip mode, in which it lets you preview and work with one clip at a time. I also like to work with Source Tape. This can be opened by clicking on the drop-down menu in the top left of the source viewer or pressing Shift + Q to switch between Source Clip and Tape.

The clips in the current bin are then available in the source viewer as if they were one clip. This makes it super-fast to go through a lot of footage and find the needed B-Roll, e.g., to add into a Source Timeline. Which leads me to one feature I find very useful: using a Timeline in the Source Viewer. If you’re the person who likes to preselect clips in a timeline, this is the tool for you! Simply drag and drop your preselection Timeline into your Source Viewer, or right-click on it in the Media Pool and select Open in Timeline with source viewer.

You can then use the Timeline like a clip and insert from it into your main edit without the need to switch between timelines all the time. Using a Timeline as Source Timeline will be indicated by the playhead turning blue.

Getting shots into the Timeline

To only insert the needed clip part into the Timeline, I set my in point with I and my out point with O. Alternatively, you can use the in and out mark buttons in the lower left corner of the source viewer. Accidentally set points and want to get rid of them again? Press alt / opt + I or O to delete the in or out point. For Resolve, it’s important to know that shortcuts do different things, depending on what is currently active. E.g., if you press X in the source viewer, it will delete both in and out points. If you press X while the Timeline is active, it’ll mark the clip at the playhead’s position.

A tip that helped me a lot: lots of buttons show a small overlay when you hover that gives you information about the functionality and shortcuts. There are seven insert options for adding footage to the Timeline.

Important to know: The behaviour when inserting a clip depends on the number of tracks and whether Auto Select is active. In addition to the most frequently used, the insert options are: fit to fill, place on top, append at end, and ripple overwrite. Their shortcuts are assigned to the F-buttons F9-F12 and Shift+F10-F12. They can also be found in the edit menu at the top of your screen. Beware Mac users: You might need to switch the fn keys from volume and brightness to the standard fn key on your Mac to use this.

You like to drag and drop? Check out the possibility to drag and drop from the source viewer into the Timeline Viewers Insert Option Menu. This will open when moving footage above the source viewer and gives you the option to drop onto an insert option.

Mismatched Resolution: Wait, is this already scaled?

When editing, handling different framerates and resolutions is an everyday task. Thankfully, when working with DaVinci Resolve, that’s no problem at all, since mixed frame rates are possible in a single Timeline.
When switching, I liked how Resolve sped up my workflow by handling scaling for mismatched resolutions. I think Premiere Pro handles this quite poorly, since I’ve always had to scale clips manually in the Timeline. Resolve offers four distinct options: Crop, Fill, Fit, and Stretch.

The option to scale the entire image to fit is the default setting and ensures the entire image is visible without blanking. When Crop is activated, Resolve will centre Crop without resizing. Larger clips will be cropped, smaller ones will have black borders. Using a full-frame scale with Crop will scale the clip to fill the frame, zooming in until the shortest dimension fits. The last option is to use a stretch frame on all corners. In this case, Resolve will distort the image to fit the frame.

By default, higher-resolution media will always be scaled down to the Timeline resolution. If you want to change that, go to Project Settings > Image Scaling > Input Scaling. If you want to change the scaling mode for individual clips, you can do so easily in the inspector’s retime and scaling window. Since Resolves Timeline resolution can always be changed, it’s good to know that correct scaling will be maintained. This gives you a lot of flexibility when working with different distribution aspect ratios.

Timeline navigation

When looking at the Timeline, Resolve should look familiar to you from Premiere Pro. The height of the audio and video Timeline can be adapted by clicking and dragging the Timeline divider. The height of the tracks can be adjusted by pressing Shift and scrolling, or by dragging the track divider to adjust only one track. To scroll through the Timeline, you can use strg / cmd + scrolling. Zooming in and out is possible with opt/alt + scrolling.

But there’s one advantage with zooming in Resolve: The Timeline toolbar offers three buttons for predefined zoom settings and one slider for individual adjustments. The left button will zoom to the full extent, the right to full detail zoom. The middle one will zoom to the current slider setting. You can therefore quickly jump to different settings without a lot of clicking or scrolling.

What I found quite annoying was the different navigation in the Timeline between Resolve and Premiere. When using Premiere, I liked to zoom around the mouse pointer. By default, resolve zooms around the playhead. If you don’t want that, simply change it in the menu view > zoom around mouse pointer. Honestly, when I finally realised I could change that, I had already gotten used to the Resolve default, and my Premiere way suddenly felt like chaos.

What still irritated me was only being able to see one open Timeline at a time. But this can be fixed by going into the Timeline View options. These open when you click the left icon on the Timeline toolbar and give you options to modify how your Timeline looks. The Display Stacked Timelines setting at the top lets you see all your open Timelines as tabs, like in Premiere Pro.

To open another Timeline, simply double-click on it in the Media Pool. Alternatively, you can open and switch between Timelines by using the drop-down menu at the top of the Timeline Viewer.

If you want to work from one Timeline into another, you can view multiple timelines simultaneously. To do so, click the small Symbol on the right, above the Timeline, while Display Stacked Timeline is activated. This will open a second Timeline Space below the first one. To open a Timeline in this space, double-click the wanted Timeline while the new space is selected. This is indicated by its Timeline Name being red.

Editing modes: Different workflows for different editors

As one major difference, editing tools in Resolve are consolidated into three editing modes: Selection Mode, Trim Edit Mode, and Blade Mode. The Key Advantage: Fewer tools mean fewer hotkeys to remember. Different editing operations are therefore intuitively performed by clicking on different parts of the clip. For example, if you’re in Trim Edit Mode, you can ripple by positioning the mouse pointer near an edit point, roll by positioning the mouse pointer over the edit point, slip with the mouse over the upper part of it, or slide by positioning the mouse on the lower part of the clip in the Timeline.

If you want to move a clip freely or delete something, Selection Mode is the one you want to go for, since this isn’t possible in any other Mode. You can still ripple and roll in Selection Mode, but Slip and Slide aren’t available. If you want to use the Blade, well, Blade Edit Mode would be the one. To switch between modes, you can either use the icons in the Timeline toolbar or their shortcuts. Like I said before, knowing which button does what and having a routine in that makes you fast, which is why the Edit Mode shortcuts irritated me the most when switching: instead of the shortcut v for Selection, it’s a, and instead of c it’s b for Blade.

It might take some time to get used to the new shortcuts, but all the functions you know from Premiere are there, too. E.g., cutting at the playhead can be done with Cmd/Ctrl+B. What I wish I had known earlier: alt/option + y lets you mark everything from the playhead forward, as you would in Premiere Pro. Playhead can be moved backwards with strg/cmd + y. If you want to turn snapping or linked Selection on or off, you can use the magnet and chain buttons in the Timeline toolbar. Alternatively, linked Selection can be temporarily disabled by pressing Alt, or by snapping with N while holding the mouse button. In addition, when dragging, holding Alt will copy the clip.

Need to fix something? Inspector.

With all shots in the Timeline, there might be a need for some refinement. This is what the inspector is for. It’s the place to optimise and adjust your clips and to work on effects you’ve added. To make adjustments in the inspector, check that the clip you want to work on is selected. This will be visible through a red outline.
What I really appreciate: Basic adjustments can be found here without having to add them from the effects panel.

First, there’s reframing. You can do this with the Transform tool in the inspector, which gives you easy access to zooming, position changing, rotation, and flipping. If the Studio version of Resolve is available to you, the AI Smart Reframe function helps you quickly reframe individual clips to other aspect ratios. For fast cropping, there’s a cropping function integrated directly into the inspector, too. Looking for a way to adjust across a defined range of clips? Adjustment clips can be added from the effects panel—these work just like in Premiere Pro.

If you need some speed adjustments, Speed Change will help you. With this, the Clips speed can be changed as a percentage or in fps. Important when switching from Premiere: By default, Resolve does not ripple the Timeline when adjusting a clip’s speed. This can be changed by checking the Ripple Timeline checkbox. Speed Change also gives you direction-change and freeze-frame options.

The stabilisation is one thing that really annoyed me when using Premiere Pro, since it was slow and didn’t work too well. Thinking about Resolves: it’s fast, accessible through the inspector, and yields a good outcome. You can choose between three modes: Perspective, Similarity, and Translation. When using Blackmagic Cameras, gyroscopic stabilisation is also available. Most of the time, the Perspective does the job. You can also adjust the cropping ratio, smoothness, and strength the way you like. Good to know: Unlike Premiere Pro, Resolve stabilisation can be applied to every clip, whether or not a speed change has been applied. Clips don’t need to be nested to apply stabilisation.

By now, you’ve got everything you need to edit the visual side of your video. For input on working with your audio and music, and on sharing and delivering your final clip, stay tuned.

The post Switching to Davinci Resolve: Your first cut first appeared on DIGITAL PRODUCTION and was written by Jana Johnston.

ONYX builds ONYX Ai Matte as a GPU-accelerated matte extraction tool for segmentation, tracking, and mask refinement inside OFX-compatible hosts. It targets hair and fur edge work and shots with more than one subject, and it frames the speed and quality claims as marketing claims. Under the hood, it uses Meta SAM3 and VitMatte models, packaged via ONNX in FP16 and accelerated with NVIDIA CUDA 12.6 and TensorRT 10.x.

Prompts, trimaps, and tracking

The UI exposes five pipeline modes: box or point prompts with auto track, box or point prompts with manual track, text prompts with auto track, mask prompts with auto track, and a trimap workflow using VitMatte with manual track. Point and box workflows let you set foreground and background points and a bounding box. The interface supports up to 32 points.

Text prompt mode detects objects that match your text. If it finds multiple matches, one foreground point picks the instance. Mask prompt mode takes a rough input mask and uses it as the prompt for a refined segmentation. The trimap path expects white foreground, black background, and a grey uncertainty band for edge refinement. Tracking integrates directly into the prompt workflows. In Nuke, the box center can be driven by expressions so a tracker can push it through the shot while size stays consistent. You still need to test any new tool before it goes into production, especially when the alhpa becomes the single point of failure.

Hosts and compatibility

The published host list includes DaVinci Resolve 18 and later, Fusion Studio 18 and later, and Nuke 13 and later. It also positions the plug-in as working in any OFX compatible app, like Autodesk Flame specifically.

System requirements and what is not supported

Minimum requirements list Windows 10 64 bit, an NVIDIA RTX GPU, 6GB of VRAM, 16GB of RAM, and 8GB free space. Windows 11 64 bit is also supported. Text prompts require 8GB of VRAM or more. The baseline GPU callout is an NVIDIA RTX 2060 or better with SM 7.0 or higher. Not supported: GTX 1000 series, AMD Radeon, and Intel Arc.

Trial, licensing, and pricing

A full featured 7-day trial is offered with no credit card required. Licenses are sold as lifetime, one time payments with no subscription, plus free minor updates. Pricing is published in euros as lifetime tiers on the official pricing page. Indie costs €80 for one machine node locked. Studio 3 costs €180 for three machines node locked. Studio 10 costs €450 for ten machines node locked. Studio 10 also includes priority support.

https://onyxofx.com/

The post ONYX Ai Matte for OFX hosts first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Even if you really want to, you have your workflow and rarely have the time to really get to know the new software. In the end, I was tired of getting slowed down by a constantly crashing software and not being able to render without artefacts. I thought the time spent on these issues with Premiere would have been better spent switching, especially since I was already colour grading in Davinci Resolve. To make the transition easier, here are some tips for switching from Premiere Pro to Davinci Resolve so you can get started as quickly and efficiently as possible:

Project Manager: Wait, where did I save my project?

One big difference between Davinci Resolve and Premiere Pro is how projects are managed. For this, the first thing you will see when opening the software is the Project Manager. This is the place to create and manage your projects. I’m honest: when switching, that was something that needed some time to adapt to, but it’s worth it.

While Premiere Pro projects are saved as files where you decide where, Davinci Resolve works with managed Libraries. These are structured containers that serve as a central repository for all project data. Libraries are managed via the Project Manager and can be hosted on your computer, on a networked server or in the Blackmagic Cloud. To switch between the three options, simply click on the one you choose in the top left corner of the Project Manager.

If you tend to make copies of your project on your computer to keep backups, this will change your workflow. But we’ll take a look at that later. For now, it’s important to know that projects saved in your active project library can easily be exported to your hard drive as a .drp file for a manual backup or transfer to another system. To export your project, right-click it and choose export.

Libraries come with some advantages. My favourite one: multiuser collaboration. I can’t describe how useful this is! Editors, colourists, VFX artists and sound engineers – everybody can work with the same project file on different workstations. Even at the same time, in the same timeline. Brilliant and timesaving.

Also speeding me up: powerbins. These are useful when working with media I use in multiple projects. They make media easily accessible across different projects, as long as it is in the same Project Library.  

Pages: Where do I start?

When switching from Premiere Pro, you’ll probably be used to using Dynamic Linking to get your edit into Audition, After Effects and Media Encoder to complete your postproduction process. In Resolve, this is what the Pages are for.

These follow the typical postproduction process from ingest to delivery, which provides a great advantage: you can have your whole postproduction in just one software. No exporting timelines for audio postproduction, visual effects or colour and no translation issues between software. There’s no need to manage multiple project files or export assets to get them from one project into another. Changes made in one page are instantly accessible in others, and you can quickly go back and forth as needed to change things.

I think to start, it’s important to say: Most things can be achieved in the Edit Page. Don’t get scared away by the masses of pages and functions! There are different ways to achieve your goal when editing, and you will get around very well, mostly by starting in Edit Page. Lots of functions from other pages are also available there. If you like, you can even turn off pages you don’t want to use in the preferences. To still give you a bit of orientation, here’s a quick overview of what the different pages are for:

The Media Page is for ingesting and organising. Right next to it we find the Cut page, which is an editing interface designed for speed. In the Edit Page, we have the traditional editing interface, which should be very familiar to you, coming from Premiere Pro. Quite different from After Effects is Fusion, the node-based workspace for compositing and VFX. The Colorpage – quite self-explanatory – is made for colour grading. Fairlight is the page where you can mix and master your audio after editing to then, finally, render your video out in the Deliver Page.

Interface basics: Where to find what you need

It will probably need some time for you to adapt to what’s different. One of the things that took me a while to get used to was the fixed panel places. While we’re used to being able to move everything around freely in Premiere Pro, Davinci Resolve allows only view windows to pop out and be moved freely throughout all pages. But once I adapted, it made total sense where everything is.

In the Edit Page, one big part of the window is the timeline in the lower part of the screen. Above that, we’ve got the source viewer and timeline viewer. Note: When your screen is too small or your screen resolution is too low, you might only see one viewer. Don’t worry, you can easily switch between those pressing Q.

In the Edit Page there are nine panels you can open and close by clicking their buttons located in the upper part of the screen. The ones on the upper left side will then open on the left and vice versa. The Media Pool on the upper left will give you fast access to your footage. It’s the same Media Pool as in the Media Page which we’ll look at later. The Effects panel, the index, and the mixer should be intuitive when switching from Premiere, though the feature I love most in the panels is the Inspector on the upper left side.

It could be compared to the effects controls in Premiere but has basic effects like crop already integrated, as well as more advanced effects like stabilisation, speed change, retime, and scaling.

Even though most panels are fixed, you can give yourself some more space by closing the panels you don’t need. Depending on whether you have opened multiple panels from both sides or not, they can be full-screen height or half-screen height. Accidentally messed up your UI? Don’t worry. You can quickly reset your UI layout in the menu Workspace > Reset UI Layout.

You’ll find dual-screen mode, full-screen Timeline, and, using Resolve Studio, permanent full-screen video out in the same menu.

Live Save and Project Backups

When working in Premiere Pro I often feared software crashes. I tried to save after every single thing I did because autosaving just didn’t cut it. Davinci Resolves Auto Save, which is called Live Save, is on a completely different level. I never fear that something is gone! I’ve got way fewer issues with the software crashing, but if it does, I know that what I did last will be there.

To restore the backups, right-click the project in the Project Manager. This won’t overwrite the current project version you’re working in. If you’re used to copying your Premiere Pro Sequence to revert to an earlier version of your edit, you may like to check out the Timeline backup function. It works just like Project Backups and can be activated and customised in the same spot. To restore a Timeline Backup, right-click on the timeline in either the media panel or Media Page. Just note: Timeline Backups will be stored locally, even when working on Network or Cloud Libraries, so they will only be accessible on the system where they were created.

Media Page: Import and Media Organisation

The one time I’d highly recommend switching pages is when importing media into your project. Even though it is possible to import media on all pages except Deliver, the Media Page offers many options for importing and managing your media.

The Media Page is split into Media Storage and Media Pool. The upper-left is Media Storage, which might be familiar to you if you used the Media Browser in Premiere Pro. It’s effectively a file browser for finding or exploring files on drives mounted on your computer. What I find very useful about this: you can quickly review or check footage in the viewer in the top-right corner of your screen, even without importing. A little extra: hovering over the footage lets you scrub through and preview without loading a clip into the viewer.

The lower part of the screen is your Media Pool – the project-specific repository for all the assets you’re importing or creating in Resolve, like footage, audio files, timelines, etc. On the left side, you’ll find the current projects bin list with the master bin. It’s the top level of your projects’ folder structure where all the other bins containing your project’s footage are listed. The right side shows the inside of the currently opened bin.

To get your footage into Resolve, simply drag and drop it from Media Storage, Finder, or Explorer into the Media Pool. If doing so on the Media Storage Bin list, the folder structure will be translated into the bin structure of your project. When adding to the right side, all the footage will be unpacked into the current bin

But there are other import options that let you stay in Resolve, leading to the same results: when you navigate to your folder in the Media Storage and right-click it, you’ll see the option to import your footage folder and all its subfolders into the current bin. This I find useful when working e.g., with Sony in camera folder structures, where you don’t want all the extra bins. Alternatively, you can choose “add folder and Sub folders into Media Pool (creating bins)” to get your complete folder structure as sub bins in the current bin. This is helpful if you already have your folders sorted out on your hard drive and want to copy the structure into Resolve.

Ways to create and work with proxies

Depending on the footage you’re working on, you might want to render some proxies. This is one particularly strong thing in Resolve and speeds me up quite a bit. You’ve got two options: if you’ve already set up your project and imported your footage, it’s super easy to create proxies by right-clicking on some highlighted footage and choosing proxie media > generate proxy media from the project settings.

In this case, it will automatically create proxies for the highlighted clips and save them in the location that is set in the project settings > master setting when scrolling down to working folders.

The Quality of the proxies can be defined in the same menu at optimised media and render cash. The proxy resolution is defined in relation to the original resolution. Possibilities are, for example: original, half of the original, a quarter of the original, etc. By default, it’s set to “choose automatically”, which will generate at the current set timeline resolution. When working with proxies, you can switch fast between disabling All proxies, preferring proxies and preferring camera originals, in the Timeline viewer.

You can also see whether proxies are attached by the white (for high-resolution) or purple (for proxies) icon on your clip, which will be visible in the thumbnail of your clip in the media pool.

If you really want to speed up your preparation process in advance, you should look into the Blackmagic Proxy Generator, an external tool which will automatically be installed with Davinci Resolve. It gives you the opportunity to render proxies in advance, without even having to get your project set up before. The proxies will then automatically be attached when importing the footage into a project.

This process will ensure you can go straight into editing when setting up your project. The strongest part of this tool is the watch folder function, which continues to scan your chosen folders for additional footage even after generating proxies. Very useful when you keep adding footage to folders you’re already working with.

Organising footage with scene metadata and smart bins

After you’ve added everything to your bins, it’s time to organise your footage. With Premiere Pro, I used to either restructure footage directly in bins, which made everything messy quite quickly, or sort my footage into sequences. In Resolve, I recommend using the scene metadata and smart bins. I know that Premiere Pro also lets you create smart bins using metadata, but it wasn’t intuitive enough for me to use back then. Resolve on the other side makes it super easy:

On the Media Page, click one clip or highlight multiple, then navigate to the top-right to close the audio panel. This will give your open Metadata panel more space. Choose “shot and scene” from the three-dotted menu. There, you’ve got lots of options to set metadata. One thing I like to use in this context is Clip colour, since it gives me an easy way to differentiate between different footage, for example, interviews with different people. Other than that, you can set metadata and let Davinci Resolve create smart bins based on it. For a start, I’d recommend you use Keywords. To do so, enter a Keyword you want to sort your footage by into the Keyword cell.

Then navigate to the bottom-left of your screen to find the Smart Bin List. By default, there should be a bin for Keywords. Davinci Resolve automatically generates one smart bin for every keyword you set before. By clicking on ‘Keywords’, a menu with all the smart bins will open.

Personally, I love this feature because it lets me keep my original folder structure while allowing me to sort my footage more intuitively. It also allows me to have the same clip in different bins, e.g., for location and person, which speeds up my process. With all this said, you should have everything you need to make your first steps in the software. Next up: how to get your Project Settings and Timeline right to start your first edit in Davini Resolve.

The post Getting your bearings: Switching from Premiere Pro to DaVinci Resolve first appeared on DIGITAL PRODUCTION and was written by Jana Johnston.