I don't have problems when checking out… Even as anonymous (I just cleared out authentication data to check, and I can still check out the trunk)

If someone else can give his/her experience ?

1,487

(3 replies, posted in Bug reports)

Hi,
At first I would say this look similar to bug 214.
It does that for some files, still trying to find a workaround.

In the meantime, what you should do is save the keyframes in their own file. Choose the last option on the save dialog, and it will create a .kva file containing data of the keyframes, drawings, comments, etc.
If you keep the defaults (same name and same folder as the original video), it will be automatically opened and loaded when you reopen this video.

However, your de-synchronization seems to be pretty important, maybe it's a different issue. If possible, attach a small video sample to the bug (less than 1MB).

Hello,
Thanks for the pointer, I didn't know this software. I'll try the demo version.

However, as of now the Capture feature has been architectured around the other approach: an in-memory buffer that will cache frames.
From the coding perspective with such a buffer, displaying the frame from 5 seconds ago is about as easy as displaying the most recent one. We just retrieve from a different spot in the buffer.

I think that for the targeted applications (self-coaching and continuous feedback for a rotating group of students), a delay of a about 15-20 seconds would be enough (?). The athlete performs, and then come by the laptop to watch back.

For sports that takes longer attempts, or when it takes too much time to come by the computer (swimming pool comes to mind), then maybe recording and watching the recorded video will be a better approach.
For example it's possible to set the workspace to "One capture screen and one playback screen". Then you can drag the recorded files to the playback screen to watch it back, while the other screen is recording the next person.
Any feedback on this use case is welcome too, it may be be heavy on computer resources.

Yes, if you use for example high speed camera at 500fps or so, and zooming to see only what you are intersted in, these treatments will not be very interesting.
In this case, the high frame rate is already a very powerful tool for analysis.

It is most interesting for scenes where we can see the whole person moving relatively to the background smile

1,490

(1 replies, posted in Bug reports)

Hi,
Thanks for the report.

Would you have a link or a copy of the file that you could share ?
(for example by mail to joan at kinovea dot org if less than 2 or 3 MB).

Do you know what is the original size of the movie and the wanted aspect ratio (16/9, 4/3) ?

(Best is if you can have a sample of less than 1MB that I could attach to the bug tracker for reference).
Thanks

Hi,

I create this thread to gather comments of the community about the site as a whole, the forum, the wiki, the help files, etc.

So how could the site be improved ? What about the forum ? The overall communication to the outside world ?

For me, I think I answer too quickly on the forum. By doing so I feel that I don't let other members step in and become more involved. I will change this in the future.
I think I will try to step aside, and let users answer users questions as often as possible. After all, you are better placed than me for peer help.
Questions like « Can we do this, how to do that » should be answerable by most users that have used the software for some time. Sometimes, even I need to do some research to answer, whereas one of you may have the answer right away.
(So if you see an unanswered question, don't hesitate and don't be afraid. wink)

What should be different in the way the project is organized (site, forum, wiki, help, videos, release cycle, communication, etc.) ?
Thanks

1,492

(3 replies, posted in General)

Yes, you can use the menu Motion > Reverse… then you can do whatever you'd do with a normal video.

The menu is only active when the segment is sufficiently small to be held uncompressed in memory (relative to the Working Zone memory settings in the preferences).

TeamTermin wrote:

I used a Sony video camera attached via a fire-wire connection.  During capture, the screen flickered again, like I had mentioned to you before in a previous post.  Play back of the files after capture looked good and played back smoothly.  The screen flicker during live capture does not seem to affect the capture quality.

Hope that helps...

Thanks for the report.

Currently I do not have access to a Windows Vista or Windows 7 computer, my main machine is under Windows XP and I don't plan to change in the coming months.
Unfortunately, Firewire connexion doesn't work under emulated operating system, so basically, I cannot test.

People, this is a call for contributors, if you have Windows 7 (or Vista) and a DV Camcorder, and you're not afraid of C# programming, you can help (check the wiki here for starters).

1,494

(3 replies, posted in General)

Can you be a bit more verbose, I don't understand what you are referring to… smile

1,495

(6 replies, posted in Français)

Version expérimentale : elle a besoin de vos retour d'expérience pour s'améliorer !

L'installeur est [s]dispo ici[/s]. Voir topic 0.8.11 smile

Nouveautés principales de cette version :

Outil cercle
En cliquant sur un cercle ajouté, vous verrez un changement de couleur sur une portion du cercle en bas à droite. Vous pouvez faire glisser cette zone pour changer la taille du cercle.

Représentation du temps "Total en millisecondes"
En plus de la notation classique ou du "numéro des images" vous pouvez maintenant utiliser cette représentation purement numérique.

Correctifs : bugs 214, 220, 221.

Des correctifs ont été apportés dans l'écran de capture, mais le clignotement de l'image pendant l'enregistrement (Windows Vista et 7) est toujours présent.
Utilisateurs de Windows 7 : si vous avez activé une des options "moyen - 150%" ou "grande - 200%" dans le "Panneau de configuration > Affichage" vous constaterez des soucis au niveau de l'interface graphique. La correction est en cours, en attendant le seul contournement connu est de rebasculer en "petite - 100%".

Capture d'écran : quelques cercles.
http://www.kinovea.org/screencaps/0.8.x/circletool.jpg

1,496

(4 replies, posted in General)

This is an experimental version : it needs your feedback to improve itself.

The installer is [s]available here[/s]. Go check 0.8.11 instead tongue.

Most important things in this version:

Circle tool
When you click on a circle drawing, you will see a change of color in the lower right part of the circle. You can drag this zone to change the size of the circle.

"Total milliseconds" time representation
In addition to the classic time or the "number of frames" you can now use this purely numerical time representation.

Fixed bugs : 214, 220, 221.

Some fixes were done in the capture department, but image flickering during save for Vista and 7 is apparently still here. (use the dedicated thread for capture related stuff)
Windows 7 users : if you have activated the "medium - 150%" or "big - 200%" option in "Control Panel > Display", you'll experience some problems in the user interface.
This is in progress. In the meantime, the only known work around is to go back to "small - 100%".

Snapshot: Some circles.
http://www.kinovea.org/screencaps/0.8.x/circletool.jpg

1,497

(7 replies, posted in General)

Hello,
You can convert the file beforehand in VirtualDub.
Once the video is loaded, you go to Video > Filters, button "Add…", then select "rotate" or "rotate2" and click OK.
To save back the video, you can select a codec in Video > Compression… and then save with File > Save as Avi…

I will try to document my efforts to implement chronophotography and other advanced visual effects in this thread.
There is a long road before any of these makes it up in Kinovea, but an important milestone was reached this week-end so I create the thread.

The first step of almost all these effects is to compute the motion of the camera.
This is equivalent to computing how to transform each frame so it looks like as much as the previous frame as possible, and do it for all the frames in the sequence.

The transformation parameters can be combined together, so basically at this point we can map each frame on the first frame of the sequence.
We can visualize the frames boundaries and compute the total size of the background.

http://www.kinovea.org/screencaps/0.8.x/exp-jump-skeleton.jpg
Frame borders transformed and positionned against the virtual background. (high jump sequence same as below)

.
The second step is to compute an image of the panoramic background without the person moving in the foreground.
To do this we compute back all the contributing images to a given location in the final background. This gives a list of pixels each from a different frame of the video, most being of the color of background, some being the person when passing in foreground. The trick is to compute a pixel representative of the background using this group of pixels.

For this experiment, I used the median pixel of the group. It gives good results and it's easy to compute.

Here are some reconstructed backgrounds (with some pictures extracted from the corresponding videos for reference).

http://www.kinovea.org/screencaps/0.8.x/exp-jump800.jpg
High jump sequence. Distorsion accumulates on the left.

http://www.kinovea.org/screencaps/0.8.x/exp-fixie800.jpg
Fixed-gear bicycle sequence.

.
To be continued…
big_smile

This should be fixed in the next release.

Hi,
It's sounds like an interesting use case (and challenging smile)  However I thinks it's important to make sure the capture screen is robust enough and well functioning in its current implementation before attempting other sources.
(Maybe check LongoMatch software, he just added capture too during the summer. He is using a somewhat more versatile library for capture, maybe it already does network sources… And it is more tailored towards team sports too)