Resolve has a serious issue. Numerous persistent bugs.

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 11:43 am

I switched almost exclusively to using Resolve as an NLE over a year ago, after years of using the product on and off. It's matured into a powerful full featured editing and grading suite. Since I received the full version for free with my black magic pocket camera I've had access to the even more powerful tools available in Studio. However... The more time I spend with Resolve, working on professional corporate projects, the more I find myself struggling to work around what seem to be long term intractable bugs with the software. Perhaps some of these are issues with my setup, but they're just the kind of intractable inconsistent bugs that no amount of updating drivers and reinstalling Resolve can fix. Judging by the numerous threads on Blackmagics forum they seem to affect numerous users, and I suspect many of them may be ongoing issues with the software. At this point enough have accumulated that they're having a strong negative effect on my productivity. Some are minor niggles, some are really serious issues, some can be worked around, some can't; but taken together they're making the experience of using Resolve stressful and not something I can easily recommend. I've compiled the issues I've continued to run into - across multiple computers and ongoing since at least Resolve 13, below. All these issues persist on the latest full Resolve release - 16.1.1.

1. Resolve always forgets which tracks you have muted when you move between sequences with stacked timelines.

2. When working with large projects - even on a system with 32gigs RAM, editing from NVME and using fast SSD caching, switching timelines can take up to 10 seconds. This can make copying footage back and forth between timelines an absolute chore. There doesn't seem to be any consistency to this - sometimes it's quick, sometimes its slow, in the same session working on the same project.

3. After shutting down Resolve (and also after a crash), Projects almost always remain active as hidden processes that have to be manually killed in process manager before resolve can be restarted.

4. Resolve has excellent GPU acceleration, but I have to disable GPU H265 and BRAW decoding or suffer frequent crashes (this is on an RTX 2060 with 6gb of RAM and yes, the latest Nvidia creative drivers). This is the official recommended action by Blackmagic support, even though it enormously slows down render times.

5. Often after a render (as in almost every time) subsequent renders will fail and resolve must be restarted to render anything.

6. When rendering to H264 on a video with alpha transparency resolve usually creates visual glitches, especially on white block colour backgrounds. This happens so often I have to always render to H265 - which cant be used for videos intended for social media platforms.

7. Resolve sometimes temporarily forgets clip colours which have been assigned when moving between timelines.

8. Editing videos with multiple audio channels, when skipping around a timeline while playing, resolve will often emit extremely loud high pitch pops and squeals. This can even happen just clicking on any part of the timeline and playing - and it makes using headphones while editing difficult. Sometimes resolve will also emit a constant high pitch noise when scrubbing clips at double speed.

9. When you drop a PNG onto the resolve timeline that's smaller than the resolution of the timeline, the parts that should be transparent are black - unless you apply even the smallest of crops on any side of the image - in which case they immediately become transparent.

10. Resolve's OFX Deflicker plugin is fantastically effective at removing flicker. However it's incredibly unstable. Scrubbing or playing back footage that has the plugin applied to a node will often lead to 'out of GPU' memory bugs, this can also happen just attempting to render. Once this bug is seen, resolve renders will always fail until the programme is restarted.

11. When a whole sequences is selected, often cuts / pastes etc will affect locked channels - even though they were locked prior to selection. This can lead easily to accidental deletion, particularly of audio.

12. Resolve frequently renders footage darker / more saturated than it appears in the preview window.

Update: The replies to this are reminiscent of posting to a Linux user forum in the early 2000s. A combination of a) I've never seen it so it must not be a real bug, b) yes there are lots of bugs, but real users ignore such things, c) it kind of works if you use this kludge, although that of course breaks something else, and d) read these five manuals, doubtless they contain a fix. None of these are conducive to fixing this commercial software that (I assume) most users replying are actively using in their day to day work. This stuff clearly is mission critical and it clear is affecting a lot of people, as evidenced by replies here and elsewhere. It's getting worse and it needs to be fixed for Resolve to be a serious useful tool. This isn't about supporting one brand over another - I use resolve fairly exclusively, I want it to work. I want it to be great. But right now, it needs serious work.
Last edited by Gdiddy on Fri Nov 22, 2019 1:37 pm, edited 5 times in total.
Offline

paul_WCP

  • Posts: 28
  • Joined: Mon Oct 15, 2018 10:37 pm
  • Real Name: Paul Lier

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 11:58 am

Image
Point 2 If you copy between timelines i recommend this little button.


I can confirm Point 3. which is annoying.

I very rarely experience Point 5.

Point 12: have you set data levels to full in deliver window? Also the renderer of your playback program might be the cause. I get different results with VLC than I get with MPC-HC.
Online

Michael_Andreas

  • Posts: 1268
  • Joined: Sat Jan 05, 2019 9:40 pm
  • Real Name: Michael Andreas

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 12:15 pm

With regard to your point 4, this thread has relevant advice: viewtopic.php?f=21&t=102152
_________________________________________________
DR Studio 16.1.1.005 - Win10 1909 Pro 64b - i7-6700K@4GHz - 32GB RAM
- RTX 2070 8GB, "Studio" driver 441.66 (12/10prior 431.86)
- OS,Library: 1TB SSD - Project/Cache: 1 TB SSD - TBD: 1TB M.2
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 12:18 pm

paul_WCP wrote:Image
Point 12: have you set data levels to full in deliver window? Also the renderer of your playback program might be the cause. I get different results with VLC than I get with MPC-HC.


Yes, data levels set to full - in project settings, on the individual files in the media pool, and at render time. I've read through quite literally every thread relating to this problem here and elsewhere.

Re: Stacked timelines - are you suggesting they work faster than tabbing between sequences? If so this seems like another workaround to a bug in the programme.

Also it runs into another issue with Resolve I didn't paste above. Which is the fact that it doesn't scale properly in high resolutions. If the interface is run native at 4K I find it unusably tiny, if scaled to 150%, options like stacked timelines eat up all screen real estate.
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 12:25 pm

Michael_Andreas wrote:With regard to your point 4, this thread has relevant advice: viewtopic.php?f=21&t=102152


Threads advice seems to be a) disable GPU acceleration, which I'm already doing and slows down workflow and rendering, and b) use old drivers, which is inadvisable for a host of reasons (especially if you use programmes other than resolve).

Point of my thread above is that accumulating a series of workarounds is problematic when there are this many bugs happening simultaneously. I can and do work around these issues, but they are so numerous it's becoming more burdensome than it's worth. And I love using Resolve. They need to be fixed.
Online

Michael_Andreas

  • Posts: 1268
  • Joined: Sat Jan 05, 2019 9:40 pm
  • Real Name: Michael Andreas

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 12:39 pm

The recommended driver was released in September and was the "studio" driver released at the time 16.1.1 was released. I realized that a slightly older driver could be a problem for other applications, but don't know of any other reason much less a host of them.

With respect to the BRAW issue, NVIDIA has this on the Open Issues list for the latest "studio" driver version.
_________________________________________________
DR Studio 16.1.1.005 - Win10 1909 Pro 64b - i7-6700K@4GHz - 32GB RAM
- RTX 2070 8GB, "Studio" driver 441.66 (12/10prior 431.86)
- OS,Library: 1TB SSD - Project/Cache: 1 TB SSD - TBD: 1TB M.2
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 12:56 pm

Michael_Andreas wrote:The recommended driver was released in September and was the "studio" driver released at the time 16.1.1 was released. I realized that a slightly older driver could be a problem for other applications, but don't know of any other reason much less a host of them.

With respect to the BRAW issue, NVIDIA has this on the Open Issues list for the latest "studio" driver version.


Not to get into a back and forth on this but a) obviously some of the issues above are not exclusively the fault of BM, e.g.: Nvidia related drivers. But that doesn't really matter from a user point of view. b) This issue is occurring on the current studio drivers, so clearly hasn't been fixed. c) Running a stack where you're using older drivers basically means that you can't solve any issue you encounter with another programme (as first resort of support is 'latest driver') - and can't insure that any new issue that arises with Resolve aren't a side effect of old driver, also can't keep parity between different computers which can create it's own issues.

There's kind of an apologia at work here. I (and I assume essentially all other Resolve users) am not particularly concerned with the why's of why issues arise - just their cost to productivity. This is real, and measurable and affecting my work daily. The extent of the list above really points towards a serious lack of testing in the current and recent versions of Resolve. Again, I don't work in QA, I don't know what stuff is happening in the resolve codebase with the integration of Fairlight and Fusion, adapting to Apples metal drivers etc. I shouldn't have to, I'm a shooter and editor. I just need it to work.
Online

Michael_Andreas

  • Posts: 1268
  • Joined: Sat Jan 05, 2019 9:40 pm
  • Real Name: Michael Andreas

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 1:12 pm

Setting the driver issue aside, I do agree with you about the general reliability. It appears from the user side that they are not doing enough regression testing, where "regression testing" is something you do to verify that all the wonderful new features you've added haven't broken existing features.

Regression testing with a program like DR is a huge challenge with the massive number of features it has plus the wide variability of hardware and software platforms it can run on. I wonder if they're doing any automated regression testing, which would be to run a standard set of footage through a standard set of timelines with a standard set of effects into all the codecs, then do an automated comparison of the newly rendered files with a set of standard files.
_________________________________________________
DR Studio 16.1.1.005 - Win10 1909 Pro 64b - i7-6700K@4GHz - 32GB RAM
- RTX 2070 8GB, "Studio" driver 441.66 (12/10prior 431.86)
- OS,Library: 1TB SSD - Project/Cache: 1 TB SSD - TBD: 1TB M.2
Offline

Soeren Mueller

  • Posts: 601
  • Joined: Tue Sep 04, 2012 2:21 pm
  • Location: Düsseldorf, Germany

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 2:17 pm

Completely agree with the original poster, experienced all of those issues within the last week!
I was so naive to try to do a project completely within Resolve and was on a tight deadline (1 week) ... what can I say, it was a nightmare. And yes, that is after I quickly downgraded my Nvidia drivers (project was shot on Pocket 6K)...
So back to my old trusty (and snappy) NLE and external compositing.

Oh and let me add one (imho big) point: keyframing.. both the keyframe window on the color page and even worse the keyframing (esp transform!) on the edit page. Sorry to say this but both are the worst keyframing/"animation" UI/UX I have ever suffered through. Please BM, please.. before you add anymore "intelligent" features (with questionable success) improve/fix the basics - don't become Adobe 2.0 - thanks!
Offline

Jim Simon

  • Posts: 4577
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 6:25 pm

3 and 9 are genuine bugs.

12 is correctable with a proper viewing environment.

"The only way to get a REC709 image on screen from Resolve that you can trust is to run SDI out of a BMD card (or BMD Thunderbolt box) to an accurately calibrated reference monitor.
Grading by viewing the image in the GUI just doesn't work." - Jaime LeJeune

https://www.blackmagicdesign.com/products/decklink


The rest I would attribute to system issues. I don't see any of them here.
Offline

RCModelReviews

  • Posts: 487
  • Joined: Wed Jun 06, 2018 1:39 am
  • Real Name: Bruce Simpson

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 6:42 pm

I use H265 for all my social-media renders. YouTube and Facebook both accept H265 uploads and the quality is perfectly fine. The added bonus of H265 is that the file-sizes are much smaller which makes for a faster upload.
Resolve 15 Studio, Fusion 9 Studio
CPU: i7 8700, OS: Windows 10 (1709) 32GB RAM, GPU: GTX1060/6
I'm refugee from Sony Vegas slicing video for my YouTube channels.
Offline

Mel Matsuoka

  • Posts: 330
  • Joined: Wed Aug 22, 2012 9:54 am
  • Location: Honolulu, HI

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 6:50 pm

Point 2 is one my my biggest issues with 16.1.1 (on macOS 10.13.6). When switching between timeline tabs on the Edit page, Resolve beachballs for up to 5 seconds before switching the tab. It also feels as if the delays get worse the longer the project is open. This morning, I opened a project in which this issue has been annoying me for the past few weeks, and when I opened a bunch of timelines, there was a delay in switching tabs, but not interminably so. But I can guarantee that the longer I work in this project today, that it will eventually take 5 seconds just to switch to even the most simplest timelines.
Resolve Studio 16.1.1.005 / Decklink 4K Extreme (11.4.1) / MacPro5,1 (macOS 10.13.6, 3.46 Ghz 12-core) / 96GB RAM / Boot: 500GB SSD / GUI: GTX 780 (6GB) / COMPUTE: GTX 1080ti SC (11GB), in Cyclone 2707 PCIe chassis / ATTO NT11 10Gb / SNS EVO NAS (10GbE)
Offline

Joshua Morin

  • Posts: 241
  • Joined: Fri Jan 19, 2018 1:39 pm

Re: Resolve has a serious issue. Numerous persistent bugs.

PostThu Nov 21, 2019 8:14 pm

Point 3 and 10 are happening to me as well.
Windows 10 Pro
Resolve 16.1.1 Studio
Intel(R) Core(TM) i7-8750 2.20GHz, 32.0 GB
NVIDIA GeForce GTX 1070M, 8Gb
Offline
User avatar

Marc Wielage

  • Posts: 6180
  • Joined: Fri Oct 18, 2013 2:46 am
  • Location: Hollywood, USA

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 1:43 am

Gdiddy wrote:10. Resolve's OFX Deflicker plugin is fantastically effective at removing flicker. However it's incredibly unstable. Scrubbing or playing back footage that has the plugin applied to a node will often lead to 'out of GPU' memory bugs, this can also happen just attempting to render. Once this bug is seen, resolve renders will always fail until the programme is restarted.

I haven't found that to be the case, and I use DeFlicker often. My suggestion is that you cache this (and any other GPU-intensive OFX plug-in) and be careful about where you place it in the node tree. If you make further adjustments after this node, it won't affect the DeFlicker or playback speed.

12. Resolve frequently renders footage darker / more saturated than it appears in the preview window.

Read these:

Grading for Mixed Delivery: Cinema, Home, and Every Screen in Between
https://blog.frame.io/2019/10/14/gradin ... -delivery/

and I think it covers the issues and the solutions very well. Understanding color management is also helpful:

Color Management for Video Editors
https://jonnyelwyn.co.uk/film-and-video ... o-editors/

I disregard the preview window because it's not calibrated or color managed.

On the other questions, note that Resolve 16.1 is recommended only for OSX 10.14.6. I'm not sure a 5,1 Mac Pro is going to be enough to handle current Resolve these days. We're using 64GB on a Trashcan and doing OK with timeline switches. The other stuff is harder for me to say, because we do only conform editing and not real editing per se. We don't have a problem with renders, but I generally only render to ProRes and then let the platform (YouTube / Vimeo / Frame.io) do the compression.
marc wielage, csi • VP/color & workflow • chroma | hollywood
Offline

Dermot Shane

  • Posts: 1965
  • Joined: Tue Nov 11, 2014 6:48 pm
  • Location: Vancouver, Canada

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 4:21 am

i don't edit in /Resolve so can only address 3,4,5, 10 & 12, the rest are editing centric

#3: yup, me too, no biggie once you figure it out

#4: if you want to get work done, use the drivers that work - as just about every one and their uncle has said

#5: i do mutiple renders of long timelines and never see this, check your system for weak links

#10: i use deflicker alot , never have an issue, never, dead reliable, but i have more GPU power to lean on

#12: judgeing anything by a viewport in the software is very far outside my comfort zone, enough so that i normaly leave the viewport turned off in the color page, but i have callibrated monitors to rely upon, and Resolve's color management is pretty much flawless
Offline
User avatar

Roen Davis

  • Posts: 441
  • Joined: Fri Aug 29, 2014 2:06 am
  • Location: Sydney, Australia

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 6:57 am

Nothing has been a show stopper for me.

Niggles - yes.

I have been squirting out all manner of weird resolutions and set up cascade renders so that the next render relies on the output of the last for 9 in a render queue, successfully.

I have some pet quibbles but overall I am very happy (DONT STOP WORKING ON MY QUIBBLES!) with what I can achieve.

10 seconds to switch timelines doesn't seem too onerous to me.

The persistent stub in processes (W10) seems quite dependent on how you quit/crash - given time it clears itself in most situations.

I have 1 RTX 2080 TI - 11GB. 8K is like swimming in honey but it gets there.

PNG really seems to challenge Resolve - if its just a still then I transcode it to something else in Photoshop, like TIFF.

My computer monitors are part of the menu/interface - any critical colour considerations should be done on a reliable external monitor.
to the deaf person the dancer appears mad
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 1:15 pm

Jim Simon wrote:3 and 9 are genuine bugs.

12 is correctable with a proper viewing environment.

"The only way to get a REC709 image on screen from Resolve that you can trust is to run SDI out of a BMD card (or BMD Thunderbolt box) to an accurately calibrated reference monitor.
Grading by viewing the image in the GUI just doesn't work." - Jaime LeJeune

https://www.blackmagicdesign.com/products/decklink


The rest I would attribute to system issues. I don't see any of them here.


Yeah - this isn't the case of any other NLE - and it isn't even the case consistently with Resolve. It's inconsistent across installs, which means it's a bug. Calibrating correctly without a reference monitor is impossible. Not calibrating correctly between preview and render ON THE SAME MACHINE is a huge bug. Just to emphasize, this doesn't happen on any other NLE I've ever used. What you see in the viewer is always what you get in the render, assuming you're using same screen to view.
Last edited by Gdiddy on Fri Nov 22, 2019 1:49 pm, edited 1 time in total.
Offline

Gdiddy

  • Posts: 12
  • Joined: Sat Jul 28, 2018 5:35 pm
  • Real Name: Gareth Stack

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 1:18 pm

Roen Davis wrote:Nothing has been a show stopper for me.

Niggles - yes.

I have been squirting out all manner of weird resolutions and set up cascade renders so that the next render relies on the output of the last for 9 in a render queue, successfully.

I have some pet quibbles but overall I am very happy (DONT STOP WORKING ON MY QUIBBLES!) with what I can achieve.

10 seconds to switch timelines doesn't seem too onerous to me.

The persistent stub in processes (W10) seems quite dependent on how you quit/crash - given time it clears itself in most situations.

I have 1 RTX 2080 TI - 11GB. 8K is like swimming in honey but it gets there.

PNG really seems to challenge Resolve - if its just a still then I transcode it to something else in Photoshop, like TIFF.

My computer monitors are part of the menu/interface - any critical colour considerations should be done on a reliable external monitor.


Taken singly, some of these are quibbles, some are more serious. Taken together they make for an unstable working environment. 10 seconds to switch timelines is ludicrous, it's literally instant in all three other major NLEs.
Offline

Marc Salvatore

  • Posts: 103
  • Joined: Tue Oct 31, 2017 5:21 pm

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 5:28 pm

I've had issues with the switching timeline delay. Not ten seconds but enough to make it feel like a crawl...
Offline

Mel Matsuoka

  • Posts: 330
  • Joined: Wed Aug 22, 2012 9:54 am
  • Location: Honolulu, HI

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 6:54 pm

Roen Davis wrote:10 seconds to switch timelines doesn't seem too onerous to me.


You must have either have a lot of spare time, more patience than 99% of the rest of humanity, or clients who don't give you hard deadlines.

10 seconds (or even 5 seconds) to switch between timelines is absolutely unacceptable behavior in a modern, "professional" editing application.
Resolve Studio 16.1.1.005 / Decklink 4K Extreme (11.4.1) / MacPro5,1 (macOS 10.13.6, 3.46 Ghz 12-core) / 96GB RAM / Boot: 500GB SSD / GUI: GTX 780 (6GB) / COMPUTE: GTX 1080ti SC (11GB), in Cyclone 2707 PCIe chassis / ATTO NT11 10Gb / SNS EVO NAS (10GbE)
Offline

Soeren Mueller

  • Posts: 601
  • Joined: Tue Sep 04, 2012 2:21 pm
  • Location: Düsseldorf, Germany

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 7:49 pm

Yeah like you or somebody said.. the different perspective on this ("it's ok/just niggles" vs "aaaaaarghhh") seems to be mainly between people that either only or mainly grade or users like us that try to make use of all the advertised features (editing/compositing/audio). The latter (currently) gives a much different user experience. If I can I try to only use it for grading/tracking rough masks etc. for now... definitely NOT using a bunch of external mattes/PNG and OFX (which seems to be rat poison for Resolve)

As a former software dev myself the scary thing about the multisecond timeline switch delay on a current speedy workstation is not so much the delay itself but what it is saying about whats probably going on "under the hood".. and that's pretty scary to be honest.
Also a process left "dangling" after exiting the app usually points to a lot of bigger under-the-hood bugs or design problems.. just my 2 cents.. maybe slow down the aquisitions and new modules for a while and focus on this?
Offline

John Paines

  • Posts: 3065
  • Joined: Tue Jul 28, 2015 4:04 pm

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 7:56 pm

I don't like the delay either, but consider: when you switch tabs in Premiere or FCPX, you're not switching/reconstructing the timeline on 4 other panels, each of which represents a full-blown application, complete with a new and potentially huge data set.
Offline

Mel Matsuoka

  • Posts: 330
  • Joined: Wed Aug 22, 2012 9:54 am
  • Location: Honolulu, HI

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 8:00 pm

Soeren Mueller wrote:Yeah like you or somebody said.. the different perspective on this ("it's ok/just niggles" vs "aaaaaarghhh") seems to be mainly between people that either only or mainly grade or users like us that try to make use of all the advertised features (editing/compositing/audio). The latter (currently) gives a much different user experience. If I can I try to only use it for grading/tracking rough masks etc. for now... definitely NOT using a bunch of external mattes/PNG and OFX (which seems to be rat poison for Resolve)


Thank you for stating this perspective. I've been using Resolve since the first cross-platform version was released (v7) on the Mac back in 2010. But I;ve been using it exclusively for it's original intended purpose, that of color-grading.

It has only been in the last 4 weeks, when I finally jumped in the deep end, trying to use Resolve as a dedicated NLE, that I've uncovered a TON of these "niggles" and productivity-killing bugs that have certainly been there for a long time, but I've never experienced as a colorist. I've noticed the sluggish timeline switching thing for a few years now, but it hasnt been a workflow issue since I only needed to do it for infrequent organizational purposes when color-grading a project. But now that I'm using it as an actual NLE, the delay in switching tabs is a major problem, and I simply cannot recommend that the other editors in my facility spend time learning to switch from Premiere to Resolve, if such a basic and fundamental aspect of NLE user-experience is so infuriatingly slow.
Resolve Studio 16.1.1.005 / Decklink 4K Extreme (11.4.1) / MacPro5,1 (macOS 10.13.6, 3.46 Ghz 12-core) / 96GB RAM / Boot: 500GB SSD / GUI: GTX 780 (6GB) / COMPUTE: GTX 1080ti SC (11GB), in Cyclone 2707 PCIe chassis / ATTO NT11 10Gb / SNS EVO NAS (10GbE)
Offline

Mel Matsuoka

  • Posts: 330
  • Joined: Wed Aug 22, 2012 9:54 am
  • Location: Honolulu, HI

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 8:13 pm

John Paines wrote:I don't like the delay either, but consider: when you switch tabs in Premiere or FCPX, you're not switching/reconstructing the timeline on 4 other panels, each of which represents a full-blown application, complete with a new and potentially huge data set.


You're probably right. But that doesn't/shouldn't excuse the behavior.

Marco Arment--developer of the popular Overcast podcast app for iOS--mentioned once that as a developer, bugs and issues in his app are often caused by unforeseen bugs in Apple's APIs, but to his customers, the API bugs reflect as bugs that he created. He semi-famously said that such bugs are "not my fault...but they are my problem". To the end user, it doesn't matter why an issue exists. The fact is that it exists, and needs to be addressed, particularly if it's causing an advertised feature of the application to not behave with the minimum acceptable level of performance that one would reasonably expect.

While I love the promise of Resolve as an integrated NLE/VFX/Audio/Color app, this is precisely what skeptics like myself feared of back when people were asking for Resolve to become a full fledged finishing app like Smoke. Building an integrated suite of tools is very difficult, and BMD is kicking all sorts of ass with Resolve, all things considered. But excusing away basic issues like this is misguided, in my opinion.
Resolve Studio 16.1.1.005 / Decklink 4K Extreme (11.4.1) / MacPro5,1 (macOS 10.13.6, 3.46 Ghz 12-core) / 96GB RAM / Boot: 500GB SSD / GUI: GTX 780 (6GB) / COMPUTE: GTX 1080ti SC (11GB), in Cyclone 2707 PCIe chassis / ATTO NT11 10Gb / SNS EVO NAS (10GbE)
Offline

Tom Early

  • Posts: 1254
  • Joined: Wed Jul 17, 2013 11:01 am

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 9:18 pm

Gdiddy wrote:2. When working with large projects - even on a system with 32gigs RAM, editing from NVME and using fast SSD caching


How large are you timelines? What resolution/codecs are involved? I'd submit logs to BMD when this happens if I were you.

Gdiddy wrote:12. Resolve frequently renders footage darker / more saturated than it appears in the preview window.


There are a few threads recently about this. It's not a bug, just a very poorly documented feature. Baselight will export movies the same way btw, and there's a video from Filmlight explaining the feature in detail (which BMD needs to do), it's just that its viewer is much better at matching that output, and also it gives an easy way to disable the feature on export, which you can only do in Resolve if you set up your entire project a certain way.
MBP2016, MacOS 10.14.6, 2.9 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3,
Radeon Pro 460 4096 MB, Resolve Studio 16.1.1.005
Offline
User avatar

Roen Davis

  • Posts: 441
  • Joined: Fri Aug 29, 2014 2:06 am
  • Location: Sydney, Australia

Re: Resolve has a serious issue. Numerous persistent bugs.

PostFri Nov 22, 2019 11:32 pm

Gdiddy wrote:
Jim Simon wrote:3 and 9 are genuine bugs.

12 is correctable with a proper viewing environment.

"The only way to get a REC709 image on screen from Resolve that you can trust is to run SDI out of a BMD card (or BMD Thunderbolt box) to an accurately calibrated reference monitor.
Grading by viewing the image in the GUI just doesn't work." - Jaime LeJeune

https://www.blackmagicdesign.com/products/decklink


The rest I would attribute to system issues. I don't see any of them here.


Yeah - this isn't the case of any other NLE - and it isn't even the case consistently with Resolve. It's inconsistent across installs, which means it's a bug. Calibrating correctly without a reference monitor is impossible. Not calibrating correctly between preview and render ON THE SAME MACHINE is a huge bug. Just to emphasize, this doesn't happen on any other NLE I've ever used. What you see in the viewer is always what you get in the render, assuming you're using same screen to view.

External monitoring with a panel calibrated with appropriate equipment is the only reliable way to have confidence in what you are doing. This is not peculiar to BMD, it is a basic necessity for a professional working environment. I do not use the GUI to make colour or brightness judgements.
to the deaf person the dancer appears mad
Offline

totalvamp

  • Posts: 8
  • Joined: Tue Jun 04, 2019 5:30 pm
  • Real Name: Michael de Wal

Re: Resolve has a serious issue. Numerous persistent bugs.

PostSat Dec 14, 2019 8:36 am

Using Deflicker instantly freezes Resolve for me.

Running W10

Ryzen Threadripper 2990WX
2x 1080ti
128GB RAM
Offline
User avatar

Marc Wielage

  • Posts: 6180
  • Joined: Fri Oct 18, 2013 2:46 am
  • Location: Hollywood, USA

Re: Resolve has a serious issue. Numerous persistent bugs.

PostSat Dec 14, 2019 8:47 am

totalvamp wrote:Using Deflicker instantly freezes Resolve for me.

I have not had this happen on 16.1.1 with DeFlicker on a Trashcan Mac, but I have noticed that it takes quite a bit longer to cache DeFlicker nodes than it used to. However, I've noticed that the results are better now, particularly in situations that would be trying for the older 15.3 DeFlicker.

I did have one crash when engaging DeFlicker, but only one for sure in the last 2 weeks. I've gotten into the habit of saving prior to kicking in a mode like DeFlicker, and maybe once out of 200-300 times, it's crashed or hesitated with a spinning beach ball.
marc wielage, csi • VP/color & workflow • chroma | hollywood
Offline
User avatar

deBabba

  • Posts: 42
  • Joined: Sun Apr 21, 2019 3:32 pm
  • Location: Germany
  • Real Name: Andi Wilker

Re: Resolve has a serious issue. Numerous persistent bugs.

PostSat Dec 14, 2019 9:47 am

Soeren Mueller wrote:Completely agree with the original poster, experienced all of those issues within the last week!
....

Oh and let me add one (imho big) point: keyframing.. both the keyframe window on the color page and even worse the keyframing (esp transform!) on the edit page. Sorry to say this but both are the worst keyframing/"animation" UI/UX I have ever suffered through. Please BM, please.. before you add anymore "intelligent" features (with questionable success) improve/fix the basics - don't become Adobe 2.0 - thanks!

I would totally subscribe these statements Soeren :!: :!:
- I7-7700K@4,7GHz, 32GB@3600MHz, Intel HD630 + Geforce RTX2070 8GB, 960Evo 1TB(M.2)
- Sony RX100M4, RX10M3, Phantom 4pro (UHDp60)
- Win 10 Pro latest patch
- Resolve 16.1b03 (Studio)
cheers, Andi
Offline
User avatar

deBabba

  • Posts: 42
  • Joined: Sun Apr 21, 2019 3:32 pm
  • Location: Germany
  • Real Name: Andi Wilker

Re: Resolve has a serious issue. Numerous persistent bugs.

PostSat Dec 14, 2019 10:18 am

Soeren Mueller wrote:...
As a former software dev myself the scary thing about the multisecond timeline switch delay on a current speedy workstation is not so much the delay itself but what it is saying about whats probably going on "under the hood".. and that's pretty scary to be honest.
Also a process left "dangling" after exiting the app usually points to a lot of bigger under-the-hood bugs or design problems.. just my 2 cents.. maybe slow down the aquisitions and new modules for a while and focus on this?

Agreed, I think fusion integration e.g. is far away from beeing stable and the same is valid concerning handling of h.264 and h.265 footage. Memory management especially on GPU side is also a point to be focussed on.

I know similar issues from about 3 decades of software engineering at all levels
- I7-7700K@4,7GHz, 32GB@3600MHz, Intel HD630 + Geforce RTX2070 8GB, 960Evo 1TB(M.2)
- Sony RX100M4, RX10M3, Phantom 4pro (UHDp60)
- Win 10 Pro latest patch
- Resolve 16.1b03 (Studio)
cheers, Andi

Return to DaVinci Resolve

Who is online

Users browsing this forum: Majestic-12 [Bot] and 47 guests