1,501 Reply by joan

(11 replies, posted in General)

kinoveafan wrote:

Is it possible to build something like a trigger in kinovea? When I use the software my cameras are static so could it be possible to make something like:

if ( the golfball is gone)
     keep on capturing for one more second
      then playback the last 2 seconds
      and ask if the swing should be saved". ?

Well, I'm open to this sort of stuff but so far all the implementations I have seen of this were pretty confusing in my opinion (in term of user experience / user interface). I certainly wouldn't want the casual user to have to think about how much preroll he needs to account for or force him to think in terms of predefined recording scenario…

With image size of the like of 640×480, you should have a pretty large buffer. If you can slide the delay to 30 seconds or something, that should leave you time to do the swing, go back to the computer and start recording. (You record what is currently displayed on screen, not the live)

Go to forum: General

1,502 Reply by joan

(2 replies, posted in General)

bowl1820 wrote:

I'm a new user and was wondering how the development of the motion tracking is progressing.

Hi,
The algorithm itself is more or less established (see similar snooker snapshot with version 0.8.6). There is still room for improvement, but it's considered of a lesser priority with regards to other areas. The next improvements regarding tracking will be the implementation of multi point tracking, to be able to track lines, angles, etc.

bowl1820 wrote:

I'm trying the motion tracking with tracking a bowling balls path down a lane. I've noticed some of things you mentioned above like the tracking slowly shifts away from the ball or the tracking jumping off the ball to a reflection on the lane etc. happening. (I make manual adjustments to the track when this happens).

The issue with slow drift from the target and problems highlighted in the original message should be fixed in recent versions. (Unless you are using version older than 0.8.7) so it may be something special (like attaching to a small spot on the ball).

Attaching to reflection instead of the real thing is really hard to prevent. Sometimes the reflection just look more similar to the previous image than the object itself. In any case, the automation of tracking is really meant to be an aid to manual tracking.

bowl1820 wrote:

I was wondering if it would be possible to have a circular bounding box (preferably a variable size one(handles could be added to the box so as not to interfere with the manual dragging of the box.)  that could be confined to the object being tracked) and/or maybe a way to highlight elements not to be tracked (like in part of photoshop they have a way to highlight areas to select and not select.)

The internal pattern window must be rectangular. I'm not familiar with this specific Photoshop function.

Hopefully, the ability to resize the search window should be enough to avoid these issues.

Go to forum: General

1,503 Reply by joan

(6 replies, posted in General)

Hello,
Yes the ability to display the coordinates for a specifc cross marker would be nice. I'll add it to the suggestion list or maybe implement it if I can do so quickly.

Regarding export to spreadsheet, I'm not sure what would be the best way to display these data…

Currently we just group objects by type and list their various values over time. When there are several object of the same type on the same image, we can't differenciate them. (for Tracks and Stopwatches, there is a title to help, but for lines, angles and soon single points, there is nothing).
If you have many points on the same image, I don't know you will be able to set them appart for further calculations…

Go to forum: General

1,504 Reply by joan

(4 replies, posted in Bug reports)

I think I have found the root cause, and apparently the bug has always been there, although it might have been hidden.

The underlying cause is a bit complex (see bug note), but it worked before because the default codepage on your machine contained the cyrillic characters, and apparently it doesn't anymore on your new system.

This means that non Unicode programs will have issues with these filenames (Which is the case of the low level decoding library when used with default options).

Here are some instructions to change the default codepage in Windows 7, this may help with the problem until a more general solution is implemented.


edit:
To confirm the workaround, I switched the settings for non-unicode programs to use the Russian codepage on my machine, and now I can open the files with cyrillic characters. (but files with roman special chars like éêà do not work anymore)

Go to forum: Bug reports

1,505 Reply by joan

(4 replies, posted in Bug reports)

Yes, you're right. I reproduce this right away with cyrillic characters in the filename.
I added bug231, I'll try to look at this as soon as possible, fairly critical.

I'll try with older versions to see when this started to fail and what may have changed…

Go to forum: Bug reports

1,506 Reply by joan

(4 replies, posted in Bug reports)

Hmm… Maybe you were previously using one of the experimental version?
They have a more recent version of the file decoding library, so if it's an option, you may want to try that anyway.

The error is strange though. It's not saying it cannot decode the file (there is another error for that), it's saying it can't find it in the first place…

Go to forum: Bug reports

1,507 Reply by joan

(11 replies, posted in General)

kinoveafan wrote:

The camera is really great (320*240 @125fps / 640*480 @75fps) and cheap ( 20€).

Nice specs for 20€ smile
Settings change should be in the next experimental version. We'll see if it works...

About the camera, what about depth of field? Is the image quality decent when the subject is at a distance of more than a few feets? Also, does it work well outdoors? (Sometimes the cheap captors are tailored for indoor / close range video since the main application is video chat.)

Go to forum: General

1,508 Reply by joan

(45 replies, posted in Ideas and feature requests)

About framerate / size configuration.

I have just looked at this today, it should be available in the next experimental version.

What happened before is that we took the first item in the list of the camera capabilities.
Now the biggest frame size will be selected by default, but you should also be able to change to another setting in the source configuration dialog.

Tested ok with a webcam (snapshot below). For the DV camcorder, the frame size change did not translate down to the device… to be investigated later (DV should always be 720x576 anyway, I was surprised to find an other option).

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

Go to forum: Ideas and feature requests

1,509 Reply by joan

(14 replies, posted in Bug reports)

I would like to study this issue but I can't reproduce it.
Could someone attach a log file to the bug 227 please.
(remember to collect the log right after the issue, before you reopen Kinovea, because logs are rotating. Check the log in notepad, it should have the exception text at the end.)

Thanks

Go to forum: Bug reports

1,510 Reply by joan

(2 replies, posted in Bug reports)

Hello,
From what I can read these .PGI files are not actual videos but rather meta data about timestamps, duration, and other info.
The actual files would be the .MOD ones.

Go to forum: Bug reports

1,511 Reply by joan

(1 replies, posted in General)

Hi,

First of all, when the selection is short enough to fit in RAM memory (12 seconds / 1024MB by default), it will be fully extracted and then the codec will be irrelevant. Frame by frame should be good, both ways.

For longer clips, when reading directly from the file, the best results are generally achieved with codecs / profiles that use so-called "intraframe" coding, that is, each frame is compressed independently from the others. For example DV, MJPEG, or any codec if you configure the encoder to use I-Frames only (IIRC, similar to setting the GOP size to 1 in the encoder).
(These files will take more space).

In any case, forward frame-by-frame should rarely be an issue, it's more backward frame-by-frame that can be a problem.

There are also specific codecs with other issues, depending on the encoding profile and the encoder. (.wmv / .asf files have caused issues in the past.)

Go to forum: General

1,512 Reply by joan

(1 replies, posted in Français)

Bonjour,
De quel type de vidéos s'agit-il ?
Il y a un soucis connu (bug 142, toujours en investigation) avec certains fichiers VOB de DVD, notamment au niveau de la durée annoncée…

Go to forum: Français

1,513 Reply by joan

(1 replies, posted in General)

Hello,
Currently there is no way to work around this kind of perspective issues.

Maybe later, when line tracking is in place, we could define a calibration segment and programmatically force it to keep the same size in pixels over the course of the video, by resizing the whole image around it… The range of applications of this would need to be assessed though. If someone can think of other scenario where this may be of interest ?
Thanks

Go to forum: General

1,514 Reply by joan

(9 replies, posted in General)

Interesting…
An addition on this would be the ability to drag the image around even when it's at normal view (zoom 100%).
With the combination of these two, one could directly adjust/align one image over the other in a very simple way.

Go to forum: General

1,515 Reply by joan

(1 replies, posted in Français)

Bonjour,
Deux tests possible pour avancer dans le diagnostic:
- Tester la détection de la caméra par le logiciel sur un Windows 7 classique (hors bootcamp).
- Tester la détection des périphériques FireWire sur le Windows7+Bootcamp en dehors de Kinovea. (Autre logiciel de capture, disque dur connecté en FW, etc.)
Un logiciel tout simple pour tester le lien entre la caméra et le système : WinDV

Go to forum: Français