It looks like they have a Windows driver for the Kinect at codelaboratories.
Can you or someone with a Kinect try this in the experimental version and report the result ?
(I'm not too sure that it's a DirectShow driver ?)
Thanks
1,351 2011-04-02 13:02:06
Re: Using Kinovea with Microsoft's Kinect camera: Is it possible? (6 replies, posted in General)
1,352 2011-04-02 08:13:43
Re: Experimental version - 0.8.14 (20 replies, posted in General)
Sure. I'll send you a mail later today or tomorow.
1,353 2011-04-01 10:24:18
Topic: Version expérimentale - 0.8.14 (4 replies, posted in Français)
Version expérimentale : elle a besoin de vos retour d'expérience pour s'améliorer !
Si tout se passe bien cela devrait être la dernière itération avant la version stable. Merci de rapporter les plantages éventuels le plus vite possible.
L'installeur est dispo ici : [s]Kinovea.Setup.0.8.14.exe[/s] Voir Kinovea 0.8.15
Les principales améliorations sont sur la partie Capture.
- Support des caméras réseau (celles qui font du streaming JPEG ou MJPEG).
- Accès à la page de propriété native de la caméra pour les cameras FireWire ou USB.
- Page de préférences, y compris un nouveau système de nommage automatique des fichiers.
- Etc.
Correctifs : bugs 241, et autres bugs non numérotés.
Préférences capture.
1,354 2011-04-01 10:02:15
Topic: Experimental version - 0.8.14 (20 replies, posted in General)
This is an experimental version : it needs your feedback to improve.
If everything goes well, this should be the last experimental iteration before the next stable release. Please report any crash as soon as possible.
The installer is available here: [s]Kinovea.Setup.0.8.14.exe[/s] Please check Kinovea 0.8.15
The main improvements come from the Capture screen.
- Support for network cameras (when capable of JPEG or MJPEG streaming).
- Access to the device property page for FireWire or USB cameras.
- Preference pages, including advanced naming schemes.
- And more.
Fixed bugs : 241, and other non numbered bugs.
Capture preferences pages
1,355 2011-04-01 09:28:52
Re: Rethinking the drawing tools (17 replies, posted in Ideas and feature requests)
In the analysis tools department, it has been noted that the stopwatch is functional but simple.
Maybe there could be a separate cadence tool (or tempo tool). Something to simply assess the frequency of a repetitive phase. Like strokes in swimming, strides in track and field, rotations in discus or hammer throw, etc.
The usability of this will have to be top notch to keep things simple. (The lap function on a physical stopwatch can be confusing at first, the tool would have to be simpler than that if possible).
1,356 2011-04-01 09:10:11
Re: Rethinking the drawing tools (17 replies, posted in Ideas and feature requests)
jon wrote:
The next step is the ability to set the default thickness of the circle.
You would do that with the color profile. (last button on the drawing toolbar). Alternatively, you can also right click before setting the drawing. This will set the color and size for the drawing type as a whole.
Thanks for the clarification about the freehand arrow.
1,357 2011-03-31 23:48:57
Re: Rethinking the drawing tools (17 replies, posted in Ideas and feature requests)
@Alexander: yep, auto-tracking magnifier and auto-tracking spotlight sound appetizing. Loosing the target will have to be handled differently than in the current tracking tool though.
Regarding improving the general video, if you refer to some sort of deshaking feature, I think this needs a different type of tracking (a "dense" tracking to compute the whole image motion at once). I'll eventually create a separate thread for this. That would probably end up being implemented as a "Motion" menu.
jon wrote:
What i would find useful is a 'pencil' tool with an arrow.
Like drawing two big lines of the same thickness than the rest of the drawing ?
jon wrote:
Regarding the current circle tool. Would it be possible to customise the thickness of the circle?
You should be able to do this by changing the "size" parameter in context menu dialog or color profile window.
1,358 2011-03-29 21:37:53
Re: Introduction du "Dépôt RefObs" (2 replies, posted in Français)
Écrire en Français dans cette section du forum svp ! 
Il est possible que le système n'autorise pas la modification des fichiers qui sont sous "Program Files" ou autres dossiers système. (Particulièrement sous Windows Vista avec un compte non-administrateur).
Si c'est le cas, il faut obligatoirement passer par un compte administrateur je pense. (À moins qu'il n'y ait une option quelque part pour permettre la modification des fichiers par les utilisateurs normaux)
Sinon il est toujours possible de charger le fichier à chaque utilisation en passant par le menu Image > Référence d'Observation > Importer une image.
1,359 2011-03-28 20:14:19
Topic: Introduction du "Dépôt RefObs" (2 replies, posted in Français)
J'ai créé une page pour lister les références d'observation ici : Dépôt RefObs.
Il semble que le rendu des images dans le navigateur ne fonctionne pas avec les anciennes versions d'Internet Explorer (avant la 9). Dommage (surtout que IE9 n'est pas dispo pour Windows XP), mais je n'ai pas vraiment le temps de m'occupper de ça maintenant, surtout compte tenu du fait que cela fonctionne dans tous les autres navigateurs… 
(note: Il faut utiliser au moins la version 0.8.13 pour bien tirer parti de cette fonctionalité).
Pour l'instant vous pouvez m'envoyer vos contributions par mail si vous voulez.
Vous pouvez également poster vos suggestions de nouveaux fichiers dans ce sujet, si vous ne pouvez pas le créer vous même peut-être que quelqu'un d'autre le fera 
1,360 2011-03-28 18:51:59
Topic: Introducing the ObsRef repository (1 replies, posted in General)
I have set up a page to list observational references here : ObsRef Repository.
The rendering of the images in the browser might not work for some (all ?) versions of Internet Explorer. (It's a shame, I know, but I don't have the time to work out a solution right now, especially considering that it's working in every other browser I tried… edit: works in IE9).
(note: you need to use at least version 0.8.13 to fully leverage the feature)
For the time being, you can send your contributions by mail if you want.
You can also post suggestions on new reference in this thread, if you cannot create it, maybe someone else will.
1,361 2011-03-27 21:25:01
Re: Rethinking the drawing tools (17 replies, posted in Ideas and feature requests)
Thanks
yvesrpt wrote:
the clock tool, a circle with hours on it
This sounds like this could be implemented as an observational reference.
This reminds me that I wanted to craft some more "protractor" like tools there. (And possibly remove the few anatomy reference for now as they don't seem so useful as they stand).
yvesrpt wrote:
also a multidots graphics
Can you expand a bit? I'm not sure I see what you mean.
daww wrote:
link the spotlight feature with the tracking feature
Yes, it would definitely be interesting to have that. I think similar idea has been suggested with the magnifier tool as well.
Maybe you would add a spotlight, and simply right-click it and choose a "Track this area" menu.
It would have to work slightly differently than the existing track tool though to simplify the usage.
1,362 2011-03-27 12:33:47
Topic: Rethinking the drawing tools (17 replies, posted in Ideas and feature requests)
(this is for mid-term evolution, please add your thoughts to the discussion )
I am not entirely satisfied with the existing set of drawing tools. Some important tools are missing, others could be improved in their functionality and usability.
I've been thinking for a while about what to do about it, with the goal of having the most comprehensive and useful set of tools possible. On the other hand, the interface must stay as simple as possible.
I like to think of drawing tools in two categories : tools to observe and tools to show. I also call them, respectively analysis tools and telestrator tools.
(Telestrators are devices used in TV broadcasts of team sports, to explain tactics to the audience)
Typically an arrow or a circle are tools to show the viewer where to look or what to look for. These are tools used during a debriefing, when creating a video explanation, or similar "teaching" actions.
The observation tools (measuring a line, checking an angle, stopwatch, etc.) are tools that would be used during the actual analysis of the performance.
Here are some of the intended changes :
Organisation
- Better organization of the tools on the toolbar to reflect the tool usage (just sorting them differently).
- Separation of the arrow tool from the line tool. Lines and arrows serve different purpose, the fact that they are implemented by the same underlying code shouldn't be reflected on the interface.
Possible new tools
1 - Spotlight : a tool that would dim the entire image except its own area.
2 - Rotation arrow : a tool to symbolize rotative motion.
3 - Auto numbering mark : a number inside a circle. Each time you add one, the number increments.
4 - Simple rectangle.
5 - Multi line - Should also support measure on each segment and/or angle value at each joint.
Improvements to existing tools
- Circle changed into ellipse ?
Considering the number of tools and the limited place some grouping of tools might be needed.
Mockups for some of the proposed new tools
(spotlight, rotation, auto-numbering)
Comments, ideas for new tools are much welcomed, as well as improvements suggestions on the functionality and usability of existing tools.
1,363 2011-03-25 13:55:15
Re: calcul vitesse (1 replies, posted in Français)
Bonjour,
La vitesse affichée est la vitesse moyenne du segment de trajectoire précédent le point. C'est à dire la distance du segment sur la durée entre les deux images.
La distance est la distance euclidienne classique : racine de [(xi - xj)² + (yi - yj)²] (où i et j seraient deux images consécutives).
L'intervalle de temps est calculé en fonction de la fréquence d'image de la vidéo.
Si x correspond a une vitesse dans votre formule, vous calculez la variation de la vitesse sur l'intervalle, donc plutôt une accélération ?
1,364 2011-03-23 14:22:44
Re: export report (2 replies, posted in Ideas and feature requests)
I agree 100%
Actually, there was once a "PDF export" function to export key images and comments as a report, but it was later removed for various reasons.
Since then, I've added a more ambitious sub-project to the todo-list, to adress the shortcomings of the defunct PDF export function.
Ideally, it would be based on templates for maximum flexibility and easy customization, and the data be exported to something easily modifiable afterwards (like ODF).
There's a page on the developpement wiki about this sub-project here.
I don't find the time to fully get into this for now. It will later compete for priority with things like multi-point tracking, chronophotography and other effects, etc.
Also, lately I've come to think that this templates approach is maybe too complex/ambitious and a more straightforward (read: less flexible) approach should be preferred.
Existing reports done by hand would help in designing the feature though.
1,365 2011-03-22 21:40:55
Re: kinovea manufacturer (2 replies, posted in General)
Hi,
You could use :
Manufacturer/producer: Kinovea open source project.
or just www.kinovea.org
And due to this open nature, there is no "country" of origin, there is no company or formal organization. It is the result of the contributions of several individuals from all over the place.