Yes, forgot to mention that some thinking is also needed to handle the various cases of camcorders / screens.
This is probably on of the first thing to discuss.

So, basically as a user, we would be able to use the "View" menu to prepare the workspace : select one capture screen, select two capture screens, select a hybrid mode where you have one capture screen and one playback screen.

We need to clear up the user interactivity here because there are many possible scenarios. I'll give them names just in case we need to refer to them later.

Possible screen combinations :
S1 : 0 screen.
S2 : 1 playback screen.
S3 : 2 playback screens.
S4 : 1 capture screen.
S5 : 2 capture screens.
S6 : 1 playback screen + 1 capture screen.

Possible number of devices connected:
C1 : 0 camcorder
C2 : 1 camcorder
C3 : 2 camcorders
C4 : 3 or more camcorders

There are two kind of interactions here:
1 - The user plugs a camcorder to the computer. What do we do depending on the current screens cofiguration + number of camcorders already connected ?
2 - The user changes screen configuration. What do we do depending on the number of camcorders connected ?

Each and every combination will need to be taken into account at some point in the code, so it would be really nice to have a consistent and sensible behavior.

Examples for interaction 1 - The user plugs a camcorder to the computer.
S1 (0 screen) : show a dialog box inviting the user to display a capture screen. If there are already other connected devices, display a list to choose from ?
S2 (1 playback screen) : Should we display a dialog box ? Should we create a capture screen automatically ?
S3 (2 playback screens) : Should we display a dialog box ?
S4 (1 capture screen) : Is it already linked with another connected device ? if not we should directly link the device with this screen. If yes, what do we do ?
S5 (2 capture screen) : Is there an unused screen among the two ? Do we link the device with it automatically ?
etc.

OK, maybe we can group these and just need to define a globally consistent and intuitive behavior for:
- There are not any capture screen available to link the camcorder to.
- There is at least one empty capture screen that we could use.
- There is more than one camcorder that could be linked with a capture screen.
- There is more camcorders connected that we can handle.

Please anyone add your thoughts on what the behavior should be !

1,622

(7 replies, posted in General)

Thanks
Yes, being able to cancel long operations is a must !

I need more infos to be able to understand what the issue is.

When the error message appears, you should be able to click on some button to make it display the full error log.

What you are looking for is something that look like this:

************** Exception Text **************
blah, blah, blah.
blah, blah, blah.

Please copy and paste this here if possible.

Also, you may try to locate the crash logs of Kinovea as explained in this thread : http://www.kinovea.org/en/forum/viewtopic.php?id=121
If you find some files named "Unhandled Crash", please copy the content here. (or send by mail : joan at kinovea dot org )

Can you expand the details of the exception dialog and paste the exception content here ?
Also, please state which version of Kinovea you are using, and your version of Windows,
Thanks

So, this is what I came up with, it's just a rough draft / suggestions, please definitely add your thoughts and what you think we should do.

So, from my point of view : (again, do not hesitate to scratch it and input your own views)
At a very high level, we could support the following functions : 1. delayed live, 2. pause the frame grabbing and browse in recent history, 3. continuous recording to disk, 4. draw on screen.

What I mean by these are:
- delayed live : the ability to display on screen what the camera saw a few frames ago instead of what it is imaging currently.
- pause frame grabbing and browse : the ability to freeze the frame grabbing and see what the frame buffer contains, eventually save it to a file.
- continuous recording : the ability to save what is currently grabbed by the camera, or what is currently displayed on screen, to a file.

Do you think they are reasonable and compatible goals ?
Do you think there are other functions that could be interesting ?
Do you think some of these are in fact pretty useless ?

If you have some specific usage scenarios corresponding to these or a combination of these, please input them as well. Having well defined usage scenario will help for the interaction design part.

"Capture" (as in grabbing frames from a DV camcorder and processing them on the fly) is one of the 4 main functional areas that need to be addressed as soon as possible in a future stable release.

I would like as many persons as possible to help design this component which will be a key part of the project.

The areas that most need to be discussed are : what are the functionnalities offerred, how the user will interact with them, and what will be the underlying architecture.

Once we have those, we can start refactoring the current implementation of the capture screen.
(the current implementation is more or less "proof of concept" code, the architecture will probably need to be altered.)

1,627

(8 replies, posted in General)

Alexander wrote:

Could the printing option be scalable to larger picture a.s.o. ? Now the resolution drops to inrecognizable blur when there are more than 10 pictures even with HD-video. Scaling the background to postersize (A3->) before making the sequence could perhaps improve this?

Yes, there could be an intermediate dialog box to select the final pixel size…
The printing size however will depends on the dpi, I don't know if we can change that.
Currently each image is reduced so the complete "Overview" fit in the display, and this is also this size that is used when saving.

Also, one improvement that may be useful for this function is to be able to change the time resolution by mouse scrolling (the number of pictures sampled), so you start at 25 pictures for example, but you just scroll in a few times to see only 4 images (or out to get 36, 64, 81, etc.).

1,628

(24 replies, posted in General)

To all,
I have freezed and updated the translation file to the latest revision :
http://www.kinovea.org/wiki/doku.php/tr … latestfile

A few strings were added and one or two were modified. As always they are highlighted in yellow, and the missing strings in red.
This is the final round before the official release ! big_smile

1,629

(4 replies, posted in Français)

lof123 wrote:

2- Je peux récupérer les données de la trajectoire c'était un bugg de mon côté.

Ça ressemble au bug qui a été remonté. D'abord ça ne fonctionne pas, puis cela se met à fonctionner sans raison apparente.
Peut-être que c'est la première utilisation qui est problèmatique ?

lof123 wrote:

3- Par contre pour les données des images clés, lorsque j'enregistre les données sous le format .xml, je peux ensuite les récupérer sur Excel mais le tableur obtenu n'est pas organisé en colonne. je ne peux donc pas utilisé les données. C'est peut être lié à la version d'Excel 2000.

Oui, ce sont des formats qui ont été introduits dans Excel 2002…
La solution de secours sera de passer par l'export XHTML et de faire la copie…

1,630

(4 replies, posted in Français)

lof123 wrote:

1-J'ai testé le tracking avec la nouvelle version. Le tracking est bien meilleur : la vitesse d'analyse est fortement améliorée et la perte de la cible est assez rare.

Super smile
Une info qui peut être intéressante est de savoir quel type d'échecs sont rencontrés.
En gros il y a deux façons de perdre la cible pour le programme: soit la cible est à l'extérieur de la zone de recherche, soit la cible est à l'intérieur mais n'est pas retrouvée, généralement parceque l'objet à trop changé d'apparence entre les images.
Si vous remarquez que la plupart des problèmes appartiennent à l'une ou l'autre des catégories, c'est une info qui m'intéresse pour la suite.

lof123 wrote:

2-Par contre je n'arrive plus à récupérer les données de la trajectoire. Lorsque je fais "Exporter tableur" sous format XHTML puis ouvrir avec Excel, le tableur est vide. J'ai essayé avec les autres formats c'est pareil.
Je ne sais pas si ça vient de la version d'Excel (j'utilise Excel 2000) sachant qu'avant je pouvais récupérer les données des trajectoires. Dans tous les cas, le fichier ne fait que 1 ko, il est donc vide.

Ah, donc ce bug tenace est toujours là sad
Il semble que dans contexte particulier, le programme n'arrive pas à lire les fichiers qui permettent de faire la conversion.
Malheureusement ce bug est volatile et pas facile à reproduire. Je l'ai eu également à un moment, puis il a disparu sad

lof123 wrote:

3- J'aimerai récupérer le temps de chaque image clé enregistrée. Lorsque je fais "enregistrer uniquement les images clés" et que je veux ensuite les récupérer, j'obtiens un tableur Excel mais les données ne sont pas organisées en tableur et je ne peux pas les récupérer.

La technique normale pour ça est de passer par l'export tableur, mais apparament cela ne fonctionne pas dans votre cas.
le fichier .kva correspondant à "enregistrer uniquement les images clés" est écrit dans le format de Kinovea, c'est pourquoi Excel ne peut pas le formatter comme il faut.

Le vrai correctif sera de comprendre ce qui ne fonctionne pas avec l'export.
en attendant, il y a une manip un peu plus complexe à faire mais qui peut servir:

1. Renommer le fichier .kva en .xml
2. Trouver le fichier  "\Kinovea\xslt\kva2msxml-en.xsl" du dossier d'installation et le copier dans le même répertoire que le fichier de données.
3. Editer le fichier de données (anciennement .kva) et ajouter en seconde ligne (entre le prologue XML et le tag <KinoveaVideoAnalysis>) :

<?xml-stylesheet type="text/xsl" href="kva2msxml-en.xsl"?>

4. Ouvrir le fichier de données depuis MS-Excel, celui-ci va demander si on veut appliquer la feuille de style, cocher l'option et faire OK.

Voilà, c'est pas joli joli, mais c'est une solution de secours. Sauf autre bug, les données sont formattées, prêtes pour un copier/coller ou autre traitement.

1,631

(7 replies, posted in General)

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.

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,633

(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,634

(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,635

(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 ! smile
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.