Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record annotation offset #6288

Merged
merged 1 commit into from
Apr 28, 2023
Merged

Record annotation offset #6288

merged 1 commit into from
Apr 28, 2023

Conversation

NickM-27
Copy link
Sponsor Collaborator

No description provided.

@netlify
Copy link

netlify bot commented Apr 27, 2023

Deploy Preview for frigate-docs canceled.

Name Link
🔨 Latest commit d5b12b1
🔍 Latest deploy log https://app.netlify.com/sites/frigate-docs/deploys/644b2618cb2dd600086d2181

@blakeblackshear
Copy link
Owner

We could also consider baking this offset into the start/end times in the recording database entries instead. That would also fix other related inconsistencies.

@NickM-27
Copy link
Sponsor Collaborator Author

NickM-27 commented Apr 28, 2023

We could also consider baking this offset into the start/end times in the recording database entries instead. That would also fix other related inconsistencies.

The thing is, when I check my recordings they are (from what I can see) exactly in line with what they're saved as. So if it's going to be changing permanently how values are stored, I think it might make more sense to offset the frame times that are stored?

@blakeblackshear
Copy link
Owner

Yea. This may be a better solution to start with. We can at least evaluate how consistent it is with this.

@NickM-27 NickM-27 marked this pull request as ready for review April 28, 2023 01:53
@blakeblackshear blakeblackshear merged commit b48f6d7 into dev Apr 28, 2023
10 checks passed
@NickM-27 NickM-27 deleted the record-annotation-offset branch April 28, 2023 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants