You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
Re: replay folder observer,
Go to menu "File > Open replay folder observer" and point it to the folder where your files are saved. That is, the same path you set in capture preferences. What this does is create a playback screen that is constantly monitoring this particular folder for new files. When you capture a file it will open and read it.
You can now set it to automatically stop recording after a few seconds and then automatically open the file as instant replay in a loop, see "replay folder observer". The kind of programmable scenario as you quoted is still not possible.
Note that the webcam mode in the new GoPro Hero 7 & 8 is not currently supported in Kinovea so you won't be able to use these cameras for direct streaming into the program.
Another possibility could be the Daheng Imaging cameras which are supported since version 0.9.2. For example the MER-160-227U3C is based on the same sensor as the Blackfly you listed above (IMX273, 1440x1080, 227fps) and their MER-131-210U3C is based on the same sensor as the IDS (Python 1300, 1280x1024, 210fps).
Go to Options > Preferences > Capture > Memory, and increase the memory allocated for delay buffers.
No, cameras from FLIR / Point Grey Research are not supported at this time.
Yes, this was fixed in version 0.9.1.
No it wasn't removed, image objects (either from built-in SVG files, importing images, or from pasting an image from the clipboard) should have a "Visibility" menu in their context menu, like this:
Where did you get the driver from? I didn't do anything. Or is it a Kayeton camera?
Also double check the framerate received by Kinovea is the one you expect. You can see this in the infobar above the capture screen. The "Signal" value should be near the framerate you expect. If it's around half what you expect you will get a sped up video as you describe. If you are in low light conditions for example the camera can decide to increase exposure time and lower the framerate automatically, disregarding the configuration.
2) if there could be an additional keyboard shortcut for different increment amount such as IncreaseDelayby1 with Shift+Up in the CaptureScreen (in addition to the current 0.1 increment) similar to the IncreaseSpeed1, IncreaseSpeedRoundTo10 in the PlayerScreen, that would be very helpful.
Yes, good point. In order to make it homogeneous with the playback side I'm thinking of the following:
- Up/Down = increase/decrease to the next whole second. (That's also the granularity of the arrows on the numeric input control).
- Shift+Up/Down = increase/decrease to the next 0.5 second.
- Ctrl+Up/Down = increase/decrease by one frame.
Another thing to note is that when you pause the stream the delay slider can act as a sort of position slider like the main position slider in the playback screen, at some point I would like to maybe replace the delay slider control by the full one. In the meantime I think it will be interesting to have the same shortcuts to move around in the sequence, so home/end to move to the start/end, page up/down to move by 10%, left/right arrow to move frame by frame.
Reposting my comments here
If you run the executable again the name will be generated based on the order of launch. So the second instance will have name "2", the third will be named "3", etc. This means you will need to launch them in the same order.
There seems to be a bug in this feature that the numbered instances are picking the master preference file and not their respective preferences. So for now please use explicit naming. A simple way to do that is to right click the executable, create a shortcut, and then go in the properties of the shortcut and in the "Target" field add "-name foobar" at the end. Then to launch that instance you use the shortcut.
If you have a single camera in each instance, it will only use the "left" naming scheme.
Edit: I fixed the issue with the instance using the wrong preferences when it's named automatically from its order in the launch sequence. This will be fixed in the next version, in the meantime please use explicit names.
Maybe try to tweak the audio threshold so that it only triggers when you want. For example locate the microphone close to the impact area and set it to only trigger when it's really loud. You can test this directly in the preferences dialog.
At the moment there is no "cool down" period where the trigger would be disarmed for a while after recording, hopefully I can integrate this for the next version.
Hi,
1. Invoking Options->Preference via a keyboard shortcut: at the moment, no. Menu shortcuts work a bit differently. This could be added relatively easily but it won't be user-definable. Note that the other keyboard shortcuts listed in the preferences are customizable, you need to place the cursor in the text box in the lower left and type the key you want then apply.
2. Saving/restoring screen layouts. There is a work in progress on the concept of "workspaces" but the camera side is not implemented yet. There is a complication from the way the cameras are discovered dynamically.
Saving and restoring camera-specific parameters (image size, framerate, etc.) should work out of the box. This is saved in the preferences XML file and should work for instances installed in different folders or for instances launched from the same folder but with different "names".
The capture delay is not saved anywhere at the moment.
3. Yeah, this is problematic. I think there are 3 ways to go about it. First is a cooling-down period configurable from the settings, preventing any trigger for a period of time after a capture. This wouldn't really help with the scenario you described though. Second is an "arming" or enable/disable button in each capture screen. The third option is a single button (maybe in the explorer panel on the left) or a menu that would work globally for all screens (but not across instances).
3a. and 3b. You can change playback speed and camera delay with the UP/DOWN arrow keys.
3c. You can start/stop the camera stream with SPACE shortcut.
I'll note down the issue with sleep. Maybe there is a way to be notified when the computer is about to go to sleep and take some preventive measures like that.
4. Starting Kinovea using a specific "Open replay folder observer". Yes this is possible in the current state of the workspaces feature. I'll post it here but to anyone reading this in the future, please be aware that the format may change.
So there is a concept of workspaces, the end goal is that you could take your current layout of screens and save this to a file and reload it later. At the moment you have to create and edit the workspace file manually.
Here is an example file that will create a single folder observer on the "D:\temp\left" directory:
<?xml version="1.0" encoding="utf-8"?>
<KinoveaWorkspace>
<FormatVersion>1.0</FormatVersion>
<Name>Single replay</Name>
<Id>3f19d841-66b5-4853-87ce-a0ec35ccc7a7</Id>
<ScreenDescriptionPlayback>
<FullPath>D:\temp\left\*</FullPath>
<Autoplay>true</Autoplay>
<SpeedPercentage>100</SpeedPercentage>
<Stretch>true</Stretch>
<IsReplayWatcher>true</IsReplayWatcher>
</ScreenDescriptionPlayback>
</KinoveaWorkspace>Save this to a text file and rename it with a .xml extension.
In order to launch Kinovea with this workspace you can pass the file path directly on the command line, or use the -workspace option:
Kinovea.exe workspace.xml
Kinovea.exe -workspace workspace.xml
(The first variant means that just dragging the xml file on top of Kinovea .exe will also work).
If you want a dual playback screen setup you can add another `ScreenDescriptionPlayback` node. For a normal playback screen you point the exact file and `IsReplayWatcher` must be set to false. For a replay observer you point the directory and use the "*" wildcard instead of the file name. The `Name` and `Id` fields aren't really used at the moment, they will be used to differentiate between multiple workspace files.
Let me know if you find any issues with this feature.
The concept of shutter speed is called "Exposure" in the interface, it's the same thing. It's the duration the shutter stays open while the sensor is being exposed. You can get it from the camera settings (clicking the wrench or clicking the name of the camera at the top). You should get something like this:
Kinovea - Forums → Posts by joan