You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
I built a small web application to keep track of all the suggestions, their implementation status, and allow everyone to vote for their favorites.
So go to www.kinovea.org/ideas now and check it out 
You can "like" the ideas (click on the heart) or suggest new ones.
I will also publish the source code for the web application itself later on. Feedback appreciated.
Note:
I have changed the way this list is managed. I now have the entries stored in a proper database and a script to export the bbcode for the forum.
The idea is that at some point I would like this list to become a standalone page, include a voting system, and possibly allow anyone to add ideas directly.
Update on 2011 may 24th.
Removed from list because included in recent releases (up to 0.8.15) 
- Capture - Explicit file format picker for videos and snapshots. - Capture - More control over naming convention for captured files. - Capture - Save the size and frame rate configuartion selected as preference - Capture - Capture from IP Camera. - Saving - Being able to export the video including the superposed images of the other video. - Drawings - Image tool. - Workspace organization - ToolBar to change views.
Added:
- Drawings - Spotlight tool.
- Drawings - Snap image tool to borders. - Stopwatches - Cadence tool to track the evolution of tempo in cyclic performances (running, swimming, cycling, etc.). - Special effects - Anonymizer (detect faces and apply a blur on them). - Tracking - Being able to use another track as the origin of coordinates. - Tracking - Autotracking spotlight tool. - Tracking - Autotracking magnifier. - Synchronization - Create a video insert of one video on top of the other, retaining sync and navigation control. Possibly hide the original screen. - Synchronization - Send several images from one video to a single frame of the other video as observational references. - Synchronization - Support vertical alignement in dual export. - Capture - In dual capture, a common controls bar to start recording simultaneously.
- Workspace - Support for 4 playback screens.
Thanks for compiling all this. Many interesting things to read !
Regarding point 3 - markers with patterns, I think that yes, a pattern within the marker can improve tracking results.
Nested black and white rings would be the most efficient in my opinion (maximum contrast + not rotation variant).
Le fait que la tablette soit sous Windows 7 est un point positif du point de vue compatibilité, mais je ne saurais en dire plus.
Si vous pouvez trouver quelqu'un qui possède la tablette et faire le test, ce serait intéressant.
Follow-up:
With the integration of the update from the FFmpeg library for the next version, these particular files (bug 209, files from skiflyer and haeferl - Samsung camcorders) are now well supported (again).
Effectivement il semble qu'il y ait un bug quand on étalonne avec une mesure contenant une virgule (type « 25,5 » cm). 
En attendant utilisez le point « . » comme séparateur décimal…
Another thing I would like (as a user) is floating thumbnails when hovering the mouse on the list of files.
This way I wouldn't have to close the current screen in order to check the thumbnails to select the next file.
Vous pouvez essayer la fonction "Vue d'ensemble" du menu "Mouvement".
Pour l'utiliser vous devez au préalable réduire la zone de travail jusqu'à déclencher l'extraction des images en mémoire.
Bonjour,
Vous auriez un exemple ou une photo d'écran ? Je ne comprends pas très bien le problème…
Certains logiciels ont une fonction de désentrelacement qui recrée une image complète à partir de chaque demi-image (lignes paires ou lignes impaires) fournie par la source. Je pense que c'est de ce type de fonction dont vous parlez ?
Pour l'instant le désentrelacement dans Kinovea ne fonctionne pas comme ça et recréé l'image à partir des deux trames existantes plus ou moins en les combinant dans le résultat. On reste donc sur la fréquence image d'origine de la vidéo.
Peut-être dans une future version en fonction des capacités de la librairie de décodage de fichiers.
Quel type de tablette numérique ?
Attention Kinovea nécessite Windows et la plateforme .NET 2.0. Le programme n'est donc pas compatible avec les tablettes de type iPad, Android, etc.
You can also use the Tracking feature.
Right click the object and choose "Track this point". You can then move frame by frame and manually set the position of the target by dragging it where you want. (the "automation" is just a help, it tries to find the point automatically but the feature was designed to retain full manual control any time)
For each trajectory created this way, you can right click + configure and set a "label" to differentiate it from the other. This will show up later when you export to spreadsheet (menu File > Export to spreadsheet).
I premise that it is from little that I am trying to use the software kinovea 0.8.15 for the volley in the various menus I have different choices in grey that is not selezionabili that list under:
it exports on spreadsheet
riesegui
(…)
I don't know how you/they can be trained, you can help me. thanks
- Export to spreadsheet will only be enabled when you have added drawings, stopwatches or trajectory to the video.
- Common controls and invert position will only be enabled when there are two player screens.
- Image adjustment menus and menus under Motion will only be enabled when you are in "analysis mode" (frames preextracted to memory). Check this page "Observing motion" (here for Italiano)
yvesrpt wrote:Kinovea compatible with ANDROID to be abble to use it on E- Tablette?
Hi yvesrpt, It's a good question you asked. Kinovea requires a substantial amount of CPU processing to perform its tasks (especially if you dual record). I doubt tablets at this stage would have enough processing power to achieve this.
When I worked on Android (at work) it was all done in Java and we had a limit of 16MB (possibly 24MB depending on devices) per application.
Kinovea can only be ported to platform supporting .NET and with support for C# and C++/CLI languages (currently only .NET for Windows can do this, Mono cannot do C++/CLI).
The Linux / Mono port would have precedence over anything else anyway, but even that is pretty hard due to some dependencies on Windows (and the C++/CLI part).
Personally I am more inclined to work on improving the Windows version. There is a million things to keep me busy already.
I think there are efforts by others to develop video analysis applications on Android.
Hi,
Yes there are some known issues with the MTS files. You may need to restrict the working zone until it triggers the "analysis mode" (pre-extraction of frames into memory). Depending on image size / frame rate, this can be as low as 2.5 seconds.
Generally speaking, the difference between forward and backward frame by frame comes from the way the images are encoded inside the file. Some codecs use intra frame coding only (each image is compressed separately from the others) others use inter frame compression, which means for us that a given image can only be reconstructed after we also decompress another image. When we go backward, we actually need to go back a few frames first (back to the last full frame), and then decode all the frames inbetween.
There is also issues with some containers that do not index the images (VOB), or index them in a bizarre way (MTS).
Bottom line is :
- Some files are more suited to going backwards in the same ammount of time than forward.
- To even out the differences you can restrict the working zone to trigger the pre extraction of frames into memory.
- You can convert the files to a more suitable format using such tools as AviDemux or HandBrake.
Kinovea - Forums → Posts by joan