1,216

(4 replies, posted in General)

Also, maybe you can post a screen shot so we can see how severe it is, and guess the most probable cause.

bewegingstechnologie wrote:

Hi Joan,
I've installed all the components and compiled the latest version, but immediately I get an error
on ScreenManager   = new ScreenManagerKernel();. Does this have anything to do with the
visual studio version? I'm running 2010. Also I've noticed some references of the root project
aren't recognized (FileBrowser, ScreenManager, Services and the Updater), is this right?
Best regards,
BT

Hi,
I just did a "check out" from SVN in a separate directory to verify. I didn't have any issues. (Just need to make sure it's compiling for "x86", not "AnyCpu").
I am not using VS2010 right now, so I can't really say if differences in configuration is the source of the problem.

For the references, try to delete them and add them back maybe… I have had to do this with some other projects.
Go to \Root\bin\x86\Debug and check that the dependencies were copied properly: AForge dlls (x5), av* dlls (x5 + postproc-51.dll, + swscale-0.dll), OpenCV cv*.dll (x3) + Emgu (x2), SharpVector (x6).

I don't know if VS is setting some options by default, but the target framework should be set to "2.0".

Thank you very much, it helps a lot!
I am not a native speaker so pinpointing the right expression is often challenging.

I agree the term "tool" is not really meaning what is intended here. "Drawings and tool results" / "drawings and tool outputs" sounds a bit heavy for some reason, I'll give it some more thought.
Here are some of the terms that have been used (or not) to describe the output of the tools, etc.:
- Analysis
- Key image data
- Analysis data
- Metadata
- drawings and tools
- drawings and other tool results
- drawings
- drawings and other analysis objects
- Analysis objects

(last two just added - "Analysis objects", is that too abstract? )

(edit: You're definitely correct about the tracking tool. There is not really any point trying to re-track on top of the saved video)

1,219

(13 replies, posted in Français)

Je ne suis pas spécialement le mieux placé pour répondre, ce serait bien que d'autres utilisateurs nous fassent part de leur expérience !

Si c'est pour utiliser avec le module de capture, une bonne webcam devrait aller. La PS3Eye (à la base pour la PlayStation mais un internaute a écrit un pilote gratuit pour Windows) a pas mal de succès il me semble car elle est peu chère et permet de monter à plus de 60 images/s en 640x480 pixels. (à condition qu'il y ait une bonne luminosité quand même)

Pour le problème de recul s'il n'y a vraiment pas la place, voir si une caméra avec une lentille grand angle pourrait corriger le problème, mais là c'est plus le même budget !

1,220

(1 replies, posted in Français)

Tout ce qui est mesure de distances, coordonnées, suivi de trajectoire, calcul de vitesse, etc. est très sensible à la perspective.
Il est malheureusement quasiment impossible de faire des mesures vraiment rigoureuses à partir de la vidéo seule.
Donc n'oubliez pas que les mesures seront des ordres de grandeur, qui seront plus ou moins précis en fonction de la mise en œuvre.

La règle n°1 est que tout ce qui est mesuré doit être sur un plan parallèle au plan de l'image.
Pour plus de détails voir la page mesurer des distances.

1,221

(1 replies, posted in Français)

Il y aura peut-être un outil pour indiquer les rotation dans une future version…
Pour l'instant la seule option est de dessiner la flèche à la main avec l'outil crayon.

Oui c'est un problème connu et malheureusement compliqué à corriger.
Pour l'instant il n'y a pas grand chose à faire hmm

Well I wish there was a way to express the subtleties of the various options and be concise at the same time, but yes, the dialog will probably have to be more verbose to work.

I mix and matched ideas from your post and what I had in mind.
Here is the new tentative. Feedback appreciated on wording, grammar, etc.

http://www.kinovea.org/screencaps/0.8.x/savedialog.png

Guidelines
- Forbidden/obscure words: metadata, stream, muxed.
- option title: as simple as possible while retaining the meaning and not be ambiguous with other options.
- hint text: explain what will be saved and what will be the behavior of the exported file in other players as well as in Kinovea.

1,224

(6 replies, posted in Bug reports)

I tried various combinations but I couldn't reproduce the issue. Whatever I do, the mirrored video in the dual file exported is fine. Is there any specifc context I am missing ?

One bug I stumbled upon, when saving a single video with the mirror option, it's not mirrored.

1,225

(6 replies, posted in Bug reports)

www.kinovea.org/bugs/

Thanks for the samples.
I confirm the videos will work in next version.

1,227

(6 replies, posted in Bug reports)

Thanks for the report.
Can one of you guys add it to the bug tracker ?
Thanks.

1,228

(5 replies, posted in Bug reports)

Re: Drawing loosing sync with the video. There is maybe a remaining issue with a specific input format / framerate and MKV as output format. Please detail your case.

Re: other experiments.
- It is not normal that key images with no drawing don't show up in the slide show export.
- The persistence (ghosting) is irrelevant for slideshow saving.
- There shouldn't be any limit to the number of key images to be exported in the slide show. Admittedly it wasn't tested thoroughly, so maybe there is a bug somehow.

To make further experiments and help with the diagnosis:
- Deactivate the ghosting if you want (Options > Preferences > Drawings > Persistence > uncheck "Enable persistence").
- Identify the key images by drawing big numbers on them with the pencil tool. Then check what goes out in the exported video.

Thanks

1,229

(1 replies, posted in Bug reports)

Did you use the "Save video with a pause on each key image" saving method ?

1,230

(1 replies, posted in Bug reports)

Hi,
The problem is in Kinovea, not with the file formats. It is a known problem but quite tricky.
Sorry for the loss of time information in your analysis session.