Support compact single-channel Viofo filenames#24
Open
nittanygeek wants to merge 3 commits into
Open
Conversation
Owner
|
Thanks for this. What model is your camera? Does the GPS extraction work? |
Author
|
A119 mini 2, and yes GPS extraction works. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
YYYYMMDDHHMMSS_NNNNNN.MP4alongside the existing channel-suffixed formatrecorded_atso compact filenames do not produce malformed datesBackground
Some Viofo units expose recordings in their web listing without date/time separator underscores or a camera suffix. Those files were skipped because the filename parser only accepted the newer
YYYY_MMDD_HHMMSS_NNNN[FRTI].MP4style.Tests
PYTHONPATH=. .venv/bin/python -m pytest tests/test_queue_filename_parsing.py tests/test_queue_day_grouping.py tests/test_scanner_compact_filename.py