You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
Bonjour,
Tout à fait envisageable et envisagé, surtout le second point.
Un prototype d'interface avait été réalisé mais il reste des points à éclaircir.
Le plus probable est que je relance la réflexion ici, dans ce sujet ou un nouveau, pour recueillir suggestions et propositions.
Les efforts sont pour l'instant concentrés sur la finalisation de la prochaine version, j'espère pouvoir lancer une suite de sujets de reflexion de ce type à partir du mois prochain.
The installer creates a registry key under : HKEY_CURRENT_USER\SOFTWARE\Kinovea
It is used when you upgrade to a new version.
It also creates some shortcuts under the Start Menu and on the desktop.
It doesn't create anything else.
I'll try a few leads. I may require your help in testing candidate fixs if you're ok.
Thanks for the report.
If you can, please provide more infos regarding your system. Either in this thread or drop me a line at the following : joan at kinovea dot org.
Especially the following:
XP, Vista ? SP1, SP2, SP3 ?
For vista: Is UAC turned On or Off ? Do you run as Admin or standard user.
Anything else you think is relevant.
I'm currently looking into similar defects.
Thanks
Bonjour,
Kinovea n'utilise pas de codecs. Je serais intéressé par plus d'informations sur les crashes rencontrés... Si possible envoyez moi un mail à l'adresse joan at kinovea point org avec le scénario ayant conduit au plantage.
Si cela se reproduit systématiquement avec une vidéo donnée, je serai également intéressé par un petit échantillon si c'est envisageable.
Concernant l'utilisation de Kinovea dans le cadre de l'analyse d'animations, la prochaine version devrait je pense être beaucoup plus fonctionnelle.
L'outil crayon a été amélioré et reste actif tout le temps. Le simili onion-skinning sur les dessins est également une fonction qui devrait vous intéresser.
Cette version devrait être disponible d'ici la fin du mois. Je me concentre actuellement sur la correction des anomalies, donc n'hésitez surtout pas à rapporter tous les bugs que vous trouvez, merci !
Hi,
Yes, the change has been made so the saving functions use the same routines as the display.
So when you will check the 'Blend drawings on images', it will actually blend the trajectories (and chronos and grids too).
To be expected: end of january.
Hi Mike,
When you get the update ready to test send it my way and I will run some of my old videos through it to see how everything goes.
Check your mail 
I would love to see the drawings stay in the image as long as I would like. The feature you took off as far as copying a previous drawing to the current image would be nice if you could re add it.
Drawings that spread over several images is in. Hopefully it removes the need for the copy function.
Also the problem I was having with high def videos are the computer. I purchased a new laptop with a Pentium 2.0 GHz processor and 4 GB or ram and the videos work fairly smooth. They still only play at around 70 - 80% speed on there own, but they are not as jerky as before.
Yes, there is still things to be done in this area, for when even higher image size and frequencies will come...
Also, I do not know if this is possible.When you save a key image to a PDF file is there a whay to set it up so I can have more than one image per page. Or is that a function I need to perform in Acrobat.
This is something I have had on mind for quite a while and I even have the interface somewhat worked out.
The current PDF export is very weak in my opinion. I decided to remove it temporarily because it is not up to date with the latest modifications (direct zoom and persisting drawings) and I don't want to make updates to it until the very function you are talking about is in place.
Hi,
For the first error, this is because you need to copy the FFMpeg dll to the execution directory.
If you are using the 0.7.6 source archive:
You'll find them under : \Refs\FFMpeg\ffmpeg-r10461-gpl-lshared-win32\dll\
You should copy them to : \Root\bin\Debug\ for example.
For the second one, it's my big mistake... I have left absolute path for dependencies directories... 
In the projects settings (Alt+F7) go to C/C++ > General > Additional Include Directories, and replace everything that is before \Refs, by "..\.."
(Complete path would be : "..\..\Refs\FFMpeg\ffmpeg-r10461-include" )
Do the same in Linker > General > Additional Library Directories.
(Complete path : "..\..\Refs\FFMpeg\ffmpeg-r10461-gpl-lshared-win32\lib")
Note:
You may want to use the source code repository from CodingTeam.net forge as it is more up to date.
Launch your SVN client and do a checkout using the url :
http://svn.codingteam.net/code/kinovea
It shouldn't have the absolute/relative paths problem.
@michel:
Il a l'air super ton appareil .
Pour les vidéos qui sont déjà au ralentit, j'avais remarqué ce souci.
Je n'avais pas pensé que l'utilisateur puisse connaître le nombre d'images par secondes exact de la capture. Je vais voir comment on pourrait en tenir compte quelque part.
D'autre part je serais intéressé par un (petit) échantillon de vidéo HD qui fait planter le programme. (joan at kinovea point org)
@sylpub:
- Conservation de l'espace de travail => déjà ajouté récemment pour l'affichage/non affichage de l'explorateur. Pour la config écrans j'hésite encore...
- Conservation de l'outil utilisé: modifié récemment aussi pour crayon et ligne. Pour les autres la priorité est donnée à la modification plutôt qu'à l'ajout d'un nouvel élément.
- Export SWF: Ca serait très sympa mais pour l'instant je n'ai pas assez de temps pour m'y pencher de façon complète...
- Version Linux: Pareil que précédemment avec en plus des difficultés techniques plus importantes...
Merci pour le feedback !
Hmm... The bad news is that the FFMpeg update that fixed the problem on those videos also introduced several regression on other videos... (Some regular MOV files will simply not play.)
I haven't find the root cause of the problem and unfortunately I'll need to revert to the previous version of the lib for the time being.
(Argh. )
I'll try new versions as they come to see if the regression is somehow fixed.
Il y a eu de bons retours sur la version 0.7.6 et plusieurs remarques intéressantes.
Je me suis rendu compte que certaines parties ne correspondaient pas au niveau de qualité souhaité, en particulier l'outil Crayon mais également d'autres fonctions.
Donc avant de partir tête baissée dans les effets spéciaux, la capture DV, ou le support du son pour la version 0.8.x, il semblait important d'améliorer l'existant.
Périmètre à prévoir:
- Amélioration de l'outil crayon.
- Dessins apparaissant et disparaissant sur plusieurs images autour de leur image clé de référence.
- Zoom direct dans l'image.
- Tracking semi automatique.
- Correctifs.
L'objectif est d'obtenir une dernière version 0.7.x la plus stable possible, car lorsque le développement de la 0.8.x va commencer les nouveaux bugs vont pleuvoir.
Il est donc très important de rapporter tous les bugs que vous trouvez, manipulez les options dans tous les sens, essayez de le faire crasher volontairement, etc.
(Un de ces jours il y aura une plateforme plus formelle pour lister systématiquement les tests à effectuer mais pour l'instant il faut fouiner et tenter de vérifier tout ce qui parait suspect.)
Merci 
The feedback on 0.7.6 has been good (thanks) and several good points have been made.
It occurred to me that some parts weren't up to the quality standard I wanted. This was especially true of the Pencil tool but of some other bits aswell.
So before diving into special effects, DV capture, audio support or other features of 0.8.x, some polishing of the existing is necessary.
This new 0.7.x won't take 4 month to be completed though, and it should be out within the next 4 weeks now.
To be expected:
- Better pencil tool.
- Drawings that fade in/out of their key frame or stay visible for ever.
- Direct zoom into picture.
- Semi automatic tracking through template matching.
- Plus as many bug fixes as possible.
It must be as stable and bug free as possible since future versions will add many new areas for bugs to hide into.
So please, I emphasize that bug reports are the very important contribution you can do.
Try all options systematically, try to make it break, and please report when it does.
Thank you
1. The chronometer export problem should be fixed in the next release.
2. Shapes as drawings is another feature that will be worked on, I'm not too sure when though.
I want to take the best approach on this one to enable people draw shapes as complex as they want.
3. This is an interesting point.
The current tracking function was done with technical sport analysis in mind. (Incentive was for exemple: how does the knee joint moves over time ?)
Having it tweaked for team sports/tactical position sports would be a great enhancement.
So please comment/expand on this tentative "feature spec" :
- In edit mode, the trajectory display wouldn't change much.
- In normal mode you could choose between several styles through the configuration dialog:
a. Analysis trajectory (same as existing),
b. Arrow pointing towards the point being tracked, (the trajectory in itself wouldn't be visible not to clutter the view)
c. Label attached to the point being tracked.
Hi, thanks for the feedback.
It will be taken into account when building the roadmap/features goals.
It turns out the priorities vary greatly from users to users...
@Tampai: Because of perspective it is not easy to give a meaningful value for line size.
As for the angle it will only be accurate if the line is on a perpendicular plane. But unlike angles, if you want to compare several line sizes, all lines would have to be on the exact same plane.
I think this is too much a constraint and will not be practical.
However, I'm considering using the new 3d grid to let the user define a reference plane. All angles and lines could then be computed relatively to this plane.
@mag: The "12" I had in mind will be included in a new 0.7.x release soon. However I think what you describe is more of an object tracking scenario. Putting a line and have it following an object on subsequent frames. This won't be in the very next release, I still need to have a stable/consistent tracking for single points first.
Short anwser:
Will be fixed in next version.
Long answer:
I tried the file and reproduced the problem. Then I tried it in MPlayer and VideoLan, and got the same issue...
This generally means it's an issue in FFMpeg itself (the decoding library we all use) which is out of my league to fix.
I looked for topics related to errors on this specific codec and found some interesting posts on the subject.
The root cause is the little watermark in the bottom right corner, which is actually superposed in a metadata layer and modifies the way the file is encoded...
It turns out this was fixed in FFMpeg very recently.
I'm using the "unofficial builds for Windows" done by Ramiro Polla and he just made a release today ! (previous one was in august)
I integrated the new build and I can confirm that the problem is fixed.
All the credit goes to the FFMpeg developpers and the Windows builds manager. (This is definitley Open Source in motion )
Hi,
It can have several causes... Would you be able to provide a sample so I can have a look ?
Kinovea - Forums → Posts by joan