1,291

(4 replies, posted in Bug reports)

Sorry, there's no estimated time frame for audio support.
It is on my own wish list as a feature, but currently other improvements have priority.

(I can't comment on the mechanics of your serve or on tennis in general, hopefully someone more knowledgeable will chime in smile)

Indeed rotations are an extremely important part of almost all sports, so measuring angular speed would be super interesting in many contexts !

But as you point, the center of rotation is also moving, which makes things complicated.
Also, the rotation axis has to be exactly perpendicular to the image plane otherwise there is a bias due to perspective.

Technically… The first step would be to implement the "relative origin" for the tracking tool (coordinates of one tracked point expressed relatively to another tracked point).
Then we can probably figure out the maths to compute the angle change between successive images.

Speaking of baseball, rotations and angular speeds, the guys at DrivelineBaseball are apparently trying to hack a WiiMote to retrieve accurate rotation data. Sounds like a cool project !

Ollie wrote:

I really like the idea of having the spotlight feature combined with tracking, this would be ideal for highlighting a specific player and show their good/bad techniques. This is the one feature I cannot seem to be able to find in any video editing software (besides the mega bucks versions)

Actually I'm not even sure this feature exists anywhere, even in the mega bucks version as you say smile
Many video analysis packages don't even have an equivalent to a spotlight tool, let alone an auto tracking one… (I don't know about all the applications and their features, so please let me know if you know about an existing implementation, it's always interesting).

Ollie wrote:

that is easily implemented.

Well I expect some sort of complications, tracking from 2D imagery is not that straightforward wink
Can you try the existing tracking feature in your scenario ? Try to attach it to a player and see how long it can successfully track him. What is the most common case of failure ?

1,294

(20 replies, posted in General)

Hi,
This should be covered by the observational reference feature.
Image > Observational Reference > Import image… Choose your logo, position it, adjust opacity, and you're set smile

1,295

(6 replies, posted in General)

Thanks smile
Nobody is on Swedish. Someone had volunteered last year but didn't answer afterwards.

1,296

(6 replies, posted in General)

OK, the new features and improvements over 0.8.7 are now pretty stable and mature enough for prime time smile
The current cycle will be mostly focused on updating translations, user manual and bug fixing.

Translating Kinovea is about as simple as downloading a spreadsheet and filling in the gaps. (learn more on this page).
If you start a new language please post in this thread indicating which language you are starting to work on.

Here is a list of locales for which maintainers have recently confirmed (list will be updated continuously).
- Dutch (pstrikwerda)
- German (peusi)
- Italian (giobia)
- Portuguese (Fernando)
- Romanian (bogdan)
- Greek (swordfish)
- Turkish (Eray)
- Chinese (nicko)
- Finnish (Alexander)

A Polish speaking contributor is needed to update the Polish locale (currently 52% complete).

And welcome to the new locales !
- Lithuanian (Mindaugas)
- Swedish (Alexander)

The most wanted list cool :
(Languages not already in Kinovea, sorted by number of visitors of on the website (based on country of origin))
1. Japanese
2. Russian
[s]3. Swedish[/s]
4. Arabic
5. Korean

Thanks for your help !
tongue

Interesting experiment smile
(Disclaimer, the following is just guess, as I don't have an iPod and I haven't checked how its web server or camera works…)

First of all, I think you need to look for the actual stream (video or constantly overwriting image) address, not the web server's.
When your browser connects to the web server it is probably processing a web page embedding the stream, but if you want it to work in Kinovea you want the raw stream address directly.
(The URL should end with a script's name + parameters, or directly the stream file. With just the server's address, it means we are defaulting to something like index.html which would then contain the actual call to the script or file. Kinovea cannot parse the HTML to extract the camera URL).

Secondly, the stream must be MJPEG or JPEG, as they are the only IP camera streams supported in Kinovea. If it's H.264 or something else, it will not work. (If WebcamXP support the format you might use it as a "man in the middle" : you connect it to the stream, and then connect Kinovea to it).

Let us know about what you find !

Oh yes, I had forgotten about that one.
The value should be in seconds also, instead of number of frames…

Suggestions are not viewed as complaints. Constructive criticism is always appreciated. And thanks for the heads up wink
I think I'll just bump it up to something like 200/300 frames, and switch to seconds in a later stage. (I'm actually using a modified version with exactly this change to create the example videos smile)

By the way, people have noted that the persistence concept and interface could be improved in terms of usability. If anyone has a solution that would be better than the current one, feel free to propose. I've had thoughts about a sort of manipulable curve that would symbolize the amount of opacity relative to time, but that would probably make things even more complicated.

1,299

(20 replies, posted in General)

Great smile
The ability to provide the [username:password] as inline information in the URL will be supported in the next version anyway tongue

1,300

(2 replies, posted in Bug reports)

I also experienced a lot of crashes with it today. The driver seems to keep a record of previously entered addresses and it somehow fallback to old addresses for some reasons.

It would appear that when the address is not reacheable or errors out, crashes occur almost instantly. It becomes very hard to do anything when this driver is the first tried sad
The code needs to be made more robust in this area so it is at least possible to change the source !

1,301

(20 replies, posted in General)

I tried with this public camera : http://59.124.49.36:60013
(login:guest, password:guest, stream is MJPEG)

Apparently all their cameras need login/password (?)
In Firefox for example, in order to retrieve the raw images, (provided the login/pass was not saved previously or has been cleaned up), I had to use the following URL:
http://guest:guest@59.124.49.36:60013/getimage?camera=1&fmt=sif
Otherwise I get a 401 error.
(This will not work as is in Kinovea, the login/pass have to be specified differently, and currently it's not possible…)

Check in this topic for the logs location, it depends if you are under Windows XP or Windows Vista/7.
(Or you can just type %appdata%\Kinovea in the address bar of Windows file explorer, works everywhere).

Ah, an HDMI capture card… nice smile

Regarding the cause of error, there might be a few more lines in the log. (several errors can yield this message, but the log may have the specifics).
Please open the log right after the issue (before restarting Kinovea) and post the relevant lines here.

Then you say Kinovea needs to be restarted ? Hmm, not good. What is happening exactly ? The interface is frozen ? Would you be able to close the capture screen and open it again ?

1,304

(20 replies, posted in General)

Indeed, if it works in Firefox just with the URL, I would expect it to work…
What is the camera brand/model ? Maybe I can find similar camera streaming directly on Internet and try to connect to it.
Be sure to switch to MJPEG in the configuration window if it's the type of stream coming.

1,305

(5 replies, posted in Bug reports)

acer22 wrote:

I recorded a video at 60fps and when I replay it, the speed slider says it is at 100% but it is to the extreme left.  If I move the slider to the right the percentage changes, but it slides back to the extreme left as I play the video.

This specific issue should be fixed as of version 0.8.14. There was a problem with the automatic update of the slow motion factor when the program can't keep up the pace.
The slider should not go all the way left on its own anymore. (Automatic decreasing by some percentage may still occur, but not down to 1%)