smacke / smacke/ffsubsync

Syncing via bazarr failed for 2 "old" movie

Open
#100 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

out-of-sync
Dominant language
Python
Stars
7.9k
Forks
323
PR merge metrics
No merged PRs in 30d

Description

Subtitle sync failed for 2 movies (no speech found)

I'm running Bazarr on Qnap nas (Qbazarr) version V0.9.0.2, all other subs synced correctly so might be a general problem with the app ?

The movie audio is: .AVC.DTS-HD.MA.5.1

(sorry no tarball)

Traceback (most recent call last):
 File "/share/CACHEDEV1_DATA/.qpkg/QBazarr/bazarr/bazarr/subsyncer.py", line 46, in sync
  result = run(self.args)
 File "/share/CACHEDEV1_DATA/.qpkg/QBazarr/bazarr/bazarr/../libs/ffsubsync/ffsubsync.py", line 275, in run
  reference_pipe.fit(args.reference)
 File "/share/CACHEDEV1_DATA/.qpkg/QBazarr/bazarr/bazarr/../libs/ffsubsync/sklearn_shim.py", line 214, in fit
  self._final_estimator.fit(Xt, y, **fit_params)
 File "/share/CACHEDEV1_DATA/.qpkg/QBazarr/bazarr/bazarr/../libs/ffsubsync/speech_transformers.py", line 250, in fit
  raise ValueError(
ValueError: Unable to detect speech. Perhaps try specifying a different stream / track, or a different vad.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with bazarr/subsyncer.py and libs/ffsubsync/ffsubsync.py, then follow the traceback into sklearn_shim.py and speech_transformers.py. Reproduce the failure with the affected movie audio if available and determine what evidence is needed for subtitle syncing to complete without the "Unable to detect speech" error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, scikit-learn
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.