You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 10 of 129)
Topics by joan User defined search
Posts found: 136 to 150 of 1,931
Hi,
Just to be on the same page this screenshot is from a very old version.
To change the toolbar you don't need to change the source code. The toolbars for the player and the capture screen are defined in XML files that are in the program files directory (installation directory), under DrawingTools/Toolbars/player.xml an capture.xml.
In there you will see things like `<entry name="Line">` and `<subentry name="Polyline" />`. When Kinovea starts it will read this file and build the tool hierarchy from it by searching for tools by name. The `name` property corresponds to the Name field in a drawing XML file stored under DrawingTools/Standard or DrawingTools/Custom.
It's mostly machine vision cameras that are specified like this, they give the frame rate for the max resolution of the sensor but if you lower the number of lines it can actually go faster. When you do this the frame rate slider in the camera settings in Kinovea should have a wider range. For some camera types you have to click a button to refresh the slider range.
Since you are recording a high speed camera the resulting video plays back in slow motion. In your case at 10% of the original action (30/300).
Are you saying that the speed slider resets itself to be in the middle when you open a new video and you have to manually slide it right to 20% or is it something else? What version are you using?
Salut,
Le code qui implémente ça est ici: Butterworth.cs
Et le truc qui appelle cette classe est ici: FilteredTrajectory.cs#L134
En espérant que ça aide
Couldn't process file <file> due to its being in the Internet or Restricted zone or having the mark of the web on the file.
Assuming you downloaded a .zip archive of the source code. Windows marked it as being from the Internet and put some restrictions on it. You should either use a git client and do a `clone` to get the source code, or remove the "mark of the web" from the .zip file before unpacking it. I personally use "Git Extensions" as git client.
If you want to record yourself while you are doing the analysis, it is not possible within Kinovea, you will have to use an external screen casting software like OBS and record the window.
You are probably looking for Kinovea/Kinovea.ScreenManager/Measurement/Plotting/FormMultiTrajectoryAnalysis.cs > GetCSV()
https://github.com/Kinovea/Kinovea/blob … is.cs#L524
Although you can also look at the "transpose" function of the target spreadsheet application, this should be simpler to work out. See here for Excel for example: https://support.microsoft.com/en-us/off … f862209744
What about the "Arm capture trigger" button in the capture tool bar? There is also a colored band above the screen, it should be green. If it's blue it means audio trigger is disarmed. This arm/disarm mechanism was added on top of the audio trigger to avoid unwanted recordings.
Kinogram is only available when the whole video section is cached in memory so you have to either increase the memory cache from the preferences or make the selection shorter.
It should be OK to install on top, hopefully it will retain the preferences. Let me know if it doesn't work as expected I haven't tested this in a while. You can also use the .zip version and keep both in separate directories.
Unless it's a camera from one of the supported vendors it won't work. The way they work is that each vendor has a specific SDK that Kinovea camera plugins are built with and that contains the library that actually interact with the driver.
Yes you need to grab version 2023.1 from the sticky topic in this forum. Then you do right click "Sort by" in the file list or in the background of the thumbnail panel, and then "Date" and "Descending".
Bonjour,
D'après mon expérience quand la vidéo résultante est plus rapide que prévu c'est que la fréquence de capture réelle a été plus basse que celle configurée. Par exemple la capture a été configurée pour 60 fps mais en réalité il n'y a eu que 40 images enregistrée à chaque seconde de capture.
Cela peut venir de plusieurs causes. Les principales: 1. pas assez de lumière ambiente et durée d'exposition automatique (typique sur les webcams). La caméra augmente la durée d'exposition pour capter assez de lumière et force le fps à descendre. 2. images perdues pendant la capture (par exemple si l'encodage et sauvegarde prend trop de temps par rapport au fps).
Si vous faîtes la capture dans Kinovea il y a une barre d'info au dessus de l'écran de capture indiquant le fps réel et un compteur de "drops".
If you only plug the front camera it works?
A hub is good if it's powered. On the other hand two different USB ports on the PC may still internally end up on the same root and share power and bandwidth. But if it can send the camera feed to the other app it shouldn't be that. There is a log of operation which should have good info to debug this. Can you share it by email joan at kinovea dot org?
For point 1, the coordinate system is in pixels by default. If you don't do any particular calibration and show the coordinate system it will show a grid overlay with graduations in pixels. Currently you can't change the interval between labels / tick marks but I agree it would be good to have.
Posts found: 136 to 150 of 1,931
