Closed david-cattermole closed 2 years ago
The following files have been provided by a user as example files we can use to ensure the files are importing correctly: pftrack_hollywoodcameraworks_headtracking.txt pftrack_corners_v002.txt
The "headtracking" 2D tracks were tracked on the "head tracking" footage from Hollywood Camera Work: https://www.hollywoodcamerawork.com/tracking-plates.html
The files were resized to 1920x1080 (square pixels - 1.777 aspect ratio, to avoid using the 1.5 pixel aspect ratio for the HDV format as used on Hollywood Camera Work pixel aspect ratio. PFTrack 2D Tracks are resolution dependent. So this information is critical to re-producing correctly aligned markers.
I have added an importer for PFTrack .2dt/.txt files, from PFTrack5 up to modern-day PFTrack releases.
This has been released in the latest v0.3.16 version and can be downloaded and used now.
Closing for now... if there are issues I'll re-open.
Just to add... PFTrack supports both ".2dt" (PFTrack 4 and 5) and ".txt" ("node based" PFTrack) file extensions which makes things slightly confusing since 3DEqualizer also uses ".txt". The Load Markers tool will now automatically detect the correct format.
Naturally, since the PFTrack format doesn't support any "fancy" features, like the ".uv" format does, don't expect any "overscan", or distortion/undistortion features to work.
Feature
Users wish to import "2D trackers" ASCII files from PFTrack, such as exported from the User Tracks node in PFTrack: https://support-thepixelfarm.co.uk/online-documentation/docs/pftrack_node_user_track.html
Expected behavior: Load Markers UI will be able to read, parse and create Markers for files exported by PFTrack.
Usage Steps
Software Versions