Dwaine Maggart wrote:I'm not sure it's worth the effort to export projects in V12, as those should be able to be Imported in V14 from the original V12 database, if they are going to work at all, in the Project Manager area. But it also can't hurt.

Dwaine - the whole idea is to assure DR 14 never even connects to the 12.5 database, or it will crash sooner than later and never raise again. So the 12.5 database backup is really only a safety measure - should the 14 not work for any other reason (even with the empty database), one can revert safely to the 12.5 and his database copy, which of course will never be corrupted by 14's crash as the 14 never saw or accessed it.

Dwaine Maggart wrote:You can backup the database to any location you have write access to.

Sure - it's just a back-up. But again: never try to point the 14 to it, as it will stop working again...Hence the idea of individual projects' exports as .drps in addition to database backup as a whole - this will enable DR 14 user to access the projects he/she would like to continue working on, without opening the 12.5 database at all which will be fatal And yes - importing 12.5 drps into DR 14 will lose some of its contents (as Akpe described), but this is a small price for making DR 14 work at all (and being 100% stable, too - I never had a single crash since I devised an applied this whole procedure.

Hello All and good day. I have problems of using the Spatial Noise Reduction. For some reason it kinda creates a form of pixelated blocks instead of smoothing the frame. I never had problems of using this feature on the previous version (Davinci Resolve Studio 12).

Attach here on the image is I'm using the Face Refinement tool. The smoothing feature of the Facial refinement tool is just the same of the Spatial Noise Reduction feature but its mainly focused for the subject's face.

I pushed it to the extreme and I'm noticing this weird macro blocks on the face.

Here's a list of bugs I've encountered in Beta 3 while working on the latest project:

- Audio playback inconsistent with the audio volume (caching??)- Audio playback at times stops playing- Audio with VST plugins at times either don’t play, or the plugins can’t be adjusted- Keyframing audio doesn’t work consistently- There is a difference in audio quality between Fairlight and Editing pages, especially on levels and clipping- Adjusting the volume on a clip doesn’t affect playback of that clips levels. Restarting fixes forces Davinci to play it back at the proper level- Not all audio tracks playback in the Colour Page (maybe because "Insert" activated randomly at some point)- The “Insert” button in Fairlight seems to activate at random which interferes with audio playback.- Audio playback on Edit Page out of sync, especially after some Fairlight or Colour work- Power windows aren’t working properly. The affected area inside the window is severely offset or scaled down, even without any softness applied.- Undo doesn’t step back through the last series of steps sequentially. Some previous steps are skipped- Audio Snapping doesn’t seem to be active for aligning audio clips to other audio clips.- If grading is disabled in a project and that project is saved and closed, the grade becomes re-enable when reopened. Is this expected functionality?- Window layouts aren’t remembered/saved when reopening Resolve.- Updating an external file should auto-magically roll into Resolve and update the assets in the edit. e.g. an after effects animation that’s been tweaked and exported again with the same file name should just update in the timeline automatically as in Premiere and FCPX.- Audio waveform moves position within a clip when that clip is dragged- Audio waveform fails to redraw properly when zooming- There are crackles present in the exported audio where tracks have VST plugins from Izotope RX6, almost like many pops on a vinyl record. These crackles aren’t present during playback previews, just in the rendered export.- Horizontal mouse scrolling in Fairlight zooms the timeline rather than moving left and right. I feel this should have the same experience as the other areas of Resolve.- Addition of a Solo button for audio in the Edit Page. Flicking back to Fairlight to switch it off (when I forget) is a little cumbersome.

My most important bug list blocking me from playing seriously with 14.1. Maximum audio out 2 channels. Whatever i do it does not see any other output then 2 channels (neither on my blackmagic 16 chan audio capable interface via SDI, nor my 9 channel RME via system audio)2. Does not play clips from my current project involving Sony consumer avchd imnterlaced clips, that all work perfect in 12.5.5). It plays them with random offline clip frames (more offline frames then online).

1) Edit Tab: (Using 4K h264; w/ 48kz audio) simply activating and deactivating the Clip EQ causes some very strange audio sounds. It seems to recover if you move the play head backwards or stop and restart the play head.

EDIT: The above seems to be caused by my prev. error above with the audio no being removed in Fairlight when being deleted on the Edit page. The only way (short of deleting the track) to remove the audio track from the Fairlight tab is to close and restart.

The interesting part is you get double audio for a "while" on the edit page, then goes away, while the audio wave form is still present on the Fairlight tab. I'm thinking this orphaned audio wave form is causing the strange audio effect when activating the Clip EQ. Hopefully that make sense.

2) Media Tab: Ctrl F cause complete audio loss.

Last edited by Robert James on Fri May 26, 2017 6:58 pm, edited 1 time in total.

blinkin "media offline" red frames some times on icon on color pageand very often when playing and in this places "media offline" blinkin red screen stayng after render (1 frame red screen) - and it happins alltime in begin of clip near the cutif i return playhed before cut - this red frame can disappear, or can not disapper - forntuna..sometime it can disappear on playing and stayng after render

footages is cheked earler on 12.5.5 and premiere and avid - all finepromblem in all davinci projects(new and old)

1. When there is no NVidia GPU present, but CUDA is selected in preferences, the app first informs about no CUDA compliant GPU present and then hangs with a beach ball of death spinning after selecting a project.

2. Resolve 14b2 fried my Nvidia Tesla M2090 GPU. An attempt to use NeatVideo resulted in a system crash. After a restart, Tesla was not found by Nvidia drivers and did not show up in the system info. A subsequent restart attempt lead to power cycling that continued until I removed the card.

- a way of skimming through the clips for selecting I/O points, this is one of the biggest advantages for me in terms of speed when working with FCPX.

- a proper AAF export with definable audio handles (!) and contained wav files - the fairlight integration is great and I'm looking forward to use it in-house in future, but now most of the projects have to be delivered to external sound engineers who expect an OMF or AAF file with handles for being able to trim and blend clips ect.

First of all thank you BMD for all new functionality. For example all new category in Edit index serch. This is very useful and time saver. "Show clip conflict" is grat but i have a problem with conflicted clips.Normally "conflicted clip" are indicated by red [!]. To change clip double click on red ! and new window pop up. In 14b3 I can not change conflicted clip because double click make clip go to source window and new window with suggested clips does not pop up.Is it bug or something changed? How can I open suggested conflicted clips?

- Horizontal scrolling is slow.- In dual screen mode, can we remove the source monitor to increase screen realestate of the project monitor.- Resolve crashes randomly when disconnecting a database on the projects load screen.- After a project is selected, the main window doesn’t open full screen on single display rMBP.- Handles at either end of a audio clip don't show the greyed out portion of the clip when the timeline is zoomed in.- Applying “Dynamics” to the main audio channel in Fairlight, plays back the audio cleanly but it's distorted on the Edit page.- The Gain Reduction section of the Dynamics console doesn’t show when the Limiter is in operation.- Can we have a “Normalise” effect for audio please?- The opening Project Screen randomly closed the Database list on the left side when reopening Resolve- When setting up projects, relinking media and creating the save location when delivering an export, can we set certain folders as favourites so we don’t have to dig through our folders structures every time? Or can the popup File Destination window be the system OSX finder window?- Unable to export Audio Only. “Add to Render Queue” greyed out. When using a custom preset and deselecting “video”, or when using the “Audio Only” built-in preset, the box remains grey. When checking “Export Video”, the box appears.- On the deliver page, Disk pace currently used and disk spaced used after render, both read 0%. However, Finder reports that there is 117GB free.- Apply Dynamics in Fairlight turns on the “EQ” indicator in the mixer back in the Edit Page. Perhaps the dynamics effect is being read as EQ gain which is why it’s distorting?- On the Deliver page, time remaining against the Job in the queue, does not match the time remaining to the left of the stop button.- On the Edit Page, there needs to be a line under the last track of Audio (at least in the label panel) to show the track’s vertical height. At present, the grey just goes down to the bottom of the screen.- The audio meters peaking levels on the track are higher that the final M1 output, no effects are present on either track. When there is only 1 track with audio, I would expect the read out to be identical.- Regarding the scale on the Audio Meters, where the main sliders controls are located in the default state (against the white marker), shouldn’t this be 0dD?- Can we have a reset button on the audio sliders to put them back into their default level?- Audio waveforms disappear entirely when completely zoomed in.- When saving the project using CMD-S, the project saves as expected. But then when immediately quitting, a pop up advises that the project hasn’t been saved.

1. Exporting of Custom Keyboard shortcuts works, but when imported to different database default keyboard shortcuts are applied instead (Only the name of the presets loads) 2. "Compound Clip" with 2 or more Audio layers crashes Davinci Every Time. Works fine with just video selection and no audio or with video and 1 track of audio. 3. When trying to change Keyboard shortcut to "s" says "S is already in use by editToggleSlipSlide" but editToggleSlipSlide does not show up in the keyboard mapping thus not allowing it to be changed at all.

Suggestion: Database option to allow a custom Project Setting Presets to be applied to all newly created projects by default.

Loving version 14, you guys are super close. Our whole company is on the verge of leaving Premiere if all pans out with our trials with Davinci.

Last edited by Weston Childers on Mon May 29, 2017 3:17 pm, edited 1 time in total.

1) Have two clips: video (h.264 from Cinema 4k app, optimized media generated, mono audio embedded) and audio (wav, 48/24 stereo from Zoom H1)2) I select video and audio and then try to automatically link audio based on waveform.2.5) (This feature almost always fails for me btw, the exceptions are very rare. I pretty much gave up even trying)3) Because (2.5) I hit Undo4) Now the original mp4 has become silent. There seems to be no way to hear the embedded audio anymore! This reproduces 100%.

There is a trick to work around it: hitting Undo one more time (undoing some previous operation) and then Redo, restores the audio. However I cannot recover audio for the clips that lost it before I found this workaround. Deleting the clips from media pool and adding them back again does not help. Help appreciated.

Another thing: at the beginning of each clip I get a horrible crackle. Same when I scrobble. I'm 100% certain there is no crackling in the originals.

and it will be great if new windowed BIN will can resize to very small, now it's limit for downscale this windowand it will be VERY great - if we can move clips in bin with NO align to grid, like in avid mc

- 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

I was also going to say that if you try to reconform a timeline to selected bins or media storage folders, then nothing will happen, but from reading the manual on the matter I learned that in order for either to work you must disable 'Force conform enabled' on any clips you want to reconform. This wasn't the case for the 'reconform from bins' option in 12.5 (not in order to get the dialogue box to open at least), so I suggest that in order to prevent a lot of confusion/forum posts from people who haven't read the manual, that there is an error message when trying to use either 'reconform from bins' or 'reconform from media storage folders' without first disabling 'Force conform enabled' on relevant clips.

I'll also shortly be updating the bug lists I made for v12 with more that I have found that still exist in v14, and also specifying which of the previously reported bugs have been fixed.

I still haven't played that much with the Beta. However, I encountered a small bug in the Linux version.

When I try using shortcuts to switch between the different pages, it switches the first time, but then each time I try switching I have to click anywhere in the interface with the mouse before I can switch to any other page.

To explain more let's say I am on the Edit page and want to switch to Color. When I click 'Shift+6' it goes to color page as expected. Now, let's say that after going to Color page I realised -before changing or doing anything in the Color page- that I want to do something in Fairlight page. If I press 'Shift+7' now, it won't go to Fairlight. I have to click anywhere in the Color page using the mouse and then press 'Shift+7' and it will switch.

I tested that in Windows, and it worked fine, so it seems to be a Linux-only issue.

Abdelrahman Magdy wrote:I still haven't played that much with the Beta. However, I encountered a small bug in the Linux version.

When I try using shortcuts to switch between the different pages, it switches the first time, but then each time I try switching I have to click anywhere in the interface with the mouse before I can switch to any other page.

To explain more let's say I am on the Edit page and want to switch to Color. When I click 'Shift+6' it goes to color page as expected. Now, let's say that after going to Color page I realised -before changing or doing anything in the Color page- that I want to do something in Fairlight page. If I press 'Shift+7' now, it won't go to Fairlight. I have to click anywhere in the Color page using the mouse and then press 'Shift+7' and it will switch.

I tested that in Windows, and it worked fine, so it seems to be a Linux-only issue.

1) (LINUX ONLY) This one is related to the bug quoted above.. When I switch pages in the Linux version and then press Alt+F4 to close Resolve, it doesn't work until I click with the mouse anywhere in the interface, then press Alt+F4

2) (LINUX ONLY) It appears, that Resolve 14b3 doesn't close correctly on Linux. When I check the System Monitor after closing the program, the process is still there. Trying to end it in the GUI System Monitor or using the 'kill' command in Terminal doesn't work as well. The only thing that stops it is using the special command 'kill -KILL'. This causes issues when I try to shut down or restart my computer as it either gives me a warning that Resolve is still running, or it takes ages to shut down or restart. I didn't have this problem in the earlier beta versions.

3) (WINDOWS & LINUX) Issues with Fairlight Timeline View Options:

- Checking 'View Flags and Markers' and 'Show Full Waveform' doesn't work properly. When I check any of these two, the timeline doesn't update. I first have to click somewhere in the interface, and then the timeline will be updated with the new settings.

- The other options doesn't seem to be working at all. To be fair, I am not sure what 'Show Waveform Border', 'Show Audio 1' and 'Show Audio 2' do exactly. However, as far as I understand (and correct me if I am wrong), the 'Show Video' option is supposed to activate a small display of the video tracks. If I am right, then it is not working as well because nothing happens when I check it, even if I click with the mouse on the interface.

4) (WINDOWS & LINUX) Selected audio tracks doesn't seem to be recognized. To explain, let's say I have 2 video tracks and 2 audio tracks, and I need to delete specific part of everything on all of them. When I add in and out points around the part I want to delete and hit the 'Delete' or 'Backspace' buttons, it deletes everything on Video 1, Video 2, and Audio 1, but leaves Audio 2 untouched, although all the tracks are selected.

5) (WINDOWS & LINUX) The compound clip alpha issue I had in most of the Resolve 12 versions (it wasn't fixed until 12.5.4 I think). The issue is back in 14b3 (not sure if it was in the earlier beta releases). Let's say I have a couple of clips, all with alpha channels, and I want to add them into one compound clip. The moment I do that, Resolve converts the alpha channel of all of these clips into black.

Resolve 14 beta 3 seems to be getting less stable on my machine. Resolve now crashes constantly sometimes before it loads completely. I would really like to see the VST graphical User Interface scaling issue addressed. I have found no solution on my own, so I must conclude that it is a software issue. If there is a solution outside resolve please share.

SymphonyEtude wrote:Hello All and good day. I have problems of using the Spatial Noise Reduction. For some reason it kinda creates a form of pixelated blocks instead of smoothing the frame. I never had problems of using this feature on the previous version (Davinci Resolve Studio 12).

Attach here on the image is I'm using the Face Refinement tool. The smoothing feature of the Facial refinement tool is just the same of the Spatial Noise Reduction feature but its mainly focused for the subject's face.

I pushed it to the extreme and I'm noticing this weird macro blocks on the face.

Abdelrahman Magdy wrote:4) (WINDOWS & LINUX) Selected audio tracks doesn't seem to be recognized. To explain, let's say I have 2 video tracks and 2 audio tracks, and I need to delete specific part of everything on all of them. When I add in and out points around the part I want to delete and hit the 'Delete' or 'Backspace' buttons, it deletes everything on Video 1, Video 2, and Audio 1, but leaves Audio 2 untouched, although all the tracks are selected.

Ok. Couple more grabs related to this one. For some reason it appears as if Resolve doesn't even recognize any audio tracks after Audio 1. I will explain these bugs using a series of screenshots.

As a workaround for being unable to delete parts of all tracks using just in and out points I select the clips on all tracks that I would like to delete

Cuts made on all tracks by selecting all the clips and hitting Ctrl+B

resolve_bugs_01.png (50.93 KiB) Viewed 15614 times

When I select all the clips and press 'Delete' which is supposed to ripple delete all these clips, it works only on V1, V2, and A1. It deletes the clips on A2 and A3, but it doesn't ripple them

Hitting 'Delete' only ripples clips on V1, V2 and A1

resolve_bugs_02.png (39.45 KiB) Viewed 15614 times

A similar thing happens when trying to razor clips on the selected tracks using 'Ctrl+B'. Unless I select the clips, the razor works only on V1, V2 and A1, and ignores A2 and A3.

Even the timeline comparison shows clips on V1, V2, and A1 ignoring the other audio tracks, although both of the timelines compared have clips on A2 and A3.

- Edit: Undo list, is the undo list for the edit page, not the Fairlight page. The Color page has 'Undo list' greyed out, is it even supposed to be selectable in the Fairlight page, or will it have its own?

- 'Link Groups' feature is broken. I tried on a 8 track sequence, linking tracks 1 and 2 - track 2 disappears, ok fine. Link tracks 3 and 4, now track 5 disappears?! Starting again with 3 and 4, track 4 disappears as you'd expect but then linking 5 and 6 makes track 8 disappear... you get the idea, it doesn't work. Not only that, but once I've exited the dialog box, if I go back in, tracks that have disappeared do not return, I cannot unlink anything to make tracks appear back on the timeline. I had 4 submixes built in case that makes a difference, as stereo pairs (not that I can export that right now... )

Also, please see my updated bug lists that pertain to all versions of Resolve, they've disappeared off the front page pretty quick. I'd particularly like to see the ACEScc/cct clamping bug, the highlight modes insta-crash, and the right-click instant-select fixed.

Well I tried my first render today in Beta (3), and I kept running into the pthreadVC2.dll fault that has been plaguing me in Beta 3. No matter what I tried, Resolve would throw that error (at various times) during the render.

That file looked very familiar to me, so I google it and sure enough it's an open source files used in quite a few applications. (I've used it for my MQTT Mosquito application)

I have come across a bug in V14 Beta 3. NewblueFX Titler Pro is disabled in the edit page.When I load Resolve it says that OFX are disabled, I then re-enable them in the color page, at which point everything shows up in the colour page but when I switch back to the edit page, there are no OFX plugins anywhere.

Oh my god this version is riddled with bugs so much so that I want to revert to the previous version but I have projects from paid clients made with this beta.

AUDIO is still very messy to deal with.

I cannot archive and back up my project because of WAV files. No idea why. I remove the wave files 44khz 16 bit from the project and it backs up fine. When I look at the new backed up folder I notice that it took my wave files and split them up into pieces like _S001.wav _S002.wav etc.

I am completely unable to use Media Management to archive my projects which sucks because manually copying folders to a hard drive to back up forces me to keep tons of media that I didn't use in the project (more space).

Will someone please help me with this? Getting failed to export because of certain wav files. Possibly because of their length.

I have quiet a few other bugs and crashes I can report but this is the one I really need help with.

Paul Fisher wrote:Oh my god this version is riddled with bugs so much so that I want to revert to the previous version but I have projects from paid clients made with this beta.

AUDIO is still very messy to deal with.

I cannot archive and back up my project because of WAV files. No idea why. I remove the wave files 44khz 16 bit from the project and it backs up fine. When I look at the new backed up folder I notice that it took my wave files and split them up into pieces like _S001.wav _S002.wav etc.

I am completely unable to use Media Management to archive my projects which sucks because manually copying folders to a hard drive to back up forces me to keep tons of media that I didn't use in the project (more space).

Will someone please help me with this? Getting failed to export because of certain wav files. Possibly because of their length.

I have quiet a few other bugs and crashes I can report but this is the one I really need help with.

For your sanity: Your best bet is to STOP using 14 for production projects. The deeper you dig in the more pain you will suffer. Bite the bullet and recreate the project(s) in 12.5.5.

Improvement of 14: You need to get sample projects with the logs that contain the errors over to the support team ASAP. I've been sending all my 'stuff' to @Rohit Singhal