Planar Tracker does not work

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?

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

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.

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

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.

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

Yes

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.

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

Doesn't work here as well in beta 7

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?

Working for me with 264H files in beta7.

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......

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.

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.

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.

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.

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.

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.

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....

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

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.

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.

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

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

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?

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.

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

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.

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.

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.

I am trying to remove a strand of hair with the patch replacer.
Somehow when i try to track with the pointtracker in the color page the tracking points do not show.
And cannot find an option to turn on/off visibility.

Any idea's?

DV 17.4.2

Hi people,
So I got the same problem just suddenly. I've been doing effects using planar tracker for the whole day, everything has been just fine and here is the next clip I'm trying to apply Planar Tracker it just doesn't work. The whole situation is the same as all people wrote in here it just doesn't move when you press Track. Any ideas why?
*Update
I noticed that dark lit scene/shot/image impossible to track with the planar tracker, so I made it brighter, applied tracker and then made it darker back. Strange...

If I take 2 or more clips from the Edit timeline and then combine then into a Fusion composition, PLANAR TRACKER IS DEAD IN WATER in Fusion. I have tried everything possible but when you try to use planar tracker from a new Fusion composition, it just sits there until the program locks up/crashes.

Annoying!

Erik

Just updated to 17.4.5.
In Fusion Page planar tracker stopped working !
No Errors in Console...
When hitting "Track to Start" or "Track to End" it just renders one frame...

After tracking when I hit the 'Create Planar Transform', there's simply NO reaction.

No new node is generated ...

Frustration!

Note:I am using Davinci Resolve Studio 17.4.5

After tracking when I hit the 'Create Planar Transform', there's simply NO reaction.

Planar Tracker => Settings => Use GPU set to Disable, works for me

After struggling with this for hours, it occurred to me that I should check online. Never realized that something as basic as this could be dead in the water. Its like revving the accelerator when the gear is in neutral or clutch is engaged ... the tracker just doesn't move!

I am on the latest version. Is BMD listening?

Same Issue on v 18.0.1 Build 3

Same project, same source clip. Worked perfectly on first try.

Second clip, tracker dead. I even tried rendering out the clip first, importing it to a new timeline.

Here's where it gets interesting. I opened a new project and imported the rendered-in-place clip. Went into fusion and did a quick test and it tracked! Great, so I deleted the quick mask and created a better one. Dead.

Update:

I have found that messing with the "Use GPU" parameter in the "Settings" tab of the Planar Tracking node seems to alleviate the problem. I tried setting it to "Disable" as axlpixs mentioned above, but that didn't seem to work. I then switched it to "Enable" and it started working. Afterwards (at least in the same project) the tracker worked fine even if I deleted the existing node and used a new tracker (which previously activated the bug). I didn't need to adjust the GPU setting on the new node (default is Auto).

So it would seem playing with this setting knocks the rust off in some way.

So my issue is that I have set the GPU mode to Disabled and the tracker still doesn't work. I tell it to track to end, and it does nothing. I get a message at the bottom saying "Frames RenderedL2.0, Average: 24.30 frames/sec, etc." Any help would be greatly appreciated. Thanks.

doesn't work for me too. when i click "track forward" it moves 1 frame and that's it. Resolve 18.0.1 build 3

fusion simply sucks. there was no single case when i opened it and it did what i want. the premise of everything in one software is very tempting, but it is just broken. i just want it to work, but it doesn't. alas. hi, after effects.

Try to use Fusion standalone.

I'd like to add, I just had the same problem and had to export the problem clip, create the Fusion Comp in a new project and bring that back into the original project. I've been using the Planar tracker/Transform with no issue until tonight.
MacMini, 64GB memory, AMD Radeon RX 580.
Resolve Studio 18.08 Build 14

Yess! I have the exact same problem! If I track the clip, it is tracking the clip at normal speed, so my tracking is wrong, because I slowed down my clip to 25% and use optical flow. So, to resolve this issue, I created a fusion or compound clip and tried to track it from there so it would match the slowed down version of the clip with the tracker... and then nothing. Planar Tracker or Tracker doesn't work because of that. Anyone know how to make it work please I have a bunch of clip that I need to do that

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.

In fusion I was getting a message that the tracker render failed. Noticed the following: When I did control-space and typed in tracker, then hit "add", the tracker appeared *after* mediaOut. Detached it and moved it after mediaIn and it failed consistently.
Resorted to witchcraft and this is what worked for me:
1. Deleted the MediaIn node.
2. Dragged the desired clip from the media pool and connected the resulting node to mediaOut
3. Did the control-space tracker search and clicked on add. This resulted in the tracker node inserting after MediaIn and the tracker worked.
I have utterly no idea why this worked, but it did.

In fusion I was getting a message that the tracker render failed. Noticed the following: When I did control-space and typed in tracker, then hit "add", the tracker appeared *after* mediaOut. Detached it and moved it after mediaIn and it failed consistently.
Resorted to witchcraft and this is what worked for me:
1. Deleted the MediaIn node.
2. Dragged the desired clip from the media pool and connected the resulting node to mediaOut
3. Did the control-space tracker search and clicked on add. This resulted in the tracker node inserting after MediaIn and the tracker worked.
I have utterly no idea why this worked, but it did.

This witchcraft worked for me too! Thanks for saving my night. I'm using 18.5B Build 25. Bug @dev team.

In fusion I was getting a message that the tracker render failed. Noticed the following: When I did control-space and typed in tracker, then hit "add", the tracker appeared *after* mediaOut. Detached it and moved it after mediaIn and it failed consistently.
Resorted to witchcraft and this is what worked for me:
1. Deleted the MediaIn node.
2. Dragged the desired clip from the media pool and connected the resulting node to mediaOut
3. Did the control-space tracker search and clicked on add. This resulted in the tracker node inserting after MediaIn and the tracker worked.
I have utterly no idea why this worked, but it did.

This witchcraft worked for me too! Thanks for saving my night. I'm using 18.5B Build 25. Bug @dev team.

This worked for me too! Definitely a bug!

I am having this problem with the Fusion Planar Tracker as well. It is a post production stopper. Any idea if BMD is aware?

Here is my updated signature.

18.5.1
I have been using the planar tracker this morning and it worked fine for me.
W10
RTX 2080 Ti