DaVinci Resolve 14 Beta 4 Bug Reports

After launching Resolve, loading and existing project and just clicking around I get a "Resolve has stopped working" error. This is without any editing or any heavy strain on Resolve.

I'm running the Resolve on a Windows 7 machine that is fully up to date. I installed V14 over top of 12.5.5. The system is an HP elitebook 8570p laptop with a i7-3740QM processor and 16GB of ram.

I think i may revert back to 12.5.5 for the time being, is there any other information i need to provide to help with the bug fix?

Hi, Even I have the same issues.. My Clips from 5D3 even doesn't show up..

I had the same issue im MacPro under MacOS Sierra... just crash when i load any project...
Any trick?

After launching Resolve, loading and existing project and just clicking around I get a "Resolve has stopped working" error. This is without any editing or any heavy strain on Resolve.

I'm running the Resolve on a Windows 7 machine that is fully up to date. I installed V14 over top of 12.5.5. The system is an HP elitebook 8570p laptop with a i7-3740QM processor and 16GB of ram.

I think i may revert back to 12.5.5 for the time being, is there any other information i need to provide to help with the bug fix?

Probably by switching to windows 8.1 or w10 as recommended by BMD.
(W7 is no longer even supported by Microsoft since January 2015)

Probably by switching to windows 8.1 or w10 as recommended by BMD.
(W7 is no longer even supported by Microsoft since January 2015)

That's a tad misleading. While tech support has ended, "Microsoft won't end security updates for your Windows 7 PC until Jan. 14, 2020."

Source: http://www.pcmag.com/article2/0,2817,2475079,00.asp

The program is also crashing for me while loading projects. My audio tuning keyframes from existing projects do not show up either. Performance is also much slower during playback in the editor. Lots of stuttering and skipped frames.

Probably by switching to windows 8.1 or w10 as recommended by BMD.
(W7 is no longer even supported by Microsoft since January 2015)

That's a tad misleading. While tech support has ended, "Microsoft won't end security updates for your Windows 7 PC until Jan. 14, 2020."

Source: http://www.pcmag.com/article2/0,2817,2475079,00.asp

The program is also crashing for me while loading projects. My audio tuning keyframes from existing projects do not show up either. Performance is also much slower during playback in the editor. Lots of stuttering and skipped frames.

Security (intrusion fault) does not want stability of the system: it should not be confused.

Don't blame the messenger for the message. This is a "beta" release. These are not Windows 7 problems. Resolve 12.5.5 is solid as a rock on Windows 7. There are many bugs, on Mac and Linux as well. No doubt they will be addressed.

Cheers.

Yeah. It's crashing on me too. But it only crashes when I go into the Fairlight panel.

Per request over private message I submitted my error log and project file.
I was informed that they found the error and will incorporate the fix into the latest release.
I was advised to roll back to 12.5.4 for the time being.

***SOLUTION TO V14 NOT OPENING IN WINDOWS***
One solution to Resolve v14 beta crashing on startup on Windows. Thanks to Rohit Singhal at BMD for working this out.
If you find v14 stops working after the splash page shows "Loading Video Waveform" the problem could be using the old 12.5 database. [not an audio plugins issue as I originally thought]
Solution that worked for me:
1. Opened 12.5.5 studio and created a new database which I put in a new folder at ProgramData\Blackmagic Design\DaVinci Resolve\Resolve database Apr 2017
2. Closed 12.5.5. and uninstalled it and the panels program
3. Installed v14 studio with the panels update
4. Started up v14 and it got through to the projects page successfully, defaulting to the new database
5. Created a new project and opened it. It took a good 3-4 mins before DaVinci eventually opened but it did.
6. Set up all my presets and it seems good to go.
7. Shut down DVR and reopened it and this time it opened as quickly as usual (seconds).
Haven't had much time to test it but switching to Fairlight tab does not cause a crash as others have experienced. Performance is much better than 12.5 even with nasty H.264 UHD material.
I haven't tried pulling up a project from the original database as that may cause problems.
Please let me know if this helps you out.

Credit to: Scott Thomas.

I updated from 12.5 studio to 14. I had a dongle that worked well with the last version, after the update to 14 studio the Program doesnt start. It just says checking licences, loading pannels loading waveform monitor etc and then nothing happens. the software doesnt open at all. i am stuck I am in the middele of a project. will I have to go back to the older version or will I be able to use it with the dongle that I have

Interestingly, I've tried rolling back to 12.5 by exporting my Resolve 14 project and trying to import it into 12.5, but now 12.5 crashes without an error/warning. It just disappears off the screen. Anyone else had this problem? Or have found a solution? Because I'm kinda stuck in a limbo.

Running Windows 10.

Installed over 12.5

Tried to open 12.5 project (a 3 minute video). Crashed before opening.

Opened Untitled. Tried importing backup project. Now two versions of that project in database. Each one crashes on opening.

Opened Untitled. Tried importing XML backup from 12.5 resolve project. Crashed program.

Opened Untitled. Saved as a new project name. Tried importing XML backup from 12.5 resolve project. Crashed program.

Opened my new project again (still empty). Tried importing an Adobe Premiere XML. Crashed program.

Considering going back to 12.5 to finish this project. Sad, because I was hoping to use Fairlight audio on it. Maybe a future update will solve this? Will I ever be able to open 12.5 projects in 14?

Anyone else unable to even launch 14 STUDIO since b1? I sent the data that was requestioned but have heard nothing in several weeks. 12.5 still works fine.

viewtopic.php?f=21&t=54509

[Peter Chamberlain]

Please post in this thread the bugs you find with beta 4.

Thank you for your ongoing support.

System: MacPro 2013 2xD700 64gb RAM, Pegasus R2 RAID

R14 beta 4: I'm getting black frames instead of footage on either new or preexisting projects. I will quit and reopen and the project and it will be fine. Then it will revert to this behavior again. Very strange.

[Peter Chamberlain]

System: MacPro 2013 2xD700 64gb RAM, Pegasus R2 RAID

R14 beta 4: I'm getting black frames instead of footage on either new or preexisting projects. I will quit and reopen and the project and it will be fine. Then it will revert to this behavior again. Very strange.

Can you share with me a sample project that exhibits this?
and OS version?

Had a similar thing happen with DNG and CDNG sequences, but after I restarted my computer everything went back to normal.

(on a MBP mid-2012 with the latest OS X and latest CUDA drivers)

When installing DR 14 b4, I get the error DavinciPanel.inf not found. See screen capture image. I had DR v14b3 installed. This is the first time I got a DR installer error.

Windows 10 x64. nVidia 960M.

Hello,
When we have a master timeline with some timelines inside : no sound when played.
Thanks for your work

Hi BM,

First off , thanks for the amazing work on Resolve 14 !!!!!!!!!!

I experience a problem with using clips from a consumer Sony handycam, that worked fine in Resolve up untill 12.5.6 and breaks down in Resolve 14 beta 1-4. It shows itself as random frames of the clips showing as offline.

I am aware resolve does not and has never supported the audio part (ac3) of sony consumer clips , therefore i always rewrap the clips using editready (latest version) where audio becomes pcm , video untouched pass through to mov container and the resulting clips work fine in resolve. I then use resolve not to edit but to transcode and deinterlace to prores 422HQ for editorial.
Would love to use 14 for this as much faster but this problem makes it unusable unfortunately. As they worked in 12.5.6. i hope its a simple bugfix away.

Attached a link to a sample clip (password : resolve)

https://cloud.tachyon-consulting.com:55 ... kr4ovpryDV


System details:

Resolve Studio 14 beta (any beta has same problem so far) , dongle version.
Running in CUDA mode

OSX Sierra 10.12.4
CPU i7 4790
Mem 32GB
GPU 2x Nvidia GTX980TI
Driver version : 378.05.05.05f02 (latest)
Cuda : 8.0.83
Storage : SSD based

Again the old tracking problem with "Center or Scale mismatched resolution file" setting not fixed.
The problem is well explained in this old post: viewtopic.php?f=21&t=28105&p=183025&hilit=+center+crop+with+no+resizing+#p183025

Hello,
When I open project from DR14 beta 3, the sound on timeline sounds like from telephone. The other problem is that the sound is play much faster than it should. Clip speed is set as 100%, but it sounds like 150%.

Other problem:
Sometimes I see "Media Offline" alert for few frames in Edit and Color page.

I have also a sugestion. Thumbnails in media pool could be much biger. Too much room is wasted for the border.

Audio crossfades still don't work for me at all, audio always starts or stops suddenly as if the fade were not there. Dragging the corner for a fade does work, but standard crossfades (from right click menu) don't.

Many thanks,
Paul

MacPro6,1
D300
34GB Ram
MacOS 10.12.5

Audio crossfades still don't work for me at all, audio always starts or stops suddenly as if the fade were not there. Dragging the corner for a fade does work, but standard crossfades (from right click menu) don't.

Many thanks,
Paul

MacPro6,1
D300
34GB Ram
MacOS 10.12.5

Same here; Audio Crossfades are still not working at all in any way shape or form.

On Mint/Ubuntu systems, starting or loading a project now shoots out a "Segmentation fault" immediately. This was not the case with any of the previous beta versions.

Tested on 3 Linux systems - all i7 processors with:
1. i7 4/core 1.7GHz - 8GB - nVidia 420M 1GB VRAM - 500GB HD - Mint KDE
2. i7 4/core 2.67GHz - 12GB - AMD RX480 8GB VRAM - 120GB SSD & 2x1TB HDs - Ubuntu Studio
3. i7 6/core 3.2GHz - 24GB - nVidia 580GTX OC 1.5GB VRAM - 2x250GB SSD & 1x120GB SSD - Mint KDE

All OS Kernels are distribution recommended.

Time Line Audio Key frame are still not working correctly: Not honoring the position or level adjustments values. (h.264 media)

Time Line Audio Key frame are still not working correctly: Not honoring the position or level adjustments values. (h.264 media)

Same problem here.
Win10

... but some h.264 video decoding glitches from beta3 fixed.

Hello,
When we have a master timeline with some timelines inside : no sound when played.
Thanks for your work

I can confirm that. Not only with nested timelines, also with compound clips.

Here some initial bugs when editing a project this afternoon.

- Selecting a clip in the media pool and hitting delete doesn’t delete the clip. Clicking another clip and then clicking back on the first one and hitting delete does bring up the delete confirmation window.
- Playback volume from the Fairlight page compared to the Edit page is different. The Edit page plays back audio distorted whereas Fairlight does not.
- Computer crashes at some point during playback with CC and Audio effects on footage. Doesn’t happen immediately, but something eventually makes the computer crash when I was scrubbing.
- Moving the audio handle of a clip in Fairlight, resets the audio curve.
- Render queue stopped at 99% and didn't complete. Resolve locked up then the entire computer locked up. Manually turning off the computer and restarting was the only way to get the system working again.
- The Curve Editor icon on the bottom of the video clip has disappeared
- The graph in the curve editor is not displaying the bottom part of the curve. It seems to be cut off.
- Adjusting the fade in/out handles on a clip, no greyed area is displayed.
- It would be great to see the decibel number display when moving the audio levels line on the clip in the Edit page
- Resolve crashed when I was moving audio clips into position during playback
- Playback plays clip at the original volume even when the volume has been adjusted.
- Audio volume on playback is not adjusting even when keyframes have been added and the volume changed
- Can’t delete keyframes on audio clip
- Using the “reset” button in the Inspector does not reset the audio levels or remove keyframes on audio clips
- Tried deleting an audio clip from timeline, Resolve crashed
- Can we have an indicator added to the Dynamics window that shows when Limiting is working during playback of a clip?

System: iMac 5K late 2015 - i7 - 32GB RAM - 500GB SSD - GPU 4GB (can't remember sorry, top of the range at that time) - 2 external apple monitors

Audio crossfades working on the timeline, but.....if you delete them in the timeline they are still there in the Fairlight page and having an effect.

Hello
I'm still discovering the software, trying stuff at random.
Resolve 14b4 Windows 10

Trying to edit some consumer H264 files over a network (gigabit ethernet). The files are stored on a Synology 212j NAS.
Resolve's file browser is very slow at browsing folders, especially if there are lots of files in them.
While Resolve tries to open the folder, the entire program is frozen.
After a few seconds, the folders are open and Resolve can play and edit video normally.

I understand this is a very unusual scenario as most of you are used to editing local files on high speed drives, but I wonder how Resolve would cope with waking up a hard drive in sleep mode. (might produce a very uncomfortable 10+ seconds of total program freeze)

More UI remarks :
-When playback is active, cannot switch between the software's main modes (media, edit, color, fairlight, etc...)
-When playback is active and I open a context menu (rightclicking). Playback is suspended.
-Then when closing the context menu, playback fast-forwards to the equivalent amount of time the context menu was open for and resumes playing
-Opening the preferences menu stops playback.

Audio crossfades working on the timeline, but.....if you delete them in the timeline they are still there in the Fairlight page and having an effect.

I can confirm this on a project created in Beta 3 and now open in Beta 4.

Update: After switching to the Fairlight page to confirm the presence of the crossfade, the program crashed. I restarted Davinci, but the program continued to hang. It was opening to the Fairlight page again. A computer restart finally helped, and now the crossfade is gone.

Playback in this version is significantly worse than in Beta 3. I've got DNX footage and H.264 in a project that was working quite well in Beta 3. I'm on W10 x64, with 32GB RAM, Xeon E%-1620 @3.6GHz, GeForce GTX 660 Ti.

Adding Red Giant Universe OFX plugins crashes DR v14 b4. Upto b3, it used to give a video memory full error, but no crash.

Hello

Just installed the most recent beta and noticed that when one is either in the channel mixer, NR and curves tabs when A+Primary is pressed on the Element BT panel the result is the main menu switches to the primary page. When one is in the Qualifier, Windows, Tracking, Blur, Key or sizing menus the A+Primary button seems to switch the main menu into the Custom Curves window. This then onbviously doesn't correspond to the options that are shown on the Element Kb panel. Also some of the menu options on the element Bt panel once pressed do not shift the software into the appropriate windows. For example if you press B+Key it does not shift the software to the key tab. Nor does pressing the A+Primary adjustment switch into the page with midtone detail (yet midtone detail color boost temp tint shadows and highlights is what is visible on the Kb panel)

All the best

Stepan

This stuff also happens in the new 12.5 version

Resolve 14b4. Windows 10

Zooming on the timeline with the mouse wheel doesn't work in edit mode.
Using alt + mouse wheel does work though.

Too bad we can't install beta 14 without installing over 12.5.5
The beta has may issues that hinder work.

Adding "volume" keyframes on the edit page results in strange effects. For example: adding a volume keyframe 4 seconds before the end of an audioclip (m4a) with a value of 0dB and a volume keyframe (setting -100) at the end of that audioclip to create a fadeout, results in unexpected fluctuating volume-levels of that audioclip between 12 and 4 seconds before the end. Same problem with a wav-format.

Markers
(1) double clicking a marker to open the marker's pop-up and clicking in the timecode ruler adds a new marker.
Expected behaviour: marker pop-up to close without creating a new marker
Issue not in beta3.

(2) double clicking a marker and clicking the Save button, creates a new marker.
Expected behaviour: marker pop-up to close without creating a new marker, simply only saving any additional changes made.
Issue not in beta 3.

(3) Creating markers in the Fairlight tab do not appear in the Markers (Index) in the Edit tab.
workaround: only create markers on the Edit tab.

Maybe not so much a bug, than an annoyance and possible mistake. When creating a new database you cannot type any capital letters. It has no issue with existing databases that have capital letters, but you can type them in new database names. When you sort by name it puts the databases with a capital first letter at the top and newer databases with lower case first letter on the bottom. It would be great to be able to actually type a capital letter so the sorting would be accurate. For cleanliness and client privacy I create a new database for each project that's brought to me.

Command-click on a assigned plugin in Fairlight crashes Davinci Resolve. (MacOS Sierra 10.12.6)

Not a bug, but a requirement: It should be possible to copy a plugin preset from one track to another.

Upon startup an exclamation error box appears saying "fairlight interface version in library (85) doesn't match with what is used in resolve (88) it may not work as expected". Beta 4 installed over beta 3. This message never appeared before. Also a second new startup error box comes up... "failed to initialise RED Decoder with the configured number of decoders.

Window 10
16gb ram
GTX 960m

These still exist from my previous v14b3 bug report

- Poor video performance in Fairlight tab for graded material (and cannot bypass all grades without going to Color tab). Either improve performance or add a bypass button in the Fairlight tab/let the keyboard shortcut work. Even using bypass, playback can be a bit choppy despite playing back fine in Edit/Color pages. Perhaps a bypass button/checkbox in the Fairlight page could be entirely separate from the one in the Color page, so it will always bypass on the Fairlight page but then be graded on the other pages?

- Jobs cannot be updated once added to the render queue using ‘Update Job’. You can modify settings but the ‘Update Job’ button remains greyed out. Navigating away from the job, triggering the ‘do you want to save changes’ dialogue, will update the job however.

- Dragging from the ResolveFX panel to create a standalone node - these nodes do not connect to existing nodes when dragged over a connecting line


And then there's the list of bugs I've made regarding not only v14 but also previous versions of Resolve; the guaranteed crash when using highlight modes (as listed here https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=50258) might be a simple fix?

Keep up the good work!

- tom -

In preferences, I de-selected 'Use 10-bit precision in viewers if available' and restarted Resolve. No clips were visible on my timelines, and pressing play would do nothing. Shutting down my machine and rebooting brought things back to normal.

MBP2016, OSX 10.12.5, 2.9 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 460 4096 MB, Resolve Lite 14b3

The latest beta of Resolve is exhibiting very high CPU load after opening the Fairlight page. Windows x64, i7 6700K at 4.5GHz, 64GB RAM, NVIDIA 1080 Ti.

When this happens, a thread seems to be busy-looping either within this function, or is continuously invoking this function:

Code: Select all

boost::archive::detail::oserializer<boost::archive::text_oarchive,DVIP::ColorGradientParams>::save_object_data+0x49bfa3

Steps to reproduce:

1. Create new project
2. Pull in a media clip onto a new time line
3. Observe that CPU utilization is low
4. Switch to Fairlight page
5. Observe that CPU utilization is high even while idle. Process Explorer indicates the CPU-consuming thread is steadily in the above function.
6. Switch back to Edit page.
7. Observe that CPU utilization remains high while idle.

Hello,
Just registered to provide feedback on the beta. I'm running MacOS 10.12.5 on an i7 6700K, 32GB of RAM, with a GTX 1060 6GB card. Footage is on a 960 Evo NVMe drive.

I'm also still experiencing the audio disappearing in compound clips and nested timelines. Today I found a new problem- on trying to render a long project, DR gets to 4% and stops. The first time I got the following message:



None of the buttons functioned so I had to force quit. I relaunched and tried again, the render stopped at the same point. I had successfully rendered this project in beta 3 on another machine.

I've attached an export of the project document as well as the logs. Hopefully they will be helpful.

Best regards,
Allen

In Aces or Acescc there is a bad visualization of both color and brightness image only in edit page and is also present in decklink monitor output.

Frist: A Big Compliment Team DaVinci Resolve

Title issue, it worked in 14 Beta 2/3
When copying an existing title text within the timeline, with command C / V or option & mouse,
and start changing the title text - all the changes will not show up in the timeline, and I can’t play the program anymore, I can move playhead but current clip will not show up.
I can still move clips around, change audio level, I can do changes in Fairlight, Color page won't work clips are greyed out.

And In the media pool all the clip thumbnails are greyed out.

Sunny greetings from LA

Matthias