<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone, <div class=""><br class=""></div><div class="">[It is reported by Sergey that this mail hasn’t been received. So just ignore it if you have already received it :) Sorry for the spam.]</div><div class=""><br class=""></div><div class="">This is weekly report #7 of the multi-view reconstruction project. We have achieved a substantial progress this week. A multi-view camera solver with basic functions is almost ready! Here is the detailed things I have done.</div><div class=""><br class=""></div><div class="">What I did this week:</div><div class="">* Complete the multi-view reconstruction pipeline and pass the results from libmv to Blender. Now we are able to see the visualization results of multiple camera motion in Blender 3D view. Specifically, this is done by <span class="" style="font-family: HelveticaNeue;">multiview_reconstruct_retrieve_libmv_tracks function. </span></div><div class=""><span class="" style="font-family: HelveticaNeue;"><br class=""></span></div><div class=""><font face="HelveticaNeue" class="">* Fixing the correspondence saving/loading error. I found that correspondences couldn’t get loaded successfully and discussed this with my mentor (Sergey), who helped me solve the pointer error. Thanks go to him again! It appeared that ID pointers are to be restored using lib pointer map. </font></div><div class=""><font face="HelveticaNeue" class=""><br class=""></font></div><div class=""><font face="HelveticaNeue" class="">* Change the multi-view pipeline a bit to cope with single-view solver. Since we may remove single-view solver in the future, the multi-view solve button will revert to the single-view case if there are not enough correspondences between cameras.</font></div><div class=""><font face="HelveticaNeue" class=""><br class=""></font></div><div class=""><font face="HelveticaNeue" class="">* Fixing the multiview reconstruction bug, which previously got a huge re-projection error. This is a substantial progress and we can now get robust results of multi-view camera reconstruction. The re-projection error can be as low as sub-pixel level. It appeared that the previous bug is caused by using normalized track for intrinsics refinement. </font></div><div class=""><font face="HelveticaNeue" class=""><br class=""></font></div><div class=""><font face="HelveticaNeue" class="">* A bit of code formatting. move two functions with BKE_ prefix to blender kernel and revise the code to conform to blender coding style. </font></div><div class=""><font face="HelveticaNeue" class=""><br class=""></font></div><div class=""><font face="HelveticaNeue" class="">What I will do next:</font></div><div class=""><font face="HelveticaNeue" class="">* Now that a basic multi-view solver is finished, I would like to solicit everyone who is interested in this project to test the pipeline and report bugs and suggestions. The user interface (see the pic below) is crude for now and I will improve it during the next couple of days. But the basic functions should be good to go. Specifically, the pipeline works as follows:</font></div><div class=""><br class=""></div><div class=""><div class="">1. Open two video clips (one primary camera and one witness camera), specify some markers and get them tracked. </div><div class="">2. Link correspondences using the Correspondence panel in the PRIMARY video clip (See the ‘Correspondence' panel in the left). Correspondences should be more than 8 to make the multi-view solver work smoothly.</div><div class="">3. Click ‘Solve Multiview Camera’ button to reconstruct multiple cameras simultaneously. </div></div><div class=""><br class=""></div><div class="">* There are some ‘TODO’ left in the code here and there during my first implementation. I would like to finish the left components and improve the pipeline next week. </div><div class=""><br class=""></div><div class="">* Half of the project involves a decent user interface to work with multiple clips conveniently. As Sergey has pointed out, this is also the part that is undecided and open-ended. I will work on the design of the user interface in the next few weeks. At the mean time, I will continue to improve the pipeline and refactor the code. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Tianwei</div></body></html>