Here is a tentative sum up of what is known about these defects so far.
Please any additional infos or other defects specific to saving.
1. Saved files are 0 bytes or not created at all.
Reproduction scenario :
- Open a video in the program VirtualDub and do "save as avi" uncompressed. (default value in compression options)
- Open resulting video in Kinovea: reading is fine.
- Save video to file, the progress bar appears and disappears instantly.
- Resulting file is 0 bytes or non existent.
- No error message is displayed.
Expected :
- Video saved to file correctly.
- In case of an error, an error message should be displayed.
Workaround :
- Do not use the uncompressed mode of VirtualDub, go to Video > Compression and choose a codec from the list.
Root cause analysis :
- Unknwown at the moment.
Estimated date of fix :
- Unknown at the moment.
2. Saving progress hangs at some point, memory usage peaks.
Reproduction scenario :
- Video is in normal mode (not analysis mode where frames are uncompressed to memory)
- Save the video to file, starts fine, then goes slower, then hangs.
Expected :
- Video saved to file without memory usage increase.
Workaround:
- Do not save videos in normal mode. Restrict the selection until it goes to Analysis mode before saving.
Root cause analysis :
- Memory leak in the saving process.
Estimated date of fix :
- Fixed. Available in next release.
3. Saving causes the application to crash.
Reproduction scenario :
- Unknown. Please provide one if you experience this issue. (Include error log from Windows if possible)
4. Saving function creates files much bigger than original.
This is to be expected for the moment. Will be fixed later on.
Conflicting goals : simplicity of usage, quality of output, size of file, readability of the code.