Hi,
This will be fixed in the next version with support for rotation directly in the capture screen. Recorded videos will then be saved with the corresponding rotation flag, so when opening them on the playback side they will be automatically oriented correctly.

527

(36 replies, posted in General)

Thanks.

By "the dialog box that opens has a "Quick Access" section", you mean when doing menu File > Open video file? I'm not sure how the Quick Access feature of these system dialog work to be honest, we just setup the dialog title, initial directory and file type filter. The rest is handled by Windows. It seems weird that a user could have access to the files of another.

You could also try with the .zip version instead of the installer, it is self-contained in whichever folder you extract the zip to, so if the problem is coming from the application data folder (which has the preferences, shortcuts, history and is normally stored under the user files), maybe it won't have the same issue.

528

(1 replies, posted in General)

There is an auto-rotate based on the metadata of the video file. At the moment the files captured from the capture screen don't have this flag because rotation wasn't supported there but in the next version the procedure will be to orient the image in the capture screen to make it upright (using the same Image > Image rotation menu), and this will make it store the correct rotation flag in the captured videos.

529

(2 replies, posted in Ideas and feature requests)

This should be fixed in the next version with support for rotation in the capture screen.

Hi,
The automatic slow down happens when the program can't playback the video at the expected framerate because it's too much processing.
What version is this with? On recent versions (after ~0.8.20 or something) there is an optimization that should help a lot with this. Please test with 0.9.1 and let me know if you reproduce the issue.

Going all the way to 0% is strange though, I imagine the original is at 240 fps and the program detects it's missing a ton of frames repeatedly.

Regarding memory allocation: if you reduce the working zone enough that it fits in the allocated memory it will decompress the frames in advance and you shouldn't have the problem.

You're right, at the moment it's not really possible to do this.

You can use start/stop tracking to prevent objects from being tracked after the section you are interested in.
When you start tracking, it automatically changes the visibility option from the default fading to "Always visible". (You can change it back but it might become invisible before the tracking section is over.).

In the next version there will be more control over each drawing's visibility/fading. In theory it will allow you to do this as you can keep a drawing visible for a set number of frames but it will be tedious to match duration manually. I'll check how to support such an option in a more friendly way.

This sounds awesome! Thank you for looking into this.

edit: Tested with various alphabets and it seems to work beautifully. Thanks!

533

(2 replies, posted in General)

Hi,
You are right, the documentation is obsolete on this point, the capture system was rewritten for performance reasons and this particular feature, in the way it was written, wasn't compatible with the changes.
I'm looking at supporting this again for the next version with a different approach to keep the recording performance intact.

You can design your own grid. There is no "designer" application though, it has to be created manually in an XML file.

It's a bug. For some reason there was an explicit test capping the output framerate to 100 fps. I traced it to a specific commit in 0.8.22 but I don't remember why I put it there in the first place. I can't think of any adverse effects of removing this limit at the moment. Should be fixed in the next version.

535

(36 replies, posted in General)

NeilHa wrote:

* Update. 09Feb20. No response from Code Laboratories or the original author of the CL PS EYE driver regarding plans for a 64bit version so have switched to a different driver which appears to work pretty well in 64bit mode with Kinovea 9.1 on both Windows 10 and 7 64bit. It can be found here :  https://github.com/jkevin/PS3EyeDirectS … rBeta2.msi

This is great!

536

(36 replies, posted in General)

dong979us wrote:

Once the delayed video is captured, how do I make it so that it pops up in New window automatically so that i dont have to click on it.

You can do File > Open replay folder observer… and point it to the directory where the videos are captured. Any time a new video file is created in this folder it will automatically open and start playing in that screen.

dong979us wrote:

How do I make it so that delayed video is played at slower speed all the time so that I do not have to set it every recorded video?

Once you make the videos open in a replay folder observer, you can reduce the speed and it should keep that setting for the next videos.

dong979us wrote:

Can the drawing be transfered so that I don't have to draw it on every recording? Or at least save the drawing setting??

If you want to have specific drawings always loaded whenever a video is opened, you can do this:
- Add the drawing.
- Save as .KVA (File > Save, Save only the analysis).
- Rename it to "playback.kva".
- Copy it to the application data directory, which you can get from Help > Open log folder.

When you do this, every video will open playback.kva and import its content.
This can also be done with the capture screen, the file has to be named "capture.kva".

One thing that is in the works though is to have the drawings you add in the capture screen to automatically be saved as a KVA file alongside the recorded video. This would solve your problem in a better way I think and will also help with setting the time origin and other things.

Could you describe the symptoms more? When you go to the camera tab, there is no entry for the camera? Or there is a spot but the thumbnail is empty, or you see the thumbnail but when you open it the screen is empty, or the screen is black, etc.
Could you send me the log.txt at joan at kinovea.org, thanks!

538

(36 replies, posted in General)

Hi, yes the PS Eye webcam will only work with 32 bits applications. I don't know of any workaround. At the moment the 32 bit build is broken and it's a bit of a pain to maintain, so the incentive isn't there. So right now there is no plan to add back support for 32 bit. If someone contributes it and it's not a chore to maintain I'll merge it though.

539

(1 replies, posted in General)

Hi,
You can go to menu Tools > Angular kinematics. In the lower right corner there are buttons to export the data to CSV. The first column will be the time in milliseconds and then one column per angle. You can check/uncheck sources to include/exclude angles.

Hi, there are multiple framerates to distinguish, the one announced by the vendor on their website, the one exposed by the driver and that can be configured in AMCap, Kinovea or other Directshow applications, and finally the one that is actually sent by the camera.

If the info bar says something like

1280×720 @ 120 fps (MJPG) - Signal: 101.00 fps

Provided the exposure duration is low enough (less than 1/fps), it means the camera isn't really sending what the driver is announcing. Driver says 120, camera sends 101. This seems to be a recurring problem with these modules from Shenzhen.

AMCap doesn't do any dynamic measurement as far as I know, it shows what the driver says. In Kinovea you will also be shown what the driver says in the configuration window, but then while streaming it will count the frames really received from the camera and show you the actual framerate.

Does the camera not work at all in 0.9.1 or does it work with this framerate discrepancy?