OpenMOSS / OpenMOSS/MOSS-Transcribe-Diarize
Timestamps inacurate
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 126
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 5
Description
I'm seeing the timestamp drift by i.e. almost by 10s. See following audio.mp3:
Así es, así es, también músico, estaban yendo a ese [...]
That happens in the audio at 02:05 (mm:ss), while the model predicts at 01:54 the start of that phrase:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached audio.mp3 and compare the spoken phrase at 02:05 with the model's predicted start at 01:54. Trace the timestamp generation and determine where the drift is introduced; done means the phrase timestamp aligns with the audio example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- audio-video-rtc, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100