Hi,
In recent versions there are two different concepts for tracking.
Trajectory tracking is done by directly right clicking the video. This corresponds to the behavior in previous versions. Kinematics are only available in this mode.

There is also drawing tracking, where the points comprising the drawing (marker, line, angle, etc.) are tracked independently. This is done by right clicking the drawing. If you first add a marker and then right click it and "follow trajectory" you will be in this mode.
With this type of tracking the boxes are not visible. The marker should be attached to the imaged object though and if you move the playhead it should follow whatever is beneath it.

Please give more details as to which tracking type does not work.

Hi,
There is usually two ways to connect to industrial cameras, through a generic DirectShow filter or through special code based on an SDK provided by the vendor.

The DirectShow interface is simple and doesn't have all the options that the camera exposes and usually doesn't provide the same performance either. The SDK is the proper way to go but requires special code and most importantly an actual camera for testing.

Unfortunately currently Kinovea only supports IDS cameras through the DirectShow filter.

Hello,
Has anyone tried this camera ?
Ref: http://www.samsung.com/us/photography/d … C200ZWAXAR

I'm intrigued by the fact that it has a full blown Android OS on board. Maybe the potential for full programmatic access to the hardware?

Browsing the manual it seems to be the usual still-images oriented camera, with manual shutter speed only available for photography, not video.
The question is, do the installed applications have access to the low level camera hardware to change shutter speed of video? I would guess they have the same access as smartphone applications to the phone camera… Which I don't think include shutter speed (But haven't looked deep into this).

The idea of being able to write programs running directly on the capture device is certainly appealing. I don't know if the model is sufficiently open yet…

Thank you.

On my machine the following System variables have been created during Basler software installation:
PYLON_GENICAM_ROOT
PYLON_GENICAM_VERSION
PYLON_ROOT
PYLONC_ROOT

The value for the last one is "C:\Program Files\Basler\pylon 4\pylonc" on my machine.

Thanks for the logs.
I'm mostly interested in the logs for 0.8.24. There won't be any modifications on top of 0.8.15.
Fortunately, log.txt.1 is new to recent versions so it contains 0.8.24 log.

The error there is the following:
System.Exception: Environment variable PYLONC_ROOT not found. Install the pylon C Runtime.
   at PylonC.NET.Bootstrapper.Initialize()
   at PylonC.NET.Pylon..cctor()

The way it is supposed to work is: Kinovea embeds a "wrapper" library published by Basler that acts as a bridge between the program and the rest of the Pylon stuff installed on the machine. This library looks for the environment variable to know where the rest of the Pylon DLL are located.

Please check if you have such an environment variable, I imagine it should be set during Pylon installation. (Right click My Computer > Properties > Advanced system settings > Advanced > Environment variables). I will look on my machine tonight to confirm.

By thumbnails I was referring to the camera thumbnails from the camera explorer. Considering the nature of the failure I would guess there is no thumbnail at all though.

OK thanks.

Logs: please try to get in the camera configuration (in Kinovea) anyway and after it fails collect and send me the log by mail ("log.txt" and "log.txt.1" reachable from Help > Open log folder).

Now that I try it differently, there seems to be issues with memory that I hadn't noticed before. Please go to Options > Preferences > Capture > Memory. What is the current value of the slider? Try and decrease the memory allocated for capture buffers to something low, like 150MB, then retry and report.

Another question: is the thumbnail correct or is it all black or something else?

Hi,
Thanks for the details.
Indeed 0.8.24 has specific code to use the Basler "Pylon" libraries while the older versions were relying on the rather limited DirectShow filter. It improves Kinovea awareness of the camera capabilities but I could only test with one specific camera (a 50fps grayscale Ace).

Are you on Windows x64 or x86 ? Which version of Windows ? Did you install Basler software in x64 or x86 ?
It was only tested with the x86 versions of Basler Pylon libraries since Kinovea 0.8.24 is an x86 app.

Does it let you go in the camera configuration window in Kinovea and change some options?
What options are listed in the Stream format combobox ?

Did you install the Basler viewer application ? I noticed that sometimes I have to launch it first and make sure I can see the camera stream there, before it can work properly in Kinovea.

No, at the moment you can't rotate the image in Kinovea.
It is something I would like to look at in the future but haven't had time to get to.

However, if someone has a small sample video that automatically turns itself upright in other players because of a flag in the file, I'm interested in such a file to bootstrap experiments.

820

(1 replies, posted in Français)

Bonjour,
Effectivement il semble que le driver Windows pour la PS3Eye soit devenu payant…
Dans tous les cas le driver ne supportait qu'une caméra à la fois.

À l'heure actuelle pour la capture en live il y a des webcams de meilleure qualité comme la Logitech C920. Par contre elle est plus chère et filme à 30fps max (mais en 1920×1080, contre 640×480 pour la PS3Eye, ce qui fait une grosse différence sur l'exploitabilité des vidéos à mon avis).

Sinon en mode un peu plus expérimental il y a une webcam chinoise peu chère, ELP-USBFHD01M, qui fait 1280×720 @ 60 fps, mais la qualité d'image n'est pas même niveau que la logitech.

It is grouped under the line tool.
You must press the line tool button down until the popup menu with the extra tools appears. Similarly, the other tools that have the tiny triangle in the top-left corner have other tools grouped under them.

822

(28 replies, posted in General)

There is no written guidelines regarding Basler cameras at the moment.

Can you expand a bit?
- Which package did you download and install from Basler? Was it x64 or x86, and are you on Windows x64 or x86?
- Do you see the camera thumbnail or not?
- Do you have a color or monochrome camera?
- Do you have the same issues if you start by using the Pylon viewer, connect to the camera there, close the viewer, and then open Kinovea?
- Can you open the log.txt file and search for "Basler". Paste any corresponding line found.

Thanks

823

(28 replies, posted in General)

In the next version the behavior will be to read the value under Control Panel > Region > Formats > Additional settings… > List separator. The value can be ";" or ",". Then use this value as the separator for exported files and clipboard data. It should provide at least self consistency for a single machine and will work without issue as long as the files are shared with users of the same culture.

It is also the value that is used by Excel at import. You can set it to ";" in the meantime if you don't fear loosing compatibility with other applications.

824

(28 replies, posted in General)

I'm not a heavy user of Excel but I think there is a button in one of the ribbon tabs where you can specify the field separator character when importing.

The problem with using a comma is that in some locales like French it is the decimal separator and it would mangle numbers with one another. It could be an option in preferences though.

edit:
The button I mentioned will only work for copy/paste operation. It's irrelevant if you double click an exported file.
Apparently if you rename the file to .txt it will open the text import dialog which let you choose the delimiter.

825

(28 replies, posted in General)

If you are using the trajectory tool or point tool, maybe check the "Data analysis" contextual menu by right clicking the drawing.

From there you can export filtered data to a CSV file which should be read by any spreadsheet application, copy data to the clipboard, or directly export the graph as an image file.

The Excel export in the main menu will create a file in an XML format that is compatible with the version I had at the time, but I haven't checked with the most recent versions of Excel.

The text export option is mostly useful to use the data as input to another program. The CSV export from the data analysis window should be preferred in most cases anyway.