Davinci Resolve Planar Tracker Not Tracking Entire Clip

  • Print view

Planar Tracker does not work

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

  • Message

ravirai

  • Posts: 134
  • Joined: Sun Jan 06, 2019 12:54 am
  • Real Name: Ravi Rai

PostSat Jan 23, 2021 12:39 am

I haven't used planar tracker since I updated to v17, it's been a long time since I last used it but anyway I tried using it now and when I click track to end, it just sits there doing nothing. And then when I try to click something else, like say "set" just to see if it is even doing anything, it says "wait till render completes" but isn't moving a single frame. Anyone else have this issue?

dirk-pel

  • Posts: 145
  • Joined: Wed Aug 29, 2018 7:37 am
  • Location: Karlsruhe, Germany, Dutch origin.
  • Real Name: dirk pel

PostSat Jan 23, 2021 10:08 am

I've the same problem. Tried everything but no possibility!
It worked before on 17.4, nothing changed on my PC.
Perhaps a bug.

Dirk PEL

Intel i7-8700K, 32 GByte, WIN10-Pro, GeForce GTX 1070, BM Intensity pro 4K, Eizo CS2420, Davinci Resolve 17.4 Studio, Micropanel, Speed Editor
16" Macbook Pro M1 MAX 32 GB, 1TB SSD

Earl Green

  • Posts: 78
  • Joined: Mon Apr 24, 2017 8:40 pm

PostSat Jan 23, 2021 2:25 pm

I don't use it often either, but I just tested based on this post. I tried several different settings (point, hybrid...transition, perspective... even luma, green) and in each case was able to do a successful track. I was using BRAW footage.

paule96

  • Posts: 1
  • Joined: Sat Jan 23, 2021 9:40 pm
  • Real Name: Paul Jeschke

PostSat Jan 23, 2021 9:47 pm

I have the same issue. Also trying with many different settings. (try each mode, change from GPU to CPU, change Motion Type, change Track-Channel)

The behavior is that in the console the "render starts" but never finished. I have a full AMD system. Maybe this is a hint for the bug:

Threadripper 3970X
Radeon Vega 64

ravirai

  • Posts: 134
  • Joined: Sun Jan 06, 2019 12:54 am
  • Real Name: Ravi Rai

PostSat Jan 23, 2021 10:37 pm

Earl Green wrote:I don't use it often either, but I just tested based on this post. I tried several different settings (point, hybrid...transition, perspective... even luma, green) and in each case was able to do a successful track. I was using BRAW footage.

Are you on Beta 7, Earl? I was also using BRAW footage.

Earl Green

  • Posts: 78
  • Joined: Mon Apr 24, 2017 8:40 pm

PostSun Jan 24, 2021 5:39 am

ravirai wrote:Are you on Beta 7, Earl? I was also using BRAW footage.

Yes

ravirai

  • Posts: 134
  • Joined: Sun Jan 06, 2019 12:54 am
  • Real Name: Ravi Rai

PostSun Jan 24, 2021 7:07 am

Earl Green wrote:

ravirai wrote:Are you on Beta 7, Earl? I was also using BRAW footage.

Yes

Okay, then I'm not exactly sure why you're not having this issue but I and Dirk are.

User avatar

dsol1980

  • Posts: 58
  • Joined: Thu Aug 01, 2019 9:25 pm
  • Real Name: Daniel Solberg

PostSun Jan 24, 2021 1:52 pm

Planar and normal tracker in fusion have been causing big havoc, but I only noticed it recently on a project that required it for almost every clip, so I cannot say if it's due to a beta or DR17 in general, or the NVidea drivers, or this latest windows update junk that came out shortly after the new year.
The program allows me to place the points in the areas I want to track, set the reference frame, and then when I track forward or backward it's a basic crash of the whole program in the end....
I was on h264 and 5 footage so it seems that it's not just one type of codec.
I think it was beta 6

logs

download/file.php?id=40464

And a project with a ton of fusion clips where this happens in the timeline called "telephone"
.drp can be found here:

https://www.dropbox.com/s/0f133psu55qig ... 0.drp?dl=0

PostMon Jan 25, 2021 10:41 am

Doesn't work here as well in beta 7

DaVinci Resolve Studio 16.2.6, Windows 10 2004, Intel i7 9700, 32 GB HyperX DDR4-3200, MSI MPG Z390 Gaming Plus, GTX 1080 ti 11GB, HDDs: SAMSUNG SSD SM841, WDC WD20EFRX-68EUZN0

PostMon Jan 25, 2021 12:17 pm

I've just done a 30 second facial track with the planar tracker in Beta 7, so it's definitely not broken for everyone.

One thing I did notice is that if you're working with a timeline clip, you still need to remember to manually set the starting/reference frame for the track, because otherwise it defaults to 0 which is usually not where the clip is in 'Resolve time' (for lack of a better word). That's something that's easy to overlook.

Did you guys remember to set it?

Sander de Regt

ShadowMaker SdR
The Netherlands

TYKHAN

  • Posts: 175
  • Joined: Fri Aug 05, 2016 3:44 pm
  • Real Name: Abdul Majeed

PostMon Jan 25, 2021 12:24 pm

Working for me with 264H files in beta7.

OS: WIN10 Pro 21H1 Build 19043.1288 64-bit ENG
BOARD: ASUS X99-E WS
CPU: Intel Xeon E5-1650 v3 3.5GHz
RAM: 4x 16 Kingston DDR4 2133MHz ECC
GPU: GeForce GTX 1080 Ti Driver v472.12
PSU: Corsair RM750w
DaVinci Resolve Studio 17.4.1 build 4

User avatar

dsol1980

  • Posts: 58
  • Joined: Thu Aug 01, 2019 9:25 pm
  • Real Name: Daniel Solberg

PostMon Jan 25, 2021 12:25 pm

It works for me too, when I start a new project ONLY for doing any type of tracking in fusion.

But whenever I have an existing project, with color grades and such, it just won't do it......

Earl Green

  • Posts: 78
  • Joined: Mon Apr 24, 2017 8:40 pm

PostMon Jan 25, 2021 2:48 pm

dsol1980 wrote:It works for me too, when I start a new project ONLY for doing any type of tracking in fusion.

But whenever I have an existing project, with color grades and such, it just won't do it......

Just tried again based on this post. Pulled up an old project (pre-version 17) and tested using a couple different options. This time it was H.264 footage. Was able to get successful tracks each time.

wfolta

  • Posts: 598
  • Joined: Fri May 15, 2020 1:12 pm
  • Real Name: Wayne Folta

PostMon Jan 25, 2021 3:16 pm

Just tried it on a small test project that was created under v17, on a clip with Color grading, and it tracks properly. This is on a Mac, so using AMD. I forget the footage codec, but it was recorded on an iPhone, if that matters.

Resolve Studio 17 latest, Fusion Studio 17 latest, macOS Big Sur latest, MacBook Pro 2020 64GB RAM and Radeon Pro 5600M 8GB VRAM

ravirai

  • Posts: 134
  • Joined: Sun Jan 06, 2019 12:54 am
  • Real Name: Ravi Rai

PostWed Jan 27, 2021 1:18 am

So it works for some people, doesn't work for others for some odd reason. That is weird. I tried again and I know I am not doing it wrong because this isn't the first time I am using the Planar Tracker.

User avatar

Lucas D.

  • Website
  • LinkedIn
  • Posts: 90
  • Joined: Wed Oct 10, 2018 8:31 am
  • Location: 2901 W. Alameda Ave, Burbank, CA 91505
  • Real Name: Lucas Druzynski

PostWed Jan 27, 2021 9:31 am

I tested the planar tracker on Prores footage and its fine.
There was a problem with 2D tracker on previous Beta version but its working now.

Microsoft Windows 10 Pro x64
Version 1909 / Build 18363.959
AMD Ryzen 7 1800X 8cores @ 3.6 GHz
NVIDIA GeForce GTX 1080ti
48.0 GB of RAM
Resolve Studio v17.3 Build_14

wfolta

  • Posts: 598
  • Joined: Fri May 15, 2020 1:12 pm
  • Real Name: Wayne Folta

PostWed Jan 27, 2021 2:45 pm

ravirai wrote:So it works for some people, doesn't work for others for some odd reason. That is weird. I tried again and I know I am not doing it wrong because this isn't the first time I am using the Planar Tracker.

Have you posted your system specs? Is it a Windows v. Mac thing? Or a Windows 9 v. Windows 10 thing? Or an AMD v . NVIDIA thing? It's conceivable it's a codec thing (which would be related to the above), but I think unlikely.

It's probably not random, we just need to bring together enough information about systems on which it works and on which it doesn't work to see the pattern.

Resolve Studio 17 latest, Fusion Studio 17 latest, macOS Big Sur latest, MacBook Pro 2020 64GB RAM and Radeon Pro 5600M 8GB VRAM

Berlin

  • Posts: 44
  • Joined: Sun Jul 19, 2020 11:09 pm
  • Real Name: Martin Lehmann

PostWed Jan 27, 2021 4:02 pm

For me the planar tracker didn't work either (wouldn't start tracking) in an existing project (Mac OS, latest beta of DR Studio). I then opened the clip in question in a new empty project and it did work. Tried it in the other project again and it still didn't work. So I rendered it in the new project and added the file to the other project.

Macbook Pro 16" i7 - DaVinci Resolve Studio 17, After Effects, Motion

User avatar

dsol1980

  • Posts: 58
  • Joined: Thu Aug 01, 2019 9:25 pm
  • Real Name: Daniel Solberg

PostWed Jan 27, 2021 4:08 pm

Berlin wrote:For me the planar tracker didn't work either (wouldn't start tracking) in an existing project (Mac OS, latest beta of DR Studio). I then opened the clip in question in a new empty project and it did work. Tried it in the other project again and it still didn't work. So I rendered it in the new project and added the file to the other project.

YES! same. Perhaps you can't run any fusion trackers in old projects that were originally created in earlier 17 betas. But if you create a new project for the sole purpose of tracking and copy the clip, voila....

wfolta

  • Posts: 598
  • Joined: Fri May 15, 2020 1:12 pm
  • Real Name: Wayne Folta

PostWed Jan 27, 2021 4:08 pm

Ooo, that's another good way to slice it: existing project versus new project.

Resolve Studio 17 latest, Fusion Studio 17 latest, macOS Big Sur latest, MacBook Pro 2020 64GB RAM and Radeon Pro 5600M 8GB VRAM

ravirai

  • Posts: 134
  • Joined: Sun Jan 06, 2019 12:54 am
  • Real Name: Ravi Rai

PostWed Jan 27, 2021 11:07 pm

wfolta wrote:Have you posted your system specs? Is it a Windows v. Mac thing? Or a Windows 9 v. Windows 10 thing? Or an AMD v . NVIDIA thing? It's conceivable it's a codec thing (which would be related to the above), but I think unlikely.

It's probably not random, we just need to bring together enough information about systems on which it works and on which it doesn't work to see the pattern.

I have NVIDIA Studio driver 460.89. PC I run on has Windows 10 20H2 Build 19042.746. CPU is i7 8700, with 32 GB DDR4 and an NVIDIA GTX 1070.

pkyhan

  • Posts: 1
  • Joined: Thu Jan 28, 2021 10:38 pm
  • Real Name: Patrick Kung-Yuan Han

PostThu Jan 28, 2021 10:44 pm

I am encountering the same issue with Beta 7. When I clicked on the track to end, the tracker only tracks for one frame and that was that. The project was created on Jan 17th so I guess it was created with Beta 6 instead of 7.

Actually I have just figured out what my issue was. The area I selected for tracking was probably too small. I selected a larger area and then it was able to work.

imbtan1105

  • Posts: 1
  • Joined: Tue Feb 23, 2021 6:05 am
  • Real Name: Ian Tan

PostTue Feb 23, 2021 6:18 am

Hello to everyone, this is my very first post and I don't know what I'm doing. My planar tracker seems to be glitching and I have no idea why.

I'm using Version 16.2.8.005

Here's a video:

https://drive.google.com/file/d/1vVUCKa ... sp=sharing

Thank you for anyone who might be of help

User avatar

Lucas D.

  • Website
  • LinkedIn
  • Posts: 90
  • Joined: Wed Oct 10, 2018 8:31 am
  • Location: 2901 W. Alameda Ave, Burbank, CA 91505
  • Real Name: Lucas Druzynski

PostThu Feb 25, 2021 4:25 am

Why are you using green channel for tracking ?
Leave it in default setting (LUMA).

Microsoft Windows 10 Pro x64
Version 1909 / Build 18363.959
AMD Ryzen 7 1800X 8cores @ 3.6 GHz
NVIDIA GeForce GTX 1080ti
48.0 GB of RAM
Resolve Studio v17.3 Build_14

PostThu Apr 29, 2021 10:32 am

I've got the same problem with the Planar tracker, using DaVinci Resolve 17.1.1., latest Windows and nVidia updates too.

What happens:
I put in the tracker node, make the shape I want to track, set the time hit the track button and nothing. The tracker doesn't track it just sits there.

Did anybody find any solution or just waited for a fix?

CPU- Xeon E3-1231 v3 4-cores,8-threads 3.40 Ghz | GPU- nVidia GeForce GTX 1070 8GB | RAM- 16 GB Corsair Vengence DDR3 1600 Mhz | Sound Card- Asus Xonar DG | Dell ULTRASHARP u2413 | EIZO FlexScan s2231w | AOC that doesn't matter

GreyCarl

  • Posts: 32
  • Joined: Wed Nov 25, 2020 10:58 pm
  • Real Name: Carl Edwards

PostThu Apr 29, 2021 6:15 pm

Just throwing in my 2 cents.

Having the same issue, oddly enough on a clip that I had already done a bunch of tracking on. I think I was successful in 17.1 but now it just sits in 17.1.1? Really annoying.

This is on mac, running Catalina.

StormeNet

  • Posts: 5
  • Joined: Sun Mar 17, 2019 11:55 pm
  • Real Name: Thomas Storme

PostTue May 11, 2021 7:00 am

TLDR: Disable all the color grading on the clip going into fusion.

I had the same issue today. Tracking on a clip didn't work in an existing project. The same clip in a new project could successfully track.

So I went back and could get it to work in the original project with these changes:
On the clip I want to track, I did object removal in the color tab. When I disabled the node with the object removal the tracking did work.

.. One of those typical DR bugs ... DR 17.1.1 Build 9

aimishboy

  • Posts: 1
  • Joined: Fri Nov 20, 2020 9:58 pm
  • Real Name: Nadav Bagim

PostSat May 29, 2021 3:53 pm

Ok, It didn't work when the clip was part of a fusion clip.
When I opened it in timeline and worked on the specific clip individually it worked.

georgekg

  • Posts: 117
  • Joined: Sat Sep 23, 2017 8:23 pm
  • Real Name: Aleksandar Djordjevic

PostFri Oct 01, 2021 3:50 pm

Bug still exists. I'm on a Win 10, DR v17.3.1 build 5 nVidia drivers 472.12 and it works OK when clip speed is 100% With any clip that has speed different than 100% it start to behave like it was mentioned in the first post - it doesn't move and it allows me to switch to another tab, but if I want to delete planar tracker node in the fusion tab I got the message that planar tracker is working.

User avatar

TheBloke

  • Posts: 1777
  • Joined: Sat Nov 02, 2019 11:49 pm
  • Real Name: Tom Jobbins

PostFri Oct 01, 2021 7:57 pm

georgekg wrote:Bug still exists. I'm on a Win 10, DR v17.3.1 build 5 nVidia drivers 472.12 and it works OK when clip speed is 100% With any clip that has speed different than 100% it start to behave like it was mentioned in the first post - it doesn't move and it allows me to switch to another tab, but if I want to delete planar tracker node in the fusion tab I got the message that planar tracker is working.

We diagnosed an issue the other day in another thread, where the problem is caused by trying to track in a Fusion Clip, where the source media (inside the Fusion Clip) has Optical Flow enabled on it, and some FPS adjustments are occurring (eg because of speed changes, or because of using different-FPS media.)

Might that be the same for you?

Here's the other thread:

viewtopic.php?f=21&t=146525

It may also happen when Color page Noise Reduction is involved. Basically, any temporal effects.

Resolve Studio 17.4.2 and Fusion Studio 17.4.2 on macOS 11.6.1

Hackintosh:: X299, Intel i9-10980XE, 128GB DDR4, AMD 6900XT 16GB
Monitors: 1 x 3840x2160 & 3 x 1920x1200
Disk: 2TB NVMe + 4TB RAID0 NVMe; NAS: 36TB RAID6
BMD Speed Editor


Return to DaVinci Resolve

Who is online

Users browsing this forum: crtkecnkl659, Google [Bot], John Richard, John_W, jonathanljs, Multi4G, panos_mts, tclark513, Thomas Dove and 77 guests

Davinci Resolve Planar Tracker Not Tracking Entire Clip

Source: https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=132474

0 Response to "Davinci Resolve Planar Tracker Not Tracking Entire Clip"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel