Is Resolve Studio V20 Stable or should I wait for V20.2

As the title says, is Resolve Studio V20 stable enough to use or am I better off waiting forV20.1 (or what ever) V20.0.1 was released 4 hours after I posted this,

I don't, so far, use Fusion much and the audio is 2-6 tracks mono and sometimes a stereo pair.

What is the verdict?
Any idea how soon V20.1 will be here?

It's a great question. I suppose with 20.0.1 just released, we'll need to wait for a bit to hear if there are any new issues. I suppose it will depend on your workflow and your hardware as to whether or not Resolve v20 is 'good enough' for production work.

Resolve 20.0.1 just came out today. It's stable.

Anyone here using Resolve v20 for production workflow in long-form content and/or documentaries and if so, what aspects of Resolve? Just grading / round-tripping to another NLE or the whole nine yards including final delivery?

XX.1 releases usually add multiple new features and associated sharp edges... I wouldn't wait for / jump in on a 'point one' release... XX.X.2 releases are usually the sweet spot for me (XX.1.2 if I'm honest), but that does mean I miss out on the new stuff for longer.

XX.1 releases usually add multiple new features and associated sharp edges... I wouldn't wait for / jump in on a 'point one' release... XX.X.2 releases are usually the sweet spot for me (XX.1.2 if I'm honest), but that does mean I miss out on the new stuff for longer.

That makes sense for me. Especially with V20 as most previous versions seem to have 6 beta's over 6 months. This one had 4 beta's over 4 months and added a lot of stuff.

So waiting for 20.0.2 in 4-6 weeks time would make some sense. (I am sure there wasn't a 20.0.1 when I originally posted earlier today, I think BMD did it on purpose to discredit my post ) This release should fix the major and easier fixes. Though, as others note, they often throw up new problems. Swings and roundabouts.

BTW Software of this type is impossible to test fully. So it is a matter of risk assessment on when to jump.

Resolve 20.0.1 just came out today. It's stable.

How do you know it is stable?

Resolve 20.0.1 just came out today. It's stable.

How do you know it is stable?

I used it?

Anyone here using Resolve v20 for production workflow in long-form content and/or documentaries and if so, what aspects of Resolve? Just grading / round-tripping to another NLE or the whole nine yards including final delivery?

5x longform features, including 2x feature doco in v20 so far, conform / online fixes / grade / master / festival DCP only - typicaly versioning and deliverables are done by delivery partner

no use of fusion or fairlight, minimal editing, only small tweaks to get past Qc

no major issues, a few minor with easy workarounds, a few have been sorted already with the .1 update

Thanks Dermot. Sounds like the bread and butter workflow we used back in the Avid days.

Resolve 20.0.1 just came out today. It's stable.

How do you know it is stable?

I used it?

So you have no idea if it is stable.

You posted a couple of hours after it was released. There is no way you can have tested the features I, or many people, use in the way we use d them. So you have no idea if this version is stable, only that it didn't crash inthe very short time you used a few of it's features.

As the title says, is Resolve Studio V20 stable enough to use or am I better off waiting forV20.1 (or what ever) V20.0.1 was released 4 hours after I posted this,

I don't, so far, use Fusion much and the audio is 2-6 tracks mono and sometimes a stereo pair.

What is the verdict?
Any idea how soon V20.1 will be here?

Do Yourself A Favour And Wait Until All Reported UI Bugs Get Fixed By BlackMagicDesign. For More Information, You Can Visit My Topic Regarding UI Bugs In Davinci Resolve Studio v20, From My Signature

Do Yourself A Favour And Wait Until All Reported UI Bugs Get Fixed By BlackMagicDesign. For More Information, You Can Visit My Topic Regarding UI Bugs In Davinci Resolve Studio v20, From My Signature

That is a lot of items not mentioned by many others in the forum. Though I note according to BMDs response your bug reports are "feature requests"

I’m using 20 from first beta, now 20.0.1.
With the exception of first beta where I had some crash, I just closed without problem three short of 15-19 minutes, and now I’m working on a 5 camera (8k and 6k, h265 and braw) for since 110 minutes of a theatre show without problem with editing, fusion for some quirk of scene, color and fair light.

Under Mac intel, sequoia.

I played a bit on M2Max with Sonoma, resolve was stable, fusion page sometimes stay to thought


Inviato dal mio iPhone utilizzando Tapatalk

Unless you need a feature in the new version, stay on 19.1.4 or 18.6.6.

Ultimately Black Magic is following the modern software developer mantra of prioritizing shiny new features over stability and performance. So if you find a version that is stable on your machine, stick with it as long as you can.

That is a lot of items not mentioned by many others in the forum. Though I note according to BMDs response your bug reports are "feature requests"

According To Wikipedia, A Software Bug Is A Design Defect In The Software Itself. Take Your Time To Read My Annotations On Posted Screen Shots In My Topic, Then You Can Decide If My Reported Bugs Can Be Considered As Design Defects Or As Feature Requests.

Unless you need a feature in the new version, stay on 19.1.4 or 18.6.6.

Ultimately Black Magic is following the modern software developer mantra of prioritizing shiny new features over stability and performance. So if you find a version that is stable on your machine, stick with it as long as you can.

Absolutely True

I think it's worth remembering that the reports of problems you see in the forum here come from maybe a dozen or two users who are motivated to report them, compared to a much, much larger base of users who are either not having problems or are having problems minor enough or easily enough worked around that they don't bother reporting them.

The prudent course of action, IMHO, is to monitor the forum for a month or two, noting if there are any reported problems which might affect you. If not, it's probably reasonably safe to upgrade. I'd advise keeping exported copies of your projects pre-upgrade as a safeguard so that you have the option of rolling back to a previous version of Resolve in the unlikely even that you run into serious issues.

If there were major issues with the new release, this forum would be filled with yelling unhappy customers. While there are certainly a few people who are adversely effected, it certainly doesn't seem to be a major theme.

I think it's worth remembering that the reports of problems you see in the forum here come from maybe a dozen or two users who are motivated to report them, compared to a much

Sometimes, You Have To Knock Multiple Doors Before Walking Away To Another Video Editing Solution.

I'd advise keeping exported copies of your projects pre-upgrade as a safeguard so that you have the option of rolling back to a previous version of Resolve in the unlikely even that you run into serious issues.

Unfortunately, You Don't Have The Ability To Install Two Versions of Davinci Resolve On The Same Machine (Like Premiere Pro), This is Very Understandable Because Of Packed Drivers (To Operate Resolve's Panels) Inside Davinci Resolve Installers.

It's not stable, I am uninstalling as of this writing and re-stalling V20. It gave me a strange rendering error on a .mov file that has been working fine for the last few weeks.

Once reverted, the render is fine again. Something is broken in this latest version.

[Peter Chamberlain]

It's not stable, I am uninstalling as of this writing and re-stalling V20. It gave me a strange rendering error on a .mov file that has been working fine for the last few weeks.

Once reverted, the render is fine again. Something is broken in this latest version.

It would be helpful if you could submit a Resolve generated diagnostic log so we have a chance to repo what you see.

According To Wikipedia, A Software Bug Is .....

Wikipedia is not a credible source for anything, much less software processes and definitions.

Much of the time Wikipedia is wrong. The problem is the many people who don't know better use Wikipedia as though it is reliable.

According To Wikipedia, A Software Bug Is .....

Wikipedia is not a credible source for anything, much less software processes and definitions.

Much of the time Wikipedia is wrong. The problem is the many people who don't know better use Wikipedia as though it is reliable.

Well Then, My Screenshots Were Provided From My Real Experiences (Not From Wikipedia). The Normal Person Doesn't Have To Visit Wikipedia To Identify How Buggy Software Looks Like !

I'd advise keeping exported copies of your projects pre-upgrade as a safeguard so that you have the option of rolling back to a previous version of Resolve in the unlikely even that you run into serious issues.

Unfortunately, You Don't Have The Ability To Install Two Versions of Davinci Resolve On The Same Machine (Like Premiere Pro), This is Very Understandable Because Of Packed Drivers (To Operate Resolve's Panels) Inside Davinci Resolve Installers.

I didn't mean to imply that I thought that was possible. My advice was to save the projects so that if you uninstall version 20 and reinstall a previous version you wouldn't get caught in the trap that the project wouldn't be usable by the previous version because it had been upgraded to something that was only compatible with V20.

The Normal Person Doesn't Have To Visit Wikipedia To Identify How Buggy Software Looks Like

To be fair, Ahmed, a normal Resolve user isn't trying to use the software on a setup with displays running at lower than effective 1680x1050 screen resolutions, which is (apparently) the minimum required for proper UI display.

The Normal Person Doesn't Have To Visit Wikipedia To Identify How Buggy Software Looks Like

To be fair, Ahmed, a normal Resolve user isn't trying to use the software on a setup with displays running at lower than effective 1680x1050 screen resolutions, which is (apparently) the minimum required for proper UI display.

I Have Two Monitors With 1920*1080, Still The Text Of Timelines Is Blurry @ UI Display Scale = Auto (Windows DPI = 125%), Besides The First Launch Wizard Of Divinci Resolve, Gives Me Two Green Check Marks (One On Monitor + One on Graphics Card). Yet, Davinci Resolve Looks Like *&^# (Bigger Panel.Sizes With Zero Ability To Resize Or Close) On My Dual Monitor Setup When UI Display Scale Gets Adjusted @Auto)

I think we already discussed this in your own thread, Ahmed, but I gather 1920x1080 at 125% gives Resolve an effective working resolution that's lower than 1680x1050 ... a problem likely further compounded for you by 125% not being a native scaling option in Resolve.

Perhaps that Resolve even allows itself to be run at less than minimal resolutions is itself a bug? I don't know. But more likely it's an intentional design decision to allow us to choose to use the software regardless, consequent issues notwithstanding.

I think we already discussed this in your own thread, Ahmed, but I gather 1920x1080 at 125% gives Resolve an effective working resolution that's lower than 1680x1050 ... a problem likely further compounded for you by 125% not being a native scaling option in Resolve.

Perhaps that Resolve even allows itself to be run at less than minimal resolutions is itself a bug? I don't know. But more likely it's an intentional design decision to allow us to choose to use the software regardless, consequent issues notwithstanding.

So You're Saying That Davinci Resolve Has No.DPI Awareness, Should I Create A New Topic For It ?

Many Modern Video Editing Solutions Have DPI Awareness Feature Which Adjusts The Font Size & Other Elements Of UI To Give You The Same Feeling Of Clear View & Sharpness As If Your DPI Were Adjusted To 100%.

I Can Solve The Blurry Text of 125% UI Display Scale, By Increasing Scale To 150%, But, I Don't Understand Why Users With Two Full HD Monitors (1920*1080 + 1920*1080 = 3840*1080) Can't Get All UI Elements Displayed Properly @ UI Display Scale = 150 % ?

Looks Like Some Fixations Must Be Made On Behalf Of BMD, Right ?

It's not stable, I am uninstalling as of this writing and re-stalling V20. It gave me a strange rendering error on a .mov file that has been working fine for the last few weeks.

Once reverted, the render is fine again. Something is broken in this latest version.

It would be helpful if you could submit a Resolve generated diagnostic log so we have a chance to repo what you see.

Hi Peter,

Sure, I'm happy to help. Can you show the steps on how to do that? Do I have to reinstall and go through all this again, or are there error files stored somewhere?

It's not stable, I am uninstalling as of this writing and re-stalling V20. It gave me a strange rendering error on a .mov file that has been working fine for the last few weeks.

Once reverted, the render is fine again. Something is broken in this latest version.

It would be helpful if you could submit a Resolve generated diagnostic log so we have a chance to repo what you see.

Hi Peter,

Sure, I'm happy to help. Can you show the steps on how to do that? Do I have to reinstall and go through all this again, or are there error files stored somewhere?

Looks Like Some Fixations Must Be Made On Behalf Of BMD, Right ?

Not entirely sure I understand what you mean here, but feature requests for native 125% scaling support and improved support for lower resolution monitors, spanned or otherwise, are 100% valid. Go for it. This isn't the right thread for doing that tho.

This isn't the right thread for doing that tho.

The OP Asking For Some Advice Before Upgrading To V20, And I Told Him About My Experinces Regarding V20.

No Off-Topic Intended, I Swear

I Have Two Monitors With 1920*1080

You will get the best experience from Resolve using displays with a minimum resolution of 1440 and Display Scaling of 100%

I Have Two Monitors With 1920*1080

You will get the best experience from Resolve using displays with a minimum resolution of 1440 and Display Scaling of 100%

The Problem Is Located inside Malfunctioned Display Scaling System Of Davinci Resolve (UI Display Scales), Not With My Monitors. I Can List More Than 10 Video Editing Solutions That Works Flawlessly With Windows DPI = 125%.

If Resolve Was Created To Use 100% Display Scale, Why BMD Offered The Following Options : (Auto - 150% - 200) Under User Settings ?

Why Automatic Display Scale (Of Davinci Resolve) Gives Blurry Timelines\Text if Windows DPI Was Configured @ 125%,
While 150% Or 200% Display Scales (Of Davinci Resolve) Provide The Best Clarity For Timelines\Text, If Windows DPI Was Configured @ 125% ?

By the way, There Are Many Users Asking For The Same Thing In This Topic :
https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=194385

I Have Two Monitors With 1920*1080

You will get the best experience from Resolve using displays with a minimum resolution of 1440 and Display Scaling of 100%

All three of mine are 1920 x 1080. Which seems fairly standard. Especially for those of us working in HD rather than 4K or up.

I have been using v20.0 since it came out of beta and completed two medium size projects including multicam clips, utilising fusion and fairlight including various vst plugins. I would have to say in my case, this is the smoothest upgrade since I started using DR in V16. It seems that unlike previous versions, v20 only updates individual projects that are opened, rather than the entire database, so there is a bit of a safety net there. That said, I have had zero issues so have had no need to roll back and test this theory:)

No showstoppers here. The trouble is, if someone happens to use some combination of features, hardware, plugins etc that are problematic for any number of reasons, it can seem like the entire update is buggy. For that reason you will see threads with titles like 'V20 completely unusable'. Even these declarations seem to be fewer with this update though.