J'oubliais,
merci également d'indiquer votre système d'exploitation (XP / Vista + 32 bits / 64 bits).
1,891 2009-05-29 18:32:16
Re: lancement kinovea (8 replies, posted in Français)
1,892 2009-05-29 17:43:19
Re: lancement kinovea (8 replies, posted in Français)
Bonjour,
Si vous avez eu la fenêtre classique de Windows "Voulez vous envoyer un rapport d'erreur"... Le rapport d'erreur est envoyé chez Microsoft et je n'en suis pas informé.
Vous pouvez par contre rapporter un bug pour Kinovea à http://www.kinovea.org/bugs. Copiez-y le contenu du rapport si possible (bloc sous *** Exception Text *** ).
Il y avait un soucis de lancement sur certaines machines dans la version 0.7.6, vous confirmez que vous avez installé la version 0.7.10 ?
1,893 2009-05-27 14:12:23
Re: What would be your top priorities for 0.8 ? (25 replies, posted in General)
Hi,
@jenki:
I don't think that capture should be deprioritized at all (it has been requested a lot):
Eventhough one can use the software bundled with the camcorder or say, Windows Movie Maker, these programs are lacking many features we will expect.
The most basic one would be the "delayed live", not present in those packages but very interesting in sport for self coaching and unattended feedback.
There is an hardware abstraction layer that most vendors follow, so I'm hoping that hardware support will not be too troublesome.
@neil:
For everything regarding video formats, Kinovea is 100% relying on the FFMpeg libraries set.
Fortunately the guys at FFMpeg are the ultimate gurus in this topic and if it's doable, they will do it.
It's actually very possible that the current versions of the libraries are already supporting AVCHD, it's been a while since I last checked. (Of course the current version of Kinovea is shipped with an older version of the libraries).
1,894 2009-05-25 16:27:39
Re: program crush saving a video .mov (1 replies, posted in Bug reports)
Hi,
I am sorry for the data loss.
Please add more infos about the issue in the other thread here.
Comments:
- It might be tied to issue #2 of the other thread. Try to only save a video if you are in analysis mode.
- You can save the data without saving the video. Saving the data only (just the description of drawings, trajectory etc.) has less chances to crash than saving the video as a whole, and doesn't recompress the video.
1,895 2009-05-25 16:20:30
Topic: Status of defects regarding "Save Video" function. (1 replies, posted in Bug reports)
Here is a tentative sum up of what is known about these defects so far.
Please any additional infos or other defects specific to saving.
1. Saved files are 0 bytes or not created at all.
Reproduction scenario :
- Open a video in the program VirtualDub and do "save as avi" uncompressed. (default value in compression options)
- Open resulting video in Kinovea: reading is fine.
- Save video to file, the progress bar appears and disappears instantly.
- Resulting file is 0 bytes or non existent.
- No error message is displayed.
Expected :
- Video saved to file correctly.
- In case of an error, an error message should be displayed.
Workaround :
- Do not use the uncompressed mode of VirtualDub, go to Video > Compression and choose a codec from the list.
Root cause analysis :
- Unknwown at the moment.
Estimated date of fix :
- Unknown at the moment.
2. Saving progress hangs at some point, memory usage peaks.
Reproduction scenario :
- Video is in normal mode (not analysis mode where frames are uncompressed to memory)
- Save the video to file, starts fine, then goes slower, then hangs.
Expected :
- Video saved to file without memory usage increase.
Workaround:
- Do not save videos in normal mode. Restrict the selection until it goes to Analysis mode before saving.
Root cause analysis :
- Memory leak in the saving process.
Estimated date of fix :
- Fixed. Available in next release.
3. Saving causes the application to crash.
Reproduction scenario :
- Unknown. Please provide one if you experience this issue. (Include error log from Windows if possible)
4. Saving function creates files much bigger than original.
This is to be expected for the moment. Will be fixed later on.
Conflicting goals : simplicity of usage, quality of output, size of file, readability of the code.
1,896 2009-05-25 15:23:10
Re: Kinovea 0.7.10 - Bugs and defects go here (11 replies, posted in Bug reports)
Hi,
There are several issues with saving, not all with the same causes, so it makes it a bit hard to manage.
I'll try to clear things up in a separated thread, and ask for more details on scenarios, etc. there.
Thanks.
edit: ok I've created the thread here.
To me, it sounds like your problem is not related to RZHC's one (which is the #1 from the other thread), but most probably #2.
See if the proposed workaround work or not.
1,897 2009-05-23 15:04:52
Re: Toutes les suggestions et leurs chances d'intégration (6 replies, posted in Français)
Mise à jour du Samedi 23 mai 2009. (Le post d'origine a été modifié en conséquence)
Changement de statut :
->
- (Fichiers) Nouvel onglet avec dossiers favoris.
->
- (Fichiers) Possibilité de renommer les fichiers depuis la vue des miniatures.
->
- (Fichiers) Possibilité de supprimer les fichiers depuis la vue des miniatures.
->
- (Capture) La possibilité d'une retransmission décalée de quelques secondes de la source.
->
- (Images clés) Pouvoir masquer de façon plus permanente la zone des images clés.
->
- (Chronomètres) Compte à rebours
->
- (Données) Visualisation sous forme de tableau.
->
- (Données) Passerelle OpenOffice calc.
Nouveaux :
- (Lecture) Nouveau format d'affichage temporel : "Temps + numéro image".
- (Lecture) Lecture à reculons.
- (Lecture) CTRL+Up et CTRL+Down modifie la vitesse par tranches de 25%.
- (Images clés) Séparer le traitement du titre et la mise à jour du temps dans les miniatures.
- (Images clés) Pouvoir mettre à jour le titre de l'image clé sans passer par la fenêtre de commentaire.
- (Données) Passerelle MS-Excel.
- (Données) Passerelle navigateurs web.
- (Export print) Kinogramme basique dans une image composite.
1,898 2009-05-23 01:48:54
Re: Version Mono - Linux (5 replies, posted in Français)
Le dépot SVN est sur CodingTeam : http://codingteam.net/project/kinovea/browse
L'accès par un client SVN se fait via http://svn.codingteam.net/code/kinovea
(Note: Il est mis à jour par vague, lors de la disponibilité des versions expérimentales.
Dans l'état actuel, il est donc synchro avec la version 0.7.10)
edit: Précision, depuis début 2009, le dépot SVN est mis à jour au fur et à mesure du développement.
1,899 2009-05-15 12:29:35
Re: Fichier WMM (1 replies, posted in Français)
Bonjour,
Il s'agit du fichier projet de movie maker ?
Du coup il est possible qu'il ne contienne pas vraiment de vidéo mais seulement des points de coupe, des effets de transition etc.
Je pense qu'il faut repartir de Windows Movie Maker et exporter vers un format vidéo (avi ou wmv). (Fichier > Enregistrer le fichier video... )
1,900 2009-05-04 15:06:46
Re: Overlay video (6 replies, posted in General)
No, it's not possible for the moment...
1,901 2009-04-30 14:31:08
Re: impossible de lancer le logiciel (1 replies, posted in Français)
Bonjour,
La dernière version est la 0.7.10, le programme d'installation fait 8,94 Mo.
(il est plus petit que les anciennes versions car la compression à été modifiée, mais c'est bien la nouvelle version)
C'est uniquement cette version que vous devriez tenter d'installer.
Pouvez vous m'envoyer le rapport d'erreur en question par mail (joan at kinovea point org) ?
(alternativement vous pouvez créer un rapport de bug ici)
Merci.
1,902 2009-04-30 14:22:42
Re: Playing Kinovea movie in Windows player (2 replies, posted in Bug reports)
Hi,
The avi files should be readable in Windows Media Player using Mpeg4 compatible codecs...
=> XviD, ffdshow or Divx codecs should work fine.
1,903 2009-04-22 14:19:30
Re: Praise and suggestions (3 replies, posted in General)
- No, it doesn't always warn me when my work hasn't been saved yet, at least when it's just key images, so I loose them quite regularly...
Hum... sorry for that. Would you have a scenario that I could follow that would expose the issue ?
Also, using comments is not as easy as I thought it would be (...) It would be much easier to just click on the comment text underneath the key image, and be able to enter the text right there without using that extra window. That would speed things up a lot.
I think that should be feasible for the title (headline). It didn't occurred to me but yes, I can see how that will be much more efficient.
Here's some more comments I collected:
- hitting the space bar to play doesn't work when the cursor is over the key images
- a shortcut to create a key image?
The shortcut is 'F6' key. Others are listed here : http://www.kinovea.org/help/en/403_Shortcuts.html
Thanks.
1,904 2009-03-31 12:15:11
Re: Quelles seraient vos priorités pour la version 0.8 ? (30 replies, posted in Français)
Bonjour, Petite réponse rapide,
Concernant les distances et la fonction proposée par Dartfish (telle que je l'ai compris):
On peut effectivement spécifier manuellement la distance d'un segment donné (référence) dont on connait la taille par avance. La taille des autres segments est calculée en partant du principe que les longueurs réelles sont proportionnelles aux longueurs à l'image...
C'est vrai en 2D mais loin d'être vrai en 3D. (distance à la caméra, ouverture de l'optique, perspective, etc.)
Pour moi une telle fonction est très trompeuse dans la mesure où elle donne l'impression de calculer des tailles relatives alors que le moindre décalage d'alignement, sortie du plan perpendiculaire, etc. fausse tout les calculs.
Le problème étant qu'il est visuellement impossible de vérifier si les conditions d'alignement etc. sont réunies pour que la justesse des mesures soit assurée.
Le manuel d'utilisation de DF s'entoure d'ailleurs de nombreuses précautions d'usage.
S'il s'agit juste d'associer un texte à un segment, peut-être qu'un objet "label" bien positionné suffit ?
Pour une vraie mesure de distances relatives, comme évoqué dans d'autres sujets, je pense qu'il faudra passer par une amélioration de l'outil "grille de perspective".
Un mode "compte à rebours" dans l'outil chronomètre à été implémenté et est en cours de tests.
Il sera dispo dans la prochaine version (date de diffusion encore inconnue). ![]()
1,905 2009-03-31 09:13:04
Re: Praise and suggestions (3 replies, posted in General)
Hi,
thank you for all the suggestions and kind words.
- Play in reverse (backwards); helps to judge animation
- Have a shortcut or button to quickly set the playback speed to 25%, 50%, 75, 100,... I use those the most and it always takes some time to get there...
Yes... This will probably end up as CTRL+UP and CTRL+Down to move the speed slider to the next 25% spot.
I think it would be better not to have an additionnal button in this area not to clutter the interface... (?)
- Upon exit, a warning would be nice if stuff hasn't been saved. (i think sometimes there is one..?)
It should warn you if you have changed or added key images and/or drawings. If it doesn't, then there is a problem.
- Love the tracking feature, but it would be even cooler to be able to stabilize the background plate with it! Reference material is often filmed by hand, so it's jittery, which makes it hard to concentrate on the motion
Well, this will be part of a long term work to provide functions that completely decorrelate the background from the moving foreground.
- when switching from timecode to frame display, the key images don't reflect that change; would be nice to have the option. Now they have to be deleted and re-done.
Ah, that... This is really one point where I seem to have failed to communicate what I had in mind...
Actually the little text you see under the key image thumbnail is not the timecode per se. It is the key image title.
It so happens that the title is defaulted to the current timecode at the time of the key image creation.
You can change the title by clicking the "Show Comments" button.
From the feedback received on this, I guess it would make more sense to actually always put the current timecode in there, instead of the title, which may not be used so much.
Or better, make the title dynamically follow the current timecode and time format unless the user has explicitely changed the title. That way we get both functions.
thanks.
