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,248

(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,249

(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,250

(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,253

(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,254

(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%)

1,255

(10 replies, posted in Bug reports)

litch09 wrote:

When I first try to export (without saving the key image data to the .kva file) I get zeros in the x and y coordinates

This was a different issue that had been overlooked and it has just been fixed in version 0.8.14.
Due to decimal separator differences (comma vs point) in languages the data with decimal part could be output as 0.
This impacted track coordinates, cross marker coordinates, and length of lines, for every language where the decimal separator is a point.
bug 241.

It looks like they have a Windows driver for the Kinect at codelaboratories.
Can you or someone with a Kinect try this in the experimental version and report the result ?
(I'm not too sure that it's a DirectShow driver ?)
Thanks

1,257

(20 replies, posted in General)

Sure. I'll send you a mail later today or tomorow.

1,258

(4 replies, posted in Français)

Version expérimentale : elle a besoin de vos retour d'expérience pour s'améliorer !
Si tout se passe bien cela devrait être la dernière itération avant la version stable. Merci de rapporter les plantages éventuels le plus vite possible.

L'installeur est dispo ici : [s]Kinovea.Setup.0.8.14.exe[/s] Voir Kinovea 0.8.15

Les principales améliorations sont sur la partie Capture.
- Support des caméras réseau (celles qui font du streaming JPEG ou MJPEG).
- Accès à la page de propriété native de la caméra pour les cameras FireWire ou USB.
- Page de préférences, y compris un nouveau système de nommage automatique des fichiers.
- Etc.

Correctifs : bugs 241, et autres bugs non numérotés.

changelog.

Préférences capture.
http://www.kinovea.org/screencaps/0.8.x/captureprefs-general-fr.png
http://www.kinovea.org/screencaps/0.8.x/captureprefs-naming-fr.png
http://www.kinovea.org/screencaps/0.8.x/devicenetworkconfig-fr.png

1,259

(20 replies, posted in General)

This is an experimental version : it needs your feedback to improve.
If everything goes well, this should be the last experimental iteration before the next stable release. Please report any crash as soon as possible.

The installer is available here: [s]Kinovea.Setup.0.8.14.exe[/s] Please check Kinovea 0.8.15

The main improvements come from the Capture screen.
- Support for network cameras (when capable of JPEG or MJPEG streaming).
- Access to the device property page for FireWire or USB cameras.
- Preference pages, including advanced naming schemes.
- And more.

Fixed bugs : 241, and other non numbered bugs.

Full changelog.

Capture preferences pages
http://www.kinovea.org/screencaps/0.8.x/captureprefs-general.png
http://www.kinovea.org/screencaps/0.8.x/captureprefs-naming.png
http://www.kinovea.org/screencaps/0.8.x/devicenetworkconfig2.png

In the analysis tools department, it has been noted that the stopwatch is functional but simple.

Maybe there could be a separate cadence tool (or tempo tool). Something to simply assess the frequency of a repetitive phase. Like strokes in swimming, strides in track and field, rotations in discus or hammer throw, etc.
The usability of this will have to be top notch to keep things simple. (The lap function on a physical stopwatch can be confusing at first, the tool would have to be simpler than that if possible).