Trim Bug in Beta v15 Final

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

Tony Hailstone

  • Posts: 85
  • Joined: Sat Dec 16, 2017 2:34 pm

Trim Bug in Beta v15 Final

PostMon Jul 23, 2018 11:09 am

I've come across a bug whilst using ripple trim commands that then impact playback performance.

The issue appears to be when making some type of cuts, the next clip in the timeline has the audio thrown out of alignment by a few frames (even though all tracks set to move together) and then becomes unplayable in real-time. For example, I'm editing in 25p and when this clip issue occurs, playback will drop to about 2-3 frames per second for the next clip in the timeline, then will resume just fine for the clip after.

It only affects the clip after the edit was made so if it was simply a rolling edit problem you would expect all clips on that track to be affected which is not the case.

To replicate the fault, I have assigned keyboard shortcuts to ripple start & end to playhead. It seems to be when using the "end to playhead" trim whilst scrubbing (i.e. holding down the left mouse button on the playhead) that's when the clips will be trimmed incorrectly (audio cut will not match video cut for the next clip, not current clip). I'm using 4k 10 bit H265 HEVC footage from a GH5 - I've not tried this on other footage yet. Playback has to be stopped for the edit to be made properly.

Please see snapshot of what this looks like. Manually sliding the audio/video back into alignment does not fix the problem. The clip has to be deleted and brought back in from the Media panel.

Hopefully Blackmagic can fix this.
Attachments
Davinci Resolve 15 Bug.jpg
Screenshot Trim Bug
Davinci Resolve 15 Bug.jpg (143.53 KiB) Viewed 621 times
Last edited by Tony Hailstone on Sun Sep 02, 2018 9:14 am, edited 1 time in total.
System: 16 core (24 thread) Intel i9 13900K, 64GB Ram DDR5 3200, M.2 NVME System Drive, M2. NVME Project Drive, RTX 4090
Offline

Sam Steti

  • Posts: 3168
  • Joined: Tue Jun 17, 2014 7:29 am
  • Location: France

Re: Trim Bug in Beta 6

PostTue Jul 24, 2018 8:42 am

I saw this kind of thing recently, in trim mode too, but didn't write about it because I was too busy and also unable to reproduce it... However I don't remember any obligation to bring it back from the pool to fix it.
*MacMini M1 16 Go - Sonoma - Ext nvme SSDs on TB3 - 14 To HD in 2 x 4 disks USB3 towers
*Legacy MacPro 8core Xeons, 32 Go ram, 2 x gtx 980 ti, 3SSDs including RAID
*Resolve Studio everywhere, Fusion Studio too
*https://www.buymeacoffee.com/videorhin
Offline

Tony Hailstone

  • Posts: 85
  • Joined: Sat Dec 16, 2017 2:34 pm

Re: Trim Bug in Beta 6

PostSun Sep 02, 2018 9:14 am

I see the trim bug is back in the final version of Resolve 15. Any chance of a permanent fix?
System: 16 core (24 thread) Intel i9 13900K, 64GB Ram DDR5 3200, M.2 NVME System Drive, M2. NVME Project Drive, RTX 4090

Return to DaVinci Resolve

Who is online

Users browsing this forum: Google [Bot], Steve Alexander and 372 guests