You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
This should work out of the box in version 0.9.3 with the IDS SDK support.
IDS currently publish two different SDK, the Peak one and the classic one. The classic one is supported in Kinovea but only in the beta version, not in 0.8.15 which only supported DirectShow.
Can you try with 0.9.3?
If you want to work with the source code let me know because these machine vision plugins are in the process of being moved to a different place and will be distributed separately from now on.
The one issue I repeatedly have is that frequently, the cameras stop recording and just loop the last video recorded.
Can you clarify this? Is it that the video file is not created in the output directory or that the created file is not loaded in the replay observer?
Do you have the two observers monitoring the same folder and the capture screens saving to the same folder?
Can you send me a log to joan at kinovea dot org?
When this happens the only way to remedy is to shut down the camera windows and repoen them.
Using the pause button doesn't work? This disconnect and reconnect the camera.
Thanks
Hi,
This should already work but maybe there is a problem? If you have set a delay the resulting file should have its time origin set automatically. You should see the little red marker corresponding to the time origin and the beginning of the video should have negative time codes.
The videos are synchronize based on their respective time origin, in this case the audio trigger or manual start of recording, so if you open both videos side by side and use the slider in the joint controls at the bottom it should move in both videos in a synchronized manner.
If you haven't set a delay or don't use audio trigger you should still be able to synchronize them manually by setting a time origin in each video and using the joint controls.
If parts of this don't work as expected please describe what you are doing in more details. How many instances of Kinovea are running, what runs where, etc.
This should be fixed in the next version. In the meantime it should already work when using a replay folder observer. Otherwise you could work around it by going to Preferences > Capture > Recording and in the High speed cameras box, set Framerate replacement threshold to 100 fps (or 99 fps based on what you say) and Replacement framerate to 10 fps.
Yeah the current situation is not ideal… For me the priority should be to make the angle tool (and other trackable tools) user interface be as convenient/capable as the trajectory tool. The other big issue at the moment is that we can't easily change the sizes of the search and pattern boxes.
Maybe one way would be that when you click on "Start tracking" it creates 3 temporary trajectories objects that you can interact with as normal trajectories, and when you click "End tracking" it merges back the trajectories data into the angle points timelines.
For the point at frame i, it uses the positions at frames i-1 and i+1 and divide by 2 time intervals.
Also depending on where you are looking the speed is calculated using either the raw positions or filtered positions. If you use the Linear Kinematics dialog it uses the filtered values unless you have disabled filtered in the preferences.
You can go to "File > Open replay folder observer…" and point it to where the captured videos are saved.
No at the moment there is no generic USB 3 Vision support. Only specific vendors are supported. Although I will be looking into this for future versions.
Yes the time is the total number of milliseconds since the start of the application. So between 2226 and 6249 there are a bit more than 4 seconds. In this case the USB 2.0 camera took just 30 ms to initialize, the ~1-second gap between 543 and 1481 is from another bug that I have fixed since.
This is even stranger than I thought. One camera took about 600ms and the other 4 seconds (both pretty slow) even though they are the same model…
Thanks. Interesting!
If you open the log and check the time column (first number), is there a big gap just before the first line mentioning the camera?
Like this:
1627 - DEBUG - [HD USB Camera thumbnailer] - SnapshotRetriever - Starting HD USB Camera for thumbnail.
5808 - DEBUG - [UI314xCP-C thumbnailer] - SnapshotRetriever - Starting UI314xCP-C for thumbnail.
I'm not sure if that's what you meant but for the shortcut thing you don't have to write any code. All the commands are listed in Preferences > Keyboard. It's just that this particular one doesn't have a shortcut assigned, you'll see it says "None". But you can assign one from the preference page.
The recent observers list should be populated automatically when an observer is opened, but I imagine you could edit it manually for testing purposes.
I just pushed a change to support patterns in the filename part of the replay observer (everything was almost ready to go). This should work with observers defined in workspaces. So based on how you setup the capture output files it should be possible to have each observer specific to each capture.
For example, in the workspace file:
<FullPath>D:\temp\cam1-*.*</FullPath>This will observe the files under "D:\temp\" but only the ones that start with the "cam1-" prefix. You can use multiple "*" wildcards and also "?" for single character match. For example "?at.*" will match "bat.mp4" and "cat.avi", but it won't match "flat.mp4".
A unique "*" will still match any file and is still the default when creating an observer from the main menu by pointing a folder.
1 - The audio trigger is always live so for at least one of my instances, I do get multiple videos. I have added a line to the source code to disable the trigger but I don't have a sufficiently elegant way to re-enable it.
There is a command called "ToggleArmCaptureTrigger" that enable/disable the audio trigger, it's not bound to any keyboard shortcut by default but maybe you can use that? It's the same as clicking the speaker icon in the capture controls.
The auto disarming for a cool-off period is on the roadmap but most probably not for the next version.
2 - The replay observer will always load the most current video and I am recording from 3 cameras into the same directory. I could record into different directories to solve this.
For this what I wanted to do originally was to support glob patterns in the filename. At the moment the "filename" field for a replay observer is set to "*", as in, "any file". (further filtered by supported extensions). But the idea was to allow for finer filtering on the filename so you could have observers that only load a specific camera if the file patterns are set appropriately.
The tricky part really is where to put the UI to let the user specify this. But we could start by making it work for workspaces.
Now that there is a menu to switch between video and observer directly in the player infobar, I think it will be a good place to host that extra customization option.
Hello everyone,
There seems to be an issue with some (all?) IDS camera and slow startup time. Looking for more data about this.
When opening the program on the camera tab, how long does it take for your IDS cameras to fully show up?
I have a small USB 2.0 "UI1220LE" and based on the logs it already takes about 300ms. But I have received logs of people where the high-end cameras are taking multiple seconds.
Data I've gathered so far:
- UI1220LE: 0.3 s.
- UI3240LE: 1 s.
- UI3140CP: 4 to 5 s.
- UI3160CP: 5 s.
I don't reproduce this with other machine vision cameras so I'm wondering where the problem might be coming from and if it could be mitigated. We've already ruled out the "USB selective suspend" option in Windows power settings, we still get the same lengthy initialization with the option disabled.
Do you have similar slow startup times with high-end IDS cameras (multiple seconds)? Is it the same in uEye Cockpit?
Thanks
Great! What was the name of the software? Maybe I can reproduce the crash and see if anything can be done about it.
Kinovea - Forums → Posts by joan