106

(6 replies, posted in Ideas and feature requests)

Yes I'm thinking about a slightly more general use-case because it would make a lot of people happy that have been requesting this in one way or another over the years.

At minimum I think you should consider that there can be two capture screens with their own status so ideally we want to get information about both and control both. With that in mind and the similar requests for control from other applications, I think it should be as high as possible in the hierarchy so it has the option to control everything and return the most information.

The top level has ways to get information about the screen supervisor and individual screens rather easily. If you would consider getting back a formatted string and extracting the information from it instead of directly getting a data structure it would be super general and most useful for every other use-case. The capture screen can be in several states: empty, connected, grabbing, recording.

So I think there should be an internal API to grab the global status from the top and then one or more entry points to expose this information to interested callers based on communication tech. The advantage of using an HTTPListener is that it would be super easy to test queries for other interested applications. Example applications: controlling via a Stream Deck, interfacing with record keeping software for competitions, advanced multi-cameras record/playback setups.

107

(6 replies, posted in Ideas and feature requests)

I'm not against adding a different control interface if the windows messaging system is not adequate. Maybe having a little HTTP server would make it simpler on both ends. Something in the vein of VLC HTTP requests https://wiki.videolan.org/VLC_HTTP_requests/

108

(6 replies, posted in Ideas and feature requests)

To start the discussion there are two existing trigger mechanisms.
1. The audio-based recording trigger. The Arduino could send a signal directly on the mic input of the PC to trigger the recording.
2. Software based trigger. This goes through Windows messaging system and can trigger all the commands covered by keyboard shortcuts.

Both these mechanisms work even if the Kinovea window is in the background. These are only actions though, for the heart beat I don't remember if the Windows Messaging system is enough for back and forth comms. Ideally we can add another message to ask for status and get a response.

I haven't touched Arduino in a long time, is there a piece of software running on the PC side, in what language?

Thanks for testing. You can get the log by going to Help > Open log folder and grabbing the log.txt and log.txt1 files. (If there are any "Unhandled Crash - xxx" files in there please include them as well).

It's possible to add the comments to the "spreadsheet" JSON. It's slightly more involved, if anything to avoid breaking the JSON formatting from the comment content. But mainly this JSON is meant to be used by other programs to process the numerical data and I like this separation of concerns so if anything I would rather add another JSON export in the document export section. The markdown is essentially a plain text export so I think that's the perfect place for this, if only it worked correctly…

I had to fix an issue with Traditional Chinese locale that was partly missing so I snuck a fix for this at the same time. Please download 2023.1.2 and let me know if it fixes the problem with markdown export. https://www.kinovea.org/en/forum/viewtopic.php?id=1589

OK I see, I think I reproduce it. Do you have a working zone in place and some of the key images are outside it? There is a bogus comparison in the exporter and it aborts the export if the count doesn't match. It would fit well with the fact that you have the image folder but not the .md file.

It says "The transfer you requested has been deleted."

You can also send it to me at joan at kinovea dot org. If possible also add the log.txt in case there is an exception that prevents the file to be created. Also try to first create a new folder dedicated to the export and save the .md file inside it.

I can add an option in the settings to not include images in the document exports.

Can you give more details on "The markdown is not working"? This is the base of the "document" export so it's very important that this has the comments and it would be a bug if that doesn't work. (The JSON and Excel exports are for numerical data so they don't have these).

I can't reproduce the problem, I get the comments in the .md export. Can you share a .kva file with frame comments where exporting to markdown doesn't export them? Are we talking about frame-level comments or labels?

You can try to put the line and right click > start tracking. See if that works but it's likely it won't work in your case as the horses pass in front of the tracked post.

If you want to put on lines that "stick" to the objects in the scene despite the camera rotation, I'm working on it and there should be something in the next version. At first it will be only for qualitative markers though, I don't expect it to be accurate enough for measurements.

edit: in your case if I understand correctly the ends of the line should be attached to objects that are not visible on the same frame together is that correct?

edit2: I checked this in the dev version and it should work with the new camera motion compensation. You can lay down a line across the scene where both ends aren't visible together at any given time. Now to see if this type of busy scene will work with camera motion estimation.

115

(28 replies, posted in General)

Update to catch up with translators work. Thank you all!

Links

    Kinovea-2023.1.2.exe (installer)
    Kinovea-2023.1.2.zip (self contained archive)

This release is a translation update. Please continue reporting bugs here or in dedicated topics. This version will still receive bug fixes and translation updates until the next version is out.

Translation updates
- New locale: Chinese traditional.
- The following were also updated: Bulgarian, Dutch, Portuguese, Russian, Chinese (simplified).

This is the current state of translation:
(If you see your language below but it's not available in the interface it's because the translation is too incomplete, contributions are very welcome, click on the image to go to weblate.).

https://www.kinovea.org/setup/kinovea.2023.1/2023.1.2/weblate.png

116

(3 replies, posted in Cameras and hardware)

Hi, I just updated the Basler plugin to work with Kinovea 2023.1 and Pylon 6.1, please get the latest from the downloads page and try again and let me know if it works.

117

(28 replies, posted in General)

I rebuilt the machine vision plugins, they should work in latest Kinovea 2023.1.1.
Updated the first post with the download links.

118

(1 replies, posted in Français)

À l'heure actuelle les nouvelles caméras IDS ne sont pas encore supportées.

119

(5 replies, posted in General)

Normally they should look the same, can you try with version 2023.1.1 linked in this forum?

Skips by one or two frames?
It's probably a symptom of the recording not being able to record everything in real time so it's dropping frames once in a while when it falls behind. You can try to change the recording mode to Retroactive in the settings it should help. Make sure the memory buffer is large enough to record the duration you need.