Hi,
Regarding the angle tool: use the little circles at each line end to move the lines around.

1,697

(3 replies, posted in General)

Hi,

I would suggest trying out LongoMatch, because the notational analysis sub-project is not going to be included any time soon in Kinovea. (The current focus is more on analysis of short performances, exercises and small sequences inside longer ones).

LongoMatch is an ongoing open source project for games analysis.

1,698

(4 replies, posted in Ideas and feature requests)

Thanks for the clarification. smile

1,699

(4 replies, posted in Ideas and feature requests)

Hi,
Yes, it would be a great addition smile
What do you mean by "with keydata"?

1 - The drawings added on each video appear in the final combined video. (same as "Permanently paint key image data on the video" option)
2 - Being able to save each video's key image data in a non-destructive way, inside the combined video.
(same as "Combine video and key images data in the file" option.)

Ok. You could try to open one of them anyway from the file list on the left panel. It probably won't run, but we may get an error message that will be more explicit regarding the cause of the error.

If possible, create a new bug in the bug tracker and attach the log.txt file (see the topic "what to do in case of a bug") and possibly attach a small video that expose the problem.
Alternatively, you can send the log and the video (if not too large) to joan at kinovea dot org, and I'll create the bug report.

Edit: If you do have some small files, it would be interesting to have 2 different files, one that work and one that doesn't. (There must be a difference somewhere…)

Hi,
If I understood:
- You have several videos in a folder on your computer.
- When you browse to this folder from within Kinovea, you don't only see some of the videos files.

Is this correct ?

1,702

(2 replies, posted in Français)

Bonjour,
Non, il n'existe pas pour l'instant de version compatible.
Plus d'infos:
- Autre fil sur le même sujet.
- Et un autre fil sur le même sujet.
- Autre fil dans le forum anglais.

So, I was downloading some YouTube video when I thought about this… This will probably never turn into a feature but I need to write it down before it's lost forever big_smile

It has to do with the ability to retain the metadata in a usable form between loads (comments, drawings, paths, etc.).
Currently, there is a saving option in Kinovea that let you combine the metadata and the video in a single file (or you can save the metadata in their own file somewhere else).

But if you want to upload it to YouTube or something, obviously you need to burn the drawings on the images, and you'll loose the comments.

This is because YouTube will change the format of your video and re-encode it, so even if you download it back, you only get raw images.

But how do you transmit metadata so they survive to format change and re-encoding, and stay editable when you open the video on the other side?

The idea would be to add a special image as the first frame of the video, containing a 2D bar code:
http://upload.wikimedia.org/wikipedia/en/thumb/4/42/Wikipedia_mobile_en.png/150px-Wikipedia_mobile_en.png

This kind of matrix code can contain several Kilobytes of data, and that might be enough to transport the drawings and path stuff, or maybe the comments.
When you redownload the video from YouTube, (using a firefox plug-in for example) and open it in the software, it would detect the bar code on the first frame, translate it back to the metadata, and display the comments.
If the website encoding doesn't completely kill this specially crafted image, it could work.

Or it could also be used to transport metadata in files that don't support it initially. (Currently the only option is to use the MKV container).

/end of thoughts dump

1,704

(24 replies, posted in General)

Great smile
Please check the wiki page to get started.

There hasn't be any language with non-roman alphabet yet. I think it would be best if you can send a first draft with just a few strings as soon as you get started. This way I can try to import the draft, see if there are any general compatibility issues, and eventually get them fixed.
Thanks

1,705

(1 replies, posted in General)

Hi,

No the source code is now only available from the svn repository.
You need a SVN client like TortoiseSVN to grab it, but it's fairly easy : once the SVN client is installed, you create a new folder, right click it and do "SVN Checkout".
You then give it the source tree url, for example http://svn.codingteam.net/kinovea/trunk/

Note that you then get the very current code, it should compile but it might not be ultra stable. Older releases have been archived in /tags/

1,706

(8 replies, posted in General)

I'm seeing more and more videos of weightlifting paths done in Kinovea popping up on internet here and there. That is great ! big_smile

I guess the next step (apart from displaying more infos on the path) would be to have an easy way to visually compare two or more bar paths together. And that would certainly be useful for other sports and activities.

So let's throw some ideas and have them incubate until this can turn into a nice handy feature smile
(We can save the data as .kva and reload in another video, but I think we could have something more dedicated/powerful)

Bonjour,
Non, ce n'est pas possible pour l'instant. sad
Cela fait partie des suggestions qui ont été soumises, mais pour être honnête, ce ne sera pas pour tout de suite. (cela passera certainement après la gestion du son en entrée, car il faut que la vidéo intégrant les commentaires audio puisse au moins être relue correctement par le programme lui même).

1,708

(2 replies, posted in Ideas and feature requests)

Hi, thanks.
Some quick comments

Saf wrote:

The line tool becomes inactive if you move forward or backwards through a frame, would be useful to have it remained active.

Well… As you can see there are 3 possibilities here :
1 - instantly fall back to the "hand" tool after any use of the tool. (Angle tool, Text tool) This is because it seems more logical that the user will want to move the new drawing around or use another tool right away.
2 - keep the same tool while in the image, but fall back when changing frame. (Line tool)
It seemed to make more sense. The person is putting a bunch of lines on a specific image, possibly to highlight alignments, but when he moves out, he might aswell use another tool or move an existing drawing around. We really don't know so we fall back to the default behavior which is the "hand" tool.
3 - keep the same tool even when changing frame. This specific case is only for the cross marker (scenario: spotting a moving person or object over several frames) and the pencil (scenario: animation commenting)

This is not set in stone. It will be easy to make the change for the line tool to stay active when changing frames, but I'm not sure it is the right thing to do…

Saf wrote:

Persistence over a single frame would be good. At the moment its lowest number is 2 frames (unless you do it manually for every line shape, for every frame)

In Kinovea terms, persistence is staying on screen for more than one frame. To have the drawing visible only on the key image, you'd have to actually turn persistence off in the general preferences. (In this case the drawings won't be visible at all while playing, but they will be visible when manually browsing the frames.)
Does that match your expectations ?

Saf wrote:

Using a Wacom tablet can be infuriating at times, as Kineova is too sensitive at interpreting a single tap, as a double, opening the configure drawing window.  Is there a way we can reduce its sensitivity (using the Wacom setup tool does not affect Kineova).

Sorry about that ! It's been reported as m170 also. It should be fixed in the next version.

1,709

(24 replies, posted in General)

Hi all.
I'm back home, if you have any localisation file please send them so I can merge into the current code line.
I have merged the new Finnish locale and updated Spanish and Italian, thanks ! big_smile

Regarding German locale, I think peusi is already working on it. Since it is an update (as opposed to a complete translation from scratch) I think should be fine.

1,710

(2 replies, posted in General)

Hi,
Awesome !

0. Coding : Yes, you are very welcome. I'm not sure about the most appropriate place to discuss design and implementation issues though.
I'll try to add more details about current implementation in the wiki pages and also expose the plans for features that are currently at design stage.
See wiki - dev docs if you haven't already.

1. Live Capture : I started implementation a few months ago and paused it lately to try to gather up for a formal release.
I have a fairly well defined idea of what I think should be in feature-wise, at least for a first version of the tool.
I will write it down in the wiki as soon as I can.

To enable the current code, go to ScreenManager.cs, and look for the following comment (around line 340)
"Disabling all capture menus during dev."
Comment the next few lines to enable the menus.
Remember this almost hasn't been tested, the interface is ugly and it's probably broken in several places too smile.

The low level capture code is done by third party open source component AForge.net. (considered using either AForge.net or DirectShowNet for the devices interface.)

2. Using deinterlace mode directly : By directly you mean to turn it on by default for all videos ? If so you can do that in the Preferences. (added in 0.8.4 I think).

3. Drawings tools : I am most definitely intersted in them. The initial plan was to combine the simple shapes (ellipses, rectangles etc.) and the custom shapes by using the SVG format to define all of the next tools. I've found an open source SVG library that would help with this.

This would open up the software even more, as anyone could design it's own shapes (in one of the existing visual SVG editor like Inkscape), put them in a special folder and have them detected and usable in the software. (and also share them easily with other users, etc.)

I'll look at the patch tomorow.
Thanks.