The goal now is to pack up the capture screen until it works well enough, and then publish a stable version.
Ideally the version 0.8.14 would be the last round of changes and then 0.8.15 can be the official version. (With translations and manual updates).

So here's a list of improvements that have been suggested or scheduled for the capture screen, please add yours if it's not listed.
Very big changes will probably not make it this round, but be pushed to future versions.


1 - A "file format" drop down list directly on the capture screen to select the file format for snapshot/recording (or only changeable in the preferences ?).
2 - A "file format" drop down in the preferences to set the default format. (or we could just save the last one used ?).
(Note: probably only one of the previous two will be integrated)

Naming and directories
3 - Save the last filename used so the auto-increment works across screens and restarts.
4 - Preference page with advanced naming conventions, with formatting tags for date and auto increment.
5 - Move the settings for "directory of recording" to the preference page ?

Misc
6 - Access to the device configuration from right click on the main image.
7 - Display the current resolution / frame rate somewhere. (in the status bar maybe).
8 - Display the file size taken so far while recording is in progress ?
9 - Is the ability to hide / show the "configuration" mini panel useful at all ?
10 - Fix memory issue when the combined space of the buffer goes over Windows (32-bit) addressable space. This might mean having a single memory setting for the whole application.
11 - Detect if the camera is used in the other screen and connect to the next device.

Most probably not in this version
12 - Fix issue with frame rate of created video. (I'm afraid this is a long shot, it might not be fixed for the release).
13 - On capture freeze, change the interface to allow for better navigation in the recently captured frames (play, pause, next, prev).

Again, if you have any more, feel free to add to the list.

1,352

(16 replies, posted in Cameras and hardware)

Interesting !
There is this Link2Cam project over at SourceForge (did not test it myself). Also apparently some hardware vendors provide their own Directshow filters.
What happens exactly when you try to go to the configuration dialog ? No options are listed ?

Currently I'm trying to do the opposite : spoofing an IP camera using an USB webcam to see how the program reacts to it…

1,353

(2 replies, posted in Bug reports)

cheval3893 wrote:

Even if you copy the DVD-R video to your desktop it still does the same thing.

Hmm, this would point to the file format rather than the hardware support… Are these the same files just on different DVD or different files ?
There are some issues like this with certain VOB files. Is it the case ?

To prevent Kinovea trying to load the images in RAM, you can hit cancel during the loading, or you can go to preferences and slide the memory settings to the left.

1,354

(1 replies, posted in Français)

Bonjour,
C'est un bug, il a été corrigé dans la version 0.8.8, il vous faudra utiliser la version expérimentale pour avoir le correctif.

Ah, je comprends.
Il y a effectivement un ensemble de problèmes d'interface dans la version 0.8.7 lorsque, sous Windows 7, les options système de taille de texte sont modifiées.
Dans Windows, Panneau de configuration > Affichage, si vous métez sur Moyenne (125%) vous risquez avoir ces problèmes.

Solution : basculer sur « petite - 100% », ou utiliser la version expérimentale dans laquelle ces problèmes d'interface devraient être corrigés.

Please mail the sample to : joan at kinovea dot org.
Thanks

Hello,
I don't know if it will fix the problem (especially considering VLC cannot play the video) but the experimental versions have an updated decoding library. They also have the logs in debug mode so it will be more helpful.
If it still doesn't work, can you get a failing sample of manageable size ?

1,358

(8 replies, posted in Bug reports)

Hi, thanks for the sample. I can read it with version 0.8.7.
There is no codec to install that can help with this problem, it's the decoding library that must be fixed (similar to VLC)…

user "haeferl" on the forum sent me a video with a similar issue a while ago (also ski jumping), maybe they come from the same samsung camera ?
Anyway, I still need to report this to FFmpeg for more information.

It corresponds to bug 209.

1,359

(6 replies, posted in General)

Ah, sorry I misunderstood. You are referring to the workspace organisation of screens ?
Now that is another story smile
I guess it would be better to have the key images on the side with such a setting…

4-screen organisation is not currently part of the plan. I'm not convinced that anyone can actually watch 4 videos at the same time, and it would be super hard to manage while keeping some of the existing functionality like synchronization. Forcing 2-screens has made possible a number of shortcuts and simplifications and allowed focusing on doing more basic stuff better.

Utilisez le bouton complètement en bas à droite, dans la section des contrôles communs : "Enregistrer les deux vidéos dans une vidéo composée".

1,361

(6 replies, posted in General)

Dual export, but created file has original videos placed top/bottom instead of left/right.

It is certainly possible technically, but where to place the setting ?
- In the general preferences : it would be hidden and few persons would ever know about it.
- In a dialog just before the file name dialog : it may disrupt the flow for persons always using the default option.
- Elsewhere ?

There might still be extra logs. Go to the logs folder and look for files named "Unhandled crash" something.
Created bug 238

I didn't even know such splitting tool existed ! Could have saved me a few bucks when I first worked on the dual capture screen, instead of buying a cheapo webcam tongue

@splatent: Note that there is a bug when using the two capture screens view. You need to go to menu Options > Preferences > Playback and decrease the ammount of memory (second slider) to something like 300/400MB. Otherwise you might get a crash (actual RAM you have is irrelevant).

Also, the current design is to record exactly what happens on screen, so the ability to browse the recently captured event while still capturing in the background is not considered for now.

1,364

(18 replies, posted in General)

Say I have two videos in sync and added such a "video" insert tool.
- I can press play on common controls : both the main video and the insert play in sync.
- I can pause the main video and browse the second one : I stay on the same frame of the main video while the insert is animated.
(Maybe the insert itself can have small frame by frame controls to go back and forth.)

Second scenario is what you describe, right ?
With this type of tool, I don't see how the blend mode (overlaying on the full image) could be of any use (anything it does could be emulated with this).

edit:
Oh maybe you meant to create several image insert on a single frame of the other video ?

1,365

(18 replies, posted in General)

Thanks for the feedback and even more ideas ! smile

First of all, I think this will only be considered for later integration. I feel the current image/svg tool to be "good enough" for a formal release, so I'd like to wrap up the capture screen and publish a formal version for the general public.

Regarding sending a sequence of pictures, it is something that crossed my mind too. Seeing this image standing there coming from the other video, I'm tempted to click play on it to see what happens next smile

But there is a convergence between this and the blending mode. And it will be confusing to have two completely different tool serving the same purpose.
This will need to be thought over to see what can be done.

Maybe when the "aligned merge" function is in place the blending mode can be removed completely, and the image tool enhanced to allow for "Send video to the other screen", where instead of overlaying the video on top of the other at 50% opacity, we put it in a small - resizable insert. (In that case you'd have to keep both screens open)…