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.

Sign up for GitHub

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

Jump to bottom

The start time of the first transcript segment should start from 00:00 #863

Closed
1 task done
beastoin opened this issue Sep 17, 2024 · 0 comments
Closed
1 task done

The start time of the first transcript segment should start from 00:00 #863

beastoin opened this issue Sep 17, 2024 · 0 comments
Assignees
@beastoin

Comments

@beastoin
Copy link
Collaborator

beastoin commented Sep 17, 2024 •
edited
Loading

Actions:

  • When create the new memory from the backend, make sure the transcript of first segment start from 00:00
@beastoin beastoin self-assigned this Sep 17, 2024
@beastoin beastoin converted this from a draft issue Sep 17, 2024
@kodjima33 kodjima33 moved this from In progress to Backlog in omi TODO Sep 17, 2024
@beastoin beastoin mentioned this issue Sep 22, 2024
Merged
beastoin added a commit that referenced this issue Sep 22, 2024
@beastoin
Align start seconds for transcript segment (#906)
7953671 
Issue: #863 








<!-- This is an auto-generated comment: release notes by OSS
Entelligence.AI -->
### Summary by Entelligence.AI

- New Feature: Introduced an optional field `timer_segment_start` to the
`ProcessingMemory` class for improved segment timing.
- Refactor: Updated audio processing and memory creation logic to align
with the start seconds of transcript segments. This includes adjustments
to segment start and end times, and handling of audio frames based on
these boundaries.
- New Feature: Added a function `update_memory_finished_at` to update
the 'finished_at' field in a memory document, enhancing data accuracy.
- New Feature: Enhanced the `merge_wav_files` function to support
inserting silent segments between audio files, providing better control
over audio merging.
<!-- end of auto-generated comment: release notes by OSS Entelligence.AI
-->
@github-project-automation github-project-automation bot moved this from In review to Done in omi TODO Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beastoin beastoin

Labels
None yet
Projects
omi TODO
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@beastoin