A new version of Cineversity has been launched. This legacy site and its tutorials will remain accessible for a limited transition period

Visit the New Cineversity
   
 
3D pixel error and solve quality
Posted: 18 November 2018 07:49 AM   [ Ignore ]  
Total Posts:  9
Joined  2014-12-25

Hello,
Is there a way to evaluate the quality of the 3D camera solve with an indicator like pixel error? In other 3D tracking packages typically a 2D tracker position to projected 3D tracker position pixel error is shown per tracker or averaged for the solve to indicate the solve quality.

Regards,
Ihab

Profile
 
 
Posted: 18 November 2018 10:33 AM   [ Ignore ]   [ # 1 ]  
Administrator
Avatar
Total Posts:  12043
Joined  2011-03-04

Hi Ihab,

You can go to the Motion Tracker> Graph View and get a very precise idea about the quality.
Manual
https://help.maxon.net/us/#54623
Tutorial
https://www.cineversity.com/vidplaytut/motion_tracking_object_tracking_inside_cinema_4d_motion_tracker_graph_view

The number you mentioned is certainly a helpful indicator, if you have the same quality of footage for each shot. It is however, a value that measures the calculated model of the scene with the derivations of the accepted (i.e., not deleted) trackers features. Since foreground tracking features are more precise than background features, the comparison stops if the shots differ in this regard. Furthermore, we see more and more 8K productions and less HD source files these days, while the quality of 4K or just UHD footage has a wide variety of its own, i.e., heavily compressed (perhaps even stabilized, etc) or raw footage. Another difference is given with lenses (wide or long for example).
If then downsampled or in some cases even up-sampled footage needs to be compared, it is not simple to just put a factor to it, to be comparable. Hence, why I suggested to go with the 2D tracking error values, which seems to be the best place to evaluate and optimize the result for the 3D Solve. Missing the single error number seems to validate this idea. Besides, we see a change of that value over time, like in the little graph that Syntheyes has had introduces a while ago in the lower right corner.

Anyway: The right place to suggest this feature would be here, and if the developer see an advantage in it, it might be put on the to-do list. … and yes, while in other apps, this value gives me always a good feeling when it is low. But beware of talking it too seriously, to just get it down, might jeopardize the quality fo the camera path.
So, please voice your wish and perhaps others do so as well.
https://www.maxon.net/en-us/support/suggestions/

My best wishes

 Signature 

Dr. Sassi V. Sassmannshausen Ph.D.
Cinema 4D Mentor since 2004
Maxon Master Trainer, VES, DCS

Photography For C4D Artists: 200 Free Tutorials.
https://www.youtube.com/user/DrSassiLA/playlists

NEW:

NEW: Cineversity [CV4]

Profile
 
 
Posted: 19 November 2018 12:15 AM   [ Ignore ]   [ # 2 ]  
Total Posts:  9
Joined  2014-12-25

Thanks. Dr. Sassi, I really appreciate the information!

Profile
 
 
Posted: 26 November 2018 06:36 AM   [ Ignore ]   [ # 3 ]  
Administrator
Avatar
Total Posts:  12043
Joined  2011-03-04

You’re very welcome, ihabali.

Enjoy your exploration.

Cheers

 Signature 

Dr. Sassi V. Sassmannshausen Ph.D.
Cinema 4D Mentor since 2004
Maxon Master Trainer, VES, DCS

Photography For C4D Artists: 200 Free Tutorials.
https://www.youtube.com/user/DrSassiLA/playlists

NEW:

NEW: Cineversity [CV4]

Profile