Thanks for looking it up. OK, I'll get the latest driver and dig up the camera if I can find it and try to see what's going on.
722 2018-02-07 18:32:12
Re: 0.8.26 PS3Eye Cam bug (6 replies, posted in Bug reports)
Oh you are on Windows 7, in that case the program name in the process tab should have a *32 at the end if it's 32 bit.
It could still be this because Kinovea 0.8.24 was only released as a 32 bit app. It's only from 0.8.25 and forward that there is an x64 build. So it would be very consistent with this being the origin of the issue.
723 2018-02-07 16:32:51
Re: 0.8.26 PS3Eye Cam bug (6 replies, posted in Bug reports)
Hi,
If it's indeed a 64bit/32bit issue, it's possible that the CL-Eye test software is itself 32 bit, and that would be the reason it works with the driver. If you go to the Task manager, in the Details tab, show the "Platform" column, it will tell if the application is 32 bit.
724 2018-01-16 17:41:42
Re: Failure: Unable to open the file : inconsistencies found (4 replies, posted in Bug reports)
Try to load the file in Kinovea 0.8.26 from the download page, it has a lot of updates, including in the loading library.
725 2018-01-16 14:56:17
Re: Failure: Unable to open the file : inconsistencies found (4 replies, posted in Bug reports)
Hi,
Yeah, I haven't seen this error in a while. It happens when the loading process manages to load the file, but then when it attempts to decode the first frame something bad happens.
The exact error can be seen in the log (you can get to the log from the Help menu). It should be either "First frame couldn't be loaded" or "First frame loaded but negative timestamp", which would be my guess. In the code I have added a comment that some AVCHD files exposed the second behavior. This negative timestamp breaks a lot of things down the line for the timekeeping and so it is not supported. I think it's an encoder issue. The first timestamp shoud be zero. Some files have a positive first timestamp which Kinovea tries to work with as well. I haven't seen reports on this lately so most likely the encoder that was producing these files is either not used anymore or has been fixed.
726 2018-01-12 23:23:15
Re: Lock segments lengt (2 replies, posted in Bug reports)
Hi,
The "Lock segments length" will force the lines to keep whatever size they had when you clicked the option. So when you move the ankle joint for example, it won't move freely around, instead it will keep the size of the leg the same.
The bike fit tool doesn't display the segments length, however this can be changed in the XML description of the tool which is user-editable.
Go to Kinovea program files folder, and under "DrawingTools\Custom" open the file "Bike fit.xml" in a text editor.
Under the whole <Segments></Segments> block you can add the following:
<Distances>
<Distance point1="4" point2="5" />
<Distance point1="5" point2="6" />
</Distances>This will add length measurement for the thigh and leg segments. You can make your own changes as you like. Refer to the Segments section above for the points id.
727 2017-12-05 18:01:21
Re: For swim analysis: need rotate image function (3 replies, posted in Ideas and feature requests)
Hi,
Yeah no solution at the moment, sorry about that. Personally I use AviSynth and VirtualDub when I need to preprocess videos for rotation/crop and whatnot. But it's more of a programmer's tool and still requires to re-save the video so the workflow is not that streamlined.
This is becoming close to the top requested feature at the moment though. I will have another look at it at some point to see if doing this at the image level just before rendering is acceptable performance wise.
728 2017-11-30 16:20:27
Re: Logitec C920 (2 replies, posted in Cameras and hardware)
Sometimes for some reason you have to go into the settings for the camera in Kinovea (cog icon or click the infobar at the top) and change the stream format or the framerate to something else and apply. Then you can change back if you want.
729 2017-11-18 18:56:09
Re: Experimental version - 0.8.26 (14 replies, posted in General)
Do you see the thumbnail for the camera in the camera list tab?
Could you collect the log file (see in help menu to get to the folder containing it) and send it over at joan at kinovea dot org, thanks.
Also, try the following: right click the thumbnail of the camera and select "Forget custom settings", if you are using the installed version, to remove the settings set with the previous version.
730 2017-11-17 18:56:58
Re: Videos in Two Playback Screens playing at different speeds (9 replies, posted in Bug reports)
OK.
When you do the capture, whether in NCH Debut Video or in Kinovea, try to have almost nothing else running on the computer so the compression on the fly has more chances to sustain the framerate. Also, try to set the capture file target on an SSD if possible, it will also decrease chances of frame drops. If your camera supports MJPEG streams, doing the capture in Kinovea might give the best performance as it will store the frames coming straight from the camera without decompression/recompression.
731 2017-11-16 22:53:20
Re: Videos in Two Playback Screens playing at different speeds (9 replies, posted in Bug reports)
Hypothesis: the file on the left has non constant framerate. The capture application set a custom timestamp to each frame as it was capturing them. Marked the final file as 30fps but in reality using non-constant intervals between the frames. And there might have been frame drops during the capture process, so some frames/timestamps are missing, and the resulting video is faster than expected.
Variable framerate is pretty rare and not supported in Kinovea, but the timestamp is nonetheless read from the metadata associated with the frame, so this could explain the behavior.
Do you have a small example of such file that you could send me (joan at kinovea dot org) or upload somewhere, to verify that hypothesis?
What happens to the timestamps when you read this file on its own? Do they also progress in a non-constant fashion? Note that you can set the time format to "total milliseconds" to make it easier to experiment maybe.
732 2017-11-15 22:20:39
Re: Videos in Two Playback Screens playing at different speeds (9 replies, posted in Bug reports)
To get the complete picture, what is the FPS value read by Kinovea? This is visible in the info bar above the video. Also please confirm that both videos are at 100% playback speed and the value of checkbox in Preferences > Playback > General > "Link speed sliders when comparing videos". Also the value in menu Video > Configure video timing > High speed camera > Capture framerate. Although these options did not exist in 0.8.15 so it's unlikely the culprit.
The timestamps in Kinovea should not diverge, that definitely smells like a bug somewhere. What happens when you click a random location in the common navigation bar at the bottom?
The way it's supposed to work is that the common time position is computed first and then it is mapped to each individual video and they are adjusted accordingly. What you describe would be an issue in the time mapping for this particular video, but it's especially strange if they are coming from the same capture software.
Do you have a way to check if this video is playing back at the expected speed when it's played alone in its own screen?
733 2017-11-15 20:53:35
Re: Videos in Two Playback Screens playing at different speeds (9 replies, posted in Bug reports)
Forgot to ask, do you mean the content/action seen in the video is off but the timestamps are in sync, or do the timestamps diverge as well?
734 2017-11-15 08:50:06
Re: Videos in Two Playback Screens playing at different speeds (9 replies, posted in Bug reports)
Thanks for the report.
If you open the two videos but invert the screens they are loaded in, does the desynchronization go in the same direction or in the opposite direction?
It's possible that the right screen gets less CPU time but 640x480@30 shouldn't be an issue. Do you see the right video lagging behind?
What happens if you open the same video twice and sync it, does one of them also drift compared to the other?
735 2017-11-12 22:36:24
Topic: Experimental version - 0.8.26 (14 replies, posted in General)
This is Kinovea 0.8.26.
This version introduces new kinematic analysis tools and focuses on polishing existing features and fixing bugs.
1. General
It is now possible to run multiple instances of Kinovea at the same time by changing the option under Preferences > General > Allow multiple instances of Kinovea.
2. Annotation
The management of the opacity of drawings was simplified.
Instead of having a needlessly complicated dialog on each drawing with a "persistence" value, all the drawings are now either always visible or follow a global option for fading in/out of their reference frame.
The global value for this fading is set under Preferences > Drawings > Opacity.
3. Measurement
General
It is now possible to export the time series of trackable drawings like the angle tool and custom tools. See Angular kinematics and Linear Kinematics below.
The "data analysis" menu has been removed from individual trajectory drawings and placed in a global menu at Tools > Linear kinematics, as the window now combines data for all trajectories. See Linear kinematics below.
Angle tool
The angle tool was improved to be more versatile. It supports three new options to switch between signed or unsigned angle, change direction from counter clockwise to clockwise, and switch display to the supplementary angle.
The following screenshot shows the same angle object with different options applied.
Linear kinematics
The linear kinematics window is now found under the menu Tools > Linear kinematics and supports multiple sources. You can check/uncheck trajectories to be included in the analysis. The name and color for the plot are taken from the objects configuration.
When comparing several trajectories, three time models are available: absolute, relative and normalized. "Absolute" time will simply respect the original timeframe of the trajectory. "Relative" time will align all trajectories to a common starting point, to compare how they evolve over time. "Normalized" time will stretch trajectories to a common starting and ending point, to compare their "shape" over time.
Exporting trajectory data to CSV will export a common time column first and then one column per trajectory.
The trackable drawings (point, line, angle, custom drawings, etc.) have their individual points included in the trajectories. So if you track and angle drawing, its three points will show up in the linear kinematics window as three distinct trajectories that you can treat as any other trajectory.
Angular kinematics
A new kinematics analysis window has been introduced for angular kinematics. It is available under the menu Tools > Angular kinematics.
This window will let you visualize angular kinematics values like angular velocity or tangential velocity for angles that were tracked in the video.
Trackable drawings that have an angle, including custom tools, will show up in the list of sources and can be checked/unchecked.
The time options "relative" and "normalized" are also available.
Angle-angle diagrams
A new analysis window for angle-angle diagrams has also been introduced at Tools > Angle-angle diagrams. These are diagrams that directly map the angular value of two angles against each other.
This is useful to get insights into the dynamics of a specific motion. A typical example is to plot the knee angle against the ankle angle over a few cycles of running or cycling. The overall shape of the cyclic curve can be compared to the literature or between athletes or sessions.
The diagram is defined during the overlapping period of time of the two angles considered.
The angle-angle diagram will also work for custom tools that contain angles. This is possibly the most practical way to use this feature, for example with the bike fit tool or a tool dedicated to the angles you want to review.
In addition to the raw angle value, it is also possible to map the angular velocities or tangential velocities of two joint angles against each other.
General tracking
If you need to track the same joint angle at distinct times in the video, create several angle tools and track them independently. Each tracked point has an underlying timeline of positions that is not exposed to manipulation. Filling this timeline with discontinuous sequences will cause unexpected behavior.
It is now possible to completely bypass the data filtering by changing the global option under Preferences > Drawings > General > Enable coordinates filtering. Note that this filtering is to remove the high frequency noise created by the digitization process, it should be left enabled unless you intend to run your own filtering algorithm on the data.
4. Capture
Recording modes
In order to restore the ability to record delayed videos, a new recording mode option is available in the global preferences under Capture > Recording.
The Camera recording mode is the default and will record the video stream straight from the camera to disk, compressing it on the fly if necessary. This is the best performance path. For some combinations of framerate and image size, it is the only usable option.
The Display recording mode will let the video go through the buffering system for the delayed live feature and the composition system for mosaicing (if active), and it is the final image that will be recorded to disk.
Here is a simplified diagram of the capture pipeline and where each recording mode operates.
As an example, let's say we have a 10 second delay active and we record for 20 seconds. Let's define the press of the record button as time "0".
- In camera mode, the video will contain the action from time 0 to 20.
- In Display mode, the video will contain the action from time -10 to +10.
Camera modules
An entirely new camera module was written to support IDS cameras.
The Basler camera module was improved and updated to support Pylon 5 API.
Memory buffers
The maximum allocated memory for the capture module is now based on whether Kinovea is currently running on 32-bit or 64-bit Windows. This should allow for much longer delay when memory permits.
The option to increase the memory allocated for delay buffer can be changed under Preferences > Capture > Memory.
5. Feedback
Feel free to use this post for feedback, bug reports, usability issues, feature suggestions, etc.