You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Adding burnt timestamp to Output file motion clip frames #285
Many cheap mini cameras with internal battery save ongoing All Day Recording on SD Card as a series of varying length video clips. The supporting app often shows in live video but doesn't add a "burnt' timestamp to saved video clip frames. However the cam saves each clip to SD Card with correct Save timestamp set initially by a supporting app.
It would be really great if DVR-Scan has an UI Settings option to calculate from the original Clip Saved timestamp and add progressively changing with each frame "burnt" date & time count or timestamp track to each saved to Output file motion clip or segment, auto recognized by popular video players. Its quite important for hidden amateur surveillance videos where such mini cams are often used. Is that possible to implement as new feature? Lack of timestamp on motion videos greatly diminishes the fragments value for surveillances purposes.
I looked at the available Time related options in current DVR-Scan version UI:
I. "Set Time" option that seems to set the processing start time doesn't work for me at all, the app just waits indefinitely long despite the set time to start processing has passed.
II. "Timecode" option seems suitable if improved:
it should show on each motion frame the SOURCE FILE RECORDING DATE+TIME when motion occurred (currently shows only TIME);
if Timecode track is inaccurate or missing in the source video file(s), the app UI would offer the following Options used for all imported files set:
a) manually input 1st source file Created Date & Time (used if file EXIF Created Date & Time is wrong or missing); and
b) use each imported video file EXIF Created Date & Time (used if EXIF Created Date & Time shown in the DVR-Scan File Import window for each file is accurate in user's opinion).
In both a) and b) scenarios, DVR-Scan than would use currently processed imported file Created Date & Time to approximate running Timestamp values on each frame of Motion Clips added to the Output file, also counting for delays between different motion events in a single source video. If motion clips from several source videos are combined into single Output file, each clip added to it should have independently approximated motion Date & Time. It can be calculated using Created Date & Time stamp from each source file EXIF, or if missing in EXIF calculated with Start Time for each source video based on calculated total time length of all previous source video files, as Cams record sequential clips on SDCard without gaps.
Hope I explained the suggestion clear enough. It sounds complicated, but the algorithm is based on simple arithmetic calculations, while accurate date & time stamp presence is paramount on surveillance videos.
Set Time: this option sets the start and end position inside the video (for example, 00:05:00 starts the scan 5 minutes into the file). It is not a schedule. If the start time is after the end of the video, DVR-Scan scans 0 frames and finds no events. At the moment it does not show a warning for this, so it can look like it waits. I will add a clear warning. What values did you type?
Date/time overlay: I agree that this is useful. I plan to add an option for the timecode overlay that shows the real date and time. The base time for each input file comes from one of these:
the creation_time tag in the video file,
the file modified time (on most cameras, this is the time the clip ended),
a date/time that you type for the first file (later files continue from it).
Each frame then shows base time + position in that file. This is exact, so no approximation is necessary.
To help me test, can you send:
The camera model, and some example file names (many cameras put the date in the name).
The output of ffprobe -hide_banner your_clip.mp4 for one clip.
Whether the file "Date modified" in Explorer matches the recording time.
A timestamp track that players show automatically is not in scope for now. Most players do not show such tracks. A burnt-in overlay works in all players.
I. Set Time: I put start time 2min for a 1min video clip, so it didn't start. But now I tested same clip with start time 30sec and end time 0, and the code run that sounds strange since entered Start Time occurred later than default (0) End Time.
II. Date & Time Overlay: I tested several cheap $5-10 Mini Cam models with and without internal Li-Po battery. Their advertised brands & specs are usually fake, but acceptable for the price. They all use different Android control and video monitoring apps with similar features, but varying ability to set in Cam firmware correct or "any" current date. The apps all show running Date & Time stamp on a phone screen, but its missing in saved videos. Some Cams allow to choose saved video resolution on SDCard separately from live footage on-screen. Saved video clips size and length by some Cams depend on whether motion occurred when it was being saved, while other Cams keep clips size within close range. Useful motion distance range is within ~1-50m.
The cams with internal battery can save set by the app current Date & Time - some models for the correct time zone, other for the default China or other region time zone. Date & Time preservation by no battery Cams depend on whether they are installed within owner's router WiFi signal reach. Video folder and file names on SDCard for some Cam models include either accurate or time zone shifted Create Date & Time, for other models file names are cryptic (see pics attached) with name generation rules guessed by AI search. Some Cams have Date Modified in Explorer matching the video playback time, other show the same Created and Modified Date & Time, so they don't have any date & time records in EXIF and need manual user input at scanning videos for motion.
Overall, DVR-Scan tool gets very useful when scanning for motion hundreds of mini cams saved video files daily, especially with added timestamp features. Once a daily source files set is scanned, they can be deleted or SDCard quick formatted.
Set Time: the 2:00 start on a 1:00 clip now gives a clear error (next release). End Time 0 means "no end time", so 0:30 + 0 scans from 0:30 to the end of the file. I will add a hint for this in the app.
Date/time: your Lenovo files have the exact start time in the file name (20261116233730 = 2026-11-16 23:37:30). Many cameras do this, so I will read the time from the file name first. For cameras like the XDCam (no clock, cryptic names), you will be able to type the start time of a clip. Because these cameras save only clips with motion, a typed time is correct only for that clip, not for the files after it.
One question about the XDCam: do the numbers in the file names (057405, 057706, ...) match the time of day in seconds? For example, 057405 s = 15:56:45. If you know when one clip was recorded, that will tell us.
XDCam saves clips all day long regardless of motion, but the clip size may depend on motion presence. I didn't have XDCam files on SDcard handy at posting, so used PC hard disk folder with only SDCam motion files copied before I learned about DVR-Scan. :)
I'll try to record some clips with XDCam and see if your assumption is confirmed. Google AI hints about Mini Cams file names coding were far less realistic. :)
I recorded some consecutive clips with XD Cam today starting at 16.25.00 same timezone as yours. Tried to calculate time based on your formula, and it looks like the app set the Cam default timezone somewhere beyond New Zealand, folder date is also wrong. The app was showing correct time in mobile Live stream at Cam recording. The Cam changes temp video clips names .A to .AVI once the full clip is recorded. May be you can decipher another algorithm for XD file names based on file length etc? Further, erroneous Timezone and Daylight & Standard Time (if added by the app to Cam firmware) would require correction even if the file names were related to timeline. I tried several AI suggested ways to feed the Cam with an INI file with correct Date & Time to no avail. :)
Thank you for the test. Your screenshot shows that the numbers are possibly seconds. Each clip is approximately 5 minutes long. Each number is 301 to 306 more than the number before it.
But the camera clock is not correct. The number 035923 is 09:58:43, and you started the recording at 16:25:00. The difference is 6:26:17. A time zone error is almost always a number of full hours, thus this is not a time zone error. The folder date is also incorrect by 4 days. It is possible that the camera clock stops when the camera has no power. If this is true, the error is different each time.
Thus, I will not add a time zone setting. I plan this procedure:
You type the real start time of the first clip.
DVR-Scan uses the numbers in the file names to calculate the start times of the other clips.
With this procedure, a clock error or a time zone error has no effect.
To make sure that this procedure is correct, please send this data:
The start time of the last clip (040480), or the time that you stopped the recording. If the numbers are seconds, clip 040480 started at approximately 17:40:57.
The "Length" column for these files. Your previous clips were 5:42 long, but the difference between their numbers was only 301. It is possible that the camera records fewer frames per second than the file shows.
Also, scan only the .AVI files. Do not scan the .A files. The camera writes to a .A file until the clip is complete.
I'll do another test to collect data you requested. Yes, depending on SDCard speed, the Cam was dropping huge number of frames for slow cards. Also the app was showing 15fps, while file media info showing 30fps likely wrong for the Cam weak cpu. In prior clip picture, the clips were not strictly consecutive one after another since I deleted clips without motion before finding DVR-Scan.
I did a more careful test, namely was hooking the Cam to power first, connecting it to the phone app to get live video and push current Date & Time to the Cam, then inserting SDCard, and... found you were exactly right in every assumption:
When the Cam was connected to the app before recording started, SDCard folders have correct dates and file names show clip recording start time in sec;
When a user stops recording in the app and possibly removes SDCard, then puts it back later and restarts recording, the new clip numbers keep showing correct time in sec from moment when the recording was switched On again even if the app is later disconnected, until the power goes Off;
When the Cam is unhooked from power, current Date is auto recorded in firmware and shows as new folder Date when the Cam is re-hooked to power and recording starts without using the app. However, Time of power loss is seemingly not preserved, and when power is re-hooked and recording continues without using the app, 1st file name shows Factory default Time stored in firmware.
In the pics below, the Cam was hooked to the app, then recording manually started around 23.14.03, was interrupted after 4 clips recorded, then restarted some time later (pic 1) and continued till about 00.08.24 after midnight.
The trick to get correct Date & Time in clip names was in hooking the Cam to mobile app first, then start recording. But in real life a Mini Spy Cam may be quickly hooked to a Battery Backup and mounted without using the app, so DVR-Scan should offer ability to manually correct any (continued recording) clip's start Date & Time.
Thank you the data confirms the file name format! The folder name is the camera date (YYYYMMDD). The file name is the start time of the clip in seconds after midnight. For example, 083915 is 23:18:35. At midnight, the camera starts a new folder. 086225 (23:57:05) + 301 seconds is 000126 (00:02:06) in folder 20261121.
I can add two functions to DVR-Scan for this:
Read the date and time from these file names. If you connect the camera to the app before you record, the times are correct with no more steps.
If the camera clock is not correct, you type the real start time of the first clip. DVR-Scan can use the file names to calculate the start times of the other clips. This function is for clips from one power cycle only. After a power loss, the camera clock starts again from the factory default time.
There is one more limit: each clip plays for approximately 5:41, but the next clip starts 301 seconds later. Thus, the time in the overlay can be up to 40 seconds ahead of the real time at the end of a clip. The time is correct again at the start of the next clip. If possible, record a clock that shows seconds (for example, a phone) for one full clip. This test shows if the error is the same in each clip.
Not sure how to interpret your conclusion and do the next test. Why live stream time count overlay is 40 sec ahead of real time clip?
Are you saying the next clip starts recording before the prior one finishes recording? This seems to ensure any motion won't be lost between clips? Also, I can record the Cam live stream on mobile phone, but how would I know that one full clip has already been recorded, as the mobile app doesn't show folder info on the live footage screen?
Sorry, my comment was not clear. Here are some answers.
The overlay: I mean the time that DVR-Scan will write on the output video, not the time in the phone app. The time in the live stream is correct.
The 40 seconds: Each full clip plays for approximately 5:41, but the file names show that the next clip starts 301 seconds (5:01) later. Two things can cause this:
The clips overlap. The camera starts the next clip approximately 40 seconds before the current clip stops. In this case, the times are correct, and the same 40 seconds of video are in two clips.
The video plays slower than real time. Each clip records approximately 5:01 of real time, but the file plays for 5:41. In this case, the time that DVR-Scan writes is up to 40 seconds ahead at the end of a clip.
Your idea (1) is possible. The test shows which cause is correct.
The test: You do not need the live stream or the app for this test.
Put a clock that shows seconds in front of the camera. For example, use a computer screen or a second phone.
Start the recording on the camera. Record for approximately 15 minutes. Then the SD card has a minimum of two full clips.
On your computer, open two clips that follow each other (for example, the second and the third clip). Use a video player that can pause, for example VLC.
Send me this data:
The two file names.
The clock time in the first frame and in the last frame of the first clip.
The clock time in the first frame of the second clip.
If the last frame of the first clip shows a later time than the first frame of the second clip, the clips overlap.
Sorry, still not exactly clear. The clock start time of every individual clip is 00:00:00. The clip frames don't show any embedded time whatsoever, but the app like LosslessCut shows exact start time of each frame.
If I use VLC "multiple files playback" feature and add 2 earlier recorded consecutive clips 083915.avi and 084216.avi, none of them shows burnt-in ongoing timestamp at playback, but Windows Time App - Stopwatch shows play time for the 1st clip from 00:00:00 to 00:05:42, and the 2nd clip VLC starts at 00:05:46 onwards. Meaning a few secs VLC spent to start next video. Possibly its not what you asked for?????
Thank you for all the tests and screenshots -- you don't need to run any more tests. I have everything I need now.
I'm adding the date/time timecode overlay for the next release (v2.1). In the app (under Output -> Timecode Start) or on the command line (--time-code-start), you will be able to choose:
filename: reads the date and time from standard file names like your Lenovo camera (20261116233730.avi).
modified: uses each file's modified date (for cameras that save accurate file dates).
A typed start date and time (for example 2026-11-20 23:18:35): sets the start time of the first clip. If your files have dates in their names, DVR-Scan will also use the time gaps between them (so a wrong camera clock or time zone is corrected automatically). Otherwise it assumes the clips are back-to-back.
After looking closely at the XDCam file names (083915.AVI), I decided not to add automatic support for that format. On other cameras, 083915 means 8:39:15 AM rather than seconds since midnight, so reading it automatically would show the wrong time for those cameras. Also, because XDCam clips play slightly slower than real time (about 5:41 for 5:01 of recording), any timestamp overlay on those files can drift slightly ahead toward the end of a clip.
As a workaround for XDCam files, you can either:
Type the start date and time into Timecode Start for a clip (or a short continuous set of clips), or
Rename the files to include the date and time as YYYYMMDD_HHMMSS (for example 20261120_231835.avi) and use filename mode.
Thanks again for the detailed reports and screenshots -- they also helped catch the "Set Time" error handling and the Windows Date column issue, both of which are fixed for v2.1 as well. You can see the full summary of options that will be available in #287.
Please add 2nd "auto recognize" UI option for XDCam type file name format in addition to the manual rename option. New cam models like Lenovo cost even less while producing lower resolution clips and having less convenient to stably mount and hide form factor, so I tend to ship Lenovo models back upon testing while using mostly XDCam extended family with very narrow height but wider case profile, higher resolution clips and now shipped with small internal battery to keep date & time accurate in consecutive file names while relying on external Battery Pack for clips recording.
It will be pain in the ass to rename endless series of these 5min clips recorded day after day long. Its seldom needed to stop and later restart such recording mid day or more often. Will be much easier for a user to follow a deciphered routine far not obvious from obscure Mini Cam Manual, like hooking the Cam to power, starting mobile app and connecting phone to its WiFi signal, then start recording by locking SDCard into its slot to achieve consistent time sequence in file names.
Let the user choose between the two auto file naming schemes in the DVR-Scan UI. This thread gives exhaustive explanation for a curious user far above and beyond 1-page Cam Manual, while for a Nanny Live Cam use case the burnt in timestamp may not be required. :)
Also looking at Pull Requests, can you explain what you mean by "File modified time" in the app input list? Is it the clip's recording end time? Why it should be shown in the Date column despite clip recording start time is encoded in its file name one way or another? I think "File Created" and "Length" combo are more informative options for a user if both are shown and can be easily user verified by simple calculations if clips naming scheme is known?
Also some clips have unusually short length, do you know why it might happen mid write cycle without shutting power off or any user interference? I noticed it often occurs right after the Cam is hooked to power: the 1st clip is of standard or much longer length, but immediate next clips are a lot shorter than standard, and later clips length or size is more or less stabilized.
Activity
Breakthrough commentedon Nov 16, 2026
The timecode overlay should do this for you already - are you suggesting something else?
sambul13 commentedon Nov 16, 2026
I'm new to DVR-Scan, let me check your suggested solution carefully.
sambul13 commentedon Nov 16, 2026
I looked at the available Time related options in current DVR-Scan version UI:
I. "Set Time" option that seems to set the processing start time doesn't work for me at all, the app just waits indefinitely long despite the set time to start processing has passed.
II. "Timecode" option seems suitable if improved:
a) manually input 1st source file Created Date & Time (used if file EXIF Created Date & Time is wrong or missing); and
b) use each imported video file EXIF Created Date & Time (used if EXIF Created Date & Time shown in the DVR-Scan File Import window for each file is accurate in user's opinion).
In both a) and b) scenarios, DVR-Scan than would use currently processed imported file Created Date & Time to approximate running Timestamp values on each frame of Motion Clips added to the Output file, also counting for delays between different motion events in a single source video. If motion clips from several source videos are combined into single Output file, each clip added to it should have independently approximated motion Date & Time. It can be calculated using Created Date & Time stamp from each source file EXIF, or if missing in EXIF calculated with Start Time for each source video based on calculated total time length of all previous source video files, as Cams record sequential clips on SDCard without gaps.
Hope I explained the suggestion clear enough. It sounds complicated, but the algorithm is based on simple arithmetic calculations, while accurate date & time stamp presence is paramount on surveillance videos.
Breakthrough commentedon Nov 17, 2026
Thanks for the detail. Some notes:
Set Time: this option sets the start and end position inside the video (for example,
00:05:00starts the scan 5 minutes into the file). It is not a schedule. If the start time is after the end of the video, DVR-Scan scans 0 frames and finds no events. At the moment it does not show a warning for this, so it can look like it waits. I will add a clear warning. What values did you type?Date/time overlay: I agree that this is useful. I plan to add an option for the timecode overlay that shows the real date and time. The base time for each input file comes from one of these:
creation_timetag in the video file,Each frame then shows base time + position in that file. This is exact, so no approximation is necessary.
To help me test, can you send:
ffprobe -hide_banner your_clip.mp4for one clip.A timestamp track that players show automatically is not in scope for now. Most players do not show such tracks. A burnt-in overlay works in all players.
sambul13 commentedon Nov 17, 2026
I. Set Time: I put start time 2min for a 1min video clip, so it didn't start. But now I tested same clip with start time 30sec and end time 0, and the code run that sounds strange since entered Start Time occurred later than default (0) End Time.
II. Date & Time Overlay: I tested several cheap $5-10 Mini Cam models with and without internal Li-Po battery. Their advertised brands & specs are usually fake, but acceptable for the price. They all use different Android control and video monitoring apps with similar features, but varying ability to set in Cam firmware correct or "any" current date. The apps all show running Date & Time stamp on a phone screen, but its missing in saved videos. Some Cams allow to choose saved video resolution on SDCard separately from live footage on-screen. Saved video clips size and length by some Cams depend on whether motion occurred when it was being saved, while other Cams keep clips size within close range. Useful motion distance range is within ~1-50m.
The cams with internal battery can save set by the app current Date & Time - some models for the correct time zone, other for the default China or other region time zone. Date & Time preservation by no battery Cams depend on whether they are installed within owner's router WiFi signal reach. Video folder and file names on SDCard for some Cam models include either accurate or time zone shifted Create Date & Time, for other models file names are cryptic (see pics attached) with name generation rules guessed by AI search. Some Cams have Date Modified in Explorer matching the video playback time, other show the same Created and Modified Date & Time, so they don't have any date & time records in EXIF and need manual user input at scanning videos for motion.
Overall, DVR-Scan tool gets very useful when scanning for motion hundreds of mini cams saved video files daily, especially with added timestamp features. Once a daily source files set is scanned, they can be deleted or SDCard quick formatted.
Input #0, avi, from 'G:\XDCam\20261107\057706.avi':
Duration: 00:05:42.47, start: 0.000000, bitrate: 2839 kb/s
Stream #0:0: Video: mjpeg (Baseline) (MJPG / 0x47504A4D), yuvj420p(pc, bt470bg/unknown/unknown), 640x480, 2837 kb/s, 15 fps, 15 tbr, 15 tbn
Breakthrough commentedon Nov 18, 2026
Thanks, this helps a lot.
Set Time: the 2:00 start on a 1:00 clip now gives a clear error (next release). End Time
0means "no end time", so 0:30 + 0 scans from 0:30 to the end of the file. I will add a hint for this in the app.Date/time: your Lenovo files have the exact start time in the file name (
20261116233730= 2026-11-16 23:37:30). Many cameras do this, so I will read the time from the file name first. For cameras like the XDCam (no clock, cryptic names), you will be able to type the start time of a clip. Because these cameras save only clips with motion, a typed time is correct only for that clip, not for the files after it.One question about the XDCam: do the numbers in the file names (057405, 057706, ...) match the time of day in seconds? For example, 057405 s = 15:56:45. If you know when one clip was recorded, that will tell us.
sambul13 commentedon Nov 18, 2026
XDCam saves clips all day long regardless of motion, but the clip size may depend on motion presence. I didn't have XDCam files on SDcard handy at posting, so used PC hard disk folder with only SDCam motion files copied before I learned about DVR-Scan. :)
I'll try to record some clips with XDCam and see if your assumption is confirmed. Google AI hints about Mini Cams file names coding were far less realistic. :)
sambul13 commentedon Nov 20, 2026
I recorded some consecutive clips with XD Cam today starting at 16.25.00 same timezone as yours. Tried to calculate time based on your formula, and it looks like the app set the Cam default timezone somewhere beyond New Zealand, folder date is also wrong. The app was showing correct time in mobile Live stream at Cam recording. The Cam changes temp video clips names .A to .AVI once the full clip is recorded. May be you can decipher another algorithm for XD file names based on file length etc? Further, erroneous Timezone and Daylight & Standard Time (if added by the app to Cam firmware) would require correction even if the file names were related to timeline. I tried several AI suggested ways to feed the Cam with an INI file with correct Date & Time to no avail. :)
Breakthrough commentedon Nov 20, 2026
Thank you for the test. Your screenshot shows that the numbers are possibly seconds. Each clip is approximately 5 minutes long. Each number is 301 to 306 more than the number before it.
But the camera clock is not correct. The number 035923 is 09:58:43, and you started the recording at 16:25:00. The difference is 6:26:17. A time zone error is almost always a number of full hours, thus this is not a time zone error. The folder date is also incorrect by 4 days. It is possible that the camera clock stops when the camera has no power. If this is true, the error is different each time.
Thus, I will not add a time zone setting. I plan this procedure:
With this procedure, a clock error or a time zone error has no effect.
To make sure that this procedure is correct, please send this data:
Also, scan only the
.AVIfiles. Do not scan the.Afiles. The camera writes to a.Afile until the clip is complete.sambul13 commentedon Nov 20, 2026
I'll do another test to collect data you requested. Yes, depending on SDCard speed, the Cam was dropping huge number of frames for slow cards. Also the app was showing 15fps, while file media info showing 30fps likely wrong for the Cam weak cpu. In prior clip picture, the clips were not strictly consecutive one after another since I deleted clips without motion before finding DVR-Scan.
sambul13 commentedon Nov 21, 2026
I did a more careful test, namely was hooking the Cam to power first, connecting it to the phone app to get live video and push current Date & Time to the Cam, then inserting SDCard, and... found you were exactly right in every assumption:
In the pics below, the Cam was hooked to the app, then recording manually started around 23.14.03, was interrupted after 4 clips recorded, then restarted some time later (pic 1) and continued till about 00.08.24 after midnight.
The trick to get correct Date & Time in clip names was in hooking the Cam to mobile app first, then start recording. But in real life a Mini Spy Cam may be quickly hooked to a Battery Backup and mounted without using the app, so DVR-Scan should offer ability to manually correct any (continued recording) clip's start Date & Time.
Breakthrough commentedon Nov 22, 2026
Thank you the data confirms the file name format! The folder name is the camera date (YYYYMMDD). The file name is the start time of the clip in seconds after midnight. For example, 083915 is 23:18:35. At midnight, the camera starts a new folder. 086225 (23:57:05) + 301 seconds is 000126 (00:02:06) in folder 20261121.
I can add two functions to DVR-Scan for this:
There is one more limit: each clip plays for approximately 5:41, but the next clip starts 301 seconds later. Thus, the time in the overlay can be up to 40 seconds ahead of the real time at the end of a clip. The time is correct again at the start of the next clip. If possible, record a clock that shows seconds (for example, a phone) for one full clip. This test shows if the error is the same in each clip.
sambul13 commentedon Nov 22, 2026
Not sure how to interpret your conclusion and do the next test. Why live stream time count overlay is 40 sec ahead of real time clip?
Are you saying the next clip starts recording before the prior one finishes recording? This seems to ensure any motion won't be lost between clips? Also, I can record the Cam live stream on mobile phone, but how would I know that one full clip has already been recorded, as the mobile app doesn't show folder info on the live footage screen?
Breakthrough commentedon Nov 22, 2026
Sorry, my comment was not clear. Here are some answers.
The overlay: I mean the time that DVR-Scan will write on the output video, not the time in the phone app. The time in the live stream is correct.
The 40 seconds: Each full clip plays for approximately 5:41, but the file names show that the next clip starts 301 seconds (5:01) later. Two things can cause this:
Your idea (1) is possible. The test shows which cause is correct.
The test: You do not need the live stream or the app for this test.
If the last frame of the first clip shows a later time than the first frame of the second clip, the clips overlap.
sambul13 commentedon Nov 22, 2026
Sorry, still not exactly clear. The clock start time of every individual clip is 00:00:00. The clip frames don't show any embedded time whatsoever, but the app like LosslessCut shows exact start time of each frame.
If I use VLC "multiple files playback" feature and add 2 earlier recorded consecutive clips 083915.avi and 084216.avi, none of them shows burnt-in ongoing timestamp at playback, but Windows Time App - Stopwatch shows play time for the 1st clip from 00:00:00 to 00:05:42, and the 2nd clip VLC starts at 00:05:46 onwards. Meaning a few secs VLC spent to start next video. Possibly its not what you asked for?????
[feature] Show date and time of recording in timecode overlay #285
Breakthrough commentedon Nov 22, 2026
Thank you for all the tests and screenshots -- you don't need to run any more tests. I have everything I need now.
I'm adding the date/time timecode overlay for the next release (v2.1). In the app (under Output -> Timecode Start) or on the command line (
--time-code-start), you will be able to choose:filename: reads the date and time from standard file names like your Lenovo camera (20261116233730.avi).modified: uses each file's modified date (for cameras that save accurate file dates).2026-11-20 23:18:35): sets the start time of the first clip. If your files have dates in their names, DVR-Scan will also use the time gaps between them (so a wrong camera clock or time zone is corrected automatically). Otherwise it assumes the clips are back-to-back.After looking closely at the XDCam file names (
083915.AVI), I decided not to add automatic support for that format. On other cameras,083915means 8:39:15 AM rather than seconds since midnight, so reading it automatically would show the wrong time for those cameras. Also, because XDCam clips play slightly slower than real time (about 5:41 for 5:01 of recording), any timestamp overlay on those files can drift slightly ahead toward the end of a clip.As a workaround for XDCam files, you can either:
YYYYMMDD_HHMMSS(for example20261120_231835.avi) and usefilenamemode.Thanks again for the detailed reports and screenshots -- they also helped catch the "Set Time" error handling and the Windows Date column issue, both of which are fixed for v2.1 as well. You can see the full summary of options that will be available in #287.
sambul13 commentedon Nov 22, 2026
Please add 2nd "auto recognize" UI option for XDCam type file name format in addition to the manual rename option. New cam models like Lenovo cost even less while producing lower resolution clips and having less convenient to stably mount and hide form factor, so I tend to ship Lenovo models back upon testing while using mostly XDCam extended family with very narrow height but wider case profile, higher resolution clips and now shipped with small internal battery to keep date & time accurate in consecutive file names while relying on external Battery Pack for clips recording.
It will be pain in the ass to rename endless series of these 5min clips recorded day after day long. Its seldom needed to stop and later restart such recording mid day or more often. Will be much easier for a user to follow a deciphered routine far not obvious from obscure Mini Cam Manual, like hooking the Cam to power, starting mobile app and connecting phone to its WiFi signal, then start recording by locking SDCard into its slot to achieve consistent time sequence in file names.
Let the user choose between the two auto file naming schemes in the DVR-Scan UI. This thread gives exhaustive explanation for a curious user far above and beyond 1-page Cam Manual, while for a Nanny Live Cam use case the burnt in timestamp may not be required. :)
sambul13 commentedon Nov 22, 2026
Also looking at Pull Requests, can you explain what you mean by "File modified time" in the app input list? Is it the clip's recording end time? Why it should be shown in the Date column despite clip recording start time is encoded in its file name one way or another? I think "File Created" and "Length" combo are more informative options for a user if both are shown and can be easily user verified by simple calculations if clips naming scheme is known?
Also some clips have unusually short length, do you know why it might happen mid write cycle without shutting power off or any user interference? I noticed it often occurs right after the Cam is hooked to power: the 1st clip is of standard or much longer length, but immediate next clips are a lot shorter than standard, and later clips length or size is more or less stabilized.