DaVinci 19.1

I just upgraded to 19.1. I am running a Late 2013 12 Core 64gigs of rams a 2tb hd. When I open up 19.1 and I go to the text and I start browsing around the different text to use it just crashes on me.. Can't upload a video I did, 2mb upload only. Mp4 and .mov wont work so I can't post

This would be Resolve 19.0.1

Please include information such as Resolve build (including free vs Studio), operating system, and computer spec in your signature as this assists troubleshooting.

If the host crashes please include a link to diagnostic logs. Instructions to generate logs are provided in the FAQ at the top of the forum: viewtopic.php?f=21&t=90190#16

Hi, I have updated to 19.1 and can't open my projects. It freezes at 100% and be there forever. I am using a studio version on my MacBook Air 2020 8GB RAM - 256GB - Mac OS Ventura 13.7.1. After downgrade to 19.0.3 everything goes back to normal.

Here are my log files, as requested:
https://drive.google.com/drive/folders/ ... drive_link

Thanks!

Hello
Since installing 19.1, as soon as I press 'play' the program closes immediately !

I finally upgraded to 19.1. This was on my 2017 iMac Pro Intel with 64Gb of RAM and Vega 56 8gb gpu internally and a BMD external Vega 56 8gb gpu, which has been running flawlessly with MacOS Sonoma and Resolve Studio 18.6.6.

Right after backup and upgrading, I am encountering several issues:

1. Existing projects are running slower with playback.

2. While playing back the videos in timeline, there is a consistent flickers of random white patches over the image.

3. When I shutdown DVR, the application wouldn’t terminate. I have to force quit it and when asked to send the report, I answered yes.

4. My BMD Micro Panel (older edition) controls does not react to movements of the trackball, which I noticed the most.

None of the above issues were exhibited in 18.6.6.

Unless there are suggestions to fixes, I only have this week to take care of it otherwise I need to revert back to 18.6.6.


I have my project’s backup so I am not too concerned about restoring the projects. I’m more concerned about the registration of the license since if I delete 19.1, I am not sure if I will lose it and will have trouble registering back my 18.6.6.

I am getting crashes when in the edit page. Just trying to scrub crashes it instantly every time.
I tried the install a few times with no luck.
I uninstalled 19.1 and went back to 19.0.3 build 5 and Resolve studio works fine now on Winsows 10.

My mini panel and speed editor have not been affected by the install/uninstall and are working fine as far as I can tell so far.

This is outrageous. I don’t want to be a beta tester every time an update rolls out, and I actually waited until 19.1, keeping in mind the 19.0 and its subversions will be buggy.

[Shrinivas Ramani]

Hi all

Thanks for the reports. It would really be helpful if you can add some info:

• system details - hardware, OS version, drivers, Resolve free/studio and peripherals.
- Refer to the FAQs to see what helps and how to capture this information.
- If you're upgrading from 18.x and have an Nvidia graphics card, please note that there is a change to the minimum CUDA support that needs a driver update. Please review minimum requirements, download the latest Studio drivers and select Custom Installation > Clean Install.

• URL for diagnostic logs - Dwaine has these excellent specific instruction posts to
- capture and post logs and system info for Windows
- capture and post logs and spx for macOS

• Content - If your issue is project-specific or media-specific, please consider including a copy fo the media or the project export (DRP file) in the URL above.

You can edit your current response to include this info. If you prefer to respond in a new post in the thread, please consider including a short description of your issue in the response.

Regards
Shrinivas

This is outrageous. I don’t want to be a beta tester every time an update rolls out, and I actually waited until 19.1, keeping in mind the 19.0 and its subversions will be buggy.

From 40 years of experience I learned one rule with computer systems and software: it will be either outdated or buggy. Or even both.
Use an operating system that has been final for at least half a year and DR 18.6.6 and it will be reasonably stable. The same will be the case after a few more months with 19.

No company can test their software on all possible configurations of PC hardware and software users may have out there. The possible configurations are probably outnumbering the stars in our home galaxy. So, we are all beta testers, and it definitely helps to document bugs in a way that helps developers to identify the problem. Live with it or use a mechanical editing table, like a Moviola or a Steenbeck

Things are a bit better on the Mac side. Not because Apple is perfect, but you get the OS and the hardware from the same source. If you don't install anything but the MacOS and DR on it, it'll be reasonably stable. But as soon as you add any third-party plug-ins, or additional audio hard- and software, they are just the same. This doesn't mean that Apple and/or BM are not occasionally screwing up, like with some Sony clips recently. Oh, wait, there's a third party involved: the camera manufacturer.

Finally, I'd suggest to use a 'sandbox' system if anybody is using FCP-X too and wants to update. Unfortunately, Version 11 is forcing us into Sequoia, and there I'm still hesitant…

Hi all

Thanks for the reports. It would really be helpful if you can add some info:

• system details - hardware, OS version, drivers, Resolve free/studio and peripherals.
- Refer to the FAQs to see what helps and how to capture this information.
- If you're upgrading from 18.x and have an Nvidia graphics card, please note that there is a change to the minimum CUDA support that needs a driver update. Please review minimum requirements, download the latest Studio drivers and select Custom Installation > Clean Install.

• URL for diagnostic logs - Dwaine has these excellent specific instruction posts to
- capture and post logs and system info for Windows
- capture and post logs and spx for macOS

• Content - If your issue is project-specific or media-specific, please consider including a copy fo the media or the project export (DRP file) in the URL above.

You can edit your current response to include this info. If you prefer to respond in a new post in the thread, please consider including a short description of your issue in the response.

Regards
Shrinivas

Hi Shrinivas. Thank you for your response. I will prepare all the requested information above and package it that you can download. Hopefully it will help BM to identify and fix the problem.

From 40 years of experience I learned one rule with computer systems and software: it will be either outdated or buggy. Or even both.
Use an operating system that has been final for at least half a year and DR 18.6.6 and it will be reasonably stable. The same will be the case after a few more months with 19.

No company can test their software on all possible configurations of PC hardware and software users may have out there. The possible configurations are probably outnumbering the stars in our home galaxy. So, we are all beta testers, and it definitely helps to document bugs in a way that helps developers to identify the problem. Live with it or use a mechanical editing table, like a Moviola or a Steenbeck

Yes, I know and understand. Just my frustrations on dealing with issues that takes me out of being able to do my work. So, excuse my venting. I want to be helpful so that BM can fix this.

Things are a bit better on the Mac side. Not because Apple is perfect, but you get the OS and the hardware from the same source. If you don't install anything but the MacOS and DR on it, it'll be reasonably stable. But as soon as you add any third-party plug-ins, or additional audio hard- and software, they are just the same. This doesn't mean that Apple and/or BM are not occasionally screwing up, like with some Sony clips recently. Oh, wait, there's a third party involved: the camera manufacturer.

It happened on the Mac and it’s been stable all the way up to DR Studio 18.6.6 on MacOS Sonoma. The computer has on DVR Studio on it and no plugins. So I can attest that it was a pretty stable system.

Finally, I'd suggest to use a 'sandbox' system if anybody is using FCP-X too and wants to update. Unfortunately, Version 11 is forcing us into Sequoia, and there I'm still hesitant…

None of this for me.

So how best to go back to 18.6.6?

Hi all

Thanks for the reports. It would really be helpful if you can add some info:

• system details - hardware, OS version, drivers, Resolve free/studio and peripherals.
- Refer to the FAQs to see what helps and how to capture this information.
- If you're upgrading from 18.x and have an Nvidia graphics card, please note that there is a change to the minimum CUDA support that needs a driver update. Please review minimum requirements, download the latest Studio drivers and select Custom Installation > Clean Install.

• URL for diagnostic logs - Dwaine has these excellent specific instruction posts to
- capture and post logs and system info for Windows
- capture and post logs and spx for macOS

• Content - If your issue is project-specific or media-specific, please consider including a copy fo the media or the project export (DRP file) in the URL above.

You can edit your current response to include this info. If you prefer to respond in a new post in the thread, please consider including a short description of your issue in the response.

Regards
Shrinivas

Hi Shrinivas. Here is the link to a zip file containing all the files with the information you requested. I included a couple of capture logs too, one from before and another just now when DVR Studio 19.1 hang again when I tried to exit the app.

https://drive.google.com/file/d/1riolGv ... share_link

The main issue is that when exiting DaVinci Resolve Studio 19.1, DVRS hangs and there is no way to exit the application without doing a Force Quit on macOS Sonoma. There are times that even a Force Quit doesn't terminate the app, I have to resort to downing a hardware power off.

Also, while working on DVRS and in a project, the following happens:

1. Existing projects are running slower with playback.

2. While playing back the videos in timeline, there is a consistent flickers of random white patches over the image.

3. My BMD Micro Panel (older edition) controls does not react to movements of the trackball, which I noticed the most.

None of the above issues were exhibited in 18.6.6. I look forward to your diagnosis and hopefully a fix.

Thank you!

Hi all

Thanks for the reports. It would really be helpful if you can add some info:

• system details - hardware, OS version, drivers, Resolve free/studio and peripherals.
- Refer to the FAQs to see what helps and how to capture this information.
- If you're upgrading from 18.x and have an Nvidia graphics card, please note that there is a change to the minimum CUDA support that needs a driver update. Please review minimum requirements, download the latest Studio drivers and select Custom Installation > Clean Install.

• URL for diagnostic logs - Dwaine has these excellent specific instruction posts to
- capture and post logs and system info for Windows
- capture and post logs and spx for macOS

• Content - If your issue is project-specific or media-specific, please consider including a copy fo the media or the project export (DRP file) in the URL above.

You can edit your current response to include this info. If you prefer to respond in a new post in the thread, please consider including a short description of your issue in the response.

Regards
Shrinivas

Hi, Where you able to get the file that I shared? Here’s the link. https://drive.google.com/file/d/1riolGv ... share_link

I hope to hear back from you soon,

Thanks.

Upgraded to 19.1 (Studio) from the previous version and rendered an existing 4k/60 project.....and the file size ended up HUGE, 300+GB instead of ~9GB.
My projects normally have the DR QUALITY RESTRICT TO 48000 kb/s
Right click the 300GB MP4 in Win10, DETAILS tab, the Data rate/Total Bitrate is over 500000kbps

Setting DR QUALITY RESTRICT TO 16000 kb/s gets me back to ~48000 kbps in Win10 Details tab.

Very repeatable problem, seems like a multiplier in there somewhere has been upset.

MP4
H.265
Encoder = Nvidia
Timeline = 3840x2176
FPS = 60
Encoding Profile = Main
Rate Control = Variable Bitrate

Ian.

At this point I have no choice but to go back to 18.6.6 coz I need to be working on projects next week with a stable Resolve version. So need to ask for the community help based on their experience with downgrading Resolve.

Do I have to completely uninstall Studio 19.1 and then install Studio 18.6.6? Do I have to deactivate the license first before uninstalling 19.1 so I can use it on 18.6.6 or will it know?

Do I have to completely uninstall Studio 19.1 and then install Studio 18.6.6? Do I have to deactivate the license first before uninstalling 19.1 so I can use it on 18.6.6 or will it know?

Yes, I'd first uninstall. Deactivating the license might be a measure of caution, but you wouldn't loose it anyway if you don't. Just avoiding some hassle if the second license is already in use.
The biggest problem is going back with your projects, since any projects from 19 are not backward compatible. I understand that you want to start a new project, so I mention this as a warning to others reading this.

Finally, I'd suggest to use a 'sandbox' system if anybody is using FCP-X too and wants to update. Unfortunately, Version 11 is forcing us into Sequoia, and there I'm still hesitant…

I have to correct myself here, Apple is now offering the updates under Sonoma too. The need for Sequoia is for some of the new features only, but generally FCP 11 should work under Sonoma.

Do I have to completely uninstall Studio 19.1 and then install Studio 18.6.6? Do I have to deactivate the license first before uninstalling 19.1 so I can use it on 18.6.6 or will it know?

The biggest problem is going back with your projects, since any projects from 19 are not backward compatible. I understand that you want to start a new project, so I mention this as a warning to others reading this.

I did backup my previous projects in 18.6.6 prior to the upgrade so I expect it will restore when I downgrade to 18.6.6. It would be a disaster if I couldn’t restore it back. Thanks Uli.

If those 18.6.6 versions are .drp files, you can always import them into a fresh Library under 18.6.6.
That never failed here.

If those 18.6.6 versions are .drp files, you can always import them into a fresh Library under 18.6.6.
That never failed here.

Was able to go back to 18.6.6 and restored from backup. Good thing is I am able to get back to my working schedule this week. DVR 19.1 is buggy and not ready for prime time at the moment. To bad coz there are so many features in 19 that I really would like to use.

When are we expecting to get a stable version of 19.1.x? It’s got nice features to avail off but it’s not ready for prime time production use.

We really don't get any notice about when new versions will arrive. They just show up one day.

When are we expecting to get a stable version of 19.1.x? It’s got nice features to avail off but it’s not ready for prime time production use.

I'm in the process of finishing a new feature done entirely in Resolve 19.1, and it's been OK so far. Had a weird crash this morning, but I think it was due to some drives getting disconnected from the system. All is well now.

On my iMac 2017 Pro, DVR Studio 19.1, besides being sluggish during playback, the two major issues that is constantly happening are (1) white square patches appearing randomly appearing during playback and (2) Resolve won’t quit/exit the app no matter what I do, even with a Force Quit. The computer hangs and the only way to shut the computer down is through a hardware power off (pressing the power switch).

I have sent the logs and dumps to BMD including a copy of the offending clip. It doesn’t happen to only the offending clip… it just so happens that was when I have it crash while capturing the logs. This happens to any file size or codec.

The iMac 2017 Pro has 64gb RAM, an Intel Xeon 10 core W CPU, an internal AMD Vega 56 8gb gpu and external AMD Vega 56 8gb gpu (from Blackmagic GPU), 1tb internal SSD and 12Tb NVMe storage for working and 2Tb NVMe for cache - via TB3. OS is MacOS Sonoma.

Going back to 18.6.6, none of this happens at all. The same clips and projects run smooth like butter. So this is a 19.1 bug that still has not been addressed. I hope the logs and clips I provided BM will help but so far,mit’s been sometime now and I have not heard a peep from them.

[Peter Chamberlain]

Can you please try 19.1.1 that was just released?

Can you please try 19.1.1 that was just released?

Peter, I am wrapping up a project by Wednesday this week and I can’t do the update until then. I have some downtime the rest of the week so I will give 19.1.1 a try and hopefully it’s no longer buggy. I will report my findings here.

@Peter, as previously stated I am going to upgrade to 19.1.1 on the Apple Intel iMac to see if the issue still remains. Just so that we have a baseline environment, for the environment your having 19.1.1 working without issues, are you on MacOS Sonoma or Sequoia? Let me know so I can duplicate that environment.

On 19.1, I also noticed that sometimes, when saving the project, Resolve hangs and ultimately I have to force quit the app. Resolve, as already reported previously, hangs when you try to exit the app. I now am thinking that it could be that when I exit the app, assuming Resolve attempts to save the project before exiting, the saving part of the project is causing Resolve to hang on exit and the only recourse is to either force quit the app, and in a few cases, I had to do a hard power off because the entire computer is not responsive. There could be a correlation to the problems.

Question to the community who’s on Mac ecosystem. When installing 19.1.1, are you on MacOS Sequoia or Sonoma? Should you upgrade to Sequoia first if so? For those, again on Mac, who are not experiencing issues with 19.1.1, which MacOS are you on? Trying to figure out what’s a better path to install 19.1.1 after all the problems I’m having with it but not on 18.6.6, as well as all the reported crashes so far. Thanks!

I’m on Sonoma for the M1 and Ventura on the iMac, both now updated to 19.1.1.
just finished a pretty complex project on the M1 without any major issues. The very demanding benchmark by Team2Films (see my other thread) is getting through as well.
It crashes on the iMac if the eGPU is attached, but renders without that (very slow, of course).

I’m on Sonoma for the M1 and Ventura on the iMac, both now updated to 19.1.1.
just finished a pretty complex project on the M1 without any major issues. The very demanding benchmark by Team2Films (see my other thread) is getting through as well.
It crashes on the iMac if the eGPU is attached, but renders without that (very slow, of course).

Thanks Uli. I just finished a project so I going to attempt another upgrade to 19.1.1. I'm still on Sonoma but was wondering if there's gain to go to Sequoia, particularly if others (and of course BMD QA) are testing on Sequoia. I'll see how it goes but if it is still failing, then the ritual of going back to 18.6.6 will happen, which I hope not. TBD.

Since I observed crashes with our eGPU, could you try on your iMac without that attached?

Apart from that, those white square patches appearing randomly during playback may point to a GPU issue. Try to observe temperatures with TG Pro, it's running without a license for a while.

I've seen that crash when exiting in earlier versions, but not recently any more.

Since I observed crashes with our eGPU, could you try on your iMac without that attached?

Apart from that, those white square patches appearing randomly during playback may point to a GPU issue. Try to observe temperatures with TG Pro, it's running without a license for a while.

I've seen that crash when exiting in earlier versions, but not recently any more.

I’m using the BM eGPU Vega 56, which is the same gpu that’s on the iMac. I will test it with and without the eGPU. The same project and clip that’s exhibiting the random white square patches is not happening on 18.6.6 and with both gpu on.

The one thing I changed was the external DAS. I removed the RAID 0 and reformat the SSD to use APFS instead of HFS+. I also replaced the TB3 cable with an OWC 2.3ft TB4 cable and use a different TB port on the iMac Pro. I’m still on 18.6.6 and with these changes, everything is fine and as before. Tomorrow, when I install 9.1.1 will be the day to dread (hopefully not).

The only other thing I am curious about is the compatibility of 19.1.1 and Sequoia and if that’s how BM is testing where they are not experiencing the reported crashes and problems. That info may be beneficial.

I think they are testing with Ventura and Sonoma too, these are officially supported. My iMac can't go further than Ventura anyway, and on my MBP I'm still hesitant to go to Sequoia.
I also use the same GPU internal and external, the 580 with 8 GB VRAM, and I'm getting those reproducible crashes.
I keep my fingers crossed for your upgrade!

Okay, here’s my report. I upgraded the iMac Pro to MacOS Sequoia and upgraded Resolve Studio from 18.6.6 to 19.1.1.

The good thing:
1. Resolve did not hang on Saving the projects or exiting the application which it did before with 19.1.
2. The white square patches was not exhibited while in playback. However once in a white, the image would flash as it is played back the first time. Rewinding the play head and running the same area of the clip, the flashing no longer shows.

The bad thing:
1. On Edit page, during playback of a clip that had some NR hang up and the only way to terminate Resolve was to do a Force Quit. I think others have reported this issue so I would think it has been duly noted by BM (Peter or Dwaine).

So far, I am 80% comfortable to stay on 19.1.1 at this time.

@Uli, the T4T crashed the iMac Pro. I think I could get it to work by doing a bunch of settings like generating proxy, lowering the resolution, etc, but I figured I won’t be doing things that super stressed the computer.

I’m stay on Sonoma, Intel Mac, vega64, I saw some sluggish on 19.0 betas, from 19.0.1 work fine, I just finished two spot and one doc of 36 minutes without problems in the last month.

On Max some crash with 19.0, work fine from 19.0.1
Ps clean Os, Sonoma installed this summer on clean disk on both.


Inviato dal mio iPhone utilizzando Tapatalk

So far I have been running several projects of various length and grades and it has been running smoothly on Sequoia and DVRS 19.1.1. Watching the Activity Monitor, the GPUs are not getting saturated except when I have NR and a few effects (basic glow, blur, CST). I did notice on H.265 clips that during Edit page playback, there is a slight luminance flicker the first time it is played, but once it is optimized (red to blue bar) and I rewind and play it, the flicker disappears. This doesn’t happen on other codecs (so far). On one occasion, a 8K RedCode clip played back sluggishly and stopped, hangs the app and the computer to a point where the only option I had was to do a force quit.

I think at this juncture, it’s safe to be on an Intel Mac running Sequoia and Resolve 19.1.1 (not prior versions of 19 - did not test for this). I’m comfortable moving to 19.1.1 for now and using it for an upcoming project.

@Uli, I tested with and without the eGPU too and it was fine both ways. Watching the GPU graphs on Activity Monitor, the little notice is that the 2 gpu tend to get equal use when the clip has NR or effects like blur. So no crashes while on the eGPU on 19.1.1.

Yes, R3D needs a lot of processing power. Without caching I get only around 12 fps in a UHD timeline with 5K R3D, and my CPU cores are fully saturated. I don't get a crash with R3D, though.

The nice thing about R3D from the older cameras, which still used wavelet, is far less computing power needed if you decode in fractional resolutions, like 1/2 or 1/4. No caching needed.

Unfortunately, recent Red cameras use DCT, where this doesn't have as much of an advantage.

Upgraded to 19.1 (Studio) from the previous version and rendered an existing 4k/60 project.....and the file size ended up HUGE, 300+GB instead of ~9GB.
My projects normally have the DR QUALITY RESTRICT TO 48000 kb/s
Right click the 300GB MP4 in Win10, DETAILS tab, the Data rate/Total Bitrate is over 500000kbps

Setting DR QUALITY RESTRICT TO 16000 kb/s gets me back to ~48000 kbps in Win10 Details tab.

Very repeatable problem, seems like a multiplier in there somewhere has been upset.

MP4
H.265
Encoder = Nvidia
Timeline = 3840x2176
FPS = 60
Encoding Profile = Main
Rate Control = Variable Bitrate

Ian.

Fixed in 19.1.1..............thanks!