Page 1 of 1

Trims with Speed Ed in Cut Page not rippling Timeline

PostPosted: Sat Jan 02, 2021 8:07 pm
by Stan Willis
After working on a project for several hours in DR17 I am getting strange problems. Using the Speed Ed in the cut page, the timeline no longer ripples when I use the trim in and out keys. Instead I get a space where the audio is gone and the video space is a slightly lighter grey and it is selectable but I am unable to delete this space. If I right click it with the mouse, I don't get anything (no menu). If the playhead is in this space, then pressing delete takes the playhead to the beginning of the space.
There is only one camera and the clips are arranged on the timeline in the order shot, yet if I look in the sinc bin, the clips at the start have somehow got assigned to 9 cameras. This happens for the first 18 or so clips. After this the sinc bin is mostly empty but on some clips, these same clips reappear with the same camera assignments. In the inspector on the Media page none of the clip have any info in the Camera field. Any suggestions? It may not be a bug as it's quite possible that I have inadvertently pressed some random key on the Speed Ed or my computer keyboard.

Re: Trims with Speed Ed in Cut Page not rippling Timeline

PostPosted: Sun Jan 03, 2021 11:22 am
by bgks@bmd
Using the Speed Ed in the cut page, the timeline no longer ripples when I use the trim in and out keys.


Never, or depending on further circumstances, such as an underlying audio track?

1.1) Open the Lesson 02 project from the Resolve 16 Beginner's Guide support files.

1.2) Import the audio file from the Lesson 02 directory and drag it into the timeline → Track A1, your timeline looks like (subclip to be cut out is under the ^).
Code: Select all
 2:    BBBBB|BB|      ^         BBB|B
 1: AAAAAAAAAAA|AAAA|AAA|AAA|AAAAAAAAAA|AAAAAAA|AAAAAAAA|AAAAAAA
A1: A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1


1.3) Lock the A1-track.

1.4) Split the 2nd clip in track 1 into three parts.

1.5) Select the middle one.

[this corresponds to Step 7 in subsection Fixing small jump cuts of section Switching transitions of Lesson 2 Adding Effects and Publishing in the Cut Page of The Beginner’s Guide to DaVinci Resolve 16, but works not like documented there, while the Release Notes to 17b not state anything to Ripple Delete (except for the meaning of RIPL DEL key)]

A1) On the Cut page in track 1 of the timeline:
  • Menu Edit.Ripple Delete [non greyed out] → leaves a gap [bug]
  • Menu Edit.Delete Selected → leaves a gap [?]
  • Hit key 'Backspace' on the keyboard → leaves a gap [?]
  • Hit key 'Delete' on the keyboard → leaves a gap [bug]
  • Hit key 'Shift+Backspace' on the keyboard → leaves a gap [bug].

B) On the Edit page in track 1 of the timeline:
  • Menu Edit.Ripple Delete [non greyed out] → Ripples the rest of the timeline [✔]
  • Menu Edit.Delete Selected → leaves a gap [?]
  • Hit key 'Backspace' on the keyboard → leaves a gap [?]
  • Hit key 'Delete' on the keyboard → Ripples the rest of the timeline [✔]
  • Hit key 'Shift+Backspace' on the keyboard → Ripples the rest of the timeline [✔]

2.1) Unlock the audio track A1 and delete the audio clip (or trim it to an earlier out point than the clip to be deleted).

A2) On the Cut page in track 1 of the timeline:
  • Menu Edit.Ripple Delete [non greyed out] → Ripples the rest of the timeline [✔]
  • Menu Edit.Delete Selected → Ripples the rest of the timeline [?]
  • Hit key 'Backspace' on the keyboard → Ripples the rest of the timeline [?]
  • Hit key 'Delete' on the keyboard → Ripples the rest of the timeline [✔]
  • Hit key 'Shift+Backspace' on the keyboard → Ripples the rest of the timeline [✔]

Re: Trims with Speed Ed in Cut Page not rippling Timeline

PostPosted: Thu Jan 07, 2021 1:50 pm
by Steven Williams
That got me, too:

To ripple In/OUT in cut page without leaving gaps use the Ripple Start/End to Playhead command

cheers

trim.png
trim.png (32.19 KiB) Viewed 977 times

Re: Trims with Speed Ed in Cut Page not rippling Timeline

PostPosted: Thu Jan 07, 2021 8:50 pm
by Stan Willis
Thanks bgks@bmd for your systematic examination of the problem. Lookis like I was dealing with a bug.