But at the top of the image I see @17fps although the camera is setup in the "uEye cockpit" to have 60fps. Also, altough I configure the camera in the "uEye cockpit" to a monochrone image, the image in Kinovea will be in full colour. I looks like the camera parameters are ignored.
To clarify a point, the way the IDS cameras work, at least in regards to the IDS SDK used in Kinovea, is that each application is responsible for managing its own set of parameters for the camera.
When the program connects to the camera for the first time it will always receive a default parameter set. Then they have helper functions to save and load the parameter set as it gets customized for the application.
You can see the file where these parameters are saved for Kinovea by going to menu Help > Open log folder, and then go to the sub folder "CameraProfiles\IDS". There you should see a .INI file for your camera. There will be entries like image width, height, framerate, exposure, etc.
The parameters you set in IDS uEye Cockpit are only used by the Cockpit application.
This works differently than, say, Basler cameras, where they have a "global" parameters manager/API and all applications will read/write the same values.
In uEye Cockpit you can also see this concept by the menu File > Load parameters and File > Save parameters. This will save an .INI file that has the same format as the one you can find in the sub directory of Kinovea preference files above.
I imagine that if you had a specific parameter that you wanted changed that is not exposed in Kinovea you could try to save the .INI file from uEye Cockpit and then merge it with the file used by Kinovea. Although I would like to hear about these specific parameters to see if it would be relevant to have them supported natively in Kinovea.