1

(7 replies, posted in General)

This should be fixed in the next build.

2

(2 replies, posted in General)

Details: when you click on Enable UDP trigger in the preferences it will start listening on the UDP port configured. (You still need to "arm" the trigger as for audio in the capture screen (lightning icon)).

The UDP message itself is ignored, you can send an empty string.

It works from different computers. I just double checked by installing an app called "UDP Sender / Receiver" on my mobile phone and I was able to trigger the capture remotely. (In this case it insisted on sending a message so I just set it to "a").

Here is a small python script sending a packet every 10 seconds. You can send to the IP of the computer with Kinovea. If you don't know it you can send to 255.255.255.255.

import os
import socket
import time

# Send an empty udp broadcast every 10 seconds.
def broadcast():
    print(f'Broadcasting at {time.ctime()}')
    s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
    s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
    s.sendto(b'', ('192.168.0.228', 8875))
    s.close()


if __name__ == '__main__':
    while True:
        broadcast()
        time.sleep(10)

3

(7 replies, posted in General)

Yes you're right, the code is shared with the exporter that exports frames by time interval so it enumerates all frames and decides which ones to export. That is indeed very inefficient for key images, I'll fix it.

4

(7 replies, posted in General)

Hi,
I just tested here it took 17 seconds to export 100 key images.
Let's figure out what's different, maybe there is some context that's triggering a massive slow down. 1 minute per frame?

My source video is 1920x1080, is your video much larger and you are exporting at full HD? It has to repaint the source so performance is partly related to the source size.

To export the images I used menu File > Export images > Key images…

The resulting files are indeed very large.

OK, I think I see what's going on, it seems it's exporting PNG files in all cases even when the extension is set to JPEG. That would explain both the large size and the problem opening the file in other software. I'll check what's going on.

5

(3 replies, posted in Bug reports)

It's a very generic error message, I can't investigate without more information on how to reproduce the problem or at least a better understanding of what the program was doing when it happened.

Can you send me the Unhandled exception files and log files or create a github issue? Does it happen only on 2024.1 or also 2025.1? Are you also using remote desktop?

Thanks.

For 2. Guides, I think the simplest way to implement that at the moment would be an option to enable "snapping" to a virtual grid, like every 20 pixels or similar. I will double check how it works in various software.

I think the other solution is that the first object is placed freely and then when you move another one there is a guideline that appears to align it. This second solution means it needs to check all other objects while moving. But it allows aligning center to center which could be desirable. If you have a prototypical example of an application where it works well don't hesitate to share.

I would like to find something useful while keeping things visually simple.

I know of one example where it just snaps the center of the rectangle to evenly spaced virtual grid lines, this is nice and simple (but can't left-align, they are always center-aligned).

For 3. element size, is it about the timer/labels? The object size is based on the font size for these.

Yes, it's crucially important! I made a fix and I'm testing it.

8

(3 replies, posted in Bug reports)

Thanks, can you try again please? There was one component locked and I integrated all the pending translations into Kinovea.

The error you got appears to be an issue between weblate and github though, so in that case there is not much I can do, it will probably fix itself after a while.

I would prefer that you update the translation directly where you think it can be improved rather than submit suggestions. I don't get a notification on suggestions and they end up in limbo.

9

(4 replies, posted in General)

The "RenameSelected" command is only for the thumbnail view in the file explorer or camera explorer, to rename files or cameras.

There is not really any shortcut to bring up this properties dialog. The closest thing is to open the annotation pane on the right, on the second tab, and rename the objects from there.

Thanks. I can reproduce the issue here and I see where the problem is. The bug is in the time conversion unfortunately, not the name.

I'll look into it ASAP. Someone also reported an issue on github with the same root cause.

11

(4 replies, posted in General)

Hmm, it looks like the dual playback shortcuts only work when the joint controls bar at the bottom has the focus. I thought I fixed this a while back, I'll look into it. In the meantime if it's a shortcut that also exist in single screens in the PlayerScreen category you might set it there and it should send the command to both screens.

Which one do you mean by "Object Rename"?

12

(1 replies, posted in General)

Can you expand a bit? Are you capture the video on the camera or in Kinovea?
There is a speed slider at the bottom, does that not work?

13

(2 replies, posted in General)

Thanks for the description, I'll do some tests.

When the trigger happens do you see the capture window switching to recording at all with the red bar? Or is it not armed at all and the trigger is completely ignored?

If it's recording but the output file is not updated it's probably because it's already opened in the playback window as you mention using a static filename. Can you try with a dynamic filename just to see if that's the cause of the problem? (Just enabling "auto-numbering" should be enough to test this).

If that's the origin of the problem it might be tricky, maybe we need a different mechanism where it cycles between a few files instead of just one. This could be an extra option next to "auto-numbering" for the max allowed number and when it reaches that number it goes back to 0 and starts again.

14

(17 replies, posted in General)

When the search box is too small you can use the number boxes below, if you click in them you can then scroll up/down with the mouse to change it easily.

The forum doesn't have its own image hosting sorry. You'll have to upload the images somewhere else and link to them.
If you prefer you can create an issue in github and you can attach images there. https://github.com/Kinovea/Kinovea/issues

Are the files on a OneDrive folder or another synchronized folder like Google drive or similar by any chance? This is known to cause problems for some reason.

I remember now, the issue with immediately killing the tracking as soon as it fails is that it breaks when the object is temporarily occluded, for example an arm or leg passes in front of it. The idea was that when this happens it keeps looking and when the occlusion is over it might recover the tracking by itself if it's still inside the search window.

What I would like to do is add an option somewhere to tell how many frames of failed tracking are allowed before the playback is stopped. 3 or 4 frames should be a good default I think, but if you want you could set it to 1 and get the same behavior as in Tracker.

Or maybe playback should always stop on failure and it's the track that is force-closed after n failures.