Blackmagic Forum

Hi, after upgrade from 17.2 to 17.2.1 (Studio Version) DR became impossible to use on my PC. It was lagging even in project manager before loading any project. Regardless of action the system was frequently freezing for 5-10 seconds, then it could work for 5-30 seconds and then freeze again.

Restarted PC several times, updated OS and graphics card (NVIDIA) without any improvement. Uninstalled and went back to 17.2 (BUILD 11) and everything is now back to normal.

Anyone had similar problem?

My PC specs:

OS: Microsoft Windows 10 Pro, Version: 10.0.19043 Build 19043, x64-based PC
BaseBoard Product: ROG STRIX X570-F GAMING
Processor: AMD Ryzen 9 3900X 12-Core Processor, 3793 Mhz, 12 Core(s), 24 Logical Processor(s)
RAM: 64 GB
Grapics: NVIDIA GeForce RTX 2060 SUPER (8GB)
NVIDIA Studio Driver: 462.59

Hello,

Can you please post the captured logs from 17.2.1 - They will help us debug your issue better. More details here - viewtopic.php?f=21&t=90190

kihestad wrote:Hi, after upgrade from 17.2 to 17.2.1 (Studio Version) DR became impossible to use on my PC. It was lagging even in project manager before loading any project. Regardless of action the system was frequently freezing for 5-10 seconds, then it could work for 5-30 seconds and then freeze again.

Restarted PC several times, updated OS and graphics card (NVIDIA) without any improvement. Uninstalled and went back to 17.2 (BUILD 11) and everything is now back to normal.

Anyone had similar problem?

My PC specs:

OS: Microsoft Windows 10 Pro, Version: 10.0.19043 Build 19043, x64-based PC
BaseBoard Product: ROG STRIX X570-F GAMING
Processor: AMD Ryzen 9 3900X 12-Core Processor, 3793 Mhz, 12 Core(s), 24 Logical Processor(s)
RAM: 64 GB
Grapics: NVIDIA GeForce RTX 2060 SUPER (8GB)
NVIDIA Studio Driver: 462.59

Yes I am having this problem after upgrading to 17.2. On the first day after I upgraded was working fine, but today which is the 2nd day using it, it is now freezing all the time.

UPDATE 01

I reverted back to 17.2 and was getting the same behaviour.

Next as my Speed Editor was not getting recognised by Davinci Resolve I decided to do a test and turn off Bluetooth from Window's Bluetooth and other devices and the freezing has now stopped and davinci is working great again.

So it looks like it could be a problem with the Speed Editor connection with windows and Davinci but I won't really know until I upgrade back to 17.2.1 again and see how that works.

Update 02

Version 17.2.1 is working fine with Bluetooth turned off or by removing Speed Editor as a device and adding it again every time.

Lagging af for me also. Reverting to 17.1.1

Daz Wood wrote:UPDATE 01

I reverted back to 17.2 and was getting the same behaviour.

Next as my Speed Editor was not getting recognised by Davinci Resolve I decided to do a test and turn off Bluetooth from Window's Bluetooth and other devices and the freezing has now stopped and davinci is working great again.

So it looks like it could be a problem with the Speed Editor connection with windows and Davinci but I won't really know until I upgrade back to 17.2.1 again and see how that works.

This could make sense, I also noticed lag on first startup after I had gone back to 17.2, but did a PC restart and also reconnected my Speed Editor BT connection, and then 17.2 worked fine.

I'll try once more to upgrade to 17.2.1 without connecting Speed Editor to see if it then works.

Rohit Singhal wrote:Hello,

Can you please post the captured logs from 17.2.1 - They will help us debug your issue better. More details here - viewtopic.php?f=21&t=90190

Will, do!

Daz Wood wrote:UPDATE 01

I reverted back to 17.2 and was getting the same behaviour.

Next as my Speed Editor was not getting recognised by Davinci Resolve I decided to do a test and turn off Bluetooth from Window's Bluetooth and other devices and the freezing has now stopped and davinci is working great again.

So it looks like it could be a problem with the Speed Editor connection with windows and Davinci but I won't really know until I upgrade back to 17.2.1 again and see how that works.

Thanks for the info, this helped a lot. I have also the Speed Editor and have had quite some problems with it latest versions when using BT. I disconnected the the "DaVinci Keyboard" BT device in Win10 control panel, reinstalled 17.2.1 and now it worked just perferctly.

I also took a factory reset for the Speed Editor using the app "DaVinci Control Panels", and then connected it with BT while DR was running, and now even that works great.

I assume there are some bugs with the Speed Editor when using BT connection.

Well, honey hush.

Unpairing worked for me in 17.1.1.

Thanks!!

Daz Wood wrote:Update 02

Version 17.2.1 is working fine with Bluetooth turned off or by removing Speed Editor as a device and adding it again every time.

Found the same solution : unpair, re-pair the speed editor and it works again.

Just had the wife complaining her video is glitching/freezing every 5-10 seconds on playback. Re-generated optimized media several times, checked the PC over no issues found. Turns out it was the Speed Editor constantly connecting then disconnecting from Bluetooth in the background. This "detection" issue needs fixing..

It seems to be identified and a fix is in the works.

This was driving me up the wall today....

Was still running 17.2 and doing fine for 14 projects straight, but this morning DVR all of a sudden was choppy and lagging, even the UI froze up all the time. Appr. 4-5 sec. of playback and -boom- UI and playback lockup. Even value changes locked up the UI.....
And in addition to the freezes, any delivery renders just locked up DVR. It just sat there with 0% CPU usage.

With the SE disconnected from BT, it seems to work fine again. Even after a relink to BT it seem fine.

The BT connection with the SE needs some more love, as this is causing some dangerous blood pressure level issues

Thank god for this forum and internet!

Hi,

I am experiencing the same issue with playback as well. This has become a real frustration recently to the point where even after a clean reboot playback will sometimes not work at all when DR is opened.

My machine is running Windows 10 on a Xeon(R) CPU E5-1660 v3 @ 3.00 GHz with 36GB RAM and two NVIDIA Quadro K2200 GPU's each with 4GB of memory. So it is definitely not underpowered and I've been editing with it for some time without issue.

To be clear DR is not crashing it is just the playback that is failing to work. The playback 'arrow' lights up but does nothing. It does change when I toggle stop/play so the signal is being picked up by DR but playback does not start.

Happy to provide more detail if needed, on the latest version of DR 17.2.1.

Thanks
Chris

Chris, please in install the GPU driver, the do a full clean install, not update, of the GPU driver.
If that doesn’t work, post ur resolve generated diagnostic logs.

have just read the SE 17.2.2. thread which mentioned removing the Bluetooth pairing and then re-pairing the SE again. I can confirm it did ask to allow the pairing and after that it seems to be a stable connection.