ELP has a similar ov4689 camera that claims 260 fps. Might be worth a look.
1 2019-11-14 18:21:35
Re: Kayeton "high speed" USB camera based on OV4689 (17 replies, posted in Cameras and hardware)
2 2019-11-10 20:24:08
Re: Kayeton "high speed" USB camera based on OV4689 (17 replies, posted in Cameras and hardware)
I don't have the 330 fps camera but do have the global shutter 720p 120 fps camera.
Your results are surprising given kayeton advertises and shows your camera being configured for 60 and 120 fps etc. See screenshots at https://www.kayetoncctv.com/mini-case-h … sb-camera/
The 330 fps running 2% slow sounds sloppy on their part but perhaps there wasn't quite enough light? These are very small sensors to be running that fast, the light requirements can be surprisingly high.
The 720p global shutter camera runs at 120 fps given enough light but it does have other peculiarities. The main problem with it is the lack of configurability. It's basically a fully automatic camera working in one mode, if the user needs to change something then it's the wrong camera because changes aren't possible. It actually can change the exposure time but selecting manual mode immediately makes the image unreasonably dark (for the same 120 shutter speed) and there is no gain control to compensate so the manual adjustment is essentially useless.
3 2019-02-23 20:49:58
Re: Experimental version - 0.8.27 (33 replies, posted in General)
Faultyclubs wrote:
joan wrote:I imagine what you really would like is that when the audio from the golf club triggers the recording it still includes the few prior seconds of the swing, at the camera max framerate.
Yes, is this possible please?
If Kinovea is updated with audio trigger and a pre-recording buffer to be usable for golf (we can always hope!), there will immediately be other feature requests to make it work for typical use cases. So I include them here to avoid surprises.
1) Audio Trigger as mentioned above. User settable sensitivity.
2) Pre-recording buffer as mentioned above. User settable duration and delay
3) Portrait mode recording (in addition to the normal landscape mode). Both in the capture and playback screens. Needs to be persistent so we don't have to constantly change it.
4) Option to automatically play back the captured recording with a user defined playback start delay. User defined slow motion with looping.
5) Audio trigger capture priority. This means if the playback loop is running and a new hit occurs Kinovea should automatically switch back to capturing.
6) Support for two simultaneous cameras, both for capture and playback in the same automated loop described above. Golf is normally recorded with at least two cameras, a "down the line" (DTL) and a "face on" (FO) camera.
It would be OK if the two capture screen and two playback screen toggled back and forth since we don't need to see the capture screens when we are looking at the playback screens.
NOTE: While golf recording is typically done at the maximum camera frame rate, it is not ALWAYS done at the maximum. Indoor recording does not always have enough light to support the maximum rate. Also the maximum camera rate may not be at a suitable resolution. So recording should support all modes up to and including the maximum frame rate.
Much of golf swing recording is done at the range or in the simulator without a coach (ie solo). So automation is important. The above also works well with a coach who will typically let the automation run only stopping playback occasionally to provide detailed illustration and analysis.
Hope this helps.
4 2019-01-29 06:48:49
Re: Experimental version - 0.8.27 (33 replies, posted in General)
joan wrote:
I imagine what you really would like is that when the audio from the golf club triggers the recording it still includes the few prior seconds of the swing, at the camera max framerate.
Yes, is this possible please? The way it was in 8.15 worked for golf but the current versions (including v8.27) simply do not.
(Note: we need a user variable number of "few" prior seconds since it depends on the speed of ones swing).
The main problem with v8.15 (besides being a dead-end) is the capture pipeline is extremely inefficient. I can capture 640x480 at 120 fps on my i5 computer but cannot handle 1280x720 at 120 fps. v8.27 is dramatically more efficient at high speed camera capture but the architecture is broken for golf.
Perhaps an option to turn on a circular "pre-recording" buffer is all that's needed in the high speed camera pipeline?
Anyway, as users we're blissfully unaware of how hard it might be to fix this problem but hopefully something can be done! 
5 2017-01-15 20:14:16
Re: Experimental version - 0.8.25 (44 replies, posted in General)
That's great, thanks!
Possible explanation phrase might be:
Recording Mode:
- Camera (Record raw input stream)
- Display (Record displayed data stream)
6 2016-11-26 19:51:43
Re: Experimental version - 0.8.25 (44 replies, posted in General)
joan wrote:
I understand that there is now a missing feature of being able to record action in "pre-roll" fashion and considering various options.
Thanks Joan. Yes, the removal of the recording delay feature, or the "pre-roll" capability as you call it, is causing the problem. I'm glad to see it's being worked on. Sounds like you have a bigger picture in mind so it will be interesting to see what you come up with. If i can provide input from the golf perspective I'm happy to do that.
7 2016-11-20 00:38:11
Re: Experimental version - 0.8.25 (44 replies, posted in General)
>> 6. Feedback
>> Feel free to use this post for feedback, bug reports, usability issues, feature suggestions, etc.Hi,
OK, I will post here.
I use the stable version 8.15 for automatic recording of my golf swing. Trying v8.25 it seems the recording delay feature has been removed. Without this ability I cannot see how to automatically record my golf swing!
FYI, the standard method for automatic recording of golf swing is by sound trigger at impact and then capturing 1-2 seconds prior and post impact. Recording the swing PRIOR to impact trigger requires some kind of recording delay.
Ideally Kinovea would have this logic built in but I am able to do this with stable version 8.15 by using a 3rd party sound trigger application calling a keyboard script which causes Kinovea to record about 3 seconds and then play back the swing in slow motion. It works quite well but only if the recording can be delayed.
Can anything be done?
Thanks.
PS. My PS3eye camera works in the 32bit version and I can change resolutions and frame rate but all the camera properties are greyed out and unavailable (gain, exposure etc). They work in v8.15.