Resolve 14 bugs - Edit page

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

Tom Early

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

Resolve 14 bugs - Edit page

PostSat Jul 23, 2016 7:02 pm

I've compiled a list of bugs I've found in Resolve, some minor, others not so much. The list began in V12 and will be updated periodically. It's rather long so I've broken it down into sections. System specs are as follows:

Mac Pro 2013, 2xD700, 64GB RAM, 3.5GHz 6-Core Intel Xeon E5, 2xEizo C230 display (1920x1080), OSX 10.10.5 Yosemite, Decklink 4K Extreme running Desktop video 10.5.4 (can't install 10.7 because apparently it breaks FCP7), Resolve Studio 12.5.5

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

Edit Page

1. [UPDATE - fixed] If you try and add a transition using a keyboard shortcut, but your default transition duration is longer than the duration of the clip, then no transition will be added at all.

2. If you have a wipe transition and select a coloured border, then clicking the ‘feather’ checkbox will get rid of the colour.

3. Text generator. If you have text formatted as small caps, then if a given line of text does not contain either a space or letter entered as a capital, then the letters will be ridiculously tiny. If you then add a space, or capital letter (i.e. using shift or caps lock) the entire line of text will now be at the normal size.

4. [UPDATE - fine in 14b3 on MBP, probably a desktop video issue in 12.5 on MP2013] Slow motion playback with either jk or kl results in audio intermittently being played back and then silent. In Color page, there is no audio on slow motion playback. (dtv 10.5.4)

5. [UPDATE - fixed] Dynamic trimming with cmd-j/l will ignore ‘Bypass All Grades’ selection on Color page

6. When sliding a clip or group of clips, only one clip can be slid over, including gap clips. To slide of more you must re-select the clip(s) you want to slide.

7. Edit index – ‘show all’ doesn’t show markers

8. [UPDATE - fixed] Ganging the viewers disables transport controls in the source monitor

9. Safe Area markers do not output to an external monitor from the Edit page (but do from the Color page)

10. View menu – Show Gray Background In Viewers – toggle doesn’t update the background until the playhead is moved. It updates straight away if this option is selected via project settings (as in, as soon as you click on ‘save’). This bug also exists in the Color page.

11. The Source viewer will still show applied grades if a Timeline is loaded when Bypass All Grades is selected

12. If you try and add a transition between 2 clips using the keyboard shortcut but the handles are not enough to make the transition last as long as the ‘Standard transition duration’ listed in the Editing settings, then the ‘insufficient handles’ dialog will come up i.e. you won’t be able to add a transition using the keyboard shortcut unless the clip handles available allow it. Dragging the transition from the Effects Library bin needs no such minimum threshold.

13. If you load a media pool clip into the source viewer, then double click on a timeline clip to bring it into the source viewer, then hit the overwrite button, then the media pool clip will be edited into the timeline even though it is no longer selected

14. Clip markers don’t show if you have Timeline View set to ‘no thumbnail’ (i.e. reduced mode) and video track height is set too low. There should be a smaller marker display introduced for such views.

15. [UPDATE - fixed] Select Workspace - Audio mixer in edit page, then click on the icon to get rid of it. Audio Mixer is still ticked in the Workspace menu.

16. [UPDATE - intentional] Edit index – show through edits only – also shows the edit previous to the first through edit (intentional?)

17. [UPDATE - irrelevant now that Swap Edits no longer exist for some reason] Click a clip to select it in lieu of cmd-option dragging to swap insert with adjacent clips. Cmd-option clicking and dragging won’t do anything (previously it deselected the clip in v12). This doesn’t happen when cmd-shift clicking in order to do a normal swap edit. In other words, in order to do a swap insert, you must not have any clips selected first.

18. Multicam editing – default is blade tool when hovering over multicam angles in source window, option click for switching without a cut. But the icon doesn’t update until you move or click the mouse again after pressing/releasing option key.

19. [UPDATE - fixed] Offline clips in the timeline appear with their normal clip colour when zoomed out past a certain point – they must be sufficiently short relative to the overall duration of the timeline. But there’s no reason for them to be coloured still!

20. [UPDATE - fixed] If you have a sequence where clips are online but then subsequently go offline, the UI still shows the clips in blue. Thumbnails will have the media offline indicator, but this is no good if timeline view is set to reduced mode! (and it’s no good anyway). Timeline clips will only be in red if there is no corresponding clip in the Media Pool i.e. if they are ‘unlinked’. If this is the way it’s supposed to be then it’s REALLY unhelpful!

21. If you have a clip that is online, and then go into the finder to move it somewhere else such that it will become offline in Resolve, then Resolve will be confused as to whether or not it is online or offline. Somehow it will manage to play some picture and audio, intermittently flicking to the ‘media offline’ indicator, even though no caching is enabled. How is it doing this? Another time it played the clip back flawlessly. Trying to reveal the clip in the finder did nothing. Quitting and re-opening correctly shows the clip as being totally offline.

22. [UPDATE - probably fine] Take selector – ripple is off by default. If you add a take that’s longer, then select it and close without rippling, then the additional media is no longer available if you reopen the take selector and enable ripple. Can still be trimmed back in when out of the take selector though.

23. [UPDATE - fixed] Using keyboard shortcuts to edit multiple clips into the timeline only results in the first selected clip being edited.

24. When dragging edits points, the HUD never says where the 0 point is, it’s always at best + or – 1 frame, so you can’t tell where you were

25. Using ‘Select Clips Forward/Backward On This Track’ will select clips on the current video destination selection. Why?? Why is it not dependent on lowest track auto-select instead??

26. [UPDATE - probably fine] If you link multiple video and audio clips together, and then option-click on any one of them and move it out of sync, there’s something wrong in the way that ‘out of sync’ indicators appear. If you have clips stacked, then indicators only appear on all clips if you move the lower-left-most video clip. If they are on the same layer, then indicators only appear on all clips if you move the left-most clip. Otherwise the indicators will only appear on 2 video clips, and no audio clips.

27. [**UPDATE - fixed in 12.5.1**] If in dual screen layout with full screen timeline enabled, then pressing e.g. +10 on the number pad does nothing, regardless of whether or not a clip is selected.

28. [UPDATE - fixed] Editing marker durations – you can’t just type ‘5.’ (as in, 5 followed by a full-stop) for 5 seconds, or ‘500’, it must be ‘00000500’, or else you must click on the specific part of the timecode you want to change

29. [UPDATE - does not apply to reduced timeline view, probably reasonable as is] Transitions do not show up when zoomed out beyond a certain point

30. [**UPDATE - fixed in 12.5.1**] ‘Switch To Timeline After Edit’ doesn’t work if you are in dual screen layout with Full Screen Timeline turned on

31. [UPDATE - fixed in v14 (last point only applies still for clip colours assigned in the timeline not at bin level)] Media pool clip color settings don’t carry over into timelines for 3d clips. They can only be assigned color (and show it) when set via the timeline instance of each clip. Furthermore, if you replace a clip in a timeline with a 3d clip, the 3d clip will take on the same clip color as the clip you replaced.

32. [UPDATE - fixed] This one may be just a problem with XMLs, but if you import an XML (from FCP7) that has 2 cross dissolve next to each other, then it will be brought in as one big cross dissolve between 2 clips instead of 2 fades to black.
Last edited by Tom Early on Sat Oct 12, 2019 1:08 pm, edited 24 times in total.
MBP2021 M1 Max 64GB, macOS 14.4, Resolve Studio 18.6.6 build 7
Output: UltraStudio 4K Mini, Desktop Video 12.7
Offline

Tom Early

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

Re: Resolve 12.5 bugs - Edit page

PostMon Jul 25, 2016 6:45 pm

33. In Project Settings, set Timeline Format to 2048x1556 Full Aperture, and Pixel aspect ratio to Cinemascope. Make sure that 'Resize image in viewer for correct aspect ratio' is ticked in UI settings [I don't know where this is in v16 or if it even still exists]. The image will be stretched twice as much vertically in the Edit page as it is in the Color page - this affects all viewers AND output monitors (i.e. For Cinemascope projects where individual files have their PAR set to Cinemascope, they will display normalised in the Color and Deliver pages but natively in the edit page. Incidentally, it will also appear natively in the media page, but then this is to be expected as it's not in a timeline yet).
Last edited by Tom Early on Sat Oct 12, 2019 1:15 pm, edited 1 time in total.
MBP2021 M1 Max 64GB, macOS 14.4, Resolve Studio 18.6.6 build 7
Output: UltraStudio 4K Mini, Desktop Video 12.7
Offline
User avatar

Jack Swart

  • Posts: 769
  • Joined: Fri Aug 15, 2014 8:09 pm
  • Location: Sydney, Australia

Re: Resolve 12.5 bugs - Edit page

PostMon Jul 25, 2016 11:37 pm

34.

EDL output does not have any audio edits despite the timeline having edits on A1.
DR Studio 18.6.3 b19, OS 13.2.1
2023 Mac Studio M1 Ultra, 20 core CPU, 48 core GPU, 128 GB ram
BM 3G ultra studio, 12TB SSDs in raid 0, 16TB HDD backup, 56TB archive server.
Tangent Elements panel, TV logic XVW-245W
Offline

Tom Early

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

Re: Resolve 12.5.1 bugs - Edit page

PostFri Aug 26, 2016 8:08 pm

A few more...

35. If you retime a clip and the Retime Process is set to either Frame Blend or Optical Flow, then any part of the clip which is running at 100% speed (by means of keyframes or curves) will still show blended frames or motion artefacts, even though no speed change has occurred.

36. Turn on ‘Show Playhead Shadow’ and ‘Show Preview Marks’. Switch between single and dual screen view. Both are now disabled. Happens going either way.

37. [UPDATE - fixed] The Edge Wipe transition border settings are ridiculous. They go up to 192000 pixels! Makes it impossible to use the slider as you’ll just go way too far.

38. Snapping is greyed out when in the master timeline. Keyboard shortcut works though.

39. [UPDATE - fixed] When in dual screen view / full screen timeline, double clicking on a clip in the timeline to load it in the source monitor does not switch focus to the source monitor, so any navigation inputs will still be applied to the timeline

40. Clip markers don’t ripple with retime curves (timeline markers do though)

41. [UPDATE - fixed] Text generator – the Stroke controls are buggy. It sometimes adds white border not black. Increase the size of the stroke with the default black color selected and an outline will appear, but turn the Stroke control off then back on and the outline will be white.

42. If your ‘Mixed frame rate format’ in the Conform Options area of the Project Settings is set to anything other than ‘Final Cut Pro 7’, then if you have a clip in the source monitor whose native frame rate does not match that of the timeline, and you try and do a replace edit, it will choose a different part of the source media to place into the timeline than you selected. Just how far off it will be depends on which Mixed frame rate format you selected and where in the source footage you are; if you pick ‘Resolve’ then it will typically just be 1 frame out, but choosing ‘None’ or ‘Final Cut Pro X’ will make it 1 frame out for every second into the source footage that you have chosen to edit from. The first frame (and probably the first second) of source footage will be fine, but after that there are problems! The only way around this, and this only works for ‘Resolve’ and ‘Final Cut Pro X’ options, is to go into the media pool, and under Clip Attributes you must adjust your video frame rate to match the timeline. However, if you do this then any audio in your source footage will be out of sync (getting progressively worse as you get further into the clip), and if you have increased the frame rate then the audio will be chopped off at the end of the clip and cannot be recovered without reverting back to the original video frame rate. Is it expected behaviour that the audio should behave this way? If your Mixed frame rate format is set to Final Cut Pro X and you change the video frame rate of a clip that’s already in the timeline, all that changes is the length and pitch of the audio (but not the audio clip), nothing about the video.

43. [UPDATE - fixed] If you click on a clip and type ‘+1.’ to move the clip along by 1 second, it will be moved by 1 second and 1 frame. Also happens for ‘+2.’, ‘+3.’ Etc. This does not happen if typing ‘+100’, ‘+200’ etc

44. [UPDATE - behaviour is (now) intended to select clips, not edit points] If a clip is selected in the Edit Page, then pressing the up/down arrow in order to move the playhead to the previous/next edit point will bypass the selected clip

45. If I hover over marker text with my mouse it disappears in less than a second. If someone’s written anything I have to open it if I want to read it.

46. [UPDATE - see below] Create a 1-frame text clip and make it a compound clip. If the next clip in the timeline is closer than the duration of the default still duration, the compound clip will be removed from the timeline. Furthermore, when you edit it back in from the bin, the text will sometimes no longer be visible.

47. [UPDATE - possibly intentional, since colours assigned in the timeline do not sync up with those assigned at bin level] A clip color assigned in the timeline will remain even if that clip is subject to a Replace operation with a clip of a different color

48. [UPDATE - fixed] When in Dual Screen layout with Full Screen Timeline turned on, you cannot switch focus between timeline and source viewers using either the keyboard shortcut (Q) or menu option without first clicking somewhere within the second screen

49. In the Change Clip Speed dialogue, the duration field reflects the entire duration of the source file, not the duration of the clip you are retiming
Last edited by Tom Early on Sat Oct 12, 2019 6:37 pm, edited 2 times in total.
MBP2021 M1 Max 64GB, macOS 14.4, Resolve Studio 18.6.6 build 7
Output: UltraStudio 4K Mini, Desktop Video 12.7
Offline

Tom Early

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

Re: Resolve 14 bugs - Edit page

PostSun May 28, 2017 7:49 pm

50. [UPDATE - fixed] Navigate to a part of the timeline such that the playhead is not visible (purely for the sake of seeing how annoying this behaviour can be). Select a clip and press alt/option-up arrow to move the clip up a track level, or alt/option-down arrow to move it down a track level. The timeline view jumps to the playhead instead of remaining with the edit you just made.

51. Make a speed change to a compound clip, and in the inspector, adjust the Retime Process. No matter which setting you choose, the actual Retime Process implemented will be that which is specified in the Project Settings/Editing tab.

52. Take any sequential 3 clips in a timeline, and for this example I’ll refer to them as clips x, y and z. Add an edit to clip y, so it becomes clips y1 and y2. Add a transition (for ease of illustration it should be a cross dissolve) to both of the edits either side of this one (i.e. 1 between clips x and y1, and one between clips y2 and z). Now click on this through edit you’ve made and press delete, to join clip y back together. The transition between clips x and y is intact, but any part of the transition between clip y and z that involved clip y will be deleted: i.e. if the transition ended on the edit it will be totally deleted, if it either centred or started on the edit it will now start on the edit but instead of a cross dissolve, it will cut to clip z which will now fade up from black. but the transition between y2 and z will be deleted.

53. Playhead shadow shows on top of the timeline sidebar (where track name etc is) when pre-playhead shadow is set to more than 0 frames.

54. [UPDATE - n/a] When cycling render cache modes via the menu or a keyboard shortcut, no message appears to say which mode you are currently on like it does when changing render cache modes in the Color page. Not really a problem when using the menu, but you’re in the dark when cycling using keyboard shortcuts.

55. If I import an XML and some clips cannot be found, it will say something like ‘12 of 14 clips not yet found’. In this example there were way more than 14 clips in the timeline, so what’s it on about? Another time there were 9 clips in the timeline and it said ‘2 of 11 clips not yet found’.

56. Slip audio one frame forwards/reverse is always greyed out. ?? Not in the media page though.

57. [UPDATE - fixed in v15] Position keyframes do not appear in the curve editor

58. [UPDATE - fixed in v15] If you click on a clip and type ‘+1.’ to move the clip along by 1 second, it will be moved by 1 second and 1 frame. Also happens for ‘+2.’, ‘+3.’ Etc. This does not happen if typing ‘+100’, ‘+200’ etc. This is because while typing, any keyboard shortcut applied to the ‘.’ key will still be active. Since the default shortcut is ‘Nudge One Frame Right’, when you type in ‘+1.’ and then hit Enter, the clip will first be moved 1 frame by the Nudge command, and then one second by the ‘+1.’ command. (Likewise, if you use the ‘,’ key to enter ’00’, then clips will only be moved by one frame less than intended for a ‘+’ command, or one frame more for a ‘-‘ command, since they are being nudged one frame left first).

59. Any clip that is 1 frame long before being made into a compound clip, will be assumed to be a still image and the compound clip will then be automatically retimed to the default still duration, as specified in Project Settings. If the contents of the compound clip is a generator and the next clip in the timeline is closer than the duration of the default still duration, the compound clip will be removed from the timeline. Furthermore, if this compound clip consists of text (for example a 2-pip for theatrical trailer deliverables), when you edit it back in from the bin, the text will sometimes no longer be visible.

60. [UPDATE - n/a] Related to a previous bug report - highlight all clips in the timeline. Now, pressing up/down to move between edit points will do nothing

61. [UPDATE - fixed in v14] Add a timeline marker and increase its duration beyond 1 frame. Make sure snapping is turned on. Now, drag the handles of the marker to the playhead. You can drag the ‘in’ point of the marker such that it snaps to the playhead, but if you drag the ‘out’ point then it will not drag to the playhead, it will snap to 1 frame either side.

62. Ripple deleting - there’s a risk of deleting clips above the current clip depending on the layout of clips on various tracks that come after the deleted clip. For example, assume you have 3 clips, let’s call them a, b, and c, with clips a and b 5 seconds long, and clip c 1 second long. Place clip a on track V1 starting at 0, and clip b on V2 starting at 6 seconds. Now place clip c on V2, starting at 3 seconds. Now, if you ripple delete clip a, then clip c will also be deleted (overwritten). No other major NLE treats ripple deleting in this way.
Last edited by Tom Early on Sat Oct 12, 2019 6:55 pm, edited 6 times in total.
MBP2021 M1 Max 64GB, macOS 14.4, Resolve Studio 18.6.6 build 7
Output: UltraStudio 4K Mini, Desktop Video 12.7
Offline
User avatar

Marc Wielage

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

Re: Resolve 14 bugs - Edit page

PostMon May 29, 2017 1:09 am

This is a great list, Tom.

One of your comments:

9. Safe Area markers do not output to an external monitor from the Edit page (but do from the Color page)

I believe this has been a problem for a long time. To me, the moment the Safe Action reticle is selected, it should be up in ALL modes, 100% of the time, period. It absolutely should not turn off in the Edit page.

Also: I don't use Resolve's internal scopes, but I think the scopes SHOULD be available in the Edit page for cases where you're setting specific levels on font colors and background colors. Having to switch back and forth to the Color page for this is a huge pain in the ass.

The Titling section of the Edit page in general is a big weakness, in my opinion. (On the other hand, Avid users have been complaining for years about how lousy the titling is in that NLE.)
marc wielage, csi • VP/color & workflow • chroma | hollywood
Offline

Nicolas Guillou

  • Posts: 32
  • Joined: Tue Dec 30, 2014 10:56 pm
  • Location: France

Re: Resolve 14 bugs - Edit page

PostTue May 30, 2017 2:24 pm

Hello,
14b1.. and b3
When you have a master timeline with inside another timelines : no sound when played.
Don't forget it, think it soon please :)
Thanks
DR S 18.1.4 b9 & Fusion 18.1.4 - WIN10Pro 19045 - i9 13900KS- 128Go RAID6 1xRTX 4090 Driver:531.79 DCH
Offline
User avatar

Nick Lear

  • Posts: 116
  • Joined: Sat May 07, 2016 7:58 am

Re: Resolve 14 bugs - Edit page

PostSun Jun 11, 2017 10:28 am

14b3 Mac

I'm finding that ripple delete or cut etc is not working on the audio tracks at all even though auto select is on and the track is highlighted.

I just can't believe this could exist in Beta 3 - how could anybody edit anything? So perhaps it is just me
Win Pro 10, Threadripper 3960x, 128GB RAM, RTX 4080 16GB VRAM, Resolve Studio 18.5 b41
Offline

Deryk Eynon

  • Posts: 28
  • Joined: Sun Nov 22, 2015 2:51 am

Re: Resolve 14 bugs - Edit page

PostMon Jun 19, 2017 3:46 pm

I have also found one that I'm not sure if it is a bug or I have my settings wrong...

If I select a clip and want to set my in point, I hit the "I" key and the in-point skips ahead to roughly half-way down the clip! I'm running 14b4 and this is one of the most frustrating bugs I've ever found! I have to click the actual in icon under the preview window to get it to work? I've checked my project settings and all matches up, but it just doesn't work!

Let me know if I'm wrong on this one or if yours works correctly, but it is really frustrating on my end!

Thanks
Resolve 17.1., 2016 MBP 2.7 i7, 500GB SSD, 16GB memory, Intel HD 530, Radeon 580 eGPU
Offline

Tom Early

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

Re: Resolve 14 bugs - Edit page

PostMon Jun 19, 2017 7:41 pm

Deryk Eynon wrote:I have also found one that I'm not sure if it is a bug or I have my settings wrong...

If I select a clip and want to set my in point, I hit the "I" key and the in-point skips ahead to roughly half-way down the clip! I'm running 14b4 and this is one of the most frustrating bugs I've ever found! I have to click the actual in icon under the preview window to get it to work? I've checked my project settings and all matches up, but it just doesn't work!

Let me know if I'm wrong on this one or if yours works correctly, but it is really frustrating on my end!

Thanks


All works fine for me. Are you using the default mappings?
MBP2021 M1 Max 64GB, macOS 14.4, Resolve Studio 18.6.6 build 7
Output: UltraStudio 4K Mini, Desktop Video 12.7

Return to DaVinci Resolve

Who is online

Users browsing this forum: Google [Bot], MizxGaming, SteveMullen, Zach He and 156 guests