I have migrated my blog to – http://medium.com/@amitsarangi
From now on, you can visit this to get the latest updates.
From now on, you can visit this to get the latest updates.
Initially I thought, roadmap will be a better word , but naah! This is just a post on what “may be” in CCV in future releases ! Also people who want to contribute into CCV code base and have no idea what they can do , these are some features that can be worked on ! Some of them are pretty easy, so can be nice place to start !
This is not all , this is just a list of what comes to my mind right now ! If you want to add/modify any feature, just let me know , and I will add it up !
I have tried some of these and got success in some (like- running as service,debug mode improvements, multiple port TUIO) but the code is not mature enough to be merged into the repo. So if any of you want to work on these features, you can ask me/anyone in dev team for help !
You think you are not the “code-guy” and still want to contribute ? You are always welcome to help in documentation ! CCV is nicely documented, also the code is written so that it is easy to follow ! But better is always good 😉 !
Finally the summer is over. Google Summer of Code made this summer one of the most amazing summers I have had. There are many people I need to thank for the successful completion of my project including Pawel Solyga(Mentor), Christian Moore, Jimmy Hertz, Sharath Patali and many other users who took time to test and give feedback for the test version of CCV-COT.
Its a great pleasure for me to announce that my work will be integrated into CCV mainstream development and will be released with this release (1.4).
Note : There has been some major changes in this release, so please read this fully before trying CCV-1.4a. Also if you have not tried out CCV-COT , you may want to read this post prior to reading this.
Changelog (After CCV-COT):
Community Core Vision v 1.4a
But of course you need to be very lucky to get this mode working. A lot of adjustment will be required. But it is worth trying ;).
Thanks to jimmy hertz, he has tested this version of CCV with his DI setup. Here are some images from his test.
Compile it yourself from LATEST SOURCE CODE
Hi everyone , was a bit busy with work on CCV-COT. There were a few bugs slipped in which took most of the time. Here is the summary of some works which I did after my last post.
Somethings which are added to the roadmap are :
In the past weeks, I have been working on my Last Post’s TO DO List, and this post is to update you with my work.
CCV Debug Mode :
As the CCV users may be knowing , CCV logging was removed in CCV 1.3. This was due to several users reporting a bug that the logs become very big size(sometimes in GBs). Logs help developers to visualize a crash situation, so its quite an important part. Therefore I have tried a workaround for that. Instead of logging every time, we make the logging optional. This is called CCV Debugging mode. You just have to pass a command line argument -d for that e.g.
"Community Core Vision.exe" -d
And CCV Debugging mode is activated. Also , to make it simpler , in the next release a shortcut to CCV Debug mode will be included with the binaries. As usual this saves the Logs into the “logs” folder with the timestamp as the filename.
I know, this has been much awaited and many people have tried to do this before. Here is Stefan Schlupek’s repo where he managed to do it properly. I have integrated Fiducial support in CCV-COT.
Things TBD :
I am not releasing this time, as I have not tested them well. So in next few days, there will be changes going on. I will release them after testing it out. It must be soon though ! In case you are in a hurry to try it out , you can do it yourself by checking out the repository and compiling the code yourself. In case you run into any problems, just let me know via comments/mail.
Also for my previous version , slugmobile(noah) has compiled binaries for Mac OSX . In case you want to try them out, check here.
CCV-COT or CCV Custom Object Tracker is the modified CCV to do the object tracking. For a getting started guide to CCV, refer here : Getting Started with CCV . This post assumes that you have a basic understanding of CCV , as I will be explaining only the difference my work has.
DOWNLOAD : CCV-Custom Object Tracker
SOURCECODE : Googlecode SVN
This diagram only mentions the difference it has from CCV 1.3 . For a complete Description refer – http://wiki.nuigroup.com/Getting_Started_with_tbeta#Overview_Diagram
The configuration of this is pretty much similar to the configuration of CCV 1.3 : http://wiki.nuigroup.com/Getting_Started_with_tbeta#Configuration . While configuring for fingers switch on the Finger Tracking, to be able to see id/outlines of fingers detected.
There are some changes in the XML structure in config.xml, which end users need not worry about.
The use camera button  in the figure, is used for camera and video also.
The Calibration is same as the calibration of CCV 1.3 : http://wiki.nuigroup.com/Getting_Started_with_tbeta#Calibration
You should first configure your CCV to track finger blobs and then you should do the calibration with finger blobs. The calibration can be done by the Object tracking also, but that would not be precise.
Till now is what mostly same as in CCV 1.3.
<TEMPLATE> <WIDTH>36.000000</WIDTH> <HEIGHT>55.000000</HEIGHT> <MINWIDTH>25.520044</MINWIDTH> <MINHEIGHT>38.988960</MINHEIGHT> <MAXWIDTH>46.833553</MAXWIDTH> <MAXHEIGHT>71.551262</MAXHEIGHT> <<strong>TRUEID</strong>>0</<strong>TRUEID</strong>> <ID>180</ID> </TEMPLATE>
<TEMPLATE> <WIDTH>36.000000</WIDTH> <HEIGHT>55.000000</HEIGHT> <MINWIDTH>25.520044</MINWIDTH> <MINHEIGHT>38.988960</MINHEIGHT> <MAXWIDTH>46.833553</MAXWIDTH> <MAXHEIGHT>71.551262</MAXHEIGHT> <TRUEID>1</TRUEID> <ID>189</ID> </TEMPLATE>
Hello everyone , its a little long since my last post but yes, I had been busy coding and thought of posting after I got some results. Now that I am getting some results, I thought of posting an article about my work and plans.
Also I want to tell you that there was a slight deviation of my plan/road-map from my last post. In that post I mentioned regarding the two parts, one for template selection and one for template matching. Well, I have changed the plan a little bit. Instead of having 2 tools, one for selection and one for tracking, I integrated selection and tracking into one.So it will be just modification of CCV, which will do both template selection and tracking. Initially I thought it will be a bit slow, but it turned out to be effective. You can follow my work on http://code.google.com/p/ccv-tt.
As you can see, in the GUI I have added a “Track” section where you specify what to track (fingers/objects/fiducial). Also I added a “Template Area” panel , which decided the blue and green rectangle you see in the figure. Also I modified the settings section to have Save templates and Load templates.
Also I have included the TemplateUtils class in the sourcecode which takes care of all the template works. The templates are saved in “templates.xml” file in “data” folder.The ID will be auto assigned. In case you want to change it , you can change in the xml file and load the xml again while the CCV is running.
Right now , I am able to track objects(I am able to differentiate them from finger blob). Next what I will be doing is :
In next week, I will be implementing some of these functions and testing. Once it is ready for the release, I will have a release package for alpha testers and have a video showing the work. Also then I will be posting a step by step documentation soon how to work with this. Look for the posts here in near future.