Tue, Apr 9
Wed, Apr 3
Not sure if it would fix the problem, it will help that the problem doesnt even occur. If you tracked with the movie out of sync those tracks will probably still be problematic. But yes, building the timecode first and then doing the tracking should avoid that particular issue.
So, just to be clear, I should be able to just build a timecode (the documentation says to try "Record Run" first), and that should fix the problem without needing to pre-process the input movie clip?
Whenever you track with a movie file rather than an image sequence you have to build either a proxy or just the timecode.
Otherwise it can get out of sync with lots of back and forth tracking etc.
I know it sucks, and I'd rather have that happen automatically in the background or so, but it is not a bug, as far as I know.
Tue, Apr 2
- Please always test with latest official daily builds: https://builder.blender.org/download/
- Provide .blend and movie files with steps to reproduce the issue
Mar 18 2019
Feb 26 2019
Lol, you're welcome :D
Thank you Sebastian! It's working fine now
I think this is because Filmic is now the default View Transform, which is why the footage has to be converted for display first. If you change the View Transform from "Filmic" to "Default", it should play fast again.
Jan 31 2019
Ok, this seems fine to me now.
Jan 30 2019
I have updated the diff. Loc and Affine don't use an icon anymore.
Here's the diff: https://developer.blender.org/D4284
I second Williams opinion - icons have their specific meanings and were designed for particular functions/commands . One must not use random icon for a function that has not any pictogram designed for it. It makes GUI messy and confusing. This applies especially to python addons...
This is fine with me.
Jan 26 2019
I would like to move forward with the tracking pies. There are probably some things that can be improved and added, but it would be nice if they could be implemented now. I have updated both space_clip.py and blender_default.py in order to have them not as separated addon and have the correct key mappings.
As discussed with @William Reynish (billreynish) a while ago the icons for Affine and Loc probably need their own icon...
Once the pies are implemented I would look into an updated Specials Menu ('W'). Maybe @Sean Kennedy (hype) has some suggestions for it?
And a Diff:
Jan 14 2019
Jan 9 2019
Seems like the original issue is fixed already (apparently by rBd3160f350de2)
Jan 4 2019
I can confirm, but not completely.
Dec 18 2018
Dec 14 2018
Dec 5 2018
Dec 4 2018
@Sergey Sharybin (sergey) might want to check on this?
ASAN output is P858
track->markers is garbled.
Will run through ASAN next
Just run a test with the "Default" Color Management. The fps was 11 to 13 fps. So the performance is better, but I don't think this is the main issue here.
Dec 3 2018
This sounds very much like an issue with colormanagement. In 2.80 the default view transform is Filmic. In order to display movie clips correctly the correct mapping has to be applied first. This happens during playback. So once the clip has been played back once, the movie was "converted" internally to the correct view transform. That's why playback is realtime the second time you play it.
You can also set View Transform in Color Management panel from "Filmic" to "Default". That should give you better playback performance right from the first play of the movie.
(Sidenote: "Default" is really not an adequate term anymore, since it isn't even the default setting! :)
I have tested this with a cache setting of 1024 MB. It prefetches a video (not the video from above), could not see any GUI freezings and the progress bar updates.
But the frame rate is low: around 4 to 9 fps. (I see this in a 3d view port in the left top corner of a camera view).
If I play the video (play button, not prefetching) the frame rate is also 4 to 9 fps. But the second time I play it, the part that was "played" plays now with 24 fps.
Just as info for others. To reproduce it in the file, you just have to click "Constraint to F-Curve" in the constraint now.
Here is it the blend file:
Please provide some .blend file that allows us to easily reproduce the issue.
@Sebastian Koenig (sebastian_k), did i get it correct:
My colleague just tested this on Windows10 with the most recent Blender 2.80 build.
While it does prefetch the footage, it does act a bit weird. The interface seems to freeze until the prefetching is done. Unlike in your case however the footage is in memory after prefetching is finished.
Even though the GUI is a bit unresponsive, we could still press the little X in the prefetching progress bar to cancel it. It works pretty much the same as on my Linux system. Our systems are quite good though (32GB, Hexacore). 4GB of system memory is far from ideal for motion tracking, so poor system performance might play a role in your case. Still, I can't really see a bug here.
However, responsiveness when caching movie files could definitely be improved. When prefetching image sequences the interface stays fully repsonsive here, and the way the progress bar is reporting the prefetching progress is more realtime and repsonive as well.
When 2.8 is more stable and there is a bit more time for polishing this might be something to look at, @Sergey Sharybin (sergey)?
That would be fine, although I use Detect Features more than I use the Track Setting as Default or Copy Track Settings.
Ah, good one. Maybe instead of Detect Features? This is not used so often...
This is very nice, seems to be intuitive.
Dec 2 2018
Dec 1 2018
Interesting. Would be nice if some other windows user could test this. At the very least I'll have my colleagues in the office test this on monday.
Ram 4096 MB. Set the value to 3072 MB (good thinking, btw). But still the same issue.
How much RAM do you have, and what's set in your User Preferences, in System>General>Memory Cache Limit? If you prefetch and watch your System's memory consumption, is your RAM filling up or not?
As described above I use Windows 7. It freezes for a while, then the GUI is responsive again. But the prefetch of the footage didn't happen at all.