Hi,
I do have added a few strings though (about 10 I think, the speed units in the preferences dialog for example).
I'll freeze the file and send mails as soon as possible.
1,696 2010-04-08 11:39:57
Re: Experimental version - 0.8.6 (7 replies, posted in General)
1,697 2010-04-05 15:21:59
Re: Make persistence "Always Visible" standard? (6 replies, posted in General)
Hi,
It will be part of a future update, along with other new things in the drawings department.
(It won't be in the coming release, but most probably in the series of experimental versions starting after that.)
1,698 2010-04-04 09:56:16
Re: Many sequences per video (1 replies, posted in General)
Yes, you can only have one working zone at any time for now.
I think what people have been doing is to split the video by saving each section into its own file. This may or may not be optimal in your case…
Another thing is to set a key image at the start of each interesting section so you can later jump to it quickly.
1,699 2010-04-04 09:41:33
Re: Fichier Video Full HD m2ts (9 replies, posted in Français)
Bonjour,
Quel est le résultat exactement ?
- ils ne sont pas visible dans l'explorateur intégré ?
- ils s'affichent avec la miniature bleue d'indisponibilité ?
- ils sont accessibles mais donnent un message d'erreur ?
- la lecture démarre mais se bloque ?
Les vidéos sont elles lisibles dans:
- VLC ?
- Windows Media Player (le lecteur par défaut de Windows) ?
- Quel est le logiciel que vous utilisez habituellement pour lire ces fichiers ?
Quelle est votre version de Windows ?
1,700 2010-04-03 20:38:10
Re: Kinovea on Linux (6 replies, posted in General)
Installed Wine and winetricks on a Fedora…
Installer runs fine, then troubles starts… Same as you I don't have the menu.
Multiple crashes when doing about any action.
I copied some videos in the (Wine) Desktop folder (my home folder /.wine/drive_c/users/my user name/Desktop). I can see the animated thumbnails (I was surprised it didn't crash…:)). But can't do anything else.
I don't think I installed gdi+ or fontfix. I'll have to try that to see if it crashes a little less.
Edit:
I installed gdi+ and fontfix: much better.
It stopped crashing everytime and I can even launch the videos ! 
There seem to be an issue with the player timer though, video is very jerky. (might be my machine).
I haven't tested most areas, don't know if it'll prove anywhere usable, but that's a tiny start.
1,701 2010-04-03 20:09:29
Re: Help rename the "Mosaic" function (8 replies, posted in General)
Thanks for all the propositions !
About coining a new word for the function:
The good part is that it creates a recognizable name, and that it does not need to be translated between all languages.
The cons is that it is not obvious what the function will do before the user clicks on the menu or check the help file.
In this, way, I think it's best to have something that is the most descriptive possible. I would like the program to speak the same language as the user so there's no surprises.
We may use a brand new name when the feature to name is completely innovative and doesn't correspond to anything.
I'm also a fan of the early history of cinema .
And that is why Chronophotography is already reserved for a future feature. It was a tremendous technique to decompose motion used by Muybridge and Etienne-Jules Marey in the 1880's.
I find this incredible how these guys were studying motion from photography more than a hundred years ago. They are totally forgotten in my opinion. A century later, we should have hardware that does that kind of stuff.
In trying to get as close as possible to describing the feature in actual words, I think "Overview" is pretty much spot on.
I have switched to that in the just-posted 0.8.6 experimental version, to try it out in the light.
Let me know if you have strong objections against it, otherwise I guess it's a keeper.
1,702 2010-04-03 19:29:47
Topic: Version expérimentale - 0.8.6 (4 replies, posted in Français)
Version expérimentale : elle a besoin de vos retour d'expérience pour s'améliorer !
Veuillez considérer cette version comme une « Release Candidate »
L'installeur est dispo ici : Lien retiré. Voir version 0.8.7.
1. Suivi
- Nouvelle amélioration de l'algo, les résultats devraient être plus robustes. (fixe le problème de « template update » qui faisait que le suivi changeait de cible petit à petit.)
- Le code sous-jacent pour le matching est maintenant délégué à OpenCV, -> gain de vitesse important !
- La fenêtre de recherche est maintenant proportionnelle à la taille de l'image.
Comme d'habitude, décrivez vos scénarios de suivi qui échouent.
2. Manuel d'utilisation
La version anglaise du manuel a été mise à jour, et est en test dans cette version.
Pour le voir il faut basculer la langue en anglais puis faire F1 ou Help > Kinovea Help…
Vous pouvez aider à sa relecture :
Si vous trouvez des fautes de frappes, de grammaire, des passages obscurs ou manquants, vous pouvez les rapporter ici; dans le sujet du forum anglais; ou mieux: les fixer vous-même. Il suffit d'aller sur cette page du wiki et d'éditer le sujet correspondant.
-
En dehors de ça, les bugs suivants on été résolus : m175, m176, m177, m178, m179.
Capture : La séquence de test du Billard. N'avait jamais passé le test jusqu'à maintenant 
.
1,703 2010-04-03 16:58:42
Topic: Experimental version - 0.8.6 (7 replies, posted in General)
This is an experimental version : it needs your feedback to improve itself.
Please consider this version as a Release Candidate.
The installer is available here: link removed. Please check version 0.8.7.
1. Tracking
- The algorithm was improved again, results should be more robust. (fix for the "template update" problem, when the tracker was slowly changing target over time.)
- The underlying code for the matching is now delegated to OpenCV, which provides a great speed bump !
- The search window is now proportional to the image size.
As always, please detail your failing tracking scenarios.
2. User manual
- A candidate version for the updated manual is embedded in this version, (Hit F1 or Help > Kinovea Help…).
- Please help in proofreading it:
If you find typos, grammar issues, missing bits, obscure paragraphs, etc. you can report it here, or better yet : fix them. Just go to this wiki page and edit the corresponding topic.
-
Aside of that, the following bugs were fixed : m175, m176, m177, m178, m179.
Mandatory snapshot : the Snooker tracking test sequence. It used to fail miserably, now both balls are tracked all the way .
1,704 2010-04-01 22:52:45
Re: Kinovea on Linux (6 replies, posted in General)
I did not realize that Wine was supporting the .NET Framework…
I'll also try to experiment with that when time permits.
Thanks for the initiative ! Keep us posted if you make some progress
1,705 2010-04-01 18:47:19
Re: rotate the view of the videos (7 replies, posted in General)
Hi,
It is on the suggestion list
One other request was to be able to rotate by 90°. Technically I think it will be the same complexity to code the rotation by arbitrary angle like you suggest or by fixed 90° steps.
The end result might be of slightly less quality than the original because for arbitrary angle we will need to interpolate the pixel values.
For the user interface, I was thinking of a new dialog box where you can change the angle with a slider and validate. (Other ideas welcome)
Bug m181 will also need to be fixed during the implementation of this function.
This will not be part of the next official release, maybe in the one after, depending on other prioritized stuff.
1,706 2010-03-29 23:57:34
Re: Version expérimentale - 0.8.5 (2 replies, posted in Français)
Bonjour,
Le tracking qui est actuellement dans la version de développement est meilleur en termes de qualité et de vitesse de traitement. (bien meilleur à mon avis mais je vous laisserai juger )
Le chiffre correspond à une donnée interne de l'algo, c'est le coefficient de corrélation entre la zone de l'objet (rectangle interne) de l'image précédente et celle de l'image courante. En gros cela mesure la réussite du tracking pour l'image en cours. La valeur va de +1 à -1, mais si elle descend sous le seuil de +0.5, on estime qu'il n'y a pas de "match" et le tracking est abandonné.
Le rectangle externe correspond à la zone de recherche. (ce sera mieux expliqué dans le guide d'utilisation qui est en cours de rédaction )
1,707 2010-03-26 09:47:51
Re: downloaded wrong language version (4 replies, posted in Bug reports)
Ok, thanks. That corresponds to the bug I was mentionning. The French locale was loaded by default instead of relying on system's.
This should be fixed in the next version.
1,708 2010-03-26 00:35:43
Re: downloaded wrong language version (4 replies, posted in Bug reports)
Hi,
There is only one version, it has all the languages packed in.
The program first tries to detect if your system language is supported. If not, it should fall back to English.
However there might have been a bug that would make it fall back to French instead.
- Could you write here what the first menu is ("Fichier", "Tiedosto", something else ?)
- To change language, go to the second menu starting from the right, then first submenu.
Are you on an English Windows ?
1,709 2010-03-22 10:24:34
Re: Angle Question (6 replies, posted in General)
Hi,
No, it is not currently possible.
It was necessary to improve the tracking performance and robustness before implementing multi-point tracking.
It is planned as a future improvement though.
1,710 2010-03-19 18:37:50
Re: Best video values? (1 replies, posted in Bug reports)
Hi,
I hope someone can come and answer this better than me because I have not much experience with AVCHD, and I don't do a lot of conversions.
If you are not much concerned with storage size, you can use the highest quality option available in your conversion software.
Regarding blurriness/quality, bitrate is not as much relevant as the compression method used, because most of the time is spend decoding the image. This is especially true for large image size like full HD.
For a given codec and image size, you can use a higher bitrate. That should improve quality without degrading rendering speed. (You could use uncompressed files).
Regarding jerkiness, this will really depends on the machine performances and you'll have to make tests to find your threshold.
If you see the speed slider decreasing on its own, then the program can't keep the pace.
I would target for 25 or 30 fps, and then reduce size until it plays smoothly if you have jerkiness issues or automatic slow down.
Also, if possible try to use an intra-frame only codec (like DV or MJPEG) since that will make the backward navigation easier and decoding faster.