Apertus.FeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
OneArtPlease (talk | contribs) Created page with "=camogm= * bug/feature: add a way to see if a new file segment has been started and how many file segments a single recording already has (like new parameters: <file_segments> ..." |
OneArtPlease (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
=camogm= | =camogm= | ||
* bug/feature: add a way to see if a new file segment has been started and how many file segments a single recording already has (like new parameters: <file_segments> <current_file_segment> in xml status output) | * bug/feature request: add a way to see if a new file segment has been started and how many file segments a single recording already has (like new parameters: <file_segments> <current_file_segment> in xml status output) | ||
=ElphelVision= | =ElphelVision= | ||
Revision as of 16:05, 23 March 2011
camogm
- bug/feature request: add a way to see if a new file segment has been started and how many file segments a single recording already has (like new parameters: <file_segments> <current_file_segment> in xml status output)
ElphelVision
- automatically create a new folder for every recording, store all file segments of the same recording in there,
- after finishing a recording create md5 hashes of all video segment files (video123.mov -> video123.md5), this will help making sure that (ftp) transfered files match the file on the camera HDD
- automatically create a textfile in every clip folder after finishing a recording with metadata (eg: meta.txt with recording settings, dates, number of file segments and their filenames, etc.)
- add button to mainlayout to disable live video stream
- add warning notice on circbuffer buffer overflow